[copyleft-next] [PATCH] Handling extraordinary private communications via publication.

Richard Fontana fontana at sharpeleven.org
Tue Jul 31 03:10:55 UTC 2012


On 07/30/2012 09:48 PM, Bradley M. Kuhn wrote:
> It seems to me that private communication is inevitable in a project.
> Here's a patch that I propose to add a rule to CONTRIBUTING to handle
> the issue.
> 
> Not sure what the preferred protocol for patch submission/pull requests
> is in this project yet, so I just did everything that was possible.
> 
> A Gitorious Merge request:
>   https://gitorious.org/copyleft-next/copyleft-next/merge_requests/8
> 
> You can pull the change via:
>   git pull git at gitorious.org:~bkuhn/copyleft-next/bkuhn-copyleft-next-proposals.git bkuhn/public-forum-pub-of-private-conversations   
> 
> And, for good measure, the patch is attached:

Just a comment on the 'Signed-off-by:' - we haven't defined any
Developer's Certificate of Origin so I'm not sure if this means
anything. :)

(mcgrof proposed this in a patch archived here:
https://lkml.org/lkml/2012/7/11/624 - my inclination at the time was
that a DCO/Signed-off-by: mechanism for copyleft-next was more
heavyweight than needed for a license-drafting project.)

> Fontana, for future reference, which of this do you actually prefer?

Not sure, since thus far I've only dealt with GitHub pull requests
(back before you reported the bug concerning the use of GitHub) and
Gitorious merge requests. I was kind of envisioning a multitude of
acceptable ways of submitting changes, so that individual preferences
could be accommodated. Indeed, I think it ought to be possible for
someone to suggest a (sufficiently detailed) change in an informal
manner in a posting on this mailing list, without having to attach a
patch. What we don't want are things like redlined Word docs, which of
course would violate what was once known as the Harvey Birdman Rule. :-)

- RF



More information about the copyleft-next mailing list