You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Erik de Bruin <er...@ixsoftware.nl> on 2013/03/20 17:05:27 UTC

[Git] repos open?

Hi,

I know they aren't, and I know we can't "pressure" INFRA, but come on.
It's nearly two weeks now, and all projects but the SDK are still on
hold.

This way the move to git is causing the project to lose contributors,
instead of gaining them, as the proponents promised.

Is there anything (but be patient, which isn't working) that I (we)
can do to make this happen anytime soon?

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [Git] repos open?

Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi,

As I said before: "That's ok for me, I see no points for not going forward 
:)"

-Fred

-----Message d'origine----- 
From: Om
Sent: Wednesday, March 20, 2013 5:12 PM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

On Mar 20, 2013 9:06 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> Hi,
>
> I know they aren't, and I know we can't "pressure" INFRA, but come on.
> It's nearly two weeks now, and all projects but the SDK are still on
> hold.

What are we waiting file INFRA to do?  It is up to us to ask them to open
up the repos for read write.

>
> This way the move to git is causing the project to lose contributors,
> instead of gaining them, as the proponents promised.
>
> Is there anything (but be patient, which isn't working) that I (we)
> can do to make this happen anytime soon?
>
> EdB

I have asked a bunch of times already.  Can we move on and open up the
repos.  If anyone has objections, this is the time to speak up.

Again, we are the ones delaying things, not Infra.

Thanks,
Om

>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl 


Re: [Git] repos open?

Posted by Om <bi...@gmail.com>.
FYI, I have asked Infra to open up Falcon and ASJS.  I will send out an
update when it is done.

Thanks,
Om

On Wed, Mar 20, 2013 at 3:51 PM, Om <bi...@gmail.com> wrote:

> On Wed, Mar 20, 2013 at 2:49 PM, Justin Mclean <ju...@classsoftware.com>wrote:
>
>> HI,
>>
>> > If you read that thread in its entirety, Justin had some serious
>> objections
>> > to moving forward.
>> I still have some objections and noone has stepped forward to help with
>> the documentation, but at this point I'd say we'll just have to work with
>> it the best we can. It would of been better if these issues were thought
>> about before the move (or even when the original vote was called).
>>
>> Currently we have:
>> - Broken release build
>> - Unclear process for committers and users
>> - Jenkins is broken (well more than it usually is)
>> - Github mirrors broken
>>
>> Justin
>
>
>
> It does look like no one else has objections. And indeed, we have to do
> work with what we have now.
>
> I will ask Infra to open Falcon and ASJS repos in a while.  I suggest you
> continue discussing the issues you raised in a different thread.
>
> Thanks,
> Om
>

Re: [Git] repos open?

Posted by Om <bi...@gmail.com>.
On Wed, Mar 20, 2013 at 2:49 PM, Justin Mclean <ju...@classsoftware.com>wrote:

> HI,
>
> > If you read that thread in its entirety, Justin had some serious
> objections
> > to moving forward.
> I still have some objections and noone has stepped forward to help with
> the documentation, but at this point I'd say we'll just have to work with
> it the best we can. It would of been better if these issues were thought
> about before the move (or even when the original vote was called).
>
> Currently we have:
> - Broken release build
> - Unclear process for committers and users
> - Jenkins is broken (well more than it usually is)
> - Github mirrors broken
>
> Justin



It does look like no one else has objections. And indeed, we have to do
work with what we have now.

I will ask Infra to open Falcon and ASJS repos in a while.  I suggest you
continue discussing the issues you raised in a different thread.

Thanks,
Om

Re: [Git] repos open?

Posted by Justin Mclean <ju...@classsoftware.com>.
HI,

> If you read that thread in its entirety, Justin had some serious objections
> to moving forward.
I still have some objections and noone has stepped forward to help with the documentation, but at this point I'd say we'll just have to work with it the best we can. It would of been better if these issues were thought about before the move (or even when the original vote was called).

Currently we have:
- Broken release build
- Unclear process for committers and users
- Jenkins is broken (well more than it usually is)
- Github mirrors broken

Justin

Re: [Git] repos open?

Posted by Alex Harui <ah...@adobe.com>.



> No, 3.1 is not dependent on 3.3.  Sparse checkout lets you use the
> whiteboard git repo as it is today.  No changes required.
> 
Ah, sorry, didn't notice that 3.3 said GitHub and not just Git.

OK, then I am voting for 3.1.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Re: [Git] repos open?

Posted by Om <bi...@gmail.com>.
On Wed, Mar 20, 2013 at 1:25 PM, Alex Harui <ah...@adobe.com> wrote:

>
>
>
> On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
>
> > Here is my proposal in the meantime:
> >
> > 1.  We open up Falcon and ASJS repos first since there are no issues with
> > that
> +1.  Peter and I probably have merge conflicts in ASJS which would be a
> good
> testing ground since there isn't critical history in there.
> > 2.  I have pinged Infra about the missing history in Utilities.  Let them
> > come back to us with a definitive answer.
> +0.  That's fine, but to me, it isn't worth the wait.  Let's open it up
> too.
> > 3.  We need to figure out what to do about the whiteboard.  The current
> > proposals to fix this problem are:
> >
> >    1. Use the sparse checkout option as described here (
> >    http://markmail.org/message/dg7hplezkzwiroes)
> >    2. Create a branch per user in the whiteboard
> >    3. Move to github for whiteboards
> >    4. Let whiteboards remain in SVN
> >
> I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't horribly slow
> for Fred the second time he tried it.  The 240MB in there isn't the biggest
> download I've seen.  I think FB was larger.
>
>
No, 3.1 is not dependent on 3.3.  Sparse checkout lets you use the
whiteboard git repo as it is today.  No changes required.

Thanks,
Om

Re: [Git] repos open?

Posted by Frédéric THOMAS <we...@hotmail.com>.
> IIRC, it wasn't horribly slow for Fred the second time he tried it

It was the 1rst times where it took that time, 12 hours later or so, it was 
ok, less than 15mn.

So, 3.1 -> +1

-Fred

-----Message d'origine----- 
From: Alex Harui
Sent: Wednesday, March 20, 2013 9:25 PM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?




On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:

> Here is my proposal in the meantime:
>
> 1.  We open up Falcon and ASJS repos first since there are no issues with
> that
+1.  Peter and I probably have merge conflicts in ASJS which would be a good
testing ground since there isn't critical history in there.
> 2.  I have pinged Infra about the missing history in Utilities.  Let them
> come back to us with a definitive answer.
+0.  That's fine, but to me, it isn't worth the wait.  Let's open it up too.
> 3.  We need to figure out what to do about the whiteboard.  The current
> proposals to fix this problem are:
>
>    1. Use the sparse checkout option as described here (
>    http://markmail.org/message/dg7hplezkzwiroes)
>    2. Create a branch per user in the whiteboard
>    3. Move to github for whiteboards
>    4. Let whiteboards remain in SVN
>
I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't horribly slow
for Fred the second time he tried it.  The 240MB in there isn't the biggest
download I've seen.  I think FB was larger.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


RE: [Git] repos open?

Posted by Gordon Smith <go...@adobe.com>.
3.2 seems quite different from 3.5. 3.2 refers to "the whiteboard", implying to me that there is a repo just for whiteboards. In 3.5 there would be no such repo.

I'm not going to vote on whiteboards, because I don't have a strong opinion on how they should be done. And therefore I'm not going to start a new poll on them. I was just trying to understand the various options.

- Gordon

-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
Sent: Thursday, March 21, 2013 11:36 AM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

On Thu, Mar 21, 2013 at 11:22 AM, Gordon Smith <go...@adobe.com> wrote:

> >
> https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spa
> ces-for-branches
> ?
>
> So are we adding a voting option 3.5?
>
> - Gordon
>
>
Please feel free to add this option and send out a new poll.  In that case, you should remove 3.2, since this would cover that as well.

Thanks,
Om


>
> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> Sent: Wednesday, March 20, 2013 8:46 PM
> To: dev@flex.apache.org
> Subject: Re: [Git] repos open?
>
> On Wed, Mar 20, 2013 at 5:02 PM, Gordon Smith <go...@adobe.com> wrote:
>
> > Why can't each developer's whiteboard for flex-sdk be a branch in 
> > the flex-sdk repo? Is there some reason why dozens of branches are bad?
> >
> >
> I believe this is what you mean:
>
> https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spa
> ces-for-branches
> ?
> If we want to do this, we can ask Infra to help support this.
>
>
> > If there is a single whiteboard repo, is it for flex-sdk, 
> > flex-falcon, or what?
> >
> >
> If we go with the branch per user for each repo, we would have more 
> clarity.  But that is not how the whiteboard in SVN was used.
>
>
> > - Gordon
> >
> >
>
> Thanks,
> Om
>
>
> > -----Original Message-----
> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> > Sent: Wednesday, March 20, 2013 2:04 PM
> > To: dev@flex.apache.org
> > Subject: Re: [Git] repos open?
> >
> > I am sorry, it is a bit confusing which 1 you are voting for.  My 
> > bad for re-using numbers in a nested way.  Can you be specific and 
> > vote for 3.1, etc. if you mean the options under 3?
> >
> > Thanks,
> > Om
> >
> > On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:
> >
> > > +1 for #1. Be good to figure out merge/conflict early in the game.
> > >
> > > Peter Ent
> > > Flex SDK Team
> > > Adobe Systems
> > >
> > > On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
> > >
> > > >
> > > >
> > > >
> > > >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> > > >
> > > >> Here is my proposal in the meantime:
> > > >>
> > > >> 1.  We open up Falcon and ASJS repos first since there are no 
> > > >>issues with  that
> > > >+1.  Peter and I probably have merge conflicts in ASJS which 
> > > >+would be a
> > > >good
> > > >testing ground since there isn't critical history in there.
> > > >> 2.  I have pinged Infra about the missing history in Utilities.
> > > >>Let them  come back to us with a definitive answer.
> > > >+0.  That's fine, but to me, it isn't worth the wait.  Let's open 
> > > >+it up
> > > >too.
> > > >> 3.  We need to figure out what to do about the whiteboard.  The 
> > > >> current proposals to fix this problem are:
> > > >>
> > > >>    1. Use the sparse checkout option as described here
> > > >>    http://markmail.org/message/dg7hplezkzwiroes)
> > > >>    2. Create a branch per user in the whiteboard
> > > >>    3. Move to github for whiteboards
> > > >>    4. Let whiteboards remain in SVN
> > > >>
> > > >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't 
> > > >horribly slow for Fred the second time he tried it.  The 240MB in 
> > > >there isn't the biggest download I've seen.  I think FB was larger.
> > > >
> > > >--
> > > >Alex Harui
> > > >Flex SDK Team
> > > >Adobe Systems, Inc.
> > > >http://blogs.adobe.com/aharui
> > > >
> > >
> > >
> >
>

Re: [Git] repos open?

Posted by Om <bi...@gmail.com>.
On Thu, Mar 21, 2013 at 11:22 AM, Gordon Smith <go...@adobe.com> wrote:

> >
> https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches
> ?
>
> So are we adding a voting option 3.5?
>
> - Gordon
>
>
Please feel free to add this option and send out a new poll.  In that case,
you should remove 3.2, since this would cover that as well.

Thanks,
Om


>
> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> Sent: Wednesday, March 20, 2013 8:46 PM
> To: dev@flex.apache.org
> Subject: Re: [Git] repos open?
>
> On Wed, Mar 20, 2013 at 5:02 PM, Gordon Smith <go...@adobe.com> wrote:
>
> > Why can't each developer's whiteboard for flex-sdk be a branch in the
> > flex-sdk repo? Is there some reason why dozens of branches are bad?
> >
> >
> I believe this is what you mean:
>
> https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches
> ?
> If we want to do this, we can ask Infra to help support this.
>
>
> > If there is a single whiteboard repo, is it for flex-sdk, flex-falcon,
> > or what?
> >
> >
> If we go with the branch per user for each repo, we would have more
> clarity.  But that is not how the whiteboard in SVN was used.
>
>
> > - Gordon
> >
> >
>
> Thanks,
> Om
>
>
> > -----Original Message-----
> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> > Sent: Wednesday, March 20, 2013 2:04 PM
> > To: dev@flex.apache.org
> > Subject: Re: [Git] repos open?
> >
> > I am sorry, it is a bit confusing which 1 you are voting for.  My bad
> > for re-using numbers in a nested way.  Can you be specific and vote
> > for 3.1, etc. if you mean the options under 3?
> >
> > Thanks,
> > Om
> >
> > On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:
> >
> > > +1 for #1. Be good to figure out merge/conflict early in the game.
> > >
> > > Peter Ent
> > > Flex SDK Team
> > > Adobe Systems
> > >
> > > On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
> > >
> > > >
> > > >
> > > >
> > > >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> > > >
> > > >> Here is my proposal in the meantime:
> > > >>
> > > >> 1.  We open up Falcon and ASJS repos first since there are no
> > > >>issues with  that
> > > >+1.  Peter and I probably have merge conflicts in ASJS which would
> > > >+be a
> > > >good
> > > >testing ground since there isn't critical history in there.
> > > >> 2.  I have pinged Infra about the missing history in Utilities.
> > > >>Let them  come back to us with a definitive answer.
> > > >+0.  That's fine, but to me, it isn't worth the wait.  Let's open
> > > >+it up
> > > >too.
> > > >> 3.  We need to figure out what to do about the whiteboard.  The
> > > >> current proposals to fix this problem are:
> > > >>
> > > >>    1. Use the sparse checkout option as described here
> > > >>    http://markmail.org/message/dg7hplezkzwiroes)
> > > >>    2. Create a branch per user in the whiteboard
> > > >>    3. Move to github for whiteboards
> > > >>    4. Let whiteboards remain in SVN
> > > >>
> > > >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't
> > > >horribly slow for Fred the second time he tried it.  The 240MB in
> > > >there isn't the biggest download I've seen.  I think FB was larger.
> > > >
> > > >--
> > > >Alex Harui
> > > >Flex SDK Team
> > > >Adobe Systems, Inc.
> > > >http://blogs.adobe.com/aharui
> > > >
> > >
> > >
> >
>

Re: [Git] repos open?

Posted by Frédéric THOMAS <we...@hotmail.com>.
Om,

Btw, I remove my vote of 3.1 and give my +1 to the 3.4 (stay on svn), that's 
a lazy vote, I can change my mind ?

-Fred

-----Message d'origine----- 
From: Frédéric THOMAS
Sent: Thursday, March 21, 2013 9:15 PM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

A branch should belong to a project (a directory structure) and not shared
by force (it can be a local branch only), the point is that, even with what
INFRA is proposing us, as soon as we will want to do a branch, we'll have to
incorporate every whiteboard inside of it because there's only one master
for everybody, so, that's not good, create a branch per user in the
whiteboard is almost the same problematic, instead of being horizontal
problem (shared file structure), it is a vertical one (shared branches),
moving to github, yes, only if there's a repo per committer but I'm not sure
it is the apache way and finally staying on svn allows us to use svn or
git-svn (which takes a lot of time to initialize) for those who want to use
git.

Finally, I guess the 2 last ones are close to what I need and really the
last one let me the possibility to have a repo per project (even if there
are inside the same svn repo) if I go by git-svn.

Thanks,
-Fred

-----Message d'origine----- 
From: Gordon Smith
Sent: Thursday, March 21, 2013 8:18 PM
To: dev@flex.apache.org
Subject: RE: [Git] repos open?

Sorry, I don't follow you. I would think that a feature branch doesn't
belong to a particular person; it's where multiple people are developing a
particular feature.

In any case, don't all the other voting options have some drawback? If there
was an obviously-right option that had no drawbacks, we wouldn't be voting.

- Gordon

-----Original Message-----
From: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Sent: Thursday, March 21, 2013 11:57 AM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

Hi Gordon,

The drawback with those kind of structure is when a user (already a branch)
does a branch, how do you know whom the feature branch belong ?

eg. how do you know which ones are yours ?

FRED-PC /u/gitLab/work/asf/flex/whiteboard (gosmith) $ git branch
  ADD_FEATURE_1
  ADD_FEATURE_2
  aharui
  fthomas
* gosmith

-----Message d'origine-----
From: Gordon Smith
Sent: Thursday, March 21, 2013 7:22 PM
To: dev@flex.apache.org
Subject: RE: [Git] repos open?

> https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?

So are we adding a voting option 3.5?

- Gordon


-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
Sent: Wednesday, March 20, 2013 8:46 PM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

On Wed, Mar 20, 2013 at 5:02 PM, Gordon Smith <go...@adobe.com> wrote:

> Why can't each developer's whiteboard for flex-sdk be a branch in the
> flex-sdk repo? Is there some reason why dozens of branches are bad?
>
>
I believe this is what you mean:
https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?
If we want to do this, we can ask Infra to help support this.


> If there is a single whiteboard repo, is it for flex-sdk, flex-falcon,
> or what?
>
>
If we go with the branch per user for each repo, we would have more clarity.
But that is not how the whiteboard in SVN was used.


> - Gordon
>
>

Thanks,
Om


> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> Sent: Wednesday, March 20, 2013 2:04 PM
> To: dev@flex.apache.org
> Subject: Re: [Git] repos open?
>
> I am sorry, it is a bit confusing which 1 you are voting for.  My bad
> for re-using numbers in a nested way.  Can you be specific and vote
> for 3.1, etc. if you mean the options under 3?
>
> Thanks,
> Om
>
> On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:
>
> > +1 for #1. Be good to figure out merge/conflict early in the game.
> >
> > Peter Ent
> > Flex SDK Team
> > Adobe Systems
> >
> > On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > >
> > >
> > >
> > >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> > >
> > >> Here is my proposal in the meantime:
> > >>
> > >> 1.  We open up Falcon and ASJS repos first since there are no
> > >>issues with  that
> > >+1.  Peter and I probably have merge conflicts in ASJS which would
> > >+be a
> > >good
> > >testing ground since there isn't critical history in there.
> > >> 2.  I have pinged Infra about the missing history in Utilities.
> > >>Let them  come back to us with a definitive answer.
> > >+0.  That's fine, but to me, it isn't worth the wait.  Let's open
> > >+it up
> > >too.
> > >> 3.  We need to figure out what to do about the whiteboard.  The
> > >> current proposals to fix this problem are:
> > >>
> > >>    1. Use the sparse checkout option as described here
> > >>    http://markmail.org/message/dg7hplezkzwiroes)
> > >>    2. Create a branch per user in the whiteboard
> > >>    3. Move to github for whiteboards
> > >>    4. Let whiteboards remain in SVN
> > >>
> > >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't
> > >horribly slow for Fred the second time he tried it.  The 240MB in
> > >there isn't the biggest download I've seen.  I think FB was larger.
> > >
> > >--
> > >Alex Harui
> > >Flex SDK Team
> > >Adobe Systems, Inc.
> > >http://blogs.adobe.com/aharui
> > >
> >
> >
>


Re: [Git] repos open?

Posted by Frédéric THOMAS <we...@hotmail.com>.
A branch should belong to a project (a directory structure) and not shared 
by force (it can be a local branch only), the point is that, even with what 
INFRA is proposing us, as soon as we will want to do a branch, we'll have to 
incorporate every whiteboard inside of it because there's only one master 
for everybody, so, that's not good, create a branch per user in the 
whiteboard is almost the same problematic, instead of being horizontal 
problem (shared file structure), it is a vertical one (shared branches), 
moving to github, yes, only if there's a repo per committer but I'm not sure 
it is the apache way and finally staying on svn allows us to use svn or 
git-svn (which takes a lot of time to initialize) for those who want to use 
git.

Finally, I guess the 2 last ones are close to what I need and really the 
last one let me the possibility to have a repo per project (even if there 
are inside the same svn repo) if I go by git-svn.

Thanks,
-Fred

-----Message d'origine----- 
From: Gordon Smith
Sent: Thursday, March 21, 2013 8:18 PM
To: dev@flex.apache.org
Subject: RE: [Git] repos open?

Sorry, I don't follow you. I would think that a feature branch doesn't 
belong to a particular person; it's where multiple people are developing a 
particular feature.

In any case, don't all the other voting options have some drawback? If there 
was an obviously-right option that had no drawbacks, we wouldn't be voting.

- Gordon

-----Original Message-----
From: Frédéric THOMAS [mailto:webdoublefx@hotmail.com]
Sent: Thursday, March 21, 2013 11:57 AM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

Hi Gordon,

The drawback with those kind of structure is when a user (already a branch) 
does a branch, how do you know whom the feature branch belong ?

eg. how do you know which ones are yours ?

FRED-PC /u/gitLab/work/asf/flex/whiteboard (gosmith) $ git branch
  ADD_FEATURE_1
  ADD_FEATURE_2
  aharui
  fthomas
* gosmith

-----Message d'origine-----
From: Gordon Smith
Sent: Thursday, March 21, 2013 7:22 PM
To: dev@flex.apache.org
Subject: RE: [Git] repos open?

> https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?

So are we adding a voting option 3.5?

- Gordon


-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
Sent: Wednesday, March 20, 2013 8:46 PM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

On Wed, Mar 20, 2013 at 5:02 PM, Gordon Smith <go...@adobe.com> wrote:

> Why can't each developer's whiteboard for flex-sdk be a branch in the
> flex-sdk repo? Is there some reason why dozens of branches are bad?
>
>
I believe this is what you mean:
https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?
If we want to do this, we can ask Infra to help support this.


> If there is a single whiteboard repo, is it for flex-sdk, flex-falcon,
> or what?
>
>
If we go with the branch per user for each repo, we would have more clarity.
But that is not how the whiteboard in SVN was used.


> - Gordon
>
>

Thanks,
Om


> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> Sent: Wednesday, March 20, 2013 2:04 PM
> To: dev@flex.apache.org
> Subject: Re: [Git] repos open?
>
> I am sorry, it is a bit confusing which 1 you are voting for.  My bad
> for re-using numbers in a nested way.  Can you be specific and vote
> for 3.1, etc. if you mean the options under 3?
>
> Thanks,
> Om
>
> On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:
>
> > +1 for #1. Be good to figure out merge/conflict early in the game.
> >
> > Peter Ent
> > Flex SDK Team
> > Adobe Systems
> >
> > On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > >
> > >
> > >
> > >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> > >
> > >> Here is my proposal in the meantime:
> > >>
> > >> 1.  We open up Falcon and ASJS repos first since there are no
> > >>issues with  that
> > >+1.  Peter and I probably have merge conflicts in ASJS which would
> > >+be a
> > >good
> > >testing ground since there isn't critical history in there.
> > >> 2.  I have pinged Infra about the missing history in Utilities.
> > >>Let them  come back to us with a definitive answer.
> > >+0.  That's fine, but to me, it isn't worth the wait.  Let's open
> > >+it up
> > >too.
> > >> 3.  We need to figure out what to do about the whiteboard.  The
> > >> current proposals to fix this problem are:
> > >>
> > >>    1. Use the sparse checkout option as described here
> > >>    http://markmail.org/message/dg7hplezkzwiroes)
> > >>    2. Create a branch per user in the whiteboard
> > >>    3. Move to github for whiteboards
> > >>    4. Let whiteboards remain in SVN
> > >>
> > >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't
> > >horribly slow for Fred the second time he tried it.  The 240MB in
> > >there isn't the biggest download I've seen.  I think FB was larger.
> > >
> > >--
> > >Alex Harui
> > >Flex SDK Team
> > >Adobe Systems, Inc.
> > >http://blogs.adobe.com/aharui
> > >
> >
> >
>


RE: [Git] repos open?

Posted by Gordon Smith <go...@adobe.com>.
Sorry, I don't follow you. I would think that a feature branch doesn't belong to a particular person; it's where multiple people are developing a particular feature.

In any case, don't all the other voting options have some drawback? If there was an obviously-right option that had no drawbacks, we wouldn't be voting.

- Gordon

-----Original Message-----
From: Frédéric THOMAS [mailto:webdoublefx@hotmail.com] 
Sent: Thursday, March 21, 2013 11:57 AM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

Hi Gordon,

The drawback with those kind of structure is when a user (already a branch) does a branch, how do you know whom the feature branch belong ?

eg. how do you know which ones are yours ?

FRED-PC /u/gitLab/work/asf/flex/whiteboard (gosmith) $ git branch
  ADD_FEATURE_1
  ADD_FEATURE_2
  aharui
  fthomas
* gosmith

-----Message d'origine-----
From: Gordon Smith
Sent: Thursday, March 21, 2013 7:22 PM
To: dev@flex.apache.org
Subject: RE: [Git] repos open?

> https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?

So are we adding a voting option 3.5?

- Gordon


-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
Sent: Wednesday, March 20, 2013 8:46 PM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

On Wed, Mar 20, 2013 at 5:02 PM, Gordon Smith <go...@adobe.com> wrote:

> Why can't each developer's whiteboard for flex-sdk be a branch in the 
> flex-sdk repo? Is there some reason why dozens of branches are bad?
>
>
I believe this is what you mean:
https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?
If we want to do this, we can ask Infra to help support this.


> If there is a single whiteboard repo, is it for flex-sdk, flex-falcon, 
> or what?
>
>
If we go with the branch per user for each repo, we would have more clarity. 
But that is not how the whiteboard in SVN was used.


> - Gordon
>
>

Thanks,
Om


> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> Sent: Wednesday, March 20, 2013 2:04 PM
> To: dev@flex.apache.org
> Subject: Re: [Git] repos open?
>
> I am sorry, it is a bit confusing which 1 you are voting for.  My bad 
> for re-using numbers in a nested way.  Can you be specific and vote 
> for 3.1, etc. if you mean the options under 3?
>
> Thanks,
> Om
>
> On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:
>
> > +1 for #1. Be good to figure out merge/conflict early in the game.
> >
> > Peter Ent
> > Flex SDK Team
> > Adobe Systems
> >
> > On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > >
> > >
> > >
> > >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> > >
> > >> Here is my proposal in the meantime:
> > >>
> > >> 1.  We open up Falcon and ASJS repos first since there are no 
> > >>issues with  that
> > >+1.  Peter and I probably have merge conflicts in ASJS which would 
> > >+be a
> > >good
> > >testing ground since there isn't critical history in there.
> > >> 2.  I have pinged Infra about the missing history in Utilities.
> > >>Let them  come back to us with a definitive answer.
> > >+0.  That's fine, but to me, it isn't worth the wait.  Let's open 
> > >+it up
> > >too.
> > >> 3.  We need to figure out what to do about the whiteboard.  The 
> > >> current proposals to fix this problem are:
> > >>
> > >>    1. Use the sparse checkout option as described here
> > >>    http://markmail.org/message/dg7hplezkzwiroes)
> > >>    2. Create a branch per user in the whiteboard
> > >>    3. Move to github for whiteboards
> > >>    4. Let whiteboards remain in SVN
> > >>
> > >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't 
> > >horribly slow for Fred the second time he tried it.  The 240MB in 
> > >there isn't the biggest download I've seen.  I think FB was larger.
> > >
> > >--
> > >Alex Harui
> > >Flex SDK Team
> > >Adobe Systems, Inc.
> > >http://blogs.adobe.com/aharui
> > >
> >
> >
> 


Re: [Git] repos open?

Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Gordon,

The drawback with those kind of structure is when a user (already a branch) 
does a branch, how do you know whom the feature branch belong ?

eg. how do you know which ones are yours ?

FRED-PC /u/gitLab/work/asf/flex/whiteboard (gosmith)
$ git branch
  ADD_FEATURE_1
  ADD_FEATURE_2
  aharui
  fthomas
* gosmith

-----Message d'origine----- 
From: Gordon Smith
Sent: Thursday, March 21, 2013 7:22 PM
To: dev@flex.apache.org
Subject: RE: [Git] repos open?

> https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?

So are we adding a voting option 3.5?

- Gordon


-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
Sent: Wednesday, March 20, 2013 8:46 PM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

On Wed, Mar 20, 2013 at 5:02 PM, Gordon Smith <go...@adobe.com> wrote:

> Why can't each developer's whiteboard for flex-sdk be a branch in the
> flex-sdk repo? Is there some reason why dozens of branches are bad?
>
>
I believe this is what you mean:
https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?
If we want to do this, we can ask Infra to help support this.


> If there is a single whiteboard repo, is it for flex-sdk, flex-falcon,
> or what?
>
>
If we go with the branch per user for each repo, we would have more clarity. 
But that is not how the whiteboard in SVN was used.


> - Gordon
>
>

Thanks,
Om


> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> Sent: Wednesday, March 20, 2013 2:04 PM
> To: dev@flex.apache.org
> Subject: Re: [Git] repos open?
>
> I am sorry, it is a bit confusing which 1 you are voting for.  My bad
> for re-using numbers in a nested way.  Can you be specific and vote
> for 3.1, etc. if you mean the options under 3?
>
> Thanks,
> Om
>
> On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:
>
> > +1 for #1. Be good to figure out merge/conflict early in the game.
> >
> > Peter Ent
> > Flex SDK Team
> > Adobe Systems
> >
> > On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > >
> > >
> > >
> > >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> > >
> > >> Here is my proposal in the meantime:
> > >>
> > >> 1.  We open up Falcon and ASJS repos first since there are no
> > >>issues with  that
> > >+1.  Peter and I probably have merge conflicts in ASJS which would
> > >+be a
> > >good
> > >testing ground since there isn't critical history in there.
> > >> 2.  I have pinged Infra about the missing history in Utilities.
> > >>Let them  come back to us with a definitive answer.
> > >+0.  That's fine, but to me, it isn't worth the wait.  Let's open
> > >+it up
> > >too.
> > >> 3.  We need to figure out what to do about the whiteboard.  The
> > >> current proposals to fix this problem are:
> > >>
> > >>    1. Use the sparse checkout option as described here
> > >>    http://markmail.org/message/dg7hplezkzwiroes)
> > >>    2. Create a branch per user in the whiteboard
> > >>    3. Move to github for whiteboards
> > >>    4. Let whiteboards remain in SVN
> > >>
> > >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't
> > >horribly slow for Fred the second time he tried it.  The 240MB in
> > >there isn't the biggest download I've seen.  I think FB was larger.
> > >
> > >--
> > >Alex Harui
> > >Flex SDK Team
> > >Adobe Systems, Inc.
> > >http://blogs.adobe.com/aharui
> > >
> >
> >
> 


RE: [Git] repos open?

Posted by Gordon Smith <go...@adobe.com>.
> https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?

So are we adding a voting option 3.5?

- Gordon


-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
Sent: Wednesday, March 20, 2013 8:46 PM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

On Wed, Mar 20, 2013 at 5:02 PM, Gordon Smith <go...@adobe.com> wrote:

> Why can't each developer's whiteboard for flex-sdk be a branch in the 
> flex-sdk repo? Is there some reason why dozens of branches are bad?
>
>
I believe this is what you mean:
https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?
If we want to do this, we can ask Infra to help support this.


> If there is a single whiteboard repo, is it for flex-sdk, flex-falcon, 
> or what?
>
>
If we go with the branch per user for each repo, we would have more clarity.  But that is not how the whiteboard in SVN was used.


> - Gordon
>
>

Thanks,
Om


> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> Sent: Wednesday, March 20, 2013 2:04 PM
> To: dev@flex.apache.org
> Subject: Re: [Git] repos open?
>
> I am sorry, it is a bit confusing which 1 you are voting for.  My bad 
> for re-using numbers in a nested way.  Can you be specific and vote 
> for 3.1, etc. if you mean the options under 3?
>
> Thanks,
> Om
>
> On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:
>
> > +1 for #1. Be good to figure out merge/conflict early in the game.
> >
> > Peter Ent
> > Flex SDK Team
> > Adobe Systems
> >
> > On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > >
> > >
> > >
> > >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> > >
> > >> Here is my proposal in the meantime:
> > >>
> > >> 1.  We open up Falcon and ASJS repos first since there are no 
> > >>issues with  that
> > >+1.  Peter and I probably have merge conflicts in ASJS which would 
> > >+be a
> > >good
> > >testing ground since there isn't critical history in there.
> > >> 2.  I have pinged Infra about the missing history in Utilities.
> > >>Let them  come back to us with a definitive answer.
> > >+0.  That's fine, but to me, it isn't worth the wait.  Let's open 
> > >+it up
> > >too.
> > >> 3.  We need to figure out what to do about the whiteboard.  The 
> > >> current proposals to fix this problem are:
> > >>
> > >>    1. Use the sparse checkout option as described here
> > >>    http://markmail.org/message/dg7hplezkzwiroes)
> > >>    2. Create a branch per user in the whiteboard
> > >>    3. Move to github for whiteboards
> > >>    4. Let whiteboards remain in SVN
> > >>
> > >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't 
> > >horribly slow for Fred the second time he tried it.  The 240MB in 
> > >there isn't the biggest download I've seen.  I think FB was larger.
> > >
> > >--
> > >Alex Harui
> > >Flex SDK Team
> > >Adobe Systems, Inc.
> > >http://blogs.adobe.com/aharui
> > >
> >
> >
>

Re: [Git] repos open?

Posted by Om <bi...@gmail.com>.
On Wed, Mar 20, 2013 at 5:02 PM, Gordon Smith <go...@adobe.com> wrote:

> Why can't each developer's whiteboard for flex-sdk be a branch in the
> flex-sdk repo? Is there some reason why dozens of branches are bad?
>
>
I believe this is what you mean:
https://git-wip-us.apache.org/docs/switching-to-git.html#user-name-spaces-for-branches?
If we want to do this, we can ask Infra to help support this.


> If there is a single whiteboard repo, is it for flex-sdk, flex-falcon, or
> what?
>
>
If we go with the branch per user for each repo, we would have more
clarity.  But that is not how the whiteboard in SVN was used.


> - Gordon
>
>

Thanks,
Om


> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> Sent: Wednesday, March 20, 2013 2:04 PM
> To: dev@flex.apache.org
> Subject: Re: [Git] repos open?
>
> I am sorry, it is a bit confusing which 1 you are voting for.  My bad for
> re-using numbers in a nested way.  Can you be specific and vote for 3.1,
> etc. if you mean the options under 3?
>
> Thanks,
> Om
>
> On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:
>
> > +1 for #1. Be good to figure out merge/conflict early in the game.
> >
> > Peter Ent
> > Flex SDK Team
> > Adobe Systems
> >
> > On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > >
> > >
> > >
> > >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> > >
> > >> Here is my proposal in the meantime:
> > >>
> > >> 1.  We open up Falcon and ASJS repos first since there are no
> > >>issues with  that
> > >+1.  Peter and I probably have merge conflicts in ASJS which would be
> > >+a
> > >good
> > >testing ground since there isn't critical history in there.
> > >> 2.  I have pinged Infra about the missing history in Utilities.
> > >>Let them  come back to us with a definitive answer.
> > >+0.  That's fine, but to me, it isn't worth the wait.  Let's open it
> > >+up
> > >too.
> > >> 3.  We need to figure out what to do about the whiteboard.  The
> > >> current proposals to fix this problem are:
> > >>
> > >>    1. Use the sparse checkout option as described here
> > >>    http://markmail.org/message/dg7hplezkzwiroes)
> > >>    2. Create a branch per user in the whiteboard
> > >>    3. Move to github for whiteboards
> > >>    4. Let whiteboards remain in SVN
> > >>
> > >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't horribly
> > >slow for Fred the second time he tried it.  The 240MB in there isn't
> > >the biggest download I've seen.  I think FB was larger.
> > >
> > >--
> > >Alex Harui
> > >Flex SDK Team
> > >Adobe Systems, Inc.
> > >http://blogs.adobe.com/aharui
> > >
> >
> >
>

RE: [Git] repos open?

Posted by Gordon Smith <go...@adobe.com>.
Why can't each developer's whiteboard for flex-sdk be a branch in the flex-sdk repo? Is there some reason why dozens of branches are bad?

If there is a single whiteboard repo, is it for flex-sdk, flex-falcon, or what?

- Gordon

-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
Sent: Wednesday, March 20, 2013 2:04 PM
To: dev@flex.apache.org
Subject: Re: [Git] repos open?

I am sorry, it is a bit confusing which 1 you are voting for.  My bad for re-using numbers in a nested way.  Can you be specific and vote for 3.1, etc. if you mean the options under 3?

Thanks,
Om

On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:

> +1 for #1. Be good to figure out merge/conflict early in the game.
>
> Peter Ent
> Flex SDK Team
> Adobe Systems
>
> On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >
> >
> >
> >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> >
> >> Here is my proposal in the meantime:
> >>
> >> 1.  We open up Falcon and ASJS repos first since there are no 
> >>issues with  that
> >+1.  Peter and I probably have merge conflicts in ASJS which would be 
> >+a
> >good
> >testing ground since there isn't critical history in there.
> >> 2.  I have pinged Infra about the missing history in Utilities.  
> >>Let them  come back to us with a definitive answer.
> >+0.  That's fine, but to me, it isn't worth the wait.  Let's open it 
> >+up
> >too.
> >> 3.  We need to figure out what to do about the whiteboard.  The 
> >> current proposals to fix this problem are:
> >>
> >>    1. Use the sparse checkout option as described here
> >>    http://markmail.org/message/dg7hplezkzwiroes)
> >>    2. Create a branch per user in the whiteboard
> >>    3. Move to github for whiteboards
> >>    4. Let whiteboards remain in SVN
> >>
> >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't horribly 
> >slow for Fred the second time he tried it.  The 240MB in there isn't 
> >the biggest download I've seen.  I think FB was larger.
> >
> >--
> >Alex Harui
> >Flex SDK Team
> >Adobe Systems, Inc.
> >http://blogs.adobe.com/aharui
> >
>
>

Re: [Git] repos open?

Posted by Om <bi...@gmail.com>.
I am sorry, it is a bit confusing which 1 you are voting for.  My bad for
re-using numbers in a nested way.  Can you be specific and vote for 3.1,
etc. if you mean the options under 3?

Thanks,
Om

On Wed, Mar 20, 2013 at 1:33 PM, Peter Ent <pe...@adobe.com> wrote:

> +1 for #1. Be good to figure out merge/conflict early in the game.
>
> Peter Ent
> Flex SDK Team
> Adobe Systems
>
> On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >
> >
> >
> >On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
> >
> >> Here is my proposal in the meantime:
> >>
> >> 1.  We open up Falcon and ASJS repos first since there are no issues
> >>with
> >> that
> >+1.  Peter and I probably have merge conflicts in ASJS which would be a
> >good
> >testing ground since there isn't critical history in there.
> >> 2.  I have pinged Infra about the missing history in Utilities.  Let
> >>them
> >> come back to us with a definitive answer.
> >+0.  That's fine, but to me, it isn't worth the wait.  Let's open it up
> >too.
> >> 3.  We need to figure out what to do about the whiteboard.  The current
> >> proposals to fix this problem are:
> >>
> >>    1. Use the sparse checkout option as described here
> >>    http://markmail.org/message/dg7hplezkzwiroes)
> >>    2. Create a branch per user in the whiteboard
> >>    3. Move to github for whiteboards
> >>    4. Let whiteboards remain in SVN
> >>
> >I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't horribly slow
> >for Fred the second time he tried it.  The 240MB in there isn't the
> >biggest
> >download I've seen.  I think FB was larger.
> >
> >--
> >Alex Harui
> >Flex SDK Team
> >Adobe Systems, Inc.
> >http://blogs.adobe.com/aharui
> >
>
>

Re: [Git] repos open?

Posted by Peter Ent <pe...@adobe.com>.
+1 for #1. Be good to figure out merge/conflict early in the game.

Peter Ent
Flex SDK Team
Adobe Systems

On 3/20/13 4:25 PM, "Alex Harui" <ah...@adobe.com> wrote:

>
>
>
>On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:
>
>> Here is my proposal in the meantime:
>> 
>> 1.  We open up Falcon and ASJS repos first since there are no issues
>>with
>> that
>+1.  Peter and I probably have merge conflicts in ASJS which would be a
>good
>testing ground since there isn't critical history in there.
>> 2.  I have pinged Infra about the missing history in Utilities.  Let
>>them
>> come back to us with a definitive answer.
>+0.  That's fine, but to me, it isn't worth the wait.  Let's open it up
>too.
>> 3.  We need to figure out what to do about the whiteboard.  The current
>> proposals to fix this problem are:
>> 
>>    1. Use the sparse checkout option as described here
>>    http://markmail.org/message/dg7hplezkzwiroes)
>>    2. Create a branch per user in the whiteboard
>>    3. Move to github for whiteboards
>>    4. Let whiteboards remain in SVN
>> 
>I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't horribly slow
>for Fred the second time he tried it.  The 240MB in there isn't the
>biggest
>download I've seen.  I think FB was larger.
>
>-- 
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.
>http://blogs.adobe.com/aharui
>


Re: [Git] repos open?

Posted by Alex Harui <ah...@adobe.com>.


On 3/20/13 12:26 PM, "Om" <bi...@gmail.com> wrote:

> Here is my proposal in the meantime:
> 
> 1.  We open up Falcon and ASJS repos first since there are no issues with
> that
+1.  Peter and I probably have merge conflicts in ASJS which would be a good
testing ground since there isn't critical history in there.
> 2.  I have pinged Infra about the missing history in Utilities.  Let them
> come back to us with a definitive answer.
+0.  That's fine, but to me, it isn't worth the wait.  Let's open it up too.
> 3.  We need to figure out what to do about the whiteboard.  The current
> proposals to fix this problem are:
> 
>    1. Use the sparse checkout option as described here (
>    http://markmail.org/message/dg7hplezkzwiroes)
>    2. Create a branch per user in the whiteboard
>    3. Move to github for whiteboards
>    4. Let whiteboards remain in SVN
> 
I vote for #3 (isn't #1 dependent on #3?).  IIRC, it wasn't horribly slow
for Fred the second time he tried it.  The 240MB in there isn't the biggest
download I've seen.  I think FB was larger.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Re: [Git] repos open?

Posted by Om <bi...@gmail.com>.
On Wed, Mar 20, 2013 at 10:23 AM, Om <bi...@gmail.com> wrote:

> On Wed, Mar 20, 2013 at 9:41 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
>> Ah, I must've misunderstood: you called a LAZY consensus, which, if I
>> understand voting rules correctly, means that when no-one objects,
>> whatever you called it for passes... and besides a minor - at least, I
>> think was the consensus - issue on missing history on deleted files,
>> no-one objected. Actually, most of the people that are actively
>> involved in the move even voiced their consent explicitly.
>>
>>
> If you read that thread in its entirety, Justin had some serious
> objections to moving forward.  I completely disagree with him in this
> regard, but I definitely value his opinion.  Heck, he has been the release
> manager for our last two releases, so we better get is 'okay' before we
> move forward.
>
>
>> I think everyone is now ready to move on. Give it a couple of hours
>> (both US and Europe are up and answering emails) and if there are no
>> major objections, please ask INFRA to make all repos writable.
>>
>>
> Again, I will wait for Justin to chip in and comment in this thread before
> moving on.
>
> Thanks,
> Om
>
>
Here is my proposal in the meantime:

1.  We open up Falcon and ASJS repos first since there are no issues with
that
2.  I have pinged Infra about the missing history in Utilities.  Let them
come back to us with a definitive answer.
3.  We need to figure out what to do about the whiteboard.  The current
proposals to fix this problem are:

   1. Use the sparse checkout option as described here (
   http://markmail.org/message/dg7hplezkzwiroes)
   2. Create a branch per user in the whiteboard
   3. Move to github for whiteboards
   4. Let whiteboards remain in SVN

Thanks,
Om




>
>
>> Thanks,
>>
>> EdB
>>
>>
>>
>> On Wed, Mar 20, 2013 at 5:12 PM, Om <bi...@gmail.com> wrote:
>> > On Mar 20, 2013 9:06 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>> >>
>> >> Hi,
>> >>
>> >> I know they aren't, and I know we can't "pressure" INFRA, but come on.
>> >> It's nearly two weeks now, and all projects but the SDK are still on
>> >> hold.
>> >
>> > What are we waiting file INFRA to do?  It is up to us to ask them to
>> open
>> > up the repos for read write.
>> >
>> >>
>> >> This way the move to git is causing the project to lose contributors,
>> >> instead of gaining them, as the proponents promised.
>> >>
>> >> Is there anything (but be patient, which isn't working) that I (we)
>> >> can do to make this happen anytime soon?
>> >>
>> >> EdB
>> >
>> > I have asked a bunch of times already.  Can we move on and open up the
>> > repos.  If anyone has objections, this is the time to speak up.
>> >
>> > Again, we are the ones delaying things, not Infra.
>> >
>> > Thanks,
>> > Om
>> >
>> >>
>> >>
>> >>
>> >> --
>> >> 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
>>
>
>

Re: [Git] repos open?

Posted by Om <bi...@gmail.com>.
On Wed, Mar 20, 2013 at 9:41 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> Ah, I must've misunderstood: you called a LAZY consensus, which, if I
> understand voting rules correctly, means that when no-one objects,
> whatever you called it for passes... and besides a minor - at least, I
> think was the consensus - issue on missing history on deleted files,
> no-one objected. Actually, most of the people that are actively
> involved in the move even voiced their consent explicitly.
>
>
If you read that thread in its entirety, Justin had some serious objections
to moving forward.  I completely disagree with him in this regard, but I
definitely value his opinion.  Heck, he has been the release manager for
our last two releases, so we better get is 'okay' before we move forward.


> I think everyone is now ready to move on. Give it a couple of hours
> (both US and Europe are up and answering emails) and if there are no
> major objections, please ask INFRA to make all repos writable.
>
>
Again, I will wait for Justin to chip in and comment in this thread before
moving on.

Thanks,
Om



> Thanks,
>
> EdB
>
>
>
> On Wed, Mar 20, 2013 at 5:12 PM, Om <bi...@gmail.com> wrote:
> > On Mar 20, 2013 9:06 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
> >>
> >> Hi,
> >>
> >> I know they aren't, and I know we can't "pressure" INFRA, but come on.
> >> It's nearly two weeks now, and all projects but the SDK are still on
> >> hold.
> >
> > What are we waiting file INFRA to do?  It is up to us to ask them to open
> > up the repos for read write.
> >
> >>
> >> This way the move to git is causing the project to lose contributors,
> >> instead of gaining them, as the proponents promised.
> >>
> >> Is there anything (but be patient, which isn't working) that I (we)
> >> can do to make this happen anytime soon?
> >>
> >> EdB
> >
> > I have asked a bunch of times already.  Can we move on and open up the
> > repos.  If anyone has objections, this is the time to speak up.
> >
> > Again, we are the ones delaying things, not Infra.
> >
> > Thanks,
> > Om
> >
> >>
> >>
> >>
> >> --
> >> 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
>

Re: [Git] repos open?

Posted by Erik de Bruin <er...@ixsoftware.nl>.
Ah, I must've misunderstood: you called a LAZY consensus, which, if I
understand voting rules correctly, means that when no-one objects,
whatever you called it for passes... and besides a minor - at least, I
think was the consensus - issue on missing history on deleted files,
no-one objected. Actually, most of the people that are actively
involved in the move even voiced their consent explicitly.

I think everyone is now ready to move on. Give it a couple of hours
(both US and Europe are up and answering emails) and if there are no
major objections, please ask INFRA to make all repos writable.

Thanks,

EdB



On Wed, Mar 20, 2013 at 5:12 PM, Om <bi...@gmail.com> wrote:
> On Mar 20, 2013 9:06 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>>
>> Hi,
>>
>> I know they aren't, and I know we can't "pressure" INFRA, but come on.
>> It's nearly two weeks now, and all projects but the SDK are still on
>> hold.
>
> What are we waiting file INFRA to do?  It is up to us to ask them to open
> up the repos for read write.
>
>>
>> This way the move to git is causing the project to lose contributors,
>> instead of gaining them, as the proponents promised.
>>
>> Is there anything (but be patient, which isn't working) that I (we)
>> can do to make this happen anytime soon?
>>
>> EdB
>
> I have asked a bunch of times already.  Can we move on and open up the
> repos.  If anyone has objections, this is the time to speak up.
>
> Again, we are the ones delaying things, not Infra.
>
> Thanks,
> Om
>
>>
>>
>>
>> --
>> 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

Re: [Git] repos open?

Posted by Om <bi...@gmail.com>.
On Mar 20, 2013 9:06 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> Hi,
>
> I know they aren't, and I know we can't "pressure" INFRA, but come on.
> It's nearly two weeks now, and all projects but the SDK are still on
> hold.

What are we waiting file INFRA to do?  It is up to us to ask them to open
up the repos for read write.

>
> This way the move to git is causing the project to lose contributors,
> instead of gaining them, as the proponents promised.
>
> Is there anything (but be patient, which isn't working) that I (we)
> can do to make this happen anytime soon?
>
> EdB

I have asked a bunch of times already.  Can we move on and open up the
repos.  If anyone has objections, this is the time to speak up.

Again, we are the ones delaying things, not Infra.

Thanks,
Om

>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl