Git Migration Needs YOU!

[Aaron J. Seigo]

On March 1, 2010, Cornelius Schumacher wrote:
> On Monday 01 March 2010 Aaron J. Seigo wrote:
> > playground should be left up to the people working on things in there.
> 
> So how does a project in playground become part of the git migration?

imho: do it yourself. there's a lot of dead code in playground and even more 
uninteresting bits of history in there. 

it's tempting to say that git relieves a lot of the need for a playground like 
module since it's easy to create new modules on the fly.

in the case of plasma:

* we have one app that we want to eventually be part of extragear (plasmate), 
so that's not a big deal as it could become its own module right away.

* some of the items in there would have been better off in a feature branch

* the rest of the items are plugins with no definite destination: they could 
end up in kdebase or kdeplasma-addons or even in a future extragear module; 
being able to have a place to develop these plugins without worrying where 
they will eventually end up is really very useful. so having a way to move 
code from one git module to another, which i understand is non-trivial right 
now?, would also be very useful to have.

again, this is something the git gurus amongst us really should be working on 
solutions for and documenting on techbase.

> > kdereview needs to be addressed ASAP since it's part of our workflow.
> > 
> > git gurus: how can we best approximate such a staging area with git?
> 
> Do we need to move code for this at all? Wouldn't it be enough to have a
> list somewhere (e.g. on the community Wiki) with those projects who are
> under review?

as long as they are announced here, i'd imagine that could work. it's a bit 
nicer to have this managed directly in the scm, though.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks