Mickael, I believe you do not understand me.
I'm not questioning if we move to github etc.
I'm missing trivial plan / workflow / guidelines related to the changed way to contribute.
Shouldn't be there some? or we just let the things "flow" and see if that will be enough, because we are "standing on the giant's shoulders"?
Here is the very first example where a policy should exist IMHO, it was the first thing I've stumbled upon looking on a new repo in git:
Surely we don't want that our git history contains some vendor specific "committers"?
And there will be lot of similar guidelines / policies to define.
E.g. should anyone "fork" and create PR's from own fork or "clone" the main repo and create PR's from branches to master using main repo clone?
Both is possible, but shouldn't there be a guideline?
Спасение утопающих - дело рук самих утопающих
Gesendet: Mittwoch, 09. Februar 2022 um 17:45 Uhr
Von: "Mickael Istria" <mistria@xxxxxxxxxx>
Betreff: Re: [eclipse-pmc] Merge strategy for projects moved to Github
OK, so we will not define any policies / guidelines etc?
Nothing regarding signing / ECA / IP checks / quiet period / API checks / branch management / bug linking whatever else?
Changing where the repository is hosted and how people submit contribution don't change anything to project policies.
Most tools that are existing with Gerrit will be ported to GitHub, as it has been documented and discussed in Mid-October in the thread "[eclipse-dev] RFC: Eclipse TLP migration to Github". Contributions towards that are welcome, as you see some updates require to update all Eclipse projects repositories. The more this effort is shared, the shorter the annoyance will last.
_______________________________________________ eclipse-pmc mailing list eclipse-pmc@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-pmc