[mplspm]: Submitting patches to module maintainers

[Matt Johnson]

[It was nice to meet all of you last night, esp Chris, Charles and James.]

I don't currently have any code on sourceforge.net, but from what I can see, it is a free hosting.  Is that true, James?   SourceForge does have nice project management features and I believe they are owned by the same company that owns slashdot.  Check it out if you haven't been there before. http://www.sourceforge.net

  -Matt Johnson

The following message was sent by "James.FitzGibbon" <James.FitzGibbon at target.com> on Thu, 31 Jan 2002 08:16:05 -0600.

> At last night's meeting, there was a point raised about maintainers
> of open source projects and getting them to actually incorporate them
> into future releases.  I had an idea on the way home that I wanted to
> bounce off people.
> 
> I think one of the big problems with reporting bugs and submitting
> patches is that a) a single email reporting a bug is easily deleted
> and forgotten (hopefully not on purpose) and b) if you are too busy
> to incorporate the patch, it's difficult to delegate that task to
> someone else.
> 
> Hopefully most people are familiar with SourceForge, the Open-Source
> project hosting site where you can start an Open Source project and
> have access to a private CVS repository, web space, the ability to
> release tarballs, mailing lists, bug reporting, etc.  If you're not
> familiar, please check out www.sf.net.
> 
> The idea I had was to promote the idea of getting module developers
> to host their modules on SourceForge.  That way when a bug is reported
> it goes into the tracking database for that module and the author can't
> just indiscriminately delete it.  The author could also start discussion
> groups so that potential patch submitters could bounce their ideas off
> of other users of the module before sending the final patch to the
> author.
> 
> Best of all, if the author needed to take a temporary hiatus, it would
> be easy to give CVS commit access to a trusted lieutenant who could
> take on the task of committing patches.  When the author was ready to
> come back, they would be able to track the exact changes that had taken
> place in their absence with CVS.
> 
> These arguments of course apply to all Open Source projects, not just Perl.
> The benefits are (I would argue) required when a project reaches a certain
> size, and with the exception of large modules like Event, DBI, Mason, etc.,
> people may not have thought about using something like SF for this.
> 
> Discuss?
> 
> -- 
> j.
> 
> James FitzGibbon                       voice/fax 612-761-6121/4277 
> Consultant, TTS-3D at TPN4H               james.fitzgibbon at target.com
> 
> 
> --------------------------------------------------
> Minneapolis Perl Mongers mailing list
> 
> To unsubscribe, send mail to majordomo at pm.org
> with "unsubscribe mpls" in the body of the message.
> 


--------------------------------------------------
Minneapolis Perl Mongers mailing list

To unsubscribe, send mail to majordomo at pm.org
with "unsubscribe mpls" in the body of the message.