« Catalyst Actions, Part 2 (Details and Clarification) | Main | A Mediation on Open Source Development. »

05/03/2009

Comments

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

pete

Hi John,You have EPO linked twice.. the planet catalyst link should be http://planet.catalystframework.org/

John Napiorkowski

Thanks for the correction! I updated the link. Feel free to mention more if you can think of any.

zby

[this is good] I totally agree - CPAN and the community around it is what makes Perl still at the avant garde of the Open Source movement.

John Napiorkowski

thanks for the link, it's a great read. I recommend it to anyone listening!

Andrew Rodland (hobbs)

[this is good] I never thought of it in such concrete terms but you're right about the fluidity of maintainership -- it's happened very often to me that I've looked up a module on search.cpan, seen the author of the latest release, and thought "hey, wasn't

Andrew Rodland (hobbs)

Uhm. Vox seems to have lost half of my comment. Trying again?I never thought of it in such concrete terms but you're right about the
fluidity of maintainership -- it's happened very often to me that I've
looked up a module on search.cpan, seen the author of the latest
release, and thought "hey, wasn't that (someone else)'s project? I guess they must have asked (whoever) to lend a hand." There seems to be a pretty widely shared assumption that with the amount of time and effort that maintenance can involve, anyone willing and able to do the job should be allowed to -- and that it's in the interest of a project's long-term health for the chief users to have a hand in its maintenance.

John Napiorkowski

I would say this kind of shared responsibility is becoming more normal, particular for the very 'big' projects, such as Moose, Catalyst, and similar. In part, I think as the Perl community has solidified some key practices, it's become much easier to integrate new developers into existing projects. Personally, I believe Moose has played and will play a big role in this. That's one reason why I heavily advocate Moose, it's a great shared context that lowers the learning curve and increases accessibility to the code. Thanks for the comment.If anyone out there is interested in joining a CPAN development community, but is a little lost in how to start, feel free to message me or response in comments.

The comments to this entry are closed.