yade-dev team mailing list archive

[janek_listy@xxxxx]

Ok, so it seems that at the moment nothing can beat the launchpad interface, especially the questions & answers database with its history. So I agree the we keep launchpad for this.

Regarding the sole git server choice - we know that decentralized nature of git turns this into a non issue.

However there may by still some ways to unify or simplify current process with gitlab. So let's use what they have in their offer.

Janek
On 20 Dec 2018, 10:39 +0100, Duriez Jerome <jerome.duriez@xxxxxxxxx>, wrote:
> Hi,
>
> I'm also proposing we keep our Launchpad interface. This lack of a convenient Questions interface on Gitlab seems a problem to me.
>
> Frontpage such as https://launchpad.net/yade look also to me less "geek" than e.g. https://gitlab.com/axiom-micro/hardware (which should just compare to https://github.com/yade)
>
> As for the bugs, I like the possibility we currently have to link Launchpad bugs with Launchpad questions (which leans me towards keeping Launchpad bug management), even though this is a less major thing to me.
>
>
> Jérôme
>
> De: "bruno chareyre" <bruno.chareyre@xxxxxxxxxxxxxxx>
> À: "Yade developers" <yade-dev@xxxxxxxxxxxxxxxxxxx>
> Cc: "remi cailletaud" <remi.cailletaud@xxxxxxxxxxxxxxx>
> Envoyé: Vendredi 14 Décembre 2018 15:59:14
> Objet: [Yade-dev] (no subject)
>
> Thanks for investigations Robert. That's convincing.
> Mixing bugs and questions does not seem to be a good idea.
> A mixed option could be to move bugs to gitlab and keep Q&A on LP, hence separating them even more.
> Not sure there is any real advantage in doing that, though.
>
> Bruno
>
>
>
> On 12/14/18 11:15 AM, Robert Caulk wrote:
> >  >> If you asked me it is probably time to move everything (incl. code, Q&A, bug tracking etc.)
> > >> If source code was migrated, same question for bug tracking and answers?
> >
> > I looked into this. From what I can tell, GitLab only offers issue tracking, which is analgous to bug tracking on LP. Issue tracking was not meant to be a Q&A forum, however, some projects use issue tracking (aka bug tracking on LP) as a place for community support [1], despite the awkward interface. GitLab does provide a nice labeling system, so questions or "support requests" can be filtered as such. But it is likely that Yade users will become confused since it is not a traditional forum format, they will simply search through all bugs and questions at once, they will post without considering the labels, or worse, they will use the wrong labels. I'm scared of a disorganized mess. What do you guys think? Was it useful to keep bugs and community questions separate?
> >
> > If we decide it is preferable to combine bugs (issues) with community questions, then I vote for an effort to migrate the launchpad Q&A archives over to GitLab issues. I looked around and found some apathetic conclusions regarding Launchpad->GitLab bug migrations [2]. Ultimately, some tools exist but they will likely need to be retooled. This could be a significant project, tough to tell...
> >
> > Given all this information, I lean toward leaving the Q&A on launchpad. What is your opinion?
> >
> > [1]https://gitlab.com/gitlab-org/gitlab-ce/issues/20851
> > [2]https://gitlab.com/gitlab-org/gitlab-ce/issues/47399
> >
> > rc
> >
> > > Le mer. 12 déc. 2018 à 07:52, Klaus Thoeni <klaus.thoeni@xxxxxxxxx> a écrit :
> > > > Hi Bruno,
> > > >
> > > > yes, that's right. Dev's should have the rights to do that.
> > > >
> > > > K
> > > >
> > > > > On Wed, Dec 12, 2018 at 2:00 AM Bruno Chareyre <bruno.chareyre@xxxxxxxxxxxxxxx> wrote:
> > > > > >
> > > > > >
> > > > > > On 12/5/18 7:21 AM, Klaus Thoeni wrote:
> > > > > > > I terms of branching, I think this should be kept flexible. I think
> > > > > > > branches make sense if you work on major changes. However, I still
> > > > > > > think main devs should be able to push directly to the trunk,
> > > > > > > obviously with care ;-)
> > > > > > I think we need to distinguish two aspects:
> > > > > > 1- do we "push" or do we "request-merge"?
> > > > > > 2- who is allowed to accept the merge requests?
> > > > > >
> > > > > > I don't see a real need to use direct push (point 1), one exception is
> > > > > > when fixing simple bugs maybe.
> > > > > > What you say is more  (I guess) that some devs need enough rights to
> > > > > > accept their own MR (point 2). Right?
> > > > > >
> > > > > > Bruno
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > _______________________________________________
> > > > Mailing list: https://launchpad.net/~yade-dev
> > > > Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
> > > > Unsubscribe : https://launchpad.net/~yade-dev
> > > > More help   : https://help.launchpad.net/ListHelp
>
> --
> _______________
> Bruno Chareyre
> Associate Professor
> ENSE³ - Grenoble INP
> Lab. 3SR
> BP 53
> 38041 Grenoble cedex 9
> Tél : +33 4 56 52 86 21
> Fax : +33 4 76 82 70 43
> ________________
>
> Email too brief?
> Here's why! http://emailcharter.org
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help   : https://help.launchpad.net/ListHelp
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
>