[oe] Git Migration Status

[Richard Purdie]

Hi,

We've made the decision we want to switch to git so what happens now? We
now have:

* Agreed policies (pending no major objections from openembedded-devel)
* A git server setup
* Web browsing of the git server
* Commit hooks for CIA and email notification of commits

What remains:

* A final mtn -> git conversion
  - There is a known problem with the mtn -> git conversion which needs 
    to be addressed. Holger has the details of this
  - We also need to decide how to map the key names
* Collection of keys for access to the git server
* Creating a BKCVS history import and graft this onto the monotone 
  history
  - There are some conversion defects. Richard has the details and is 
    trying to look into this
  - We also need to decide on key name mappings, preferably consistent 
    with the git ones.
* Rename "gittrial" -> "git" on amethyst

Of these the BKCVS import and be done and also redone at a later date so
I'm not worried about this and it doesn't affect timescales. Renaming
gittrial -> git is pretty much trivial and won't take long. Collection
of keys is also relatively straightforward, we just need someone to
document key generation and collect them. They're basically ssh public
keys and gitosis makes them trivial to add so I can take on collection
role if existing developers with access to monotone want to start
sending me keys (ssh v2 keys please).

This leaves the mtn -> git conversion which isn't trivial. Holger is our
expert in this area and I'd really like to let him have the time needed
to sort this out to his satisfaction. I appreciate he has many time
constraints so this may not happen immediately.

There is also the issue of commit ID naming. I'm tempted to propose we
use commit IDs with a domain such as userid at developers.openembedded.org.
This would allow email redirection should we ever want it without
interfering with the main domain. The alternative is to let people use
their own domains but this means the IDs change when people change email
address and isn't really consistent for the metadata and maintaining a
single identity. I'm really open to opinions on this though. 

Also documenting all users with access on the wiki might be a good idea
(we used to do this but I think the data is stale).

Once we have the mtn -> git conversion working to satisfaction I propose
we give 1 weeks warning before monotone becomes readonly, the conversion
is made and we open up git for read/write. This email serves as notice
that people need to be ready to watch out for that time.

I hope this covers everything but any questions just ask...

Cheers,

Richard