I'm still more inclined to vote 2 as I'm familiar with BZ and I like that it's detailed. And also using buzilla means having a website which has only one purpose, bug reporting. I like that I can visit sections and see bugs for each piece of software, instead of having to visit repo URLs one by one and click on their "issues" subpage...
But since I don't have much experience with GitLab and GitHub issues, don't take my vote too seriously. Whatever is okay to me. 2014-06-24 16:01 GMT+02:00 <sfietkonstan...@free.fr>: > Hi ! > > (Mandatory: "Sorry for top posting, webmail") > As I already said on IRC, I prefer not using bz, because it's heavy and > hard to use. > Not saying it's a bad tool, but for our developement, I would prefer > having github > issue tracking, that is much simpler to use, and have some other bonuses > (integration > in commit messages etc.) > > qwazix said that gitlab have an even better issue tracking. And we also > have Mer gitlab, that > might be even more integrated to the mer project (for example webhooks), > so I would vote for > 1. move to gitlab (have a specific Nemo UI section if it's possible) > 2. stay on github > > ----- Mail original ----- > De: "Andrea Bernabei" <and.berna...@gmail.com> > À: mer-general@lists.merproject.org > Envoyé: Mardi 24 Juin 2014 15:51:25 > Objet: [mer-general] [NEMO UI] PLEASE VOTE: Nemo UI bug reporting platform > > > Hello people :) > > > Since Nemo Middleware is being folded into Mer Core, it's not clear what > it will be of Nemo bugzilla instance. > > > We either: > 1) move Nemo UI repos to Mer Gitlab, and use gitlab as the bug reporting > tool > or 2) rename Nemo bugzilla to something and keep using that > or 3) use github issues > > > Please reply to this post expressing your opinion ;) > > > The voting closes in 1 week! :) > > >
