(top post etc.)

I don't know what's the state of the vote currently, but it seems that
we didn't reached a consensus. However, I would like to add something to
the topic (and change my mind).

Actually, I'm wondering if what we are discussing makes sense. Well, of course
the Nemo UI is a project that now (kinda) have it's own life, but I wonder why
we shouldn't profit from the full Mer infra power: more a discussion about the 
hosting of the whole project instead of just the fate of the bugtracking system.

We already compiles on mer buildservice, why just not use mer gitlab as well 
instead
(or in complement) of github ? The bugtracking system can be decided later. We 
can
see if devs prefer gitlab's bug tracking system, or if they still want a bz. And
if devs want a bz, it might be better to use Mer bz as well, instead of having 
two 
bz instances. 

So the Nemo UI project would live as a subproject, directly inside Mer infra, a 
bit 
like Android Qt lived inside KDE infrastructure (before being attached to 
Digia).

Of course, we still have to know if people of the Mer project are willing to 
provide a
space for Nemo UI inside their infra (a category in BZ, a section in gitlab 
etc.)

What do you think ?



----- Mail original -----
De: "Andrea Bernabei" <and.berna...@gmail.com>
À: mer-general@lists.merproject.org
Envoyé: Mardi 24 Juin 2014 23:39:59
Objet: Re: [mer-general] [NEMO UI] PLEASE VOTE: Nemo UI bug reporting platform


>From Aard on IRC: 


"<Aard> faenil: when considering dropping bz in favour of github -- we're 
working on getting our CI infrastructure in shape that we can offer mer/nemo to 
set up their own like we're using for proper issue tracking over releases and 
stuff. if you move to github you won't be able to benefit from that" 


he also specified that he doesn't make any promise about how long that update 
is going to take, as it's a lot of work 


(also consider holidays are starting soon) 



2014-06-24 22:26 GMT+02:00 Michael Demetriou < qwa...@gmail.com > : 


I'll vote for number 1 so that everyone votes for something different :P 

Jokes aside, I find gitlab to be a very nice system and I have come to 
trust third party providers very little (and incidentally, I just now 
received a message from one of my hosting providers that I have 
exactly one month to move my VPS away - not enough time to migrate 
properly). 

I don't mind github repos as migrating somewhere else is just a clone 
away, but issues aren't so portable (though there is a way to export). 

As a plus Gitlab allows you to see all issues (or all group issues) in 
one place. 





Reply via email to