Re: [eigen] GitLab migration is starting now!

[Christoph Hertzberg <chtz@xxxxxxxxxxxxxxxxxxxxxxxx>]

I should have checked for new mails, before sending my last.

I just granted you Reporter rights (as well as to two other people who 
requested access -- I did not grant Developer access, of course).

I think the manual approval of new members won't be as tedious as the 
previous procedure of granting access to our bugzilla. And having a 
manual step with a small time delay might be a good way to avoid 
bug/PR-SPAM.

Cheers,
Christoph

On 05/12/2019 18.16, Joel Holdsworth wrote:
> Ok... manual approval sounds tedious. I would recommend figuring out a 
> way to automate the approval e.g. with a button on the website. 
> Otherwise, it's just pointless admin for you guys.
>
> Anyway, my username is "jhol", so can you make me reporter?
>
> Joel
>
> On 12/5/19 5:07 PM, Gael Guennebaud wrote:
> > On Thu, Dec 5, 2019 at 5:33 PM Joel Holdsworth 
> > <joel@xxxxxxxxxxxxxxxxxxx <mailto:joel@xxxxxxxxxxxxxxxxxxx>> wrote:
> >
> >     Hi Gael!
> >
> >     Thanks for this. It's going to make my work so much easier.
> >
> >     I just wanted to resubmit my int8 ostream patches, but it seems 
> > that I
> >     dodn't have permissions to submit a merge request. Do you need to 
> > open
> >     up the MRs to non-members?
> >
> >
> > thank you for trying. I was indeed unsure whether MR was open to 
> > anybody. According to this page: 
> > https://docs.gitlab.com/ee/user/permissions.html, MR is open for 
> > "reporter" members only, meaning that we'll have to manually approve 
> > people wanting to join the project to propose MR.
> >
> > For the record, compared to "guests" (aka everybody for a public 
> > project as Eigen), reporters have the following additional permissions:
> >
> > View Security reports
> > See a list of jobs
> > See a job log
> > Download and browse job artifacts
> > View confidential issues
> > Assign issues
> > Label issues
> > Lock issue threads
> > Manage issue tracker
> > Manage related issues
> > Manage labels
> > Create code snippets
> > See a commit status
> > See a container registry
> > See environments
> > See a list of merge requests
> > View project statistics
> > View Error Tracking list
> >
> > This seems OK to me.
> >
> > gael.
> >
> >
> >     Thanks
> >     Joel
> >
> >
> >     On 12/4/19 9:17 PM, Gael Guennebaud wrote:
> >      >
> >      > The critical steps of the migration are done. I've thus made
> >     public the
> >      > new repo:
> >      >
> >      > https://gitlab.com/libeigen/eigen
> >      >
> >      > I've also re-opened the deprecated mercurial repo on bitbucket so
> >     that
> >      > people can smoothly migrate their clones, links, etc.
> >      >
> >      > Please report any outdated links and mercurial/bitbucket 
> > references
> >      > you'll find. I'm already aware of some pages on our wiki, like:
> >      > -
> >      >
> >     
> > http://eigen.tuxfamily.org/index.php?title=Developer%27s_Corner<http://eigen.tuxfamily.org/index.php?title=Developer%27s_Corner> 
> >
> >      > - http://eigen.tuxfamily.org/index.php?title=Mercurial
> >      >
> >      > Any help on updating those old documentations will be greatly
> >     appreciated!
> >      >
> >      > Gael
> >      >
> >      > On Wed, Dec 4, 2019 at 9:04 AM Gael Guennebaud
> >      > <gael.guennebaud@xxxxxxxxx <mailto:gael.guennebaud@xxxxxxxxx>
> >     <mailto:gael.guennebaud@xxxxxxxxx
> >     <mailto:gael.guennebaud@xxxxxxxxx>>> wrote:
> >      >
> >      >     Hi,
> >      >
> >      >     as planed we'll start the migration to GitLab today. This
> >     means that
> >      >     the Eigen's bitbucket project (repository+pull-requests) 
> > won't be
> >      >     accessible within a few minutes. Same for our bugzilla that
> >     will be
> >      >     turned as read-only.
> >      >
> >      >     Wish me good luck and see you soon for announcing the
> >     availability
> >      >     of the new git repository!
> >      >
> >      >     Cheers,
> >      >     Gael
> >      >

--
 Dr.-Ing. Christoph Hertzberg

 Besuchsadresse der Nebengeschäftsstelle:
 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 5
 28359 Bremen, Germany

 Postadresse der Hauptgeschäftsstelle Standort Bremen:
 DFKI GmbH
 Robotics Innovation Center
 Robert-Hooke-Straße 1
 28359 Bremen, Germany

 Tel.:     +49 421 178 45-4021
 Zentrale: +49 421 178 45-0
 E-Mail:   christoph.hertzberg@xxxxxxx

 Weitere Informationen: http://www.dfki.de/robotik
  -------------------------------------------------------------
  Deutsches Forschungszentrum für Künstliche Intelligenz GmbH
  Trippstadter Straße 122, D-67663 Kaiserslautern, Germany

  Geschäftsführung:
  Prof. Dr. Antonio Krüger (Vorsitzender)
  Dr. Walter Olthoff

  Vorsitzender des Aufsichtsrats:
  Dr. Gabriël Clemens
  Amtsgericht Kaiserslautern, HRB 2313
  -------------------------------------------------------------