I did notice that according to the post you linked to, Spring also
requires an additional step beyond a pull-request to document license
compliance:
-------------------------------------------------------------------------
I skirted over this in the article, but it's an important point. In
general, I'd like to see release change management be built right into
the contribution process. The same goes for Contributor License
Agreement (CLA) processing. I do not think we should be sending
contributors to three different places (e.g. Github to submit a pull
request, JIRA to create a issue containing duplicate information, and
springsource.org to sign the CLA). It should be one integrated,
streamlined process with no duplication.
It's my understanding Github has some nice hooks for customization, and
we should look into those. For the time being, the project teams will
need to manually ensure changes applied from pull requests get tracked
with the release(s) they are included in. In addition, project teams
will need to verify each contributor has signed a CLA to ensure all code
contributions are clean from a licensing perspective.
-------------------------------------------------------------------------
On 2/20/2012 11:21 AM, David Smiley (@MITRE.org) wrote:
Ok, that's disappointing. So much for ASF projects being part of the
social coding revolution. It's a big deal, by the way. When people
ask me what it's all about, I point them to this blob post by the
Springframework team:
http://blog.springsource.com/2010/12/21/social-coding-in-spring-projects/
I suspect you are enlightened Mark but others reading our conversation
might not be.
So this guy's patch, the one I replied to, is a typo amounting to two
characters. Are there ASF guidelines on size of contributions?
Wether guidelines exist or not, IANAL but I believe there are
practical considerations on the size of patches to not concern
yourself with copyright. I've seen estimates before ranging from
20-100 lines of code.
~ David
On Feb 20, 2012, at 11:07 AM, Mark Miller-3 [via Lucene] wrote:
I think the problem is around the ASF's thoughts on what it means to
contribute a patch in JIRA and click the check box about donating.
They seem to find that important, and you don't have the same
mechanism when grabbing pull requests from github.
On Feb 20, 2012, at 10:56 AM, David Smiley (@MITRE.org) wrote:
> Cool; pull-requests via GitHub. Has anyone reacted to one of these
messages
> and applied the change before? If so what was the process? Since
> lucene-solr is a mirror, is it impossible?
>
> ~ David
>
> -----
> Author:
http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
> --
> View this message in context:
http://lucene.472066.n3.nabble.com/lucene-solr-pull-request-Fixing-typo-in-example-schema-salves-slaves-tp3760050p3761098.html
> Sent from the Lucene - Java Developer mailing list archive at
Nabble.com <http://Nabble.com>.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: <a
href="x-msg://101/user/SendEmail.jtp?type=node&node=3761133&i=0"
target="_top" rel="nofollow" link="external"> [hidden email]
> For additional commands, e-mail: <a
href="x-msg://101/user/SendEmail.jtp?type=node&node=3761133&i=1"
target="_top" rel="nofollow" link="external"> [hidden email]
>
- Mark Miller
lucidimagination.com <http://lucidimagination.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: <a
href="x-msg://101/user/SendEmail.jtp?type=node&node=3761133&i=2"
target="_top" rel="nofollow" link="external"> [hidden email]
For additional commands, e-mail: <a
href="x-msg://101/user/SendEmail.jtp?type=node&node=3761133&i=3"
target="_top" rel="nofollow" link="external"> [hidden email]
------------------------------------------------------------------------
If you reply to this email, your message will be added to the
discussion below:
http://lucene.472066.n3.nabble.com/lucene-solr-pull-request-Fixing-typo-in-example-schema-salves-slaves-tp3760050p3761133.html
To unsubscribe from lucene-solr pull request: Fixing typo in example
schema: 'salves' => 'slaves', click here.
NAML
<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
Author:
http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
------------------------------------------------------------------------
View this message in context: Re: lucene-solr pull request: Fixing
typo in example schema: 'salves' => 'slaves'
<http://lucene.472066.n3.nabble.com/lucene-solr-pull-request-Fixing-typo-in-example-schema-salves-slaves-tp3760050p3761181.html>
Sent from the Lucene - Java Developer mailing list archive
<http://lucene.472066.n3.nabble.com/Lucene-Java-Developer-f564358.html> at
Nabble.com.
