[Members] git access

Steven Lloyd Watkin lloyd at evilprofessor.co.uk
Tue Jul 30 13:25:00 UTC 2013

Would it be possible to host everything on github? Github pages/Jekyll
seems to be the ideal way to handle this behaviour:

   - Website has full commit access by all XSF members (and *could* auto
   - XEPs get their own repo which could be pulled in to the website (but
   controlled by council)

I've heard mention of github on here before but not aware of the backstory
so apologies if I've said something out of place.

Failing that an XSF install of Gitlab or similar where everyone gets an
account but with controlled access. Fork and then a pull request which can
be quickly/easily checked over by a council member for merging in?

Visual tools for quickly checking changes + a fork + pull request model
would seem ideal behaviour. Especially if this were all publically
available, all helps the exposure of XMPP.

....Just saw Kevin's response, in which case my suggestion would be gitlab
and then what he said :)



Steven Lloyd Watkin
Software Engineer
PHP ::: Java ::: Ruby ::: Node.js ::: XMPP
lloyd at evilprofessor.co.uk (email+jid) ::: http://www.evilprofessor.co.uk
Facebook / Twitter / Flickr: lloydwatkin

Organiser of WORLD RECORD breaking charity event:
Scuba Santas ::: http://www.scuba-santas.co.uk
Supporting the RNLI & DDRC - 15th December 2013 - NDAC, Chepstow

On 30 July 2013 14:00, Peter Saint-Andre <stpeter at stpeter.im> wrote:

> Hash: SHA1
> Currently most of our key information (XEPs, schemas, registries) is
> under source in a git repository that lives on one of the XSF's
> machines. (Ideally, our full website would be under source control.)
> The question arises: what is the best policy for granting access to
> the source control repository?
> I would be comfortable with giving access to all XSF members, so that
> more people could help with improving / fixing things.
> I could understand if XSF members would prefer some other policy
> (e.g., only XMPP Council members have commit access).
> Please note that there is a difference between committing to the
> source control repository and pushing changes to the website. For
> example, even if we give XEP authors check-in privileges we still
> wouldn't push Draft or Final specs to the website unless the Council
> approves. Similarly, the XEP Editor role (which might be a team) might
> need to review changes that have been submitted before updating an
> Experimental XEP.
> Your thoughts are welcome.
> Peter
> - --
> Peter Saint-Andre
> https://stpeter.im/
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> U7zwMAB7/IBF0VxFW8XQrHmo6am8qMMR/AJsiPz/CahxrJ9nHhQ7VTXzo9KCE2pb
> ExcbulQA0+e2epFcGRe5rokDzl9f25DU6BFxpkGYxK8cQ5bIt9MuGUiueT/scpeO
> xq519YbuaWrgc42KIPsPqVeqI3/cmfj/2+eRlFAD5hviNT18MgpDvXg1NkY9h9km
> X2cfTqBKIvXFyqNcaP0ajwBmvW+yetYPWtPMu+6neDDTgG43RTy3nmNTZ+RdbDX6
> WuEJuCBy+BYQzC4zr3lYUq4y8oGClohENdS16hcbKXShAncpvYfSlzHrERWBlzGz
> RU46l5soxFatx+DKmpluEciGeMOmNjpmJ6vkgKfHT3csk9ctsoPpRn2e66DNFwsl
> EOTaDi7Abms0u6CooTlAbwxjBCfPTEfMpBg/f9rr96w2ghrEl4WH3km50SAdL1cG
> 3QCs460A1fx8m/j5E6oMgqHyH+ICmchnOGBQTHVPdVVxjvz3MoIXkRC0GPK5dn8W
> 5zZA5WSAzZAnOmgqfDl2kzSJSY/7vKW6S1Lw2hCm1f/T8zBPwTT9OSH35aKepSXI
> NjCME+jGwHL5hfxBC4X61TcjrQvP+1zEIQ+DLwengN/S/WFF/vczk0ANU321Pyv2
> EqdCZc2PUCItlKeoNcCW
> =YKjF
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/members/attachments/20130730/2c8fd427/attachment-0001.html>

More information about the Members mailing list