As I said, the integration is still cumbersome.
There are legal issues with not uploading patches to Jira.
Anyway, +1 for moving Piggybank to git (github could be a good choice in
this case).
Cheers,
--
Gianmarco
On Wed, Apr 4, 2012 at 06:48, Russell Jurney russell.jur...@gmail.comwrote:
I agree. I think we'll see a massive uptick in contributors to Piggybank
if it is on github. I think we can start getting companies like Twitter
and LinkedIn to think about contributing to Piggybank instead of rolling
their own github repos.
On Wed, Apr 4, 2012 at 7:49 AM, Gianmarco De
+1 to piggybank on github.
The one tricky part will be setting up the repos, build and artifact
publishing components in a way that handles dependency management of
version X of piggybank with version Y of Pig.
On Wed, Apr 4, 2012 at 11:35 AM, Russell Jurney russell.jur...@gmail.comwrote:
I
I figure we can tackle that on hackday.
On Wed, Apr 4, 2012 at 1:30 PM, Bill Graham billgra...@gmail.com wrote:
+1 to piggybank on github.
The one tricky part will be setting up the repos, build and artifact
publishing components in a way that handles dependency management of
version X of
Some more info is available here, for the Cassandra project:
https://issues.apache.org/jira/browse/INFRA-4254
https://github.com/apache/cassandra
http://wiki.apache.org/cassandra/HowToContribute
I have a proposal to make... since we're not yet up for this, but do agree
that it is the future:
Oh, and https://issues.apache.org/jira/browse/CASSANDRA-3676
On Tue, Apr 3, 2012 at 3:36 PM, Russell Jurney russell.jur...@gmail.comwrote:
Some more info is available here, for the Cassandra project:
https://issues.apache.org/jira/browse/INFRA-4254
https://github.com/apache/cassandra
Major +1 for moving Piggybank to github.
Alan.
On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
Some more info is available here, for the Cassandra project:
https://issues.apache.org/jira/browse/INFRA-4254
https://github.com/apache/cassandra
Ok, so we just need a date. Twitter on April blank we will be moving
piggybank to github (and other awesome things).
On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates ga...@hortonworks.com wrote:
Major +1 for moving Piggybank to github.
Alan.
On Apr 3, 2012, at 3:36 PM, Russell Jurney wrote:
Do people prefer a workday or a weekend?
2012/4/3 Russell Jurney russell.jur...@gmail.com
Ok, so we just need a date. Twitter on April blank we will be moving
piggybank to github (and other awesome things).
On Tue, Apr 3, 2012 at 3:55 PM, Alan Gates ga...@hortonworks.com wrote:
Major +1
I prefer weekdays, but I'm flexible.
Russell Jurney http://datasyndrome.com
On Apr 3, 2012, at 5:11 PM, Jonathan Coveney jcove...@gmail.com wrote:
Do people prefer a workday or a weekend?
2012/4/3 Russell Jurney russell.jur...@gmail.com
Ok, so we just need a date. Twitter on April blank
+1 workday
Thanks,
Prashant
On Apr 3, 2012, at 5:11 PM, Jonathan Coveney jcove...@gmail.com wrote:
Do people prefer a workday or a weekend?
2012/4/3 Russell Jurney russell.jur...@gmail.com
Ok, so we just need a date. Twitter on April blank we will be moving
piggybank to github (and other
No, that is not good :(
Weekday for the hackathon?
Russell Jurney http://datasyndrome.com
On Apr 3, 2012, at 8:59 PM, Dmitriy Ryaboy dvrya...@gmail.com wrote:
Russell, you saw that the Cassandra thing still requires people to
upload patches to JIRA?
D
On Tue, Apr 3, 2012 at 5:16 PM,
I usually do that for two reasons.
One, I feel better when I test that the patch correctly applies to the svn
tree. What I usually do is to generate a diff from git and apply it with
patch on the svn tree.
Two, I need to use the svn tree to commit the patch anyway.
Cheers,
--
Gianmarco
On
Git was built with use case #1 being Linux developers exchanging patches
as text via e-mail. I am not sure what binary patch support Linus plans
or what it would help other than being more compact. One disadvantage is
that it is then hard to review simple changes by simply reading the patch
My 2 cents, based on the S4 project experience so far (they have git) is +1
but later.
The process with git is still a bit fuzzy and not fully integrated and
standardized like the one with svn.
I personally use git for all my dev work with Pig, but then switch to svn
to generate the final patch.
Gianmarco, can you elaborate a bit on the fuzziness?
On Tue, Mar 27, 2012 at 2:26 AM, Gianmarco De Francisci Morales
g...@apache.org wrote:
My 2 cents, based on the S4 project experience so far (they have git) is +1
but later.
The process with git is still a bit fuzzy and not fully
The fact is that git does not impose a development model, so it requires a
bit more self discipline compared to svn.
For example, let's say you create one branch for every Jira.
And imagine you want to keep posting patches to Jira so that people can
download and apply them, or have an equivalent.
As much as I love git I also don't think now is the time to switch. We
currently have a solution that allows people to develop with svn or with
git, depending on their preferences. It's also possible to collaborate with
other developers on large patches using git and post links to diff's on
Using text patches is the problem as I see it. We should be using...
something else. Doesn't git's functionality enable phasing out text
patches?
On Tue, Mar 27, 2012 at 11:16 AM, Scott Carey sc...@richrelevance.comwrote:
On the Avro project, several folk generate a patch using git and upload
Could you enumerate the problems you have with text patches?
I can think of 1, but would like to hear your list.
Dmitriy
On Tue, Mar 27, 2012 at 2:48 PM, Russell Jurney
russell.jur...@gmail.com wrote:
Using text patches is the problem as I see it. We should be using...
something else.
There is a check box you check when you upload a patch. If we committed without
verifying you checked it, thats an unfortunate oversight.
No, you cant send a pull request via github to apache. That's a github
(commercial entity) feature, not a git (open source vcs) feature.
Yes you can post
Start here: http://www.apache.org/dev/git.html
I don't think having an out of date svn repo is a good idea, since that's
where newcomers will check.
D
On Wed, Mar 21, 2012 at 10:30 PM, Russell Jurney
russell.jur...@gmail.comwrote:
Let's start using github and publish to svn during releases.
(With my member and PMC hat on) No, that's a violation of Apache policy.
Apache code is hosted on Apache sites, not on github. If we want to use git we
have to sell Apache on letting us use it through their infrastructure, not by
moving the code somewhere else.
Alan.
On Mar 21, 2012, at
Viva el Chancho!
Russell Jurney http://datasyndrome.com
On Mar 21, 2012, at 11:10 PM, Alan Gates ga...@hortonworks.com wrote:
(With my member and PMC hat on) No, that's a violation of Apache policy.
Apache code is hosted on Apache sites, not on github. If we want to use git
we have to
Am 22.03.12 06:30, schrieb Russell Jurney:
Let's start using github and publish to svn during releases.
+1
On 3/20/12 11:22 PM, Jonathan Coveney jcove...@gmail.com wrote:
forcing developers to use svn to work with pig is just another
barrier, imho.
Some might say forcing developers to use git to work with pig is just
another
barrier.
Many people don't know how to use git well (or at all), many
Apache is currently doing a trial with git as the primary repo using the
CouchDB project. Other projects may be able to volunteer to join the
trial, I'm not sure.
see http://git-wip-us.apache.org/
I suggest that if you are interested in this join the apache
infrastructure-dev list.
On
If people don't know git or svn, they are going to have to learn one or the
other if they want to work with open source projects. It might as well be
git, since that's where things are going.
2012/3/22 Scott Carey sc...@richrelevance.com
Apache is currently doing a trial with git as the primary
This can be done in the future but I don't see there is an urgent need
for that. I'd rather wait for Apache to standardize the process and we
can easily follow and switch, rather than become the first several to
try and solve the infrastructure problem.
Daniel
On Thu, Mar 22, 2012 at 12:02 PM,
Thanks, Scott. Can a committer plz join that list with me and we can hash
this out?
On Thu, Mar 22, 2012 at 10:40 AM, Scott Carey sc...@richrelevance.comwrote:
Apache is currently doing a trial with git as the primary repo using the
CouchDB project. Other projects may be able to volunteer to
Uhhh how do you even get on the infrastructure-dev list? Can't find
link/instructions. Feeling dumb.
On Thu, Mar 22, 2012 at 2:02 PM, Russell Jurney russell.jur...@gmail.comwrote:
Thanks, Scott. Can a committer plz join that list with me and we can hash
this out?
On Thu, Mar 22, 2012 at
infrastructure-subscr...@apache.org
On Thu, Mar 22, 2012 at 2:06 PM, Russell Jurney
russell.jur...@gmail.com wrote:
Uhhh how do you even get on the infrastructure-dev list? Can't find
link/instructions. Feeling dumb.
On Thu, Mar 22, 2012 at 2:02 PM, Russell Jurney
If there is already a trial going, the project would benefit from switching
to git, as we could then (I think?) accept pull requests on github. Maybe
not, I'm not familiar with integrating multiple gits. Barrier of entry for
contributing would then drop dramatically, making happy for all.
On
There is downside for switching now:
* Lose Jira integration
* Lose review board integration
* Lose code search integration
It would be more beneficial if we get more Apache infrastructure
support before we switch.
On Thu, Mar 22, 2012 at 2:08 PM, Russell Jurney
russell.jur...@gmail.com wrote:
Wait, this was discussed in that thread, and on twitter when I knocked
JIRA/svn. We don't have to lose JIRA integration. You can specify a url
to the git code in the tickets. This is SO much better than uploading a
patch that it is a huge win, not a loss.
On Thu, Mar 22, 2012 at 2:18 PM,
There is a legal issue as well. Uploading a patch to JIRA requires the
user to grant apache license to use the code. A pull request from github
does not.
This is all being hashed out elsewhere, none of us here are experts.
On 3/22/12 2:08 PM, Russell Jurney russell.jur...@gmail.com wrote:
That is fine. Only committers can merge pull requests. Not a problem.
I've never signed anything, and committers take my patches. Works the same.
On Thu, Mar 22, 2012 at 3:33 PM, Scott Carey sc...@richrelevance.comwrote:
There is a legal issue as well. Uploading a patch to JIRA requires
Would anyone be opposed to doing this? I think you can apply to do this via
Apache, no? It would be nice to make git the first class citizen of
choice... forcing developers to use svn to work with pig is just another
barrier, imho. I thought this had been bandied about on Twitter and the
like, but
Please, yes.
Russell Jurney http://datasyndrome.com
On Mar 20, 2012, at 11:22 PM, Jonathan Coveney jcove...@gmail.com wrote:
Would anyone be opposed to doing this? I think you can apply to do this via
Apache, no? It would be nice to make git the first class citizen of
choice... forcing
AFAIK Apache still does not support git as a primary repository. You can use
the git mirror, which Pig does. If this has changed (or when it does), I'm +0
on changing, by which I mean I don't care which we use.
Alan.
On Mar 20, 2012, at 11:22 PM, Jonathan Coveney wrote:
Would anyone be
I think this changed, and you are now allowed. Looking for the tweets.
Russell Jurney http://datasyndrome.com
On Mar 21, 2012, at 9:36 AM, Alan Gates ga...@hortonworks.com wrote:
AFAIK Apache still does not support git as a primary repository. You can use
the git mirror, which Pig does.
I think this is the tweet (lacking the entire discussion tree that we had
re git) where I was pointing out that some incubator projects were using
git.
https://twitter.com/#!/billgraham/status/174744199407738880
On Wed, Mar 21, 2012 at 12:47 PM, Russell Jurney
russell.jur...@gmail.comwrote:
I
What do we have to do to be the first real project that uses git?
Let's do that. Or, let's just sink svn to github.
It will propel the project forward.
Russell Jurney
twitter.com/rjurney
russell.jur...@gmail.com
datasyndrome.com
On Mar 21, 2012, at 9:04 PM, Bill Graham billgra...@gmail.com
All that's left is for someone to volunteer to do the work.
On Mar 21, 2012, at 9:17 PM, Russell Jurney russell.jur...@gmail.com wrote:
What do we have to do to be the first real project that uses git?
Let's do that. Or, let's just sink svn to github.
It will propel the project forward.
What's the work?
Russell Jurney http://datasyndrome.com
On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy dvrya...@gmail.com wrote:
All that's left is for someone to volunteer to do the work.
On Mar 21, 2012, at 9:17 PM, Russell Jurney russell.jur...@gmail.com wrote:
What do we have to do to
Answering that question is the first part of the answer to that question.
#recursion
D
On Wed, Mar 21, 2012 at 9:57 PM, Russell Jurney russell.jur...@gmail.comwrote:
What's the work?
Russell Jurney http://datasyndrome.com
On Mar 21, 2012, at 9:39 PM, Dmitriy Ryaboy dvrya...@gmail.com
Let's start using github and publish to svn during releases.
Russell Jurney http://datasyndrome.com
On Mar 21, 2012, at 10:20 PM, Dmitriy Ryaboy dvrya...@gmail.com wrote:
Answering that question is the first part of the answer to that question.
#recursion
D
On Wed, Mar 21, 2012 at 9:57
47 matches
Mail list logo
