« Resume Writing Services | Main | Moose Dependent Type Constraints »

05/20/2009

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Iftekharul Haque

[this is good] Hi John,I was wondering how putting corporate code onto the CPAN would particularly help? Like in terms of the code itself, does making the code CPAN-friendly actually make the code more robust, or easily maintainable, etc?My organization is currently in the process of cleaning up all of its code in the DarkPAN, and this seems like a good idea at face-value, but I'm wondering what the long-term benefits are of putting code up on the CPAN, basically.I would have to pitch this to management, to take advantage of a for-pay CPAN service (which, again, at face-value, sounds really good).Thanks in advance,Ifty.

Gabor Szabo

[this is good] Encouraging companies to put their code on CPAN is good but I think only if the license is compatible. That would mean the "perl license" or at least to be some open source license. Otherwise I don't think anyone will have any benefit.Actually I don't think companies would put their secret code on CPAN anyway.As to answer Ifty, I think there can be huge benefits to put your code on CPANassuming it can be reused by others. (that is, assuming it has an open source license). These are usual things that open source can provide with the extra features of the Perl community. So you will get free of charge:1) Peer review2) Automated testingPossibly you'll get3) Patches to fix issues4) Patches for further features5) Your deployment process can be further streamlined and standardized.If you put new versions on CPAN early maybe even before you start using itthen you have a chance that others will find the bugs in it and maybe even fix them before your company encounters them.

John Napiorkowski

My thoughts on the matter are a little scattered, but I was thinking we could allow graduated licensing of code in the 'for pay' CPAN. For example, they could block source code but allow pod to be indexed, which would allow people to see the code in search results, but would have to get access to the code via a specified process. This level would basically smoke test the code across CPAN's vast, distributed testing system, which has a clear monetary value associated.Another level could be to grant source access to authors of dependent modules. This would assist in debugging, and again could be part of the thing you pay for.I'm envisioning this as another way for CPAN authors to make some extra money supporting thier open source stuff for Darkpan stuff, as well as bringing in some money for all of CPAN to use for feature enhancements or to fund grants.Basically it's a pay to play system, where the more secret you want your code and or the more support you want would have a price associated. Right now most CPAN authors maintain their code for free, as part of their feeling of duty to the community and as a way to gain merit, but this model has a downside in that if I am busy getting paid to do something else, I might not have time to support the code. On the other hand, this has lead to how we are really getting better at sharing co-maintence for modules where many people have shared interest. So I don't want to destroy that. Just some stuff on CPAN get's busted and no one ever fixes it :) I'm just brainstorming on ways to tweak the model a bit. I definitely don't want to turn CPAN into some sort of global repository for code no one can use. The idea would need a lot more thought.As for the issue of making your code a CPAN module even if you don't plan CPAN release, well, that's considered a best practice, although not really documented in one place. I have a very late blog for the next BlueChild installment that discusses this in detail (too much probably, which is why I am so late with it.)

Kent Fredric

[this is good] There also becomes the prospective of CPAN -

Kent Fredric

I wrote more, but vox saw my literal gt; character and decided to chomp everything :(, and now I forgot what I wrote.

John Napiorkowski

I'm sorry that happened. I emailed Vox your problem. It should really warn you about that.

Baby Stallman

If you're trying to make the world a better place, don't enable artificial scarcity.There's already enough REAL scarcity in the world.

Baby Stallman

The Vox bug got me, too, but the main point survived.

mysoberlife

[this is good] This was a helpful article to me.Thank you!

The comments to this entry are closed.