Excuse the top post, I'm on my phone. I personally think GitHub would work really well for this workflow for a number of reasons. It's simple for anyone to obtain an account, it would encourage more people to contribute, it lowers the barrier and makes changes much less onerous, encouraging minor incremental changes, which would help improve the quality of xeps.
We could host gitlab or gitorious but I think the authentication issue is a real one - for someone to have to track down an xsf admin to obtain an account would, I believe, put some people off of contributing. Just my 2c Ash Sent from my iPhone On 1 Sep 2014, at 22:39, Steven Lloyd Watkin <[email protected]> wrote: Which is the bigger advantage, more exposure, more convenience, more bugs raised, and more pull requests. I do however understand that its more complicated than it seems on the surface. But projects being posted on google code or bitbucket that almost puts me off contributing. Unfortunately this comes up every 6 months and seemingly the status quo doesn't work for people joining the XSF and some of the current membership (not that current efforts are not appreciated obviously). I'm happy to discuss again but we need to make a firm plan to either do something or remain as we are. On 1 Sep 2014 22:03, "Dave Cridland" <[email protected]> wrote: > On 1 September 2014 21:43, Evgeny Khramtsov <[email protected]> wrote: > >> Mon, 1 Sep 2014 20:43:57 +0100 >> Dave Cridland <[email protected]> wrote: >> >> > Not all our contributors currently will use github. >> >> Who will not? And why? >> > > See Kurt's comment as to one possible reason why. > > I use it for both work and pleasure; I'm more in the camp of wanting to > avoid a proprietary outsourced lockin for a core concern. I don't mind a > mirror on github, but then people expect to do pull requests and issue > tracking. > > Dave. >
