[antlr-interest] pull requests at github

Kyle Ferrio kferrio at gmail.com
Thu Jul 12 13:27:25 PDT 2012

I probably should eat lunch before I try to understand this, but here I

I like.  Sounds easy enough that it will not be a barrier to use or

It sounds like you envision multiple "simple text documents" for the
contrib license.  Or do you mean each project (antlr, stringtemplate, etc.)
would have it's own (versioned) contrib agreement?  I would think that each
project would have exactly one (versioned) contrib agreement which would
exist within the repo of its respective project.

So...when you refer to "the commit hash for that document" do you mean the
guid for the main project repo or the guid for the contributor's fork?  Its
important that it reference the main repo in some way, since a contributor
could permanently delete his fork at any time after the pull.  Didn't quite
follow your logic there.

I like the idea of having github link directly from the commit log to the
committed document if that really works the way you envision and pulls up
the whole changeset which license and code together.  But since that relies
in part on behavior of githib -- not just git itself -- the design may be
brittle to changes in githib.  Even if githib does not change, you're
locked into githib.  I doubt github is going away (a $100MM in VC should
last at least a few months even in the valley) and git itself isn't going
anywhere.  So the worst-case scenario would be that contributions might be
put on hold when you have to adapt to changes at github (all the more
reason to make github aware of the need) or you migrate to another
git-based provider.


On Thu, Jul 12, 2012 at 10:46 AM, Terence Parr <parrt at cs.usfca.edu> wrote:

> Hi guys, okay, I have another idea.
> Let's make a directory that's part of the source code itself that contains
> simple text documents with the language of the contributors license
> followed by the sign off line. Then, the commit hash for that document is
> the user's unique contributors ID. It's also unique in principle across all
> projects so the same user could sign a different contributors license for a
> different project.
>  During a commit, users would put their ID hash number into the comment
> and then I think github would automatically link to the document containing
> their signature.
> would that work? I think so. I also like the idea that I don't have to
> maintain the signatures anymore. They are just in the source code
> distribution.
> Ter
> List: http://www.antlr.org/mailman/listinfo/antlr-interest
> Unsubscribe:
> http://www.antlr.org/mailman/options/antlr-interest/your-email-address

More information about the antlr-interest mailing list