[Draft] Pear web

I tried to write a minimal draft of the needed work to put the packages distribution system up. If we could finish this draft and set up a small team of developers we could start to build it. I make me volunteer to be part of this team. Don't you? :) I would recommend to people who wants discuss an specific area of this doc, to open a new thread, so we won't get crazy tracking different topics. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CONVENTION for HTML widgets: |url: foo |------------------------------ web page | Text | |------------------------------ Input text |_______| Button |Text| Link _Text_ Check button |*| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ USERS POINT OF VIEW (how the public web will look) url: pear.php.net/packages/ ------------------------------ search: |_______| Top Level Categories: _HTML_ _MAIL_ _DB_ _XML_ _NET_ |Download all packages| ------------------------------ url: pear.php.net/packages/category.php?idcat=X ------------------------------ search: |_______| NET category Packages: |*| _Net_CheckIP-1.1_ summary |Download| |View Doc| |View Source| |*| _Net_NNTP-1.3_ summary |Download| |View Doc| |View Source| |*| _Net_Ping-1.4_ summary |Download| |View Doc| |View Source| |Download all "Net" packages| |Download selected packages| Leyend: - Red packages means Experimental State ------------------------------ url: pear.php.net/packages/package.php?idpack=X ------------------------------ Net_NNTP-1.3 Authors: |photo :-)| Summary: Release Date: Release Notes: |View Doc| |View Source| |View Changelog| Net_NNTP dependencies: PHP > 4.0.2 PHP imap extension _Net_Foo-1.5_ |Download| |View Doc| |View Source| _Net_Ping-1.3_ |Download| |View Doc| |View Source| |Download all| |Download only Net_NNTP| Other releases download: _last cvs_ _1.2_ _1.1_ _1.0_ |Visit Net_NNTP users meeting point| ------------------------------ - View doc -> shows all the files marked as Role="doc", includes READMEs, api doc, examples and other documentation - View source -> link to cvs.php.net - View changelog -> dinamicly generated changelog from release tags of package.xml - Download all -> the last release and dependencies - Other releases -> cvs download from certain cvs tags (links generated from releases in package.xml) - Users meeting point -> Link to the authors page of the package, a forum, etc. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ RELATED TASKS -Write the DEVELOPER POINT OF VIEW -"package.xml" support for multiple authors -"package.xml" support for multiple release tags -"Install/Package" support for multi-package tar's -finish the pear package local database (update/remove/list packages) -implement package dependencies ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PREDEFINED PACKAGES SETS We have been adviced by the problems of CPAN. One idea is to have predefined sets of packages ready to install. url: pear.php.net/packages/core/ ------------------------------ Core packages |*| _Level 1_ recomendation |Download| |*| _Level 2_ recomendation |Download| |*| _Level 3_ recomendation |Download| |Download selected| |Download all| |Download required| ------------------------------ recomendation-> required, highly recomended, recomended, optional url: pear.php.net/packages/core/level.php?idlevel=X ------------------------------ Level 1 Contains: _XML_Parser_ summary _Pear_DB_ summary |Download Level 1 packages| ------------------------------ Each package correspond to one level. A package belong a certain level according to: is used by lot of other packages and/or is a popular/widthly used package. We could also give recomendations to ISPs/users/developers that levels from 1 to 3 are required, from 4 to 6 highly recomended, etc. Tomas V.V.Cox