You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2007/02/05 17:16:13 UTC

[DISCUSS] Incubating Project Policy

Isn't it normal to have a discussion before calling for a vote?  :-)

A vote seems premature, given the current level of discussion.  As you have later noted:

> the thread's grown too long - it needs summarization.  Early in the
> week I'll start a wiki page to begin the clarifications (whys) and
> let folks add-on other examples (which are scattered right now
> throughout this thread.)

> I'm proposing the following policy become explicit across the incubator;

>   Where the project policy permits commit-then-review contributions to its
>   Subversion repository, committers may commit code they personally authored,
>   or with proper attribution, commit patches posted on the project's mailing
>   list or posted to the project's bug tracking system (Jira/Bugzilla).
>
>   No third-party code (beyond bugzilla and mailing list submissions) may be
>   directly committed without first posing the submission to the mailing list.
>   This goes for submissions by associates who are unaffiliated with the
>   project, private correspondence to a committer, and third party open source
>   code which is otherwise compatible with the Apache Software License.

> Where the project's policy is review-then-commit, there truly is no change
> to their current practice.

As noted by James Margaris, yourself, Bertrand, et al, this does not actually address the issue where someone is committing co-workers' work, rather than having the co-workers participating on-list.  We are really looking to have those co-workers be the one's directly posting to the mailing list or JIRA.  To get what you want, your second paragraph should clarify that "first [posting] the submission" means BY THE ACTUAL CONTRIBUTOR, not a proxy.

How do we express what normative behavior should be without unduly restricting cases that ought to be permitted?  What, if any, are the corner cases?

Zukka, I agree that this is more of an ASF-wide issue, but we often set the course here in the Incubator, and it carries over to the rest of the ASF, which is why we really need to make sure that Best Practices *are* Best Practices, and adjust them if not.

	--- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] Incubating Project Policy

Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Noel J. Bergman wrote:
> As noted by James Margaris, yourself, Bertrand, et al, this does 
> not actually address the issue where someone is committing co-workers' 
> work, rather than having the co-workers participating on-list.  

It does when the project pushes back; but I concur...

> We are really looking to have those co-workers be the one's directly 
> posting to the mailing list or JIRA.  To get what you want, your second 
> paragraph should clarify that "first [posting] the submission" means BY 
> THE ACTUAL CONTRIBUTOR, not a proxy.

"...without the Author of the patch first [posting] the submission, or
in the case of an open source or public domain external work, one of the
project contributors posting the proposal to the list."

I'll work something up, good point.  I agree the 'Q & A - why this policy?'
should spell out lots of little edge cases, while keeping the main policy
clear and short.

> Zukka, I agree that this is more of an ASF-wide issue, but we often set 
> the course here in the Incubator, and it carries over to the rest of the 
> ASF, which is why we really need to make sure that Best Practices *are* 
> Best Practices, and adjust them if not.

+1 to that.  I'd like to see it proven out over 6 mos/1 year, tweaked as
necessary, and then mention it as an aside to the board to adopt somewhere
within www.apache.org/dev/ as ASF-wide.  Should it's final form become ASF
wide policy?  Probably, time will tell, but I think we agree it's worth
watching to expand the policy's scope in time.

We graduate a project with their policies firmly in place, so if the project
chooses a different policy that's their choice after graduation, but if they
don't go out of their way, the policies from the incubator are 'sticky' in
their newly elevated TLP status.




---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


RE: [DISCUSS] Incubating Project Policy

Posted by "Noel J. Bergman" <no...@devtech.com>.
Ted Husted wrote:

> Noel J. Bergman wrote:
> > As noted by James Margaris, yourself, Bertrand, et al, this does not
> > actually address the issue where someone is committing co-workers'
> > work, rather than having the co-workers participating on-list.  We
> > are really looking to have those co-workers be the one's directly
> > posting to the mailing list or JIRA.  To get what you want, your
> > second paragraph should clarify that "first [posting] the submission"
> > means BY THE ACTUAL CONTRIBUTOR, not a proxy.

> In the "committing for employer under a CCLA" scenario, the co-workers
> have probably assigned all their rights to the code to their employer.
> Accordingly, the individual is not the contributor, the employer is
> the contributor.

No, no.  This defeats the real purpose.  We're not talking about IP.  OK,
perhaps some folks are, but the CLA means that the person making a commit
must be claiming to do so properly under the terms of the CLA.  If you
commit some code, I must assume that you are doing so with proper authority.
The CCLA exists to ensure that in a work-for-hire situation, that your
employer is confirming your ability to act under the terms of your CLA.

The real purpose is community building, and to make sure that all
discussions and decisions take place on the mailing list as part of the
community.  If the co-workers are working off-list and some agent is just
committing their collective work, that detracts from the ability to have all
of those internal discussions on-list as part of the community.

> If these co-workers want to participate,  they can. But, these
> individuals may or may not be authorized to discuss the code in
> public. It's easy to imagine an environment where a senior
> employee is trusted to contribute and discuss this work outside
> the office domain, while other employers have not yet earned that
> trust with their employer.

That iss something we need to encourage the employer to fix.  As noted
above, the scenario you envision is one rife with back-channel discussions
and decisions being made off-list, even if they are later ratified by the
community when the code is eventually committed.  But there is a difference
between collective development and collectively maintaining a public
repository.

	--- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [DISCUSS] Incubating Project Policy

Posted by Ted Husted <hu...@apache.org>.
On 2/5/07, Noel J. Bergman <no...@devtech.com> wrote:
> As noted by James Margaris, yourself, Bertrand, et al, this does not actually address the
> issue where someone is committing co-workers' work, rather than having the co-workers
>participating on-list.  We are really looking to have those
co-workers be the one's directly
>posting to the mailing list or JIRA.  To get what you want, your
second paragraph should
>clarify that "first [posting] the submission" means BY THE ACTUAL
CONTRIBUTOR, not
> a proxy.

In the "committing for employer under a CCLA" scenario, the co-workers
have probably assigned all their rights to the code to their employer.
Accordingly, the individual is not the contributor, the employer is
the contributor. The actual contributor is the corporate entity, and
the committer is probably wearing two hats. One hat is the "ASF
liason", another hat is "ASF committer".

In this scenario, the appropriate course of action would seem to be to
credit the contribution to the corporate entity, citing that a CCLA is
on file.

If the contribution is the least bit controversial, then, of course,
it should be brought up for discussion first -- just as we would with
a controversial contribution written by an individual contributor,
even when that individual is also a committer and PMC member.

Meanwhile, our lists are open to all comers. If these co-workers want
to participate,  they can. But, these individuals may or may not be
authorized to discuss the code in public. It's easy to imagine an
environment where a senior employee is trusted to contribute and
discuss this work outside the office domain, while other employers
have not yet earned that trust with their employer. It's also easy to
imagine that the co-workers may choose to lurk and do not want to
volunteer their own time to the foundation.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org