Re: Github tools and discussions

2012-04-16 Thread Jérôme Vieilledent
Some people at eZ engineering do it. We still don't have clear
responsibilities for that. This is currently in discussion with the
community project board.
The best would be to have 1 or 2 persons being the entry point and pinging
the right people then.

Le lundi 16 avril 2012, Maxime Thomas a écrit :

 @Jerome Vieilledent : How do you manage that at eZ ?

 2012/4/15 David Neilsen da...@panmedia.co.nz javascript:;

  Whos going to be responsible for managing pull requests?
 
  David Neilsen | 07 834 3366 | PANmedia ®
 
 
  2012/4/15 Jérôme Vieilledent j...@ez.no javascript:;
 
   Hi
  
   As Christian asked for, here's the github thread :).
   For CI : Travis should be OK. It's very well integrated with Github.
We also talked few months ago about extra tools for code reviewing.
  
   For people that have push access to the repository, it is possible to
 do
   internal pull requests (ie. from a branch to master). It's then
 possible
  to
   discuss, comment line by line, just like any other PR.
  
   About the issue tracker, I think Github is sufficient, but of course
 wer
   could have another stuff. Github has a lot of service hooks to link
   external tools like Mantis (or even Jira since Zeta is full Open
 Source)s
   ---
   Jérôme Vieilledent
   Software engineer
  
   eZ Systems | 26 rue de la République, 69002 Lyon, France
  
   mailto:j...@ez.no javascript:;
   skype lolautruche | twitter @jvieilledent
  
  
 



 --
 Maxime
 maxime.tho...@wascou.org javascript:; | www.wascou.org |
 http://twitter.com/wascou



Github tools and discussions

2012-04-15 Thread Jérôme Vieilledent
Hi  

As Christian asked for, here's the github thread :).
For CI : Travis should be OK. It's very well integrated with Github.
 We also talked few months ago about extra tools for code reviewing.

For people that have push access to the repository, it is possible to do 
internal pull requests (ie. from a branch to master). It's then possible to 
discuss, comment line by line, just like any other PR.

About the issue tracker, I think Github is sufficient, but of course we could 
have another stuff. Github has a lot of service hooks to link external tools 
like Mantis (or even Jira since Zeta is full Open Source)
---
Jérôme Vieilledent
Software engineer

eZ Systems | 26 rue de la République, 69002 Lyon, France

mailto:j...@ez.no
skype lolautruche | twitter @jvieilledent



Re: Github tools and discussions

2012-04-15 Thread David Neilsen
Whos going to be responsible for managing pull requests?

David Neilsen | 07 834 3366 | PANmedia ®


2012/4/15 Jérôme Vieilledent j...@ez.no

 Hi

 As Christian asked for, here's the github thread :).
 For CI : Travis should be OK. It's very well integrated with Github.
  We also talked few months ago about extra tools for code reviewing.

 For people that have push access to the repository, it is possible to do
 internal pull requests (ie. from a branch to master). It's then possible to
 discuss, comment line by line, just like any other PR.

 About the issue tracker, I think Github is sufficient, but of course we
 could have another stuff. Github has a lot of service hooks to link
 external tools like Mantis (or even Jira since Zeta is full Open Source)
 ---
 Jérôme Vieilledent
 Software engineer

 eZ Systems | 26 rue de la République, 69002 Lyon, France

 mailto:j...@ez.no
 skype lolautruche | twitter @jvieilledent




Re: Github tools and discussions

2012-04-15 Thread Maxime Thomas
@Jerome Vieilledent : How do you manage that at eZ ?

2012/4/15 David Neilsen da...@panmedia.co.nz

 Whos going to be responsible for managing pull requests?

 David Neilsen | 07 834 3366 | PANmedia ®


 2012/4/15 Jérôme Vieilledent j...@ez.no

  Hi
 
  As Christian asked for, here's the github thread :).
  For CI : Travis should be OK. It's very well integrated with Github.
   We also talked few months ago about extra tools for code reviewing.
 
  For people that have push access to the repository, it is possible to do
  internal pull requests (ie. from a branch to master). It's then possible
 to
  discuss, comment line by line, just like any other PR.
 
  About the issue tracker, I think Github is sufficient, but of course we
  could have another stuff. Github has a lot of service hooks to link
  external tools like Mantis (or even Jira since Zeta is full Open Source)
  ---
  Jérôme Vieilledent
  Software engineer
 
  eZ Systems | 26 rue de la République, 69002 Lyon, France
 
  mailto:j...@ez.no
  skype lolautruche | twitter @jvieilledent
 
 




-- 
Maxime
maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou