Custom Query (1408 matches)

The current setup I have for writing new OF controllers, is a little bit complicated at best. Not my brightest decision to mix git and svn:-) I think it is time to clean this up so that it's easier to keep track of controllers, share them within GPO and also give back patches to Nox. To clean this up it will be much better to have gpo's nox deployment, on a local repository. Already chatted with Chaos about this and she mentioned that the needed information is :

1. short name for the repo : noxgpo (other suggestions are welcome)
2. description for the repo : "GPO's development efforts with nox controller"
3. who at GPO should have write access to the repo : I don't have any particular preference on that, but Chaos mentioned that starting with a small group is easier, so I guess Mark, Josh and me, since I do not know of anyone else that is interested in writing nox code. Of course whatever is easier. If for example it's easier to give access to groups (experimenter, infra) instead of individual people, that is fine as well. And read access, I guess to all at gpo-tech. If this is too vague and it's easy to add people later on, we can leave it empty for now and add people if needed later.

Determine/coordinate demo needs and plan for supporting demos.

This milestone is not part of Spiral 3, so shouldn't be in the milestone pulldown list