On Sun, 2 Jun 2002, Rasmus Lerdorf wrote:
>I don't think a dictator is needed. Even if I or someone else was to
I did not mean 'dictator' to be one person but an elected group
of people who decides what goes in what doesn't.
>dictate that PHP was a web-only scripting language, do you really think
>that people would stop working on and using PHP for other things?
Of course not. But currently the image for PHP is that it's ONLY
meant for web scripting. Even as it can be used in various other
places too.
I think it would clean some air too if there was a group which
stands behind the certain main ideas behind PHP.
Like for example, CS. That issue pops up quite frequently and
somewhat litters the mailing list with these long debates whether
or not PHP should be fully CS or not. If there was some group
which says that no, this will not change, maybe we wouldn't have
to waste time fighting over it? (or some other similar issues)
>We can, and should, be able to reach concensus on these various issues.
>And we definitely need to stay open-minded and not rule out things just
>because it doesn't show up in some roadmap somewhere. Case in point, the
I did not mean some specific list of things that will be done next or not.
More like a 'road-guide' of general issues. Also, like someone suggested,
it could contain list of tasks people are currently working on and in
which release they're targeting their work on.
For example openssl has something like this:
http://marc.theaimsgroup.com/?l=openssl-dev&m=102304945526862&w=2
They post that STATUS email to their dev-list weekly or so.
(Yes, we have TODO..but who really reads that? :)
I think this kind of status email would be a good thing for us too.
Just needs some person(s) who take care of it..OR, as we have this
nice web scripting language, have a web app where it is edited
and it handles the posting automatically..
>IActiveScript hack. One thing you would think is marked in stone is that
>PHP is a server-side language and it would never end up sitting alongside
>Javascript embedded in a browser as a client-side language. Yet it can
>now do this.
Of course, but is this part of the general vision of PHP? :)
>People are going to take PHP where they think it should go. 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.
No roadmap or group or anything can prevent people doing whatever
they like. But what is 'official'? It could prevent duplicate work
and release some eyes,hands,minds to other tasks. And also,
if it contained stuff that never ever will be done, prevent some
useless emails going out? (like this one :)
>It leads to forking of the project, which in itself isn't bad, but it is
>cooler if we can hold things together and work as a group to accomodate
>the various ideas and approaches in a somewhat organized manner.
See above. I would really like to avoid any forking of PHP..but
if you're suggesting that that's the only way to go..fine.
Is the current way of doing things _organized_ ?
--Jani
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
