You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Chris Hostetter <ho...@fucit.org> on 2014/02/12 23:29:03 UTC
DISCUSS: Go "all in" on github integration
As some folks may know, apache infra has been making lots of improvements
to how the users of the github mirrors of ASF projects can interact with
the regular apache dev cycle.
A while back, some of these features were enabled for the Lucene/Solr code
base, and we have already had a few contributions submitted as Github Pull
Requests that were then committed.
Infra has recently announced more autoamted integration between github
concepts and regular Apache work flow on the mailing lists & Jira -- on a
per-project Opt-In basis...
https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
...It's not entirely clear to me how fine grained the enable/disable
controls are for some of these features -- wether we already have all of
these features enabled based on our past infra requests, or if we need to
"opt-in again" to the new ones before we'll see any changes ... but my
suggestion is that we file a Jira with infra that says something to the
effect of...
"The Lucene PMC wishs to opt-in on any and all github related project
linkages that are available that we may not already be opted-in to."
Any objections?
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: DISCUSS: Go "all in" on github integration
Posted by Uwe Schindler <uw...@thetaphi.de>.
+1
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Chris Hostetter [mailto:hossman_lucene@fucit.org]
> Sent: Wednesday, February 12, 2014 11:29 PM
> To: Lucene Dev
> Subject: DISCUSS: Go "all in" on github integration
>
>
> As some folks may know, apache infra has been making lots of
> improvements to how the users of the github mirrors of ASF projects can
> interact with the regular apache dev cycle.
>
> A while back, some of these features were enabled for the Lucene/Solr code
> base, and we have already had a few contributions submitted as Github Pull
> Requests that were then committed.
>
> Infra has recently announced more autoamted integration between github
> concepts and regular Apache work flow on the mailing lists & Jira -- on a per-
> project Opt-In basis...
>
> https://blogs.apache.org/infra/entry/improved_integration_between_apac
> he_and
>
> ...It's not entirely clear to me how fine grained the enable/disable controls
> are for some of these features -- wether we already have all of these
> features enabled based on our past infra requests, or if we need to "opt-in
> again" to the new ones before we'll see any changes ... but my suggestion is
> that we file a Jira with infra that says something to the effect of...
>
> "The Lucene PMC wishs to opt-in on any and all github related project
> linkages that are available that we may not already be opted-in to."
>
>
> Any objections?
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional
> commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: DISCUSS: Go "all in" on github integration
Posted by "David Smiley (@MITRE.org)" <DS...@mitre.org>.
Nice!
And I see the infra ticket was "fixed" today.
Hopefully it will encourage more contributions. If someone can show an
example of this in action (not necessarily Lucene/Solr) it'd be nice to see.
Unfortunately, there's still a huge gap between an actual bona-fide GitHub
run project, and what we have with respect to us committers. Although
perhaps for a contributing user there is little difference now, and that's
fantastic since that's part of the point of being on GitHub -- ease of
contribution.
~ David
Chris Hostetter-3 wrote
> As some folks may know, apache infra has been making lots of improvements
> to how the users of the github mirrors of ASF projects can interact with
> the regular apache dev cycle.
>
> A while back, some of these features were enabled for the Lucene/Solr code
> base, and we have already had a few contributions submitted as Github Pull
> Requests that were then committed.
>
> Infra has recently announced more autoamted integration between github
> concepts and regular Apache work flow on the mailing lists & Jira -- on a
> per-project Opt-In basis...
>
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>
> ...It's not entirely clear to me how fine grained the enable/disable
> controls are for some of these features -- wether we already have all of
> these features enabled based on our past infra requests, or if we need to
> "opt-in again" to the new ones before we'll see any changes ... but my
> suggestion is that we file a Jira with infra that says something to the
> effect of...
>
> "The Lucene PMC wishs to opt-in on any and all github related project
> linkages that are available that we may not already be opted-in to."
>
>
> Any objections?
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@.apache
> For additional commands, e-mail:
> dev-help@.apache
-----
Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
--
View this message in context: http://lucene.472066.n3.nabble.com/DISCUSS-Go-all-in-on-github-integration-tp4117011p4117314.html
Sent from the Lucene - Java Developer mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: DISCUSS: Go "all in" on github integration
Posted by Shai Erera <se...@gmail.com>.
OK, so all I need is to reply and change the To to jira@apache.org? I'll
give it a try.
Shai
On Thu, Feb 13, 2014 at 11:02 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> Hi Shai,
>
>
>
> It does not work with JIRA, because the reply is sent to dev@lao not the
> issue server. The problem here is the mailing list configuration, which
> sets the reply address to dev@lao: By default JIRA allows to post stuff
> to the JIRA's mail address and its directed to the issue comments, but for
> that to work, the "To" address has to also include jira@apache.org .
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* Shai Erera [mailto:serera@gmail.com]
> *Sent:* Thursday, February 13, 2014 9:30 AM
> *To:* dev@lucene.apache.org
> *Subject:* Re: DISCUSS: Go "all in" on github integration
>
>
>
> +1.
>
> I read on the Apache page that part of the integration lets us reply to an
> email from the GitHub issue, and the response is recorded on the issue.
> Does that work w/ JIRA as well? I gave it a quick try and seems like it
> doesn't..
>
> Shai
>
>
>
> On Thu, Feb 13, 2014 at 9:41 AM, Tommaso Teofili <
> tommaso.teofili@gmail.com> wrote:
>
> +1
>
>
>
> Tommaso
>
>
>
> 2014-02-12 23:29 GMT+01:00 Chris Hostetter <ho...@fucit.org>:
>
>
>
>
> As some folks may know, apache infra has been making lots of improvements
> to how the users of the github mirrors of ASF projects can interact with
> the regular apache dev cycle.
>
> A while back, some of these features were enabled for the Lucene/Solr code
> base, and we have already had a few contributions submitted as Github Pull
> Requests that were then committed.
>
> Infra has recently announced more autoamted integration between github
> concepts and regular Apache work flow on the mailing lists & Jira -- on a
> per-project Opt-In basis...
>
>
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>
> ...It's not entirely clear to me how fine grained the enable/disable
> controls are for some of these features -- wether we already have all of
> these features enabled based on our past infra requests, or if we need to
> "opt-in again" to the new ones before we'll see any changes ... but my
> suggestion is that we file a Jira with infra that says something to the
> effect of...
>
> "The Lucene PMC wishs to opt-in on any and all github related project
> linkages that are available that we may not already be opted-in to."
>
>
> Any objections?
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
>
>
RE: DISCUSS: Go "all in" on github integration
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi Shai,
It does not work with JIRA, because the reply is sent to dev@lao not the issue server. The problem here is the mailing list configuration, which sets the reply address to dev@lao: By default JIRA allows to post stuff to the JIRA’s mail address and its directed to the issue comments, but for that to work, the “To” address has to also include jira@apache.org .
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
<http://www.thetaphi.de/> http://www.thetaphi.de
eMail: uwe@thetaphi.de
From: Shai Erera [mailto:serera@gmail.com]
Sent: Thursday, February 13, 2014 9:30 AM
To: dev@lucene.apache.org
Subject: Re: DISCUSS: Go "all in" on github integration
+1.
I read on the Apache page that part of the integration lets us reply to an email from the GitHub issue, and the response is recorded on the issue.
Does that work w/ JIRA as well? I gave it a quick try and seems like it doesn't..
Shai
On Thu, Feb 13, 2014 at 9:41 AM, Tommaso Teofili <to...@gmail.com> wrote:
+1
Tommaso
2014-02-12 23:29 GMT+01:00 Chris Hostetter <ho...@fucit.org>:
As some folks may know, apache infra has been making lots of improvements to how the users of the github mirrors of ASF projects can interact with the regular apache dev cycle.
A while back, some of these features were enabled for the Lucene/Solr code base, and we have already had a few contributions submitted as Github Pull Requests that were then committed.
Infra has recently announced more autoamted integration between github concepts and regular Apache work flow on the mailing lists & Jira -- on a per-project Opt-In basis...
https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
...It's not entirely clear to me how fine grained the enable/disable controls are for some of these features -- wether we already have all of these features enabled based on our past infra requests, or if we need to "opt-in again" to the new ones before we'll see any changes ... but my suggestion is that we file a Jira with infra that says something to the effect of...
"The Lucene PMC wishs to opt-in on any and all github related project
linkages that are available that we may not already be opted-in to."
Any objections?
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: DISCUSS: Go "all in" on github integration
Posted by Shai Erera <se...@gmail.com>.
+1.
I read on the Apache page that part of the integration lets us reply to an
email from the GitHub issue, and the response is recorded on the issue.
Does that work w/ JIRA as well? I gave it a quick try and seems like it
doesn't..
Shai
On Thu, Feb 13, 2014 at 9:41 AM, Tommaso Teofili
<to...@gmail.com>wrote:
> +1
>
> Tommaso
>
>
> 2014-02-12 23:29 GMT+01:00 Chris Hostetter <ho...@fucit.org>:
>
>
>> As some folks may know, apache infra has been making lots of improvements
>> to how the users of the github mirrors of ASF projects can interact with
>> the regular apache dev cycle.
>>
>> A while back, some of these features were enabled for the Lucene/Solr
>> code base, and we have already had a few contributions submitted as Github
>> Pull Requests that were then committed.
>>
>> Infra has recently announced more autoamted integration between github
>> concepts and regular Apache work flow on the mailing lists & Jira -- on a
>> per-project Opt-In basis...
>>
>> https://blogs.apache.org/infra/entry/improved_
>> integration_between_apache_and
>>
>> ...It's not entirely clear to me how fine grained the enable/disable
>> controls are for some of these features -- wether we already have all of
>> these features enabled based on our past infra requests, or if we need to
>> "opt-in again" to the new ones before we'll see any changes ... but my
>> suggestion is that we file a Jira with infra that says something to the
>> effect of...
>>
>> "The Lucene PMC wishs to opt-in on any and all github related project
>> linkages that are available that we may not already be opted-in to."
>>
>>
>> Any objections?
>>
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: DISCUSS: Go "all in" on github integration
Posted by Tommaso Teofili <to...@gmail.com>.
+1
Tommaso
2014-02-12 23:29 GMT+01:00 Chris Hostetter <ho...@fucit.org>:
>
> As some folks may know, apache infra has been making lots of improvements
> to how the users of the github mirrors of ASF projects can interact with
> the regular apache dev cycle.
>
> A while back, some of these features were enabled for the Lucene/Solr code
> base, and we have already had a few contributions submitted as Github Pull
> Requests that were then committed.
>
> Infra has recently announced more autoamted integration between github
> concepts and regular Apache work flow on the mailing lists & Jira -- on a
> per-project Opt-In basis...
>
> https://blogs.apache.org/infra/entry/improved_
> integration_between_apache_and
>
> ...It's not entirely clear to me how fine grained the enable/disable
> controls are for some of these features -- wether we already have all of
> these features enabled based on our past infra requests, or if we need to
> "opt-in again" to the new ones before we'll see any changes ... but my
> suggestion is that we file a Jira with infra that says something to the
> effect of...
>
> "The Lucene PMC wishs to opt-in on any and all github related project
> linkages that are available that we may not already be opted-in to."
>
>
> Any objections?
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: DISCUSS: Go "all in" on github integration
Posted by Chris Hostetter <ho...@fucit.org>.
https://issues.apache.org/jira/browse/INFRA-7317
: Date: Wed, 12 Feb 2014 15:29:03 -0700 (MST)
: From: Chris Hostetter <ho...@fucit.org>
: To: Lucene Dev <de...@lucene.apache.org>
: Subject: DISCUSS: Go "all in" on github integration
:
:
: As some folks may know, apache infra has been making lots of improvements to
: how the users of the github mirrors of ASF projects can interact with the
: regular apache dev cycle.
:
: A while back, some of these features were enabled for the Lucene/Solr code
: base, and we have already had a few contributions submitted as Github Pull
: Requests that were then committed.
:
: Infra has recently announced more autoamted integration between github
: concepts and regular Apache work flow on the mailing lists & Jira -- on a
: per-project Opt-In basis...
:
: https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
:
: ...It's not entirely clear to me how fine grained the enable/disable controls
: are for some of these features -- wether we already have all of these features
: enabled based on our past infra requests, or if we need to "opt-in again" to
: the new ones before we'll see any changes ... but my suggestion is that we
: file a Jira with infra that says something to the effect of...
:
: "The Lucene PMC wishs to opt-in on any and all github related project
: linkages that are available that we may not already be opted-in to."
:
:
: Any objections?
:
:
: -Hoss
: http://www.lucidworks.com/
:
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: DISCUSS: Go "all in" on github integration
Posted by Shalin Shekhar Mangar <sh...@gmail.com>.
+1 to opt-in
On Thu, Feb 13, 2014 at 3:59 AM, Chris Hostetter
<ho...@fucit.org> wrote:
>
> As some folks may know, apache infra has been making lots of improvements to
> how the users of the github mirrors of ASF projects can interact with the
> regular apache dev cycle.
>
> A while back, some of these features were enabled for the Lucene/Solr code
> base, and we have already had a few contributions submitted as Github Pull
> Requests that were then committed.
>
> Infra has recently announced more autoamted integration between github
> concepts and regular Apache work flow on the mailing lists & Jira -- on a
> per-project Opt-In basis...
>
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>
> ...It's not entirely clear to me how fine grained the enable/disable
> controls are for some of these features -- wether we already have all of
> these features enabled based on our past infra requests, or if we need to
> "opt-in again" to the new ones before we'll see any changes ... but my
> suggestion is that we file a Jira with infra that says something to the
> effect of...
>
> "The Lucene PMC wishs to opt-in on any and all github related project
> linkages that are available that we may not already be opted-in to."
>
>
> Any objections?
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
--
Regards,
Shalin Shekhar Mangar.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: DISCUSS: Go "all in" on github integration
Posted by Yonik Seeley <yo...@heliosearch.com>.
Big +1!
-Yonik
http://heliosearch.org - native off-heap filters and fieldcache for solr
On Wed, Feb 12, 2014 at 5:29 PM, Chris Hostetter
<ho...@fucit.org> wrote:
>
> As some folks may know, apache infra has been making lots of improvements to
> how the users of the github mirrors of ASF projects can interact with the
> regular apache dev cycle.
>
> A while back, some of these features were enabled for the Lucene/Solr code
> base, and we have already had a few contributions submitted as Github Pull
> Requests that were then committed.
>
> Infra has recently announced more autoamted integration between github
> concepts and regular Apache work flow on the mailing lists & Jira -- on a
> per-project Opt-In basis...
>
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>
> ...It's not entirely clear to me how fine grained the enable/disable
> controls are for some of these features -- wether we already have all of
> these features enabled based on our past infra requests, or if we need to
> "opt-in again" to the new ones before we'll see any changes ... but my
> suggestion is that we file a Jira with infra that says something to the
> effect of...
>
> "The Lucene PMC wishs to opt-in on any and all github related project
> linkages that are available that we may not already be opted-in to."
>
>
> Any objections?
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org