+1 I think your plan will be a big improvement for now and allow for further rearrangement if needed.
thanks! David Jencks > On Feb 21, 2020, at 8:27 AM, Karl Pauls <[email protected]> wrote: > > Hi, > > I know i've been dragging my feet with regard to the migration to git. > Unfortunately, I didn't find the time until now. > > I would like to try to make some progress now and there are a couple > of points to consider namely, > > - our website is currently based on svn and we are using the apache > cms which IIUC doesn't translate directly to the gitbox support. > - with the ip clearance done, Tom would like to have a separate repo > for atomos as there are several submodules in atomos already. > > Hence, I would propose the following: > > We create two git repos called felix-dev and felix-atomos and keep the > current svn for the website. > > That would mean, we move all of the current svn/trunk into the new > felix-dev repo and put a Readme in the svn/trunk instead, pointing to > the two new repositories. That way, the website would still work as > is, the trunk would be in git, and we could give atomos a separate > repo. > > Effectively, that would give us 3 repos on github for now namely, > apache/felix (which is just a Readme pointing to the other two repos), > apache/felix-dev, and apache/felix-atomos. If in the future we want to > move out other parts of the trunk into their own repo we could do so > if we think it makes sense. > > I should be able to get that done next week and I'll start with it on > Tuesday unless somebody really is against it (in other words, I'm > calling for lazy consensus). > > The alternatives I see are to either create a separate repo per module > directly or to convert the current svn to just be the felix repo which > would require to rework the website with asf.yml support and not give > Tom a separate repo for atomos. However, in both cases, we would need > some volunteers as I likely don't have enough time. > > regards, > > Karl > > -- > Karl Pauls > [email protected]
