| This is a new experience ... providing information on the web site for
fellow GNQS developers. I hope what's here is useful, and I'd love
to hear what else you'd like to see on here. Before we go any further,
if you are interested at all in getting involved with future work on
GNQS, or you just want to keep your ear to the ground, then I strongly
urge you to subscribe to the NQS Developers Mailing List.
First off, we've got the following short papers for you, which
explain the GNQS development process.
- Overview Of Generic NQS Development
- Becoming A Generic NQS Developer
- Becoming A Generic NQS Maintainer
- Submitting Patches
These papers look specifically at how our development is done using
source control and the master copy of the source code:
- Introduction To Source Control
- Software You Need, And Where To Get It
- Introducing To Using Perforce In A Disconnected Environment
- The Generic NQS Source Trees
- Other Notes On Using Perforce
These papers list policy we've adopted for development (listed
alphabetically):
- Installation Software
- Portability
- Naming Conventions For Directories, Files, Functions &
Variables
- What Goes Into Which Source Tree
GNQS hackers are encouraged to contribute any short articles on
specific parts of GNQS, especially when they submit changes to me ;-) |