[Members] using GitHub for XEPs

Ralph Meijer ralphm at ik.nu
Sun May 10 19:04:28 UTC 2015


On 2015-05-08 14:04, Kurt Zeilenga wrote:
> GitHub terms of service has an indemnification clause.   The XSF should consider what the XSF is on the hook here for… and what their editor team members and employers are on the hook for… and what authors (and their employers) who choose to have GitHub accounts for XSF work on on a hook for.
> 
> Personally, I’ll just avoid using GitHub personally.  But this means that some other person/organization is going to end up being on the hook to GitHub for XEP materials I submit to the XSF.   I’m kind of surprised that others are so willing to pay for any IPR mistakes any author might make.

As a private person and as Board member, I don't particularly want to go
into why individuals may or may not be able to use GitHub, for legal
reasons or otherwise. I trust everyone to take on that responsibility
for themselves.

I don't know if you have one, but if anyone with a legal background has
a detailed reasoning on why the XSF MUST NOT use GitHub for whatever
(legal) reason, I'd be happy to discuss that with the Board. Just
mentioning a single clause in GitHub's ToS doesn't tell me anything
actionable and I don't fancy thinking about maybes and theories. My
layman's view of the ToS doesn't find anything worrying there, for what
it is worth.

As for not using GitHub yourself, that's fine. There are dozens of other
methods to contribute, including hosting your own copy of the repo with
your feature branch, and submitting patches by e-mail, IM or pigeon. How
such a contribution is then processed is up to the Editorial team and if
they are happy using GitHub to get the job done, I am all for it.

And sure, we could avoid certain issues by installing our own copy of
some open source application. But I know from experience that hosting
such things brings problems of their own, including but not limited to:
effort to set it up, effort to keep it up always, and effort to keep it
up-to-date, backed up, secure, etc. As long as no-one is actually doing
that, and GitHub is a more convenient and pragmatic choice, or at least
for now, to get work done: YAY!

Kind regards,

Ralph Meijer


More information about the Members mailing list