Re: [Zope-dev] github etiquette

2013-09-19 Thread Maurits van Rees

Op 17-09-13 17:15, Marius Gedminas schreef:

On Tue, Sep 17, 2013 at 09:35:58AM -0400, Jim Fulton wrote:

On Tue, Sep 17, 2013 at 8:58 AM, Marius Gedminas mar...@gedmin.as wrote:

FWIW the only reason I'm in favour of self-merges is that this
short-circuits the have you signed the ZF committer agreement? dance.
Only people who have can merge.


Sorry, I don't understand the point you're making.


I'll try to explain better.


I also feel silly when I ask this question from people with very
familiar names.  (I feel that I have to do when I don't see ZF
membership on their GitHub profile.)


So are you saying you don't merge other people's code because
you don't want to ask if they're contributors?


No.  I'm saying the reviewer-merges workflow looks like this:

1. Somebody creates a pull request
2. A reviewer reviews
3. OP fixes
4. Reviewer asks have you signed the agreement?  if not please sign
5. OP says he/she signed it
6. Reviewer trusts OP's word and merges

(I don't have a good short word for somebody who created the pull
request, so I abused Original Poster.)

Whereas I'd prefer

1. Somebody creates a pull request
2. A reviewer reviews
3. OP fixes
4. Reviewer says looks good to me, feel free to merge (if you're not a
committer already, see http://foundation.zope.org/agreements)
5. OP merges

It's not a very strong preference.  I can feel myself changing my mind
already ;-)

OTOH the implicit trust in step 6 makes me a bit uneasy, and I'm not
quite sure how to verify the fact of the signing.  Wait for the user to
show up in https://github.com/zopefoundation?tab=members ?


Checking that list seems the best to me.

This could be a reason to prefer that the 'pull requester' creates a 
branch in the original repository within the zopefoundation: if he can 
do that, it proves he is authorized and has signed the agreement.


BTW, I have just now seen that I am on that list in the members tab, but 
in the greyed out section, which I think means that non-members do not 
see me listed.  There was a button 'Publicize membership' next to my 
name so I clicked and am now in the top 'full-color' list.  :-)  Others 
may want to do the same.



--
Maurits van Rees: http://maurits.vanrees.org/
Zest Software: http://zestsoftware.nl

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] zope-tests - FAILED: 5, OK: 10

2013-09-19 Thread Zope tests summarizer
This is the summary for test reports received on the 
zope-tests list between 2013-09-18 00:00:00 UTC and 2013-09-19 00:00:00 UTC:

See the footnotes for test reports of unsuccessful builds.

An up-to date view of the builders is also available in our 
buildbot documentation: 
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds

Reports received


   winbot / ZODB_dev py_270_win32
   winbot / ZODB_dev py_270_win64
[1]winbot / zope.app.authentication_py_265_32
[2]winbot / zope.app.http_py_265_32
[3]winbot / zope.app.publication_py_265_32
[4]winbot / zope.app.wsgi_py_265_32
[5]winbot / zope.testbrowser_py_265_32
   winbot / ztk_10 py_254_win32
   winbot / ztk_10 py_265_win32
   winbot / ztk_10 py_265_win64
   winbot / ztk_11 py_254_win32
   winbot / ztk_11 py_265_win32
   winbot / ztk_11 py_265_win64
   winbot / ztk_11 py_270_win32
   winbot / ztk_11 py_270_win64

Non-OK results
--

[1]FAILED  winbot / zope.app.authentication_py_265_32
   https://mail.zope.org/pipermail/zope-tests/2013-September/078829.html


[2]FAILED  winbot / zope.app.http_py_265_32
   https://mail.zope.org/pipermail/zope-tests/2013-September/078830.html


[3]FAILED  winbot / zope.app.publication_py_265_32
   https://mail.zope.org/pipermail/zope-tests/2013-September/078828.html


[4]FAILED  winbot / zope.app.wsgi_py_265_32
   https://mail.zope.org/pipermail/zope-tests/2013-September/078831.html


[5]FAILED  winbot / zope.testbrowser_py_265_32
   https://mail.zope.org/pipermail/zope-tests/2013-September/078832.html


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )