Re: OpenDaylight TSC] project names
toggle quoted message Show quoted text
The lead administrator for the OpenDaylight tools is Andrew Grimberg (cc-ed).
In short, I would suggest making this a forward looking policy as opposed to an immediate implementation.
I.e. keep the existing names for the code that is already in the repo with a plan of giving the result of our combining/merging/picking a single core-controller code base a new and conforming name. Andy can perform that name change as per his comments below. For new code contribution proposals it would be best to pick a name that can persist through the project's life within OpenDaylight. We should endeavor to make project names changes the exception as opposed to the rule.
EEK!!! just saying.
I have an "easy" means of doing the name changes.
1) Project names (and descriptions!) are allocated by the TSC
2) Pending changes for projects are completed / merged and no new
commits are accepted for some amount of freeze time
3) I generate the new code repositories (and associated service silos
during the freeze)
4) The current repository is taken out of service (hard freeze, no more
5) I take a full clone of repository and do a forced import of the
entire commit history into the new repository
This is going to completely kill Gerrit history though and the only
surviving history is the commits themselves in the the git repository.
There's also fallout to Bugzilla bugs as they are going to be referring
to things that may or not exist anymore ;)
This is a lot of work of course. The alternative is that I do some weird
git rename bingo and somehow (I don't know how) get all the internal
Gerrit information in sync too. I'm far less sure I can pull this off
than the above steps.
On Fri, May 3, 2013 at 1:16 PM, David Meyer <dmm@...> wrote:
Director - Networking Solutions
The Linux Foundation