Hello,
I'd like to share a few of my concerns regarding some of the key points of your
proposal:
1. How will the move of OOM repository to git{lab,hub} itself be perceived by
it's ordinary contributors/commiters? Now it's the case for many companies that
form the ONAP community that they care for contributions tracked with LFX
Insights - after move those will be no longer tracked there; also, for many
companies contributing to ONAP repos other than Gerrit, a formal approval to
upload PRs would be required.
Would it supposedly be the case that LF will still handle that formalities
somehow (stats in git{hub,lab} for OOM repo still tracked, code contributions
to those repos handled within LF account)?
Would it be alternatively possible to leave the OOM Gerrit project code as is,
in Gerrit and just mirror it to Git{lab,hub} for CI process convenience?
2. Removing OOM from Gerrit would also affect some ONAP users; e.g. in Samsung
internal CI we use Gerrit specific plugins for OOM code retrieval in CI so
moving to git{hub,lab} won't be a seamless transition. I believe it'd be the
case for others too.
3. Would the OOM repo and CI code after transition be managed by an internal
Orange's account on any of those services or it'll be managed by LF and hence
allow any community member to contribute to CI like it's the case now within
ci-management project?
Regards,
Bartek Grzybowski
Senior DevOps Engineer
Samsung R&D Institute Poland
Samsung Electronics
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7989): https://lists.onap.org/g/onap-tsc/message/7989
Mute This Topic: https://lists.onap.org/mt/84015368/21656
Group Owner: [email protected]
Unsubscribe:
https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
