[Members] using GitHub for XEPs - legal risks

Dave Cridland dave at cridland.net
Tue May 12 19:21:29 UTC 2015


On 12 May 2015 at 12:46, Winfried Tilanus <winfried at tilanus.com> wrote:

> For the hasty people: my conclusion is that the liability risk for the
> XSF when dealing with IP-infringement may even slightly improve when the
> XSF editors workflow is done over github.
>
>
Loosely, I agree, though I think the marginal improvement is very slight.

There are a zillion reasons not to use Github, and I entirely respect the
choice of those who won't for whatever reason. I've heard it called "the
Facebook of Open Source", and with good reason. I'd love to see a federated
GitLab thing going on, and I know others would too - but it's not a problem
I have sufficient time to solve.

What I do know is that using github will solve a lot of workflow issues for
the Editors, and the Council all approve (or don't disagree), and it'd make
contributing to XEPs and tracking issues on them both an obvious process
and more friendly to the vast numbers of developers using Github, right now.

My only requirements would be that:

a) The XSF holds the git repository of record, and publishes the XEPs.

I believe this is already mentioned in the current proposal.

b) There remains a path for contributions to XEPs that does not involve
Github.

Likewise.

Therefore I have no objections.

Dave.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/members/attachments/20150512/4bb529da/attachment.html>


More information about the Members mailing list