On 28/08/2020 18:26, Greg Rundlett (freephile) wrote:
I like the idea of streamlining deprecation and
avoiding the cost of
maintaining obsolete code. I also **want** to publish my code on Gerrit.
As a 3rd-party extension developer who doesn't write a lot of code, one of
the biggest complaints that I have is that it's "hard" to publish your
work
in Gerrit (and benefit from the visibility of being in the MediaWiki
ecosystem). It's very easy to create a new repo at GitHub. It would be
wonderful if there was some facility to "import" GitHub repos into Gerrit.
<snip>
Hello,
Indeed repository creation is restricted to a handful of people since
the repositories are shared among every users, unlike Github in which
you have your own user/org namespace in which you can create any
repositories as you want.
A request for a new repository can be made on the wiki page:
https://www.mediawiki.org/wiki/Gerrit/New_repositories/Requests
And it can be asked to import an existing Github repository, which is
merely about:
git clone --mirror <github url>
git push --mirror <gerrit url>
https://www.mediawiki.org/wiki/Git/Creating_new_repositories#Importing_from…
From there eventually you will get the benefit of our
homegrown CI
system and routine maintenance by various bots (localization updates,
deprecation cleanup, libraries updates, latest code styling etc).
The Gerrit and Github models are not that different. While in the github
model one does:
1) fork repository
2) push to a user branch
3) request pull request
4) amend OR add commits and push until change is merged
In Gerrit that is:
1) clone repository
2) push to the special refs/for/<target branch>
3) **amend** and push until change is merged
I am eluding the maintenance of a serie of commits which is arguably
easier in the Github model since each pull request is for a whole branch.
There are some basics at:
https://www.mediawiki.org/wiki/Gerrit/Tutorial/tl;dr
Still, yes the repository creation is a bit annoying and maybe that can
be toolized.
--
Antoine "hashar" Musso