Thanks Mark, you are a good man :-)
Om
On Sun, Apr 14, 2013 at 5:31 AM, Mark Kessler
kesslerconsult...@gmail.comwrote:
I ended up creating a GITHub account... however, I will probably redo the
repo on it since I uploaded a clone of the Flex-SDK with my changes already
in it. This means the
@flex.apache.org
Subject: Re: [DISCUSS] How do we want to handle Whiteboard?
Thanks Mark, you are a good man :-)
Om
smime.p7s
Description: S/MIME cryptographic signature
Reviving:
Mark Kessler has some stuff that should be on a whiteboard. Can we make the
git whiteboard read-write while a couple of you experiment with Github?
-Alex
On 4/9/13 12:58 AM, Bertrand Delacretaz bdelacre...@apache.org wrote:
On Tue, Apr 9, 2013 at 8:23 AM, Dave Fisher
On Apr 13, 2013 11:13 PM, Alex Harui aha...@adobe.com wrote:
Reviving:
Mark Kessler has some stuff that should be on a whiteboard. Can we make
the
git whiteboard read-write while a couple of you experiment with Github?
-Alex
I have been experimenting with GitHub for the past couple of
On Apr 13, 2013 11:44 PM, Alex Harui aha...@adobe.com wrote:
Is the Git whiteboard read-write? Are there any issues with opening it if
we do end up going to Github? If not, can you request that it be opened?
I'm not sure how you were going about that for the other repos.
Thanks,
-Alex
I ended up creating a GITHub account... however, I will probably redo the
repo on it since I uploaded a clone of the Flex-SDK with my changes already
in it. This means the work I've done already doesn't stand out. so give
me about 20 mins and I'll have
Logistically speaking that would be least
On Apr 8, 2013, at 10:17 PM, Om wrote:
On Mon, Apr 8, 2013 at 9:31 PM, Dave Fisher w...@apache.org wrote:
This discussion seems familiar. Justin has the ASF viewpoint for the most
part. Talk to infra and David Nalley about the issues in expanding out to
github.
Regards,
Dave
-project per repo
structure (our current per committer repo whiteboard), I can't figure out
how to do that.
Someone knows ?
-Fred
-Message d'origine-
From: Om
Sent: Tuesday, April 09, 2013 1:35 AM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] How do we want to handle Whiteboard
Hi,
I would like to remind you the technical problem to do it
If the whiteboard is in SVN, Git or Github we have the same issue - the white
board area doesn't have to mirror the current SDK structure. Answer is
basically patch files in JIRA or branch existing SDK copy files over and see if
: Re: [DISCUSS] How do we want to handle Whiteboard?
Hi,
I would like to remind you the technical problem to do it
If the whiteboard is in SVN, Git or Github we have the same issue - the
white board area doesn't have to mirror the current SDK structure. Answer
is basically patch files in JIRA
On Tue, Apr 9, 2013 at 8:23 AM, Dave Fisher dave2w...@comcast.net wrote:
...The gist is that this PMC is responsible for keeping the IP in shape and
doing the work in the open
I'd also add that whoever commits (or pushes, in the Git model) to the
Apache repository (where all releases must
I don't think it would be possible to use github for the official
whiteboards as it brings up a number of issues for infra and the ASF
ie knowing who contributed, licensing issues etc etc basically the
normal issues for bit of donated code.
Ultimately I think github is the way to go. If
, April 08, 2013 6:49 PM
To: dev@flex.apache.org
Subject: RE: [DISCUSS] How do we want to handle Whiteboard?
I don't think it would be possible to use github for the official
whiteboards as it brings up a number of issues for infra and the ASF
ie knowing who contributed, licensing issues etc etc
On 4/8/13 9:49 AM, Michael A. Labriola labri...@digitalprimates.net
wrote:
I don't think it would be possible to use github for the official
whiteboards as it brings up a number of issues for infra and the ASF
ie knowing who contributed, licensing issues etc etc basically the
normal issues
an open API but I never had
a look http://developer.github.com/v3/
-Fred
-Message d'origine-
From: Om
Sent: Monday, April 08, 2013 8:50 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] How do we want to handle Whiteboard?
On Mon, Apr 8, 2013 at 11:30 AM, Frédéric THOMAS
webdoubl
such
functionality, but given their support for third-party APIs, I imagine we
can write a script for this ourselves.
Thanks,
Om
-Message d'origine- From: Om
Sent: Monday, April 08, 2013 8:13 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] How do we want to handle Whiteboard
@flex.apache.org
Subject: Re: [DISCUSS] How do we want to handle Whiteboard?
On Apr 8, 2013 12:00 PM, Alex Harui aha...@adobe.com wrote:
I'm ok with a couple of folks trying it in order to see if it can satisfy
everyone and Apache.
I'm not sure we need a gate but maybe I'm missing something.
I
I meant the contributor licence agreement. How do we do this for JIRA patches
today? Is it an implicit agreement? I am wondering if adding a note in the
main Github page would be sufficient?
I was curious about the same thing. Specifically Jira patches.
Hi,
Think we may be missing the point here there's nothing to stop a committer from
using github for their own experiments now, but if that code is eventually
donated into the Flex project it would need to:
1) Any contributors who have a made a large contribution have signed a ICLA and
agree
] How do we want to handle Whiteboard?
Hi,
Think we may be missing the point here there's nothing to stop a committer
from using github for their own experiments now, but if that code is
eventually donated into the Flex project it would need to:
1) Any contributors who have a made a large
On Mon, Apr 8, 2013 at 4:26 PM, Justin Mclean jus...@classsoftware.comwrote:
Hi,
Think we may be missing the point here there's nothing to stop a committer
from using github for their own experiments now, but if that code is
eventually donated into the Flex project it would need to:
1) Any
HI,
Notifying the contributer when they send a pull request to a committer's
whiteboard project should serve exactly this purpose.
How do we know if the pull request is legally allowed to be applied? If a patch
is submitted via JIRA at least there's some process and understanding that it's
On 4/8/13 5:32 PM, Justin Mclean jus...@classsoftware.com wrote:
HI,
Notifying the contributer when they send a pull request to a committer's
whiteboard project should serve exactly this purpose.
How do we know if the pull request is legally allowed to be applied? If a
patch is
This discussion seems familiar. Justin has the ASF viewpoint for the most part.
Talk to infra and David Nalley about the issues in expanding out to github.
Regards,
Dave
Sent from my iPhone
On Apr 8, 2013, at 4:35 PM, Om bigosma...@gmail.com wrote:
On Mon, Apr 8, 2013 at 4:26 PM, Justin
Sounds good to me as well.
Redirecting comments sounds like a good idea.
On Apr 9, 2013, at 3:32 AM, Justin Mclean wrote:
HI,
Notifying the contributer when they send a pull request to a committer's
whiteboard project should serve exactly this purpose.
How do we know if the pull request
Hi,
Assuming we get the git hub mirrors up and working there nothing stopping
anyone from using github to supply patches and diff in the usual way. A git hub
pull request can be converted directly into a patch file and applied easily.
There's one outstanding issue in how do we close pull
A lot of the people who currently have whiteboards have copies of the SDK
in there... Would it still be possible to work on a private copy of the
SDK in the whiteboard? The way I see it happening would be that you would
fork the main SDK, and work on it in your own fork rather than the
On Thu, Apr 4, 2013 at 11:23 PM, Justin Mclean jus...@classsoftware.comwrote:
Hi,
Assuming we get the git hub mirrors up and working there nothing stopping
anyone from using github to supply patches and diff in the usual way. A git
hub pull request can be converted directly into a patch file
Any more thoughts on how to manage the whiteboard repo? If its okay with
everyone, I will go ahead and start a VOTE thread soon.
Personally, I like the option of working on GitHub for the whiteboard. In
a way it levels the playing field of committer vs. non-committer. This
could foster more
On Thu, Apr 4, 2013 at 12:44 PM, Om bigosma...@gmail.com wrote:
Personally, I like the option of working on GitHub for the whiteboard. In
a way it levels the playing field of committer vs. non-committer.
I like the idea of the whiteboard being github based. Stops all the
discussion of what a
Github definitely simplifies things. Are there any advantages to keeping
content on Apache's domain?
Harbs
On Apr 4, 2013, at 8:44 PM, Om wrote:
Any more thoughts on how to manage the whiteboard repo? If its okay with
everyone, I will go ahead and start a VOTE thread soon.
Personally, I
On Thu, Apr 4, 2013 at 11:41 AM, Harbs harbs.li...@gmail.com wrote:
Github definitely simplifies things. Are there any advantages to keeping
content on Apache's domain?
Harbs
To be clear, we are talking only about moving the Whiteboard repo to
GitHub. There are no plans to move all the
Released source code must be stored on Apache servers. Did we get approval to
use github. I would imagine there would be concerns about ownership of pulled
code.
Sent via the PANTECH Discover, an ATT 4G LTE smartphone.
Harbs harbs.li...@gmail.com wrote:
Github definitely simplifies
On Thu, Apr 4, 2013 at 11:49 AM, Alex Harui aha...@adobe.com wrote:
Released source code must be stored on Apache servers. Did we get approval
to use github. I would imagine there would be concerns about ownership of
pulled code.
I am not sure if we need approval for this. How is it
Sent: Thursday, April 04, 2013 8:59 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] How do we want to handle Whiteboard?
On Thu, Apr 4, 2013 at 12:44 PM, Om bigosma...@gmail.com wrote:
Personally, I like the option of working on GitHub for the whiteboard. In
a way it levels the playing field
Yes. Of course we're not discussing release code. I don't think there's work
being done on release code in the whiteboards. Is there?
This brings up a question in my mind:
What happens when code in a whiteboard is added to the official development
branch? I assume it's removed from the
Sorry, I have not been tracking the votes. Let me start up a new vote with
these options:
===
What to do with Whiteboard?
1. Use the sparse checkout option as described here (
http://markmail.org/message/dg7hplezkzwiroes)
2. Create a branch per user in
4. Let whiteboards remain in SVN +1
-Fred
-Message d'origine-
From: Om
Sent: Thursday, March 21, 2013 9:34 PM
To: dev@flex.apache.org
Subject: [DISCUSS] How do we want to handle Whiteboard?
Sorry, I have not been tracking the votes. Let me start up a new vote with
these options
d'origine- From: Om
Sent: Thursday, March 21, 2013 9:34 PM
To: dev@flex.apache.org
Subject: [DISCUSS] How do we want to handle Whiteboard?
Sorry, I have not been tracking the votes. Let me start up a new vote with
these options:
==**=
What to do
the possibility to have a repo per project (even if there
are inside the same svn repo) if I go by git-svn.
-Fred
-Message d'origine-
From: Om
Sent: Thursday, March 21, 2013 9:40 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] How do we want to handle Whiteboard?
Just to make it clear
The way I see it:
#1 Pros: Uses Git. Therefore you only need to know one SCM. Any work with
a rich branching history retains that history when landing in the main
repos.
#1 Cons: 240MB initial download. It took several hours for some folks.
#2 Pros: Not sure.
#2 Cons: I think it would be
41 matches
Mail list logo
