Amazing job Philip, those examples look really good with the review of the patches included.Agree with Emmanuelle, seems Alberto won't have much time for the time being so let's move it to our instance if Alberto agrees. You can create a repo on your own namespace with those changes and I will move it to /GNOME.
Best
--
Carlos Soriano
GNOME Foundation
Treasurer, Board of DirectorsOn Mon, Nov 13, 2017 at 1:43 PM, Emmanuele Bassi <ebassi gmail com> wrote:Thanks, Philip: this is much appreciated.
Since Alberto won't likely have time to work on this for a while, and
since this code should live in GNOME's own GitLab instance, how about
we create a new repository there?
Ciao,
Emmanuele.
> ______________________________
On 13 November 2017 at 00:14, <philip chimento gmail com> wrote:
> Hi,
>
> I've spent the weekend hacking on Alberto's Bugzilla-to-GitLab migration
> script and I've made some nice improvements in the readability/friendliness
> of the automatically generated issues, in my opinion. With everything in
> this merge request [1] I've got it in a state where I'm happy to start
> migrating issues for GJS from Bugzilla to GitLab.
>
> I also have a couple of GJS-specific changes which are here [2] in case
> anyone else is interested in copying them.
>
> One thing I'd like to check before I do that is whether it would be possible
> to do the migration logged in as a "bugzilla-migration" user on GitLab, for
> which I've opened an issue [3]. It would be a nice bonus to not have myself
> auto-subscribed to every issue that is migrated :-) It seems like it should
> be possible for a GitLab admin to create this account and, for example, give
> out a time-limited access token to a maintainer who wanted to run the
> migration script.
>
> If the bugzilla-migration user had admin permissions, it looks like the
> script could even post comments as the user who originally made the comment
> on Bugzilla, if that GitLab user exists. (On the other hand, it seems risky
> to hand out access tokens, even time-limited ones, to an admin account.)
>
> Any GitLab gurus have thoughts on this?
>
> Here are some examples of what the tool's output now looks like, on the
> GitLab test instance:
> - https://gitlab-test.gnome.org/ptomato/gjs-test/issues/75
> - https://gitlab-test.gnome.org/ptomato/gjs-test/issues/77
> - https://gitlab-test.gnome.org/ptomato/gjs-test/issues/70
> The full list is here [4].
>
> Regards,
> Philip C
>
> [1] https://gitlab.com/aruiz/gitlab-gnome-tools/merge_requests/9
> [2] https://gitlab.com/ptomato/gitlab-gnome-tools/compare/master ...gjs
> [3] https://gitlab.com/aruiz/gitlab-gnome-tools/issues/20
> [4] https://gitlab-test.gnome.org/ptomato/gjs-test/issues?state= opened
>
>
_________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> https://mail.gnome.org/mailman/listinfo/desktop-devel-list
--
https://www.bassi.io
[@] ebassi [@gmail.com]
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
https://mail.gnome.org/mailman/listinfo/desktop- devel-list