On 02/09/14 14:08, Kevin Smith wrote: > On Tue, Sep 2, 2014 at 12:59 PM, edhelas <edhe...@movim.eu> wrote: >> Ok, so, to sum-up a little bit the discussion : >> - We all agree that we need a bugtracker to manage the issues related to >> each XEP > I haven't seen much objection to this, as long as it's going to get used. > >> - This bugtracker have to run with GIT (because the current XMPP repo is on >> GIT) > That would be the most convenient thing. > >> - This bugtracker have to be open-source and deployable on a server that the >> XSF can administrate > I think there's a strong preference for something we can deploy > ourselves from some people, and a strong preference for open-source > from others (possibly a subset, but certainly there are people in camp > 1 who are less firmly in camp 2). > >> - This bugtracker should have some nice issues that we can find on GitHub >> like the pull-request system > I don't think this one is a done deal, but pull requests are a model > that might be made to work. > >> - This bugtracker could have a nice "one XEP = one project" system to easily >> split the issues between the XEP and notify the author (and subscribers) > I think this is a good idea, but more of the Editors should chime in > before anything gets settled there. > >> - This bugtracker have to be open to anyone using a simple email adress or >> OpenID > I think this is heavily desirable. > >> We have to agree about what kind of tool we need (with which specific >> features). Then we will see how to deploy it and use it with the current XSF >> system :) > I think looking at gitlab has a lot of merit here, as it seems to tick > a lot of boxes. >
If there's (eventual) rough consensus on going gitlab, I'm pretty sure we'll be able to find a volunteer within the iteam to handle this. Edwin
