That could work. So when we push a branch to the new repo, are we going to delete the files we don't need out of there? This will also leave the history of the other files as well I presume.
-Mark -----Original Message----- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, September 02, 2014 3:17 PM To: dev@flex.apache.org Subject: Re: How to manage flex-utilities git repo Infra responded rather quickly to the flex-radii8 request. It would be already created but I didn't tell them if it was supposed to be a bare repo or an import of another repo. So, I think we should break up flex-utilities. At the top-level is: ApacheFXG FlexPMD Squiggly Common installerLocaleEditor CodeCoverage MD5Checker TourDeFlex Installer maven-flex-plugin FXGTools MobileTrader ant_on_air installerBadge Mavenizer I would argue that we should leave the following in flex-utilities. I guess it sort of means that flex-utilities is for code that we don't have release plans for, but help us do other things like modify FXG files, or check MD5s. If we end up wanting to release something in flex-utilities, hopefully we can later move it to its own repo without losing history. ApacheFXG FXGTools MD5Checker MobileTrader CodeCoverage Then we should create more repos as follows: flex-installer.git: ant_on_air Common Installer installerBadge installerLocaleEditor flex-maven.git: Maven-flex-plugin Mavenizer flex-squiggly.git Squiggly flex-pmd.git FlexPMD flex-tdf.git TourDeFlex Thoughts? -Alex On 9/2/14 9:26 AM, "Kessler CTR Mark J" <mark.kessler....@usmc.mil> wrote: >Well that is probably the ideal method to have each repo for each >utility. I believe you can push a branch to a new repository. We could >test this out on a github throw away repo. But if not, I still like the >branch separation as a second best. > > >-Mark > >-----Original Message----- >From: Alex Harui [mailto:aha...@adobe.com] >Sent: Tuesday, September 02, 2014 11:57 AM >To: dev@flex.apache.org >Subject: Re: How to manage flex-utilities git repo > > > >On 9/2/14 5:31 AM, "Kessler CTR Mark J" <mark.kessler....@usmc.mil> wrote: > >>+1 >> >>I like the idea. I can see Justin's concerns too. Is there a way to >>have multiple github repos one with each of the dev-subprojects ? >I've asked for a new repo for radii8. We'll see how quick it is to get >one. If you look at the total set of ASF git repos it is clear that a few >other projects like Cordova and CouchDB have many more repos than we do, >so maybe the best answer is to split out flex-utilities into separate >repos. Not sure how to move stuff to another repo with history. > >-Alex >
