I agree. It is probably easier to first move to git and then archive the unmaintained projects. For the project we want to delete I propose we create a branch "attic" or similar where we keep them and then delete them from master.
For the two subprojects to extract I do not know which is the best way. We could clone the full repo and then delete all that is not part of the subproject but I do not know if this is very efficient. What do you propsose there ? Christian Am Fr., 1. Feb. 2019 um 16:21 Uhr schrieb Jean-Baptiste Onofré < j...@nanthrax.net>: > Hi > > +1 > > I think we can move all to git and then split the repository (in two > steps). > > For the project already "isolated", no problem, it's already done ;) > > Regards > JB > > On 01/02/2019 15:50, Christian Schneider wrote: > > We discussed a while ago to move to git and actually have moved quite a > few > > of the sub projects. > > > > There are some more projects we could move to individual repos as they > are > > typcially released by subproject: > > - component-dsl > > - cdi > > > > So for these I propose we also create individual git repos. > > > > Apart from that the remaining projects are too diverse to release by > > subproject. Still I think moving to git might make sense there. > > So I wonder if we could simply move the rest of the aries repo to git and > > live with the small disadvantage that a tag always also tags unrelated > > files. > > > > Christian > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
