+1 On Sat, Aug 27, 2011 at 6:02 AM, Mur <[email protected]> wrote: > I have been following ROS for a while now and I see a few issues that > need to be solved before it can grow. > > 1. Setup a PR group: This group will advertise, recruit and get > supporters. It will be the job to spread word of ros, they will first > attempt to recruit developers until a time that ros is out of alpha > and can be use for daily use. They will also look for funding for ros > by contacting possible donators. This group will need to be tiered so > that we can organize what we need to do and when and have the leg > workers able to carry it out. > > 2. Delegation / authority: We need to setup a bit of authority > especially when it comes to the PR group. These people will be able to > delegate time sensitive/ priority jobs to personal and have a way of > communication between PR and Devs. > > 3. Website: The website needs to be updated (Which I have been told is > in the works) The PR’s first goal should be finding some people able > to manage that. They will need to have a template of what has > currently been done and a design of what needs to be completed. > > 4. Project Information for new devs: We need to update the list of > things that are “TODO” , the best list I have seen for something like > this is... http://www.reactos.org/wiki/Google_Summer_of_Code_2011_Ideas > This will give developers who check out the project a clear goal that > they might want to pick up. This can be bundled with the way GSoC has > a mentor program and have available mentors if someone needed more > guidance. > > _______________________________________________ > Ros-general mailing list > [email protected] > http://www.reactos.org/mailman/listinfo/ros-general >
_______________________________________________ Ros-general mailing list [email protected] http://www.reactos.org/mailman/listinfo/ros-general
