Well, I basically agree with Calin and think we need a bunch of stuff (listed below),
where source control is the most urgent (IMO), and I also have no problem on taking an
organizational role on myself.
However, since CJ has already declared that he's planning on creating a source control system
himself, and that this is still his baby and he just released the source of the editor to test the waters,
I think we are maybe a bit ahead of ourselves, and need to give him some time.
Here's the stuff I think we need:
1. Source control system.
The manual merge that Calin did to create the integrated version is
error prone and wouldn't hold in the long term.
2. Issue tracker.
We will be able to report issues & feature requests, categorize them, prioritize them
according to popular demand, and developers would be able to voluntarily assign themselves to issues,
thus assuring that an issue will not be worked on by two developers at a time.
3. Find ways to make the code more accessible for other developers.
As luck would have it, CJ is an excellent programmer and organized,
so the code is a lot more organized and clear than what I expected from a project that was
developed for years by a single person.
But still, since this is a pretty large code-base, we need to learn it and create help files for code,
class diagrams, point out the main classes and their roles, so the top level design of the application
will be clear and out in the open.
4. Have a subforum for AGS development (this also relates to #3).
We need to discuss and make some decisions, and point out some basic rules.
For instance, we need to agree on a set of coding style guidances (well, CJ has kept a consistent
coding style, we just need to assemble it into a sticky post with all the rules a developer has to adhere to).
We also need to decide on the general directions we want to take the code to, and on what is allowed and what
isn't allowed. For instance, I decided on myself to target dotnet 3.5, but maybe the community doesn't agree with me?
Also, am I allowed to integrate other source control projects? etc etc.
where source control is the most urgent (IMO), and I also have no problem on taking an
organizational role on myself.
However, since CJ has already declared that he's planning on creating a source control system
himself, and that this is still his baby and he just released the source of the editor to test the waters,
I think we are maybe a bit ahead of ourselves, and need to give him some time.
Here's the stuff I think we need:
1. Source control system.
The manual merge that Calin did to create the integrated version is
error prone and wouldn't hold in the long term.
2. Issue tracker.
We will be able to report issues & feature requests, categorize them, prioritize them
according to popular demand, and developers would be able to voluntarily assign themselves to issues,
thus assuring that an issue will not be worked on by two developers at a time.
3. Find ways to make the code more accessible for other developers.
As luck would have it, CJ is an excellent programmer and organized,
so the code is a lot more organized and clear than what I expected from a project that was
developed for years by a single person.
But still, since this is a pretty large code-base, we need to learn it and create help files for code,
class diagrams, point out the main classes and their roles, so the top level design of the application
will be clear and out in the open.
4. Have a subforum for AGS development (this also relates to #3).
We need to discuss and make some decisions, and point out some basic rules.
For instance, we need to agree on a set of coding style guidances (well, CJ has kept a consistent
coding style, we just need to assemble it into a sticky post with all the rules a developer has to adhere to).
We also need to decide on the general directions we want to take the code to, and on what is allowed and what
isn't allowed. For instance, I decided on myself to target dotnet 3.5, but maybe the community doesn't agree with me?
Also, am I allowed to integrate other source control projects? etc etc.