jvelo/Plover — comment on commit ee4f4cb1270a007622136f667518441278901f40
File: pom.xml line 9
By jvelo:

Hmm I don't recall we've voted on enforcing this rule. If read on contrib.xwiki.org :

> The project hosting forge can provide contributors with **some or all** of the following tools".

So AFAIU it's ok for a contrib project to have its own SCM. Plus, with github, it makes it easy to fork the project inside xwiki-contrib (though apparently I cannot do it myself since I already forked it in my own repos - a github UI bug I believe)
My preference for the SCM went for the winesquare organization right now since this is where it originates from and it gives it some visibility too.
The tool I'm keen on benefiting from contrib is the CI/maven repos, but indeed that needs a org.xwiki.contrib group Id.