Re: [GitLab] IMPORTANT: Mass migration plan

On Wed, Mar 21, 2018 at 6:50 AM Carlos Soriano <csoriano gnome org> wrote:
It could be that's a solution, could someone check?

For context, my plan is to modify the migration tool as soon as possible to not require admin access for running it (but admin access will still be required for the actual migration) so everyone can help me with the whole thing by testing their own modules and reporting issues.

On 21 March 2018 at 09:27, Germán Poo-Caamaño <gpoo gnome org> wrote:
On Wed, 2018-03-21 at 08:53 -0400, Carlos Soriano wrote:
> > I really don’t think it is a big deal, especially if this is
> publicly
> announced
> It's not about if admins have powers or not, is about the fact of
> impersonating a user in comments. It's true that publicly announcing
> could
> be enough.

AFAIU, it is only data migration, you are not doing anything extra that
was not in the user's intention.

> However the other big issue is that notifications would be send
> massively, and I don't know how to prevent that. So that's basically
> a no-no from the start. Maybe some trick can be done, but no idea.

Cannot you disable the email notifications during the migration?

I mean, when you create a project, set the notification to 'disabled',
and enable them after the migration finishes.

The reason wasn't fixed yet is because of a bug in GitLab. We already determined from an informal poll that people weren't bothered by the impersonation.

You can either set the user account, or the creation time, but not both, and I found the creation time to be more important. If anyone wants to either fix this upstream or advocate for it, feel free. It would be trivial to make the change in the migration tool, but it depends on how the bug is resolved in GitLab.

Philip C

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]