Re^2: Responsibilities of a module author

With a meta-grain of salt, I'd have to say that I agree with BrowserUk's general idea of a standard, non-hostile, non-emotionally charged protocol for continuing the evolution of a CPAN module when its original author has expressedly or de facto suspended the support for it.

I also agree with Perl Mouse when he says that "CPAN is just a repository. The great thing is that anyone can contribute any code to it.". Precisely, IMHO, it should be possible to contribute any code to solve any given problem, not just problems where no author before has planted its flag.

In this sense, I feel that thought could be given to a natural and agile way (built into the structure of CPAN) of branching or evolving a given module, a way that automatically took care of authorship, copyright and and other important formalities. That is, so that every bit of work by any author (no matter the level of it's original author's involvement after it is released) would be completely shared with the other authors and users.

Of course, this solution might not be simple (I'm pretty sure it wouldn't be (if it is possible, in the first place)), but that is precisely why I think it should be addressed in a formal and standarized (and agreed upon) way.

Then again, one might be told to "go make your own repository if you don't like CPAN as it is". That'd be unkind response, but a valid one.

Comment on Re^2: Responsibilities of a module author

Replies are listed 'Best First'.
Re^3: Responsibilities of a module author by Perl Mouse (Chaplain) on Nov 28, 2005 at 10:28 UTC
In this sense, I feel that thought could be given to a natural and agile way (built into the structure of CPAN) of branching or evolving a given module, a way that automatically took care of authorship, copyright and and other important formalities. I don't think this should be build in the structure of CPAN. The ability to fork is a licensing issue - most open source licenses allows you to fork. It's totally indepent of the existance of the module on CPAN. That is, so that every bit of work by any author (no matter the level of it's original author's involvement after it is released) would be completely shared with the other authors and users. That's not the task of CPAN. CPAN should not dictate what rights authors must be willing to give up for distributing a module via CPAN. The only restrictions CPAN should put on authors are those that keep CPAN from doing its work, as such, the restrictions for authors is that their work should be freely distributable. Adding the requirement that outsiders may take over authorship and copyright of a module isn't a good thing in my opinion. You'll lose people contributing code to CPAN. Not to mention all the resources you have to pour in to work out the legal details of this. `Perl --((8:>*`	[reply]
Re^4: Responsibilities of a module author by BrowserUk (Patriarch) on Nov 28, 2005 at 12:41 UTC
Adding the requirement that outsiders may take over authorship and copyright of a module isn't a good thing in my opinion. I'm at a loss to see where anyone suggested that this could/would or should happen? I'll restate that I was not suggesting anyone should be able to "take over authorship and copyright". All existing copyrights and licences would remain in place and sacrosanct, as with any other OS code. The idea was to provide a somewhat formalised mechanism for the extension and improvement of modules through the collaborative efforts of it's users, that maintained a continuity between the developments that would aid both the original authors; and existing and future users. If the original author is unable to accommodate changes that users require for their use of the module, whether through being uncontactable; unable to continue maintenance for whatever reason; sees the requested changes having undesired affects upon other users of the module; or simply that they take the module in directions he never intended it to go; A somewhat formalised mechanism for forking the development would ensure not only that the collaborating users could find each other and achieve their needs; it would also ensure continuity of both authorship and licencing of the original elements of the module. Not only does this help ensure that you don't get half a dozen unilateral forks by disparate individuals; it also allows future users to find and follow the developments rather than their being spread all over the Internet, (or worse, unavailable publicly!). It could also allow the original author to "keep a watching brief" on where the fork is going, and even offer consultative advice to it's progress. There was no intent to impose extra restrictions upon authors, nor in any way diminish their rights. Just to formalise those rights and procedures already in place--to everyones benefit. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal? "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]
Re^5: Responsibilities of a module author by Perl Mouse (Chaplain) on Nov 28, 2005 at 13:40 UTC
Adding the requirement that outsiders may take over authorship and copyright of a module isn't a good thing in my opinion. I'm at a loss to see where anyone suggested that this could/would or should happen? mifune wrote: I feel that thought could be given to a natural and agile way (built into the structure of CPAN) of branching or evolving a given module, a way that automatically took care of authorship, copyright and and other important formalities. If authorship and copyright are to be stayed at the original author, what are the "formalities" regarding authorship and copyright then? A somewhat formalised mechanism for forking the development would ensure not only that the collaborating users could find each other and achieve their needs There's no reason why this mechanism should start with changing CPAN. I'd say, hammer out the details of your mechanism. Start acting on it. Find the quircks. Work them out. Then, after you have a working mechanism, first contact the modules mailing list with your suggestion, then try to get PAUSE changed to handle your (by now proven) mechanism, and then you can see whether you can build this into CPAN. it would also ensure continuity of both authorship and licencing of the original elements of the module. No change to CPAN is required to do. Copyright and licensing laws already force this to be the default. Not only does this help ensure that you don't half a dozen unilateral forks by disparate individuals; Actually, it won't help your ensure that you don't get half a dozen forks. At best, it will prevent some forks, but there will still be people ignoring whatever framework you create, and creating their own forks. This is an open source world we live it. `Perl --((8:>*`	[reply]
Re^6: Responsibilities of a module author by BrowserUk (Patriarch) on Nov 28, 2005 at 14:34 UTC
A reply falls below the community's threshold of quality. You may see it by logging in.


"be consistent"
	PerlMonks