Hi,
there has been some chatter about windows.php.net, which drives me to
the question: Do we need that site? Why and for what?
Few data items:
* The "news" on w.p.n are not really maintained and provide
outdated info.
* Downloads are not using our 90 world-wide mirrors but a single
site giving worse connection quality than needed
* Snapshots on that site are outdated since more than a year (one
can find newer ones when looking at a small note)
* Team lists three people I don't know (might be my fault) who
probably aren't part of the php.net community (what ever that
is) and in general I don't understand the need for extra
credits.
* The site can only be updated by a small group of people
different requests to broaden this (i.e. by updating from git
like other php.net sites) have been rejected (or at least
ignored, i.e. bug #64277)
My idea would be to
* shut down most of windows.php.net
* Provide downloads via our mirrors. This might need work on a
nice downloads page, probably some configuration to make sure we
comply to US crypto export stuff (i.e. no U.S. servers for d/l)
and probably a different approach to provision the distributions
directory (git is not thaaat usable with these tons of "large"
binary files)
* either integrate snaps with snaps.php.net or create a limited
w.p.n site doing only that and..
* handle QA releases similar to snaps, if distributed from w.p.n
provide direct links from qa.php.net
* integrate team listing with credits, where needed
johannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
