A few shapeless and incomplete thoughts leap to mind:
As previously mentioned, the JIRA does have an checkbox to indicate that a
contribution is intended as a contribution. That is intended as a
reinforcement (or an explicit refutation) of the implied license for things
posted on the
On Fri, Aug 07, 2009 at 02:23:43AM -0400, Paul Davis wrote:
A few shapeless and incomplete thoughts leap to mind:
[snip a bazillion unnecessarily quoted lines]
Don't get me started on JIRA.
We could always switch to bugzilla? JIRA is a big honking pile of crap.
Best,
--
Noah Slater,
[snip a bazillion unnecessarily quoted lines]
I wouldn't want to lose providence given the current topic of discussion.
We could always switch to bugzilla?
Right. While we're at it lets use versioned tarballs and FTP instead of SVN.
HTH,
Paul Davis
On Fri, Aug 07, 2009 at 02:46:06AM -0400, Paul Davis wrote:
While we're at it lets use versioned tarballs and FTP instead of SVN.
I'm not sure what you mean. Heh.
Do any of the other committers have Bugzilla experience? Is it that bad?
Thanks,
--
Noah Slater, http://tumbolia.org/nslater
On Fri, Aug 7, 2009 at 2:53 AM, Noah Slaternsla...@apache.org wrote:
On Fri, Aug 07, 2009 at 02:46:06AM -0400, Paul Davis wrote:
While we're at it lets use versioned tarballs and FTP instead of SVN.
I'm not sure what you mean. Heh.
I mean, worse to worser is worst of all.
Do any of the
On Fri, Aug 7, 2009 at 08:53, Noah Slaternsla...@apache.org wrote:
Do any of the other committers have Bugzilla experience? Is it that bad?
Not a committer, but I think recent versions of Bugzilla (e.g. the 3.2
or 3.4 range) are substantially improved from the old 2.18/2.20 crap
everyone is used
On Fri, Aug 07, 2009 at 09:29:15AM +0200, Dirkjan Ochtman wrote:
Not a committer, but I think recent versions of Bugzilla (e.g. the 3.2
or 3.4 range) are substantially improved from the old 2.18/2.20 crap
everyone is used to hating on.
Hmm, sounds good.
I usually prefer Trac myself, because
On 7 Aug 2009, at 08:23, Paul Davis wrote:
[…]
[…]
p.s. I had mentioned Apache Labs (http://labs.apache.org), but
intended it
to be an inadequate options since it would lack the visibility of a
sandbox,
though it would address the licensing issues.
I read the rest as The ASF wants to
Trac rocks. I introduced it some time ago on a contract with a small
group of scientists working collaboratively. Being able to set up and
track milestones, doc meetings with a WIKI, integration with SVN
(perhaps it supports Git now?), it's a sweet tool.
Cheers,
Bob
On Aug 7, 2009, at
On Aug 7, 2009, at 1:23 AM, Paul Davis wrote:
A few shapeless and incomplete thoughts leap to mind:
As previously mentioned, the JIRA does have an checkbox to indicate
that a
contribution is intended as a contribution. That is intended as a
reinforcement (or an explicit refutation) of
On Fri, Aug 7, 2009 at 13:51, Robert Dionnedio...@dionne-associates.com wrote:
Trac rocks. I introduced it some time ago on a contract with a small group
of scientists working collaboratively. Being able to set up and track
milestones, doc meetings with a WIKI, integration with SVN (perhaps it
That said, using Apache SVN in an argument about providing that
paper trail prevents me from considering the issue seriously. I'm a
hacker. I hack. I judge my tools and I have judged SVN to be lacking.
I would very be very excited to see hosted git repositories for ASF
contributors and would use
On 7 Aug 2009, at 17:11, Paul Davis wrote:
That said, using Apache SVN in an argument about providing that
paper trail prevents me from considering the issue seriously. I'm a
hacker. I hack. I judge my tools and I have judged SVN to be
lacking.
I would very be very excited to see hosted git
I read the I would very be very excited to see hosted git repositories for
ASF
contributors as ASF committers. I don't know if that was implied or not.
I was thinking more like: Github on ASF hardware. So that instead of
submitting patches to JIRA we have people sign up for an ASF git repo
While I'm bringing up contentious issues, use of github for a sandbox
for developing significant modifications to CouchDB makes me uneasy.
If I start something on github and accept contributions and ideas from
other uses, I can't represent the eventual patch as my original work
(as
Git really encourages a more distributed, less centralized approach to
development, that allows the centers of gravity to move as they
evolve. This is a good and healthy thing in many contexts, perhaps
less so in others.
I'm not sure what the issue is with respect to the CLA. What prevents
On Thu, Aug 6, 2009 at 6:21 AM, Jan Lehnardtj...@apache.org wrote:
On 6 Aug 2009, at 15:13, Robert Dionne wrote:
Git really encourages a more distributed, less centralized approach to
development, that allows the centers of gravity to move as they evolve. This
is a good and healthy thing in
A CLA is required for any contribution, even patches. An SVN
repository doesn't inherently fix this as patches can still be sent to
committers over email and then checked in. While it's true git
encourages more distributed workflows it's still the responsibility of
committers to make sure
On Thu, Aug 6, 2009 at 2:12 PM, Mikeal Rogersmikeal.rog...@gmail.com wrote:
A CLA is required for any contribution, even patches.
You mean that we need to go find every person that's ever put a patch
on JIRA and get them to sign a legal document? And how does this work
if someone points out a
On 6 Aug 2009, at 20:45, Paul Davis wrote:
On Thu, Aug 6, 2009 at 2:12 PM, Mikeal
Rogersmikeal.rog...@gmail.com wrote:
A CLA is required for any contribution, even patches.
You mean that we need to go find every person that's ever put a patch
on JIRA and get them to sign a legal document?
On Thu, Aug 06, 2009 at 02:45:44PM -0400, Paul Davis wrote:
You mean that we need to go find every person that's ever put a patch
on JIRA and get them to sign a legal document?
As Jan pointed out, JIRA has a checkbox for this. Heh.
And how does this work if someone points out a one liner to
In retrospec, I should not write on a complicated topic while groggy
and then head off to my day job. Standard disclaimer that I am not a
lawyer.
There are at least two issues, neither of them is specific to using
git vs svn, but related to substantial or collaborative development
22 matches
Mail list logo
