|
Hello.
GitHub pull request along with the code has something like forum thread that may have comments attached. Initial pull request has title and description. So it does not differ much from mailing list. The problem is that IMHO it's not good to have multiple places for discussion, that's why as for me mailing list is good place, but pull request discussions should be mirrored here much like bugzilla comments usually mirrored to -dev mailing lists. Note that programmers that are used to github can propose patches with pull requests. This should not be ignored. If there will be a message to the list, community will be able to respond. The question is if patch itself should land into mailing list archives or pull request reference with all the comments is enough. Best regards, Vitalii Tymchyshyn 08.02.12 15:55, Dave Cramer написав(ла): > Hi > > How does a github pull request establish "evidence of intent" ? Please > keep in mind this question is out of ignorance as I am not that > familiar with github. > > Dave Cramer > > dave.cramer(at)credativ(dot)ca > http://www.credativ.ca > > > > On Wed, Feb 8, 2012 at 7:40 AM, Vitalii Tymchyshyn<[hidden email]> wrote: >> Hi. >> >> As for me, github pull request could be enough. No one needs to chase down >> anything and at the same time everything can be easily tracked/reused with >> all author information. It is also can be treated as "evidence of intent to >> license the code". The only minus is lack of list archiving. >> Also note that since repository is available in github, pull requests are >> expected. So, for me best thing would be to send notifications from github >> to this list (or some new list) regarding pull requests. It seems this can >> be configured in github's notification center. >> >> Best regards, Vitalii Tymchyshyn >> >> 08.02.12 14:27, Dave Cramer написав(ла): >>> I for one would like to keep the policy that we require a context >>> patch to be sent to the list. >>> Having to chase down everyone's git repo seems like more work rather than >>> less >>> >>> >>> >>> On Wed, Feb 8, 2012 at 1:39 AM, Maciek Sakrejda<[hidden email]> >>> wrote: >>>>>> As far as I >>>>>> can tell, the reason the main project requires patches was to change >>>>>> the *process* as little as possible in the course of changing the VCS >>>>>> plumbing. >>>>> That's *a* reason, but not the only one. Other large considerations are >>>>> that we consider that the act of submitting the patch to the mailing >>>>> list is evidence of intent to license the code under the Postgres >>>>> license, and further that this evidence is archived in the PG list >>>>> archives. >>>> That's an excellent point--thanks for the clarification. >> >> >> -- >> Sent via pgsql-jdbc mailing list ([hidden email]) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-jdbc -- Sent via pgsql-jdbc mailing list ([hidden email]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-jdbc |
|
In reply to this post by Dave Cramer-8
> How does a github pull request establish "evidence of intent" ? Please
> keep in mind this question is out of ignorance as I am not that > familiar with github. They're pretty nifty: https://github.com/blog/712-pull-requests-2-0 . Although if a record of attribution is a serious concern, having these under github's control is less than ideal. If this is the main concern, perhaps there's a formal way for the project to archive github pull requests (maybe the github API: http://developer.github.com/v3/pulls/ ), but that's extra work and somewhat more nebulous (as evidence) than a straight mailing list archive. --- Maciek Sakrejda | System Architect | Truviso 1065 E. Hillsdale Blvd., Suite 215 Foster City, CA 94404 (650) 242-3500 Main www.truviso.com -- Sent via pgsql-jdbc mailing list ([hidden email]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-jdbc |
|
2012/2/8 Maciek Sakrejda <[hidden email]>
That's why I propose for github to send notifications to this list. This can be simply configurable and will be more or less much like before.
Best regards, Vitalii Tymchyshyn |
|
2012/2/8 Віталій Тимчишин <[hidden email]>:
> > > 2012/2/8 Maciek Sakrejda <[hidden email]> >> >> > How does a github pull request establish "evidence of intent" ? Please >> > keep in mind this question is out of ignorance as I am not that >> > familiar with github. >> >> They're pretty nifty: https://github.com/blog/712-pull-requests-2-0 . >> Although if a record of attribution is a serious concern, having these >> under github's control is less than ideal. If this is the main >> concern, perhaps there's a formal way for the project to archive >> github pull requests (maybe the github API: >> http://developer.github.com/v3/pulls/ ), but that's extra work and >> somewhat more nebulous (as evidence) than a straight mailing list >> archive. > > > That's why I propose for github to send notifications to this list. This can > be simply configurable and will be more or less much like before. OK, I see the first pull request came to my gmail address. What has to be done to get it to the list ? I imagine we need to add the list as a user to the project ? Getting github as a subscribed user to the list will be more difficult, but manageable ? Can someone elucidate the steps to get pull requests going to the list ? Also it seems that post-receive hooks are designed to push data to a website as opposed to simply emailing ??? Is there an easy way to get email notifications ? Dave -- Sent via pgsql-jdbc mailing list ([hidden email]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-jdbc |
|
Hello.
Yep, I think it should be possible to add this list email as email for pgjdbc github user with https://github.com/account/email Later https://github.com/account/notifications can be used to regulate which emails should be in the list 10.02.12 13:35, Dave Cramer написав(ла): > 2012/2/8 Віталій Тимчишин<[hidden email]>: >> >> 2012/2/8 Maciek Sakrejda<[hidden email]> >>>> How does a github pull request establish "evidence of intent" ? Please >>>> keep in mind this question is out of ignorance as I am not that >>>> familiar with github. >>> They're pretty nifty: https://github.com/blog/712-pull-requests-2-0 . >>> Although if a record of attribution is a serious concern, having these >>> under github's control is less than ideal. If this is the main >>> concern, perhaps there's a formal way for the project to archive >>> github pull requests (maybe the github API: >>> http://developer.github.com/v3/pulls/ ), but that's extra work and >>> somewhat more nebulous (as evidence) than a straight mailing list >>> archive. >> >> That's why I propose for github to send notifications to this list. This can >> be simply configurable and will be more or less much like before. > > OK, I see the first pull request came to my gmail address. What has to > be done to get it to the list ? > > I imagine we need to add the list as a user to the project ? Getting > github as a subscribed user to the list will be more difficult, but > manageable ? > > Can someone elucidate the steps to get pull requests going to the list ? > > > Also it seems that post-receive hooks are designed to push data to a > website as opposed to simply emailing ??? Is there an easy way to get > email notifications ? > > Dave -- Sent via pgsql-jdbc mailing list ([hidden email]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-jdbc |
|
Hi Vitalii,
This is what the pull request email address for Steven's pull came in as Steven Schlansker <[hidden email]> Unless the list accepts everything at reply.github.com I don't see how it can work unless I am missing something ? Dave Cramer dave.cramer(at)credativ(dot)ca http://www.credativ.ca 2012/2/10 Vitalii Tymchyshyn <[hidden email]>: > Hello. > > Yep, I think it should be possible to add this list email as email for > pgjdbc github user with https://github.com/account/email > > Later https://github.com/account/notifications can be used to regulate which > emails should be in the list > > 10.02.12 13:35, Dave Cramer написав(ла): > >> 2012/2/8 Віталій Тимчишин<[hidden email]>: >>> >>> >>> 2012/2/8 Maciek Sakrejda<[hidden email]> >>>>> >>>>> How does a github pull request establish "evidence of intent" ? Please >>>>> keep in mind this question is out of ignorance as I am not that >>>>> familiar with github. >>>> >>>> They're pretty nifty: https://github.com/blog/712-pull-requests-2-0 . >>>> Although if a record of attribution is a serious concern, having these >>>> under github's control is less than ideal. If this is the main >>>> concern, perhaps there's a formal way for the project to archive >>>> github pull requests (maybe the github API: >>>> http://developer.github.com/v3/pulls/ ), but that's extra work and >>>> somewhat more nebulous (as evidence) than a straight mailing list >>>> archive. >>> >>> >>> That's why I propose for github to send notifications to this list. This >>> can >>> be simply configurable and will be more or less much like before. >> >> >> OK, I see the first pull request came to my gmail address. What has to >> be done to get it to the list ? >> >> I imagine we need to add the list as a user to the project ? Getting >> github as a subscribed user to the list will be more difficult, but >> manageable ? >> >> Can someone elucidate the steps to get pull requests going to the list ? >> >> >> Also it seems that post-receive hooks are designed to push data to a >> website as opposed to simply emailing ??? Is there an easy way to get >> email notifications ? >> >> Dave > > -- Sent via pgsql-jdbc mailing list ([hidden email]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-jdbc |
|
The GitHub notification email is SPF-authenticated, so if Majordomo
allows checking that it it would be best. Florent 2012/2/10 Dave Cramer <[hidden email]>: > Hi Vitalii, > > This is what the pull request email address for Steven's pull came in > as Steven Schlansker > <[hidden email]> > > Unless the list accepts everything at reply.github.com I don't see how > it can work unless I am missing something ? > > Dave Cramer > > dave.cramer(at)credativ(dot)ca > http://www.credativ.ca > > > > 2012/2/10 Vitalii Tymchyshyn <[hidden email]>: >> Hello. >> >> Yep, I think it should be possible to add this list email as email for >> pgjdbc github user with https://github.com/account/email >> >> Later https://github.com/account/notifications can be used to regulate which >> emails should be in the list >> >> 10.02.12 13:35, Dave Cramer написав(ла): >> >>> 2012/2/8 Віталій Тимчишин<[hidden email]>: >>>> >>>> >>>> 2012/2/8 Maciek Sakrejda<[hidden email]> >>>>>> >>>>>> How does a github pull request establish "evidence of intent" ? Please >>>>>> keep in mind this question is out of ignorance as I am not that >>>>>> familiar with github. >>>>> >>>>> They're pretty nifty: https://github.com/blog/712-pull-requests-2-0 . >>>>> Although if a record of attribution is a serious concern, having these >>>>> under github's control is less than ideal. If this is the main >>>>> concern, perhaps there's a formal way for the project to archive >>>>> github pull requests (maybe the github API: >>>>> http://developer.github.com/v3/pulls/ ), but that's extra work and >>>>> somewhat more nebulous (as evidence) than a straight mailing list >>>>> archive. >>>> >>>> >>>> That's why I propose for github to send notifications to this list. This >>>> can >>>> be simply configurable and will be more or less much like before. >>> >>> >>> OK, I see the first pull request came to my gmail address. What has to >>> be done to get it to the list ? >>> >>> I imagine we need to add the list as a user to the project ? Getting >>> github as a subscribed user to the list will be more difficult, but >>> manageable ? >>> >>> Can someone elucidate the steps to get pull requests going to the list ? >>> >>> >>> Also it seems that post-receive hooks are designed to push data to a >>> website as opposed to simply emailing ??? Is there an easy way to get >>> email notifications ? >>> >>> Dave >> >> > > -- > Sent via pgsql-jdbc mailing list ([hidden email]) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-jdbc -- Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 -- Sent via pgsql-jdbc mailing list ([hidden email]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-jdbc |
|
In reply to this post by Dave Cramer-8
On Feb 10, 2012, at 5:08 AM, Dave Cramer wrote: > Hi Vitalii, > > This is what the pull request email address for Steven's pull came in > as Steven Schlansker > <[hidden email]> > > Unless the list accepts everything at reply.github.com I don't see how > it can work unless I am missing something ? > It's my understanding that anything after the '+' is considered to not be part of the identity of the email address, but instead used for internal routing or filtering. So reply+x@… should be treated the same as reply+y@… Maybe adding [hidden email] is sufficient and it 'just works'? Alternately, I know at least Mailman supports regular expression matching for sender filters, and writing a regex to match the above shouldn't be too hard. > > 2012/2/10 Vitalii Tymchyshyn <[hidden email]>: >> Hello. >> >> Yep, I think it should be possible to add this list email as email for >> pgjdbc github user with https://github.com/account/email >> >> Later https://github.com/account/notifications can be used to regulate which >> emails should be in the list >> >> 10.02.12 13:35, Dave Cramer написав(ла): >> >>> 2012/2/8 Віталій Тимчишин<[hidden email]>: >>>> >>>> >>>> 2012/2/8 Maciek Sakrejda<[hidden email]> >>>>>> >>>>>> How does a github pull request establish "evidence of intent" ? Please >>>>>> keep in mind this question is out of ignorance as I am not that >>>>>> familiar with github. >>>>> >>>>> They're pretty nifty: https://github.com/blog/712-pull-requests-2-0 . >>>>> Although if a record of attribution is a serious concern, having these >>>>> under github's control is less than ideal. If this is the main >>>>> concern, perhaps there's a formal way for the project to archive >>>>> github pull requests (maybe the github API: >>>>> http://developer.github.com/v3/pulls/ ), but that's extra work and >>>>> somewhat more nebulous (as evidence) than a straight mailing list >>>>> archive. >>>> >>>> >>>> That's why I propose for github to send notifications to this list. This >>>> can >>>> be simply configurable and will be more or less much like before. >>> >>> >>> OK, I see the first pull request came to my gmail address. What has to >>> be done to get it to the list ? >>> >>> I imagine we need to add the list as a user to the project ? Getting >>> github as a subscribed user to the list will be more difficult, but >>> manageable ? >>> >>> Can someone elucidate the steps to get pull requests going to the list ? >>> >>> >>> Also it seems that post-receive hooks are designed to push data to a >>> website as opposed to simply emailing ??? Is there an easy way to get >>> email notifications ? >>> >>> Dave >> >> > > -- > Sent via pgsql-jdbc mailing list ([hidden email]) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-jdbc -- Sent via pgsql-jdbc mailing list ([hidden email]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-jdbc |
| Powered by Nabble | Edit this page |
