Support:About Arianne: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Kymara |
imported>Kymara |
||
| Line 72: | Line 72: | ||
== 10. What advice would you give to a project that's just starting out? == |
== 10. What advice would you give to a project that's just starting out? == |
||
Have a Vision. And a plan. |
|||
The vision is what you want your project to be about. It is the main source of motivation. |
|||
The plan helps you to achieve this goal in small steps. Especially at the beginning of a new project it is very easy to get lost in some interesting details. I think it is important to have a working prototype out rather quickly (within a month, better within a week). Don't be afraid to share your work just because some features are not finished. Just openly tell people what works and what does not work, yet, and ask them for feedback. |
|||
New open source projects may be very keen for contributors to join the team. Who you add to your project and invest time in, is important to get right. Early in Arianne's history were problems with commitment from developers who joined the project. These were people that joined the project, asked for tasks and vanished after that. It was a pity because they delayed the project a lot and made it much harder to keep adding new features. Since then, we ask new developers who want to contribute, to start by submitting patches to the Sourceforge Tracker for review. We counter the possible demotivating effect of this by communicating as much as possible and coordinating new and interesting tasks. New developers are only then added as project members with write access to the repositories, after agreement from the rest of the team. |
New open source projects may be very keen for contributors to join the team. Who you add to your project and invest time in, is important to get right. Early in Arianne's history were problems with commitment from developers who joined the project. These were people that joined the project, asked for tasks and vanished after that. It was a pity because they delayed the project a lot and made it much harder to keep adding new features. Since then, we ask new developers who want to contribute, to start by submitting patches to the Sourceforge Tracker for review. We counter the possible demotivating effect of this by communicating as much as possible and coordinating new and interesting tasks. New developers are only then added as project members with write access to the repositories, after agreement from the rest of the team. |
||