No, we can have modules of any license in the main tree from a namespace point of view. They might not be located on the same server as e.g Stdio and String, but that should be unimportant in the future.
/ Martin Nilsson (saturator)
Previous text:
2003-10-16 21:54: Subject: RE: more module repository ramblings
Hello,
Hmm, I would assume that accepting a module into the main tree is a non-trivial operation anyway. (Moving the sources, changing authorization, possibly changing the license/ownership of the code...) Modifying a make file is just one more step. (Which no doubt could be automated if necessary.)
Also, I could imagine certain modules, while perfectly usable, will never make it into the main tree because of code quality, documentation or licensing issues. For instance, Al might want to write a great module and allow it to be distributed, but as long as he doesn't sign over ownership to IDA it won't get into the main tree. Having your own personal space in the module tree would still allow this module to be distributed with the same tools as the main ones are.
Another two cents.
Peter.
-----Original Message----- From: pike-devel-admin@lists.lysator.liu.se [mailto:pike-devel-admin@lists.lysator.liu.se] On Behalf Of Bill Welliver Sent: donderdag 16 oktober 2003 20:46 To: peter@lemmen.net Cc: pike-devel@lists.lysator.liu.se Subject: RE: more module repository ramblings
That's actually a clever idea, but it causes problems because currently, the module name is specified in the module build files. Presumably, the author will not make the module available before he has a place for it, but it would certainly be simple to browse for modules by author.
Bill
On Thu, 16 Oct 2003, Peter M. Lemmen wrote:
Hello,
Assuming you already have an author login/handle for the system one might consider using Author.<authorhandle>.* as a location for any non-registered modules that author
has uploaded,
thus allowing users to start using/testing someone's module
before it
has gone through the entire review/acceptance process. Afterwards it would be a simple matter of search/replace when it does get accepted into the main tree.
ex: Author.Peter27.JabberClient
My two cents.
Peter.
-----Original Message----- From: pike-devel-admin@lists.lysator.liu.se [mailto:pike-devel-admin@lists.lysator.liu.se] On Behalf Of Bill Welliver Sent: donderdag 16 oktober 2003 20:28 To: pike-devel@lists.lysator.liu.se Subject: more module repository ramblings
Another thought I had was that I think that it should be possible for the repository to hold modules for both well known places in the tree (such as Protocols.HTTP.*) as well as a sort of Public area (such as the PRAWN.* namespace :)).
Modules that want to get into a well known location would
have to jump
through more hoops, from both a sanity and quality perspective. There'd be less control over the Public location, and you'd basically be able to get a whole subtree such as PRAWN.Protocols.BillsJabberClient or PRAWN.Parser.PigLatin.
Any thoughts?
Bill
/ Brevbäraren