This can all be done in ~2 years by a bunch of coders. The OpenOffice.org port is (or isn't? who knows) going on for more than two years now, with no results so far.
if we could turn the community into a utililitarian / dictatorship,. that may be possible
Style of Organization:
A group of people coordinate and prioritize projects. Each project lists tasks for Research, Development, QA and who is working on each task. Everyone signs up for at least one thing. If you cannot code, you can do research or QA (Quality Assurance – methodically finding and reporting bugs).
This could even teach non-programmers how they can help the most; teaching them how to do proper QA and how to do proper and meaningful research that will assist developers.
While this will require people to work on stuff they may not want to do, it could be a very effecient way to organize and complete projects.
IMVHO, this type of organization could very well make or break the entire community. Some people would very easily be put off by the “forced labor” style of contributing. Though if it worked, which i admit is a long shot, it could dramatically increase our productivity – maybe even draw new people to the scene…“Hey, these people have a straight-forward plan for making progess. I can see what they want and I’d like to help. In fact, according to this list, i can start by doing FooBar”
I believe that most people in our community have a serious desire to help but they simply don’t know what to work on. …Look at other posts in this forum “I know how to do such and such, what can i do to help??” This style of organization can help to inspire people.
I fully understand that most dev’s are focused on R1. IMO, they should be. IMO, Haiku is priority #1. I also realize that Haiku has its own style of organization and right now re-adjusting to a new style of organization could hurt development ( at least in the short term. Maybe once R1 is released, something of this style should be implemented. It would re-focus everyone as Haiku’s goal of re-creating beos r5 in Haiku R1 would be completed.
On a closing note, this style of organization could also further distinguish Haiku apart from the crowd: An organized system of open-source workers. I know of no other open source platform that has such a system of coordination|organization. That could even draw additional interest, both in the form of News headlines and more newbies.
In short: Once R1 is released, Haiku Inc., needs a new method to organize its workers, as aiming for R5 no longer applies. My proposed organizational scheme is rational, well-informative to users, creates well defined development paths and lists the needed objectives for each.
(PM me if y’think i should drop this to the GE or Haiku/OBOS email lists)