I don't know how useful a website will be until it's possible to build and install modules (with regard to the build process limitations I mentioned previously), though I suppose that its something that can be worked on in parallel.
Concerning the storage of actual module distributions, my past experience is that having each developer host their modules is a recipe for end user frustration. locations change, people forget to update their information, servers go down, and in the end, good code ends up getting lost forever.
I think that it would be good to get a nice short website name (no offense to the ida folks), that would be easy to remember and type in. Remember, this is as much a marketing function as writing articles and advertisements.
www.pikemodules.org www.pikeprawn.org www.pmods.org
etc.
I'd be glad to set things up at least initially, as I've got a little extra bandwidth. Eventually, my hope is that the modules and information would be replicated multiple places.
As far as documentation goes, it would be nice to have a target that extracted documentation without having to build the module. That way, when a module were uploaded, it would theoretically be possible to merge the documentation into the repository documentation tree.
On Fri, 17 Oct 2003, Martin Baehr wrote:
so far we have been discussing things that pike needs to handle a module repository, how we want the repository organized, but we have not yet looked at the steps needed to get the ball rolling.
some of these things already exist, but if so then all the better:
first:
- we need a server where people can upload their files.
- a place where they can register for an account.
- a place where they can announce their module. (this should ask questions like the desired class name)
- integration of these into the pike site.
then: it should be possible to browse the class hierarchy to download classes and read docs at the same time. both should be available by simple memorizable urls like:
http://pike.ida.liu.se/classes/Protocols/LMTP/Server/
(this would also be nice for the docs themselves. ie: generated/manual/modref/ex/predef_3A_3A could be linked to something short)
i believe the fixes to the module build process are not a prerequisite for this part here. they can be done in paralell or even after this.
does the pike site have everything we need? should we have another site? do we have volunteers to set it up?
greetings, martin.