[Members] using GitHub for XEPs

Kurt Zeilenga kurt.zeilenga at isode.com
Fri May 8 12:04:12 UTC 2015


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.

— Kurt




> On May 7, 2015, at 3:53 PM, Peter Saint-Andre - &yet <peter at andyet.net> wrote:
> 
> Last Wednesday, the Editor Team and the chair of the XMPP Council had a discussion about using GitHub to manage source control, contributions, and issues/bugs related to XEPs (along with schemas and registries). The discussion log is here:
> 
> http://logs.xmpp.org/editor/2015-04-29/
> 
> The consensus of those in the meeting - who, I might add, are the ones actively managing our standards process - is that using GitHub would have a number of significant benefits:
> 
> 1. Make it easier for XEP authors and others to contribute
> 2. Make it easier to track open issues
> 3. Reduce the workload for the Editor Team
> 4. Improve the visibility of our standards work
> 
> Please note that the XSF would still maintain a repository of record outside of GitHub, and that GitHub would be used primarily to manage contributions and issues.
> 
> With my Executive Director hat on, I plan to ask the Board to approve this approach in a future meeting, with at least a week of advance notice so that we can have community discussion among the membership.
> 
> Thanks!
> 
> Peter
> 



More information about the Members mailing list