I think it is not about a group of dictatos defining what the roadmap will look like, but more what the current active developers commit to for the next couple of months.
The important bit is giving people a better idea of what to expect next so they can make a better decision if they are in doubt because the miss a certain feature in PHP atm. We will see how much we can expect from those commitments but I hope that we can afford to set a high level of expectation in terms of developers having to follow through with what they say they will commit on. If a developer repeatedly does follow through with their commitment, then their work might not make it onto the next roadmap. The cool thing about being on the roadmap is the huge exposure your will get. Best regards, Lukas Smith [EMAIL PROTECTED] _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de [EMAIL PROTECTED] > -----Original Message----- > From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 03, 2002 7:35 AM > To: Sebastian Bergmann > Cc: [EMAIL PROTECTED] > Subject: Re: [PHP-DEV] WHAT is PHP's vision???? > > That's fine, but that is not what Jani was talking about. And I am > curious, what do all the developers who have no interest (or no > experience) with one particular topic like this do in those 3 months? > > I think people want to apply traditional software development > methodologies to open source development. Jani wants a dictator who will > set the rules and tell people what to work on. Others want refined > roadmaps, release schedules, etc. I think you are missing as key concept > here. People volunteer their time and effort to work on things that > personally interest them. If someone comes along wanting to work on X he > does not want somebody telling him to go work on Y instead and have it > done by Friday. That is simply not how volunteer-driven collaborative > software development works. > > The challenge as a project grows is how to keep people interested and > contributing while still keeping some sort of direction in mind. The > bigger things get, the less laser-like this direction can be. It has long > since become a wide-beam flash light. We'd like to try to avoid it shining > off into all directions at once and at least direct the light somewhat > towards one direction, but I don't think it is realistic to expect more > than that. The single-developer laser-like direction just won't happen. > > Writing roadmaps is fine, but unless you find developers willing to > enthusiastically put their names on each bullet point of the roadmap, it > means nothing. > > -Rasmus > > On Mon, 3 Jun 2002, Sebastian Bergmann wrote: > > > Rasmus Lerdorf wrote: > > > A roadmap marked in stone is going to alienate people and make them > > > less likely to go exploring down roads that whoever wrote the roadmap > > > didn't think of. > > > > Roadmaps can be changed. Or be short-termed. I think it'd be nice to > > have a "roadmap" like: "In the next three months, we'll focus on the > > development of a unified XML/XSLT extension." > > > > -- > > Sebastian Bergmann > > http://sebastian-bergmann.de/ > http://phpOpenTracker.de/ > > > > Did I help you? Consider a gift: http://wishlist.sebastian- > bergmann.de/ > > > > -- > > PHP Development Mailing List <http://www.php.net/> > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
