Good question. @Klaas, Danimo: What do you think? Should the Mirall bugs be isolated in the mirall repo or together with the others?
Frank On 22.10.2012, at 18:33, eMerzh <[email protected]> wrote: > Hi, > i'm happy to see we move on with a better solution :) > > one single question about organisation, should the bugs about the > clients be created in the mirall/.. repository or we keep everythin > under app / core > > and can we move an issue from one repo to another? > > Thanks :) > > > > On Mon, Oct 22, 2012 at 10:16 PM, Frank Karlitschek <[email protected]> > wrote: >> Yes. >> github issues seems to be preferred by most people. >> But it was important to find a way to structure the transition which we >> hopefully have now. >> >> Frank >> >> >> On 22.10.2012, at 18:12, Michael <[email protected]> wrote: >> >>> Frank, >>> This seems like a great solution. Thank you for working with everyone >>> to get it set up. Anything is better than what we have now - it >>> doesn't even list the bugs half the time. >>> I assume this move is starting immediately - are there any places >>> where we need to change links, update documentation, etc.? >>> >>> >>> On Mon, Oct 22, 2012 at 2:59 PM, Frank Karlitschek <[email protected]> >>> wrote: >>>> Hi everybody, >>>> >>>> our current bugtracker bugs.owncloud.org works less than optimal as we all >>>> know. We had several discussion on the mailinglist on irc and in personal >>>> about options to improve this and I think all the options are on the >>>> table. I think we need a solution because it is difficult to work with and >>>> people are complaining. >>>> >>>> github has a simple but nice issue tracker and it is also nicely >>>> integrated so the idea was and is to move to it. We don´t have a lock-in >>>> effect there because they have nice import and export APIs. Thomas even >>>> wrote a very great migration script :-) >>>> >>>> The problem is that we lose the user accounts when we move the existing >>>> issues over and urls to the old bugs won´t work anymore. >>>> >>>> So what we now do is this: >>>> >>>> We will keep the old bugtracker bugs.owncloud.org for the old bugs but I >>>> will disable the option to add new bugs. Existing bugs can still be >>>> updated and closed. >>>> New bugs can be added on github. I even saw recently that other project do >>>> it exactly like that too. >>>> So it can´t be that wrong ;-) >>>> >>>> >>>> This seems to be the best option for now and I hope that works for >>>> everybody. >>>> >>>> >>>> Frank >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Owncloud mailing list >>>> [email protected] >>>> https://mail.kde.org/mailman/listinfo/owncloud >>> _______________________________________________ >>> Owncloud mailing list >>> [email protected] >>> https://mail.kde.org/mailman/listinfo/owncloud >> >> _______________________________________________ >> Owncloud mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/owncloud > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
