Yes Erik, that's the point. They can control incomings from GIT and bypass to SVN.
2012/8/17 Erik de Bruin <e...@ixsoftware.nl> > Jose, > > Am I correct when I say that a PPMC member in this scenario has a > working copy that is controlled BOTH by git AND svn? So he can pull > changes using git and then commit them using svn? > > EdB > > > > On Fri, Aug 17, 2012 at 12:17 PM, Jose Barragan > <jose.barra...@codeoscopic.com> wrote: > > Hi Erik, > > > > The PPMC team will be able to use Git to analyze and to compare against > of apache RO repository, for this, the working-copy must furthermore agree > with “trunk” SVN and with the branch “develop” of its Git equivalent. That > way they are possible freely to be used the Git branches on my unique > version SVN, and then, commits all approved work to official repository in > SVN, just for now, until apache allows writing in Git. > > > > The goal must be, to engage to the members of the community to > collaborate with us, without too many problems or ties. > > > > And to accelerate the resolution of the present disadvantages of writing > in Apache Git repositories, even if the INFRA team, only grant writing > access to a reduced group of PPMC team, or whatever... > > > > > > > > On Aug 17, 2012, at 11:31 AM, Erik de Bruin <e...@ixsoftware.nl> wrote: > > > >> Carlos, > >> > >> I did read the thread before posting, but clearly I didn't understand > >> all that was said. I got through the first posts stating 'read-only -> > >> do patches in Jira', but got confused later on, apparently. > >> > >> The people used to the Git model should show a little patience towards > >> us 'old-school' SVN folks, please. Git takes some getting used to when > >> you come from SVN, as some of the terminology used is the same, some > >> is new, and, confusingly, SOME IS THE SAME, BUT MEANS SOMETHING > >> DIFFERENT. I'm sure we're all trying to get our heads around the new > >> way of working and the new tooling involved. > >> > >> Also, as long as there is no full support for Git, do we try to > >> 'force' Git, or do we continue in SVN. Doing both at the same time > >> seems confusing and means a lot of extra work for the committers, as > >> they have to operate both systems... > >> > >> EdB > >> > >> > >> > >> On Fri, Aug 17, 2012 at 11:11 AM, Carlos Rovira > >> <carlos.rov...@codeoscopic.com> wrote: > >>> Hi Erik, > >>> > >>> yes, please read the response from Jose Barragán in this thread (the > third > >>> one) > >>> > >>> "The PPMC team members can checkout an entire remote branch of > comunity > >>> members from github, and having reviewed and accepted all work, > push > >>> the > >>> new branch against the official apache repository." > >>> > >>> We was talking about use the apache flex mirror in github [1]. Since > PPMC > >>> controls apache flex mirror in github the can approve/disapprove all > pull > >>> request from contributors. > >>> > >>> Contributors has full commodity of development and they only need to > work > >>> for patches and propose via pull request. If the work is valid, PPMC > can > >>> commit the patch to the official repository > >>> > >>> This allows as to implement GBM asap while other people are > voluntering to > >>> bring official git support to apache and apache flex. > >>> > >>> [1] https://github.com/apache/flex > >>> > >>> > >>> > >>> 2012/8/17 Erik de Bruin <e...@ixsoftware.nl> > >>> > >>>> Hi, > >>>> > >>>> According to "http://git.apache.org/"; the Apache Git mirrors are > >>>> 'read-only'. To me that means that you can clone them at will, but > >>>> that in order to get the changes you made to your branch into the code > >>>> base, you need to create a patch from Git and apply that to the SVN > >>>> repository... Am I missing something? > >>>> > >>>> EdB > >>>> > >>>> > >>>> > >>>> On Fri, Aug 17, 2012 at 10:50 AM, Carlos Rovira > >>>> <carlos.rov...@codeoscopic.com> wrote: > >>>>> Hi Justin, > >>>>> > >>>>> since I made a pull request from github I thought attach a patch was > not > >>>>> needed. > >>>>> > >>>>> I just made one and attached to the ticket. > >>>>> > >>>>> This will be need always with new model? these seems totaly > unnecesary > >>>> with > >>>>> the mechanishm of pull request...you have all the tools to evaluate, > >>>> isn't > >>>>> it? I think the main point here is see the most efficient way to get > >>>>> contributions and for this to happen, the process should have few > steps. > >>>>> > >>>>> Thanks > >>>>> > >>>>> Carlos Rovira > >>>>> > >>>>> > >>>>> 2012/8/17 Justin Mclean <jus...@classsoftware.com> > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>>> I open a JIRA ticket and made the pull request from my forked > >>>> repository > >>>>>> in > >>>>>>> github to apache flex github repository. > >>>>>> > >>>>>> Perhaps I'm missing something but there no patch in JIRA that I can > see. > >>>>>> > >>>>>> Thanks, > >>>>>> Justin > >>>>>> > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Carlos Rovira > >>>>> Director de Tecnología > >>>>> M: +34 607 22 60 05 > >>>>> F: +34 912 35 57 77 > >>>>> <http://www.codeoscopic.com> > >>>>> CODEOSCOPIC S.A. <http://www.codeoscopic.com> > >>>>> Avd. del General Perón, 32 > >>>>> Planta 10, Puertas P-Q > >>>>> 28020 Madrid > >>>> > >>>> > >>>> > >>>> -- > >>>> Ix Multimedia Software > >>>> > >>>> Jan Luykenstraat 27 > >>>> 3521 VB Utrecht > >>>> > >>>> T. 06-51952295 > >>>> I. www.ixsoftware.nl > >>>> > >>> > >>> > >>> > >>> -- > >>> Carlos Rovira > >>> Director de Tecnología > >>> M: +34 607 22 60 05 > >>> F: +34 912 35 57 77 > >>> <http://www.codeoscopic.com> > >>> CODEOSCOPIC S.A. <http://www.codeoscopic.com> > >>> Avd. del General Perón, 32 > >>> Planta 10, Puertas P-Q > >>> 28020 Madrid > >> > >> > >> > >> -- > >> Ix Multimedia Software > >> > >> Jan Luykenstraat 27 > >> 3521 VB Utrecht > >> > >> T. 06-51952295 > >> I. www.ixsoftware.nl > > > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 <http://www.codeoscopic.com> CODEOSCOPIC S.A. <http://www.codeoscopic.com> Avd. del General Perón, 32 Planta 10, Puertas P-Q 28020 Madrid
