Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Putting aside the other technical superiorities, the entry barrier that Git removes is that of one off contributions.

    Once you have an account it's easy to regularly contribute using SVN.

    Git makes it easy to contribute to a project even if you've never contributed before, without knowing what the framework for contribution is, and without needing to be authorized.

    It fills in the gap between emailing patches to someone (which is has technical annoyances but no administrative overhead) and giving commit access (which is technically streamlined but required administration) using its distributed nature to allow sending of patch files that have all the proper metadata to be cleanly applied.

    This is taken further by hosting sites like github which let you create your own private repository from anyone else's repository, where you get full write access, so that people can pull changes from you.

    Because of this getting one off fixes from non regular contributers is much lower overhead for both parties, and usually leads to more regular contributions later.

    With subversion, even with a streamlined invite mechanism things would never be as smooth and safe.

    • (and yes, i've received many many more contributions since I've switched, even if most of them did not become collaborators afterwords)