Distribute work on the project
Page: 1
Hi all,
I am watching the aC development since a few weeks and really welcome Ilja's idea to distribute the work on more shoulders (http://www.activecollab.com/pages/31/contribute/).
In my opinion the first step to do this is to get a project structure where the different people (with their different ideas and skills) can share "their" (sub) project. The second step should be to set up a work environment for these teams. This should - at least - include a wiki, an aC installation (of course) and a mailing list for discussion.
But first things first: this is my proposal for an - incomplete - project structure and some possible content / groups. Any feedback is welcome:
1. The aC project
- strategy / goals of the project
- road map
- project internal communication (like planet.activecollab.com)
2. Development
- aC core development
- aC framework
- plug-in development
- bug tracking /qa
- theming
3. Documentation
- end user documentation (in various languages, see 4.)
- developer documentation
- non-coding development how-tos (themes, translation etc)
4. Internationalization
- translation
- local user groups
5. Marketing
- target group analysis
- visual style guide development (including logo, icons etc ... designers onboard!)
- web site -> communication with the various target groups
- marketing material
There is some inspiration for the relaunch of the GNOME project at http://desdeamericaconamor.org/blog/node/303. What do you think?
Best regards
Roland
I am watching the aC development since a few weeks and really welcome Ilja's idea to distribute the work on more shoulders (http://www.activecollab.com/pages/31/contribute/).
In my opinion the first step to do this is to get a project structure where the different people (with their different ideas and skills) can share "their" (sub) project. The second step should be to set up a work environment for these teams. This should - at least - include a wiki, an aC installation (of course) and a mailing list for discussion.
But first things first: this is my proposal for an - incomplete - project structure and some possible content / groups. Any feedback is welcome:
1. The aC project
- strategy / goals of the project
- road map
- project internal communication (like planet.activecollab.com)
2. Development
- aC core development
- aC framework
- plug-in development
- bug tracking /qa
- theming
3. Documentation
- end user documentation (in various languages, see 4.)
- developer documentation
- non-coding development how-tos (themes, translation etc)
4. Internationalization
- translation
- local user groups
5. Marketing
- target group analysis
- visual style guide development (including logo, icons etc ... designers onboard!)
- web site -> communication with the various target groups
- marketing material
There is some inspiration for the relaunch of the GNOME project at http://desdeamericaconamor.org/blog/node/303. What do you think?
Best regards
Roland
I have been using/watching aC for some time now, and decided I would like to put in some resources to help with the project.
I am a professional designer and standards based coder, and can contribute in that regard. I run a successful web design company and use this as my internal project management/client collaboration tool, so I am the perfect tester.
I will take the initiative and ask to launch the Marketing group.
Can we start this in an aC install somewhere?
I am a professional designer and standards based coder, and can contribute in that regard. I run a successful web design company and use this as my internal project management/client collaboration tool, so I am the perfect tester.
I will take the initiative and ask to launch the Marketing group.
Can we start this in an aC install somewhere?
Topic is locked. If you have something important to say about issues discussed on this page please write at hi@a51dev.com.



