Hi Todd.
I don't think thats the case. at least it wasn't a couple of years ago
when I regularly committed code into httpd, and we don't follow that
process on the hama podling.
you may want to ping gene...@incubator, but I think it's fine. the
other mentors who follow this list may want to chip in here if they
think otherwise.
remeber.. you still need the committers to vote on changing the
policy, but I think it's ok to do from a ASF standpoint.
regards
Ian
On 28/06/2009, at 7:48 PM, Todd Lipcon wrote:
On Sun, Jun 28, 2009 at 7:30 AM, Ian Holsman <i...@holsman.net> wrote:
On 27/06/2009, at 1:05 AM, Eric Evans wrote:
Ok, this raises a question for me. Assuming that we were to
develop an
RTC work-flow that included Git for version control and Gerrit for
code
review, would there still be a requirement to attach patches to
the Jira
issue?
comitters have signed a CLA already, and that applies to anything
they
check in.
so RTC or CTR doesn't really affect that. people who aren't
comitters will
still have to submit JIRAs/whatever and check the button to get
code into
the system. we could change the wording to say the patch/pointer to
the
patch is CLA'd.
You sure that's OK? We had this conversation about Thrift with some
of the
Apache guys a while back, and at that point they said that, even if
you have
a CLA on file, you still have to explicitly grant each change to the
ASF.
Is this a policy change or is it just not well defined yet?
-Todd
--
Ian Holsman
i...@holsman.net
