Project Locations and Basic Setup

[Tim Flink]

I think most of this came up in an earlier thread but I'm not finding it
right now, so I'm starting a new one.

I'm proposing that we make all the taskotron-related projects as
similar as we can with regard to git repo setup, location and how we do
reviews. If we keep them all slightly different, it makes asking for
contributions more difficult and the contributions guide (which still
needs to be written :-/) more complicated.

To be specific, the repos that I'm including in this are:
 - libtaskotron
 - taskotron-trigger
 - resultsdb
 - resultsdb_frontend
 - resultsdb_api
 - pytap13
 - fake_fedorainfra

The settings that I'm proposing for all those repos are:

 - use gitflow and set 'develop' as the default branch
 - host projects under bitbucket/fedoraqa
   * makes it easier to say "find our projects at this url" instead of
     "find projects X,Y and Z here. find A and B here"
 - code submissions and issues/tasks are tracked through phabricator

Any objections to doing this to all the repos I mentioned?

Tim

[Martin Krizek]

----- Original Message -----
>  From: "Tim Flink" <tflink(a)redhat.com&gt;
>  To: qa-devel(a)lists.fedoraproject.org
>  Sent: Friday, April 4, 2014 4:50:25 PM
>  Subject: Project Locations and Basic Setup
>  
>  I think most of this came up in an earlier thread but I'm not finding it
>  right now, so I'm starting a new one.
>  
>  I'm proposing that we make all the taskotron-related projects as
>  similar as we can with regard to git repo setup, location and how we do
>  reviews. If we keep them all slightly different, it makes asking for
>  contributions more difficult and the contributions guide (which still
>  needs to be written :-/) more complicated.
>  
>  To be specific, the repos that I'm including in this are:
>   - libtaskotron
>   - taskotron-trigger
>   - resultsdb
>   - resultsdb_frontend
>   - resultsdb_api
>   - pytap13
>   - fake_fedorainfra
>  
>  The settings that I'm proposing for all those repos are:
>  
>   - use gitflow and set 'develop' as the default branch
>   - host projects under bitbucket/fedoraqa
>     * makes it easier to say "find our projects at this url" instead of
>       "find projects X,Y and Z here. find A and B here"
>   - code submissions and issues/tasks are tracked through phabricator
>  
>  Any objections to doing this to all the repos I mentioned?
>   
No objections. In addition, we need to make sure that each repo has 
its .arcconfig file with correct project_id.

Martin

[Ralph Bean]

On Mon, Apr 07, 2014 at 03:19:41AM -0400, Martin Krizek wrote:
>  ----- Original Message -----
>  > From: "Tim Flink" <tflink(a)redhat.com&gt;
>  > To: qa-devel(a)lists.fedoraproject.org
>  > Sent: Friday, April 4, 2014 4:50:25 PM
>  > Subject: Project Locations and Basic Setup
>  > 
>  > I think most of this came up in an earlier thread but I'm not finding it
>  > right now, so I'm starting a new one.
>  > 
>  > I'm proposing that we make all the taskotron-related projects as
>  > similar as we can with regard to git repo setup, location and how we do
>  > reviews. If we keep them all slightly different, it makes asking for
>  > contributions more difficult and the contributions guide (which still
>  > needs to be written :-/) more complicated.
>  > 
>  > To be specific, the repos that I'm including in this are:
>  >  - libtaskotron
>  >  - taskotron-trigger
>  >  - resultsdb
>  >  - resultsdb_frontend
>  >  - resultsdb_api
>  >  - pytap13
>  >  - fake_fedorainfra
>  > 
>  > The settings that I'm proposing for all those repos are:
>  > 
>  >  - use gitflow and set 'develop' as the default branch
>  >  - host projects under bitbucket/fedoraqa
>  >    * makes it easier to say "find our projects at this url" instead of
>  >      "find projects X,Y and Z here. find A and B here"
>  >  - code submissions and issues/tasks are tracked through phabricator
>  > 
>  > Any objections to doing this to all the repos I mentioned?
>  > 
>  
>  No objections. In addition, we need to make sure that each repo has 
>  its .arcconfig file with correct project_id. 
No objections.

[Kamil Paral]

>  I think most of this came up in an earlier thread but I'm not
> finding it
>  right now, so I'm starting a new one.
>  
>  I'm proposing that we make all the taskotron-related projects as
>  similar as we can with regard to git repo setup, location and how we do
>  reviews. If we keep them all slightly different, it makes asking for
>  contributions more difficult and the contributions guide (which still
>  needs to be written :-/) more complicated.
>  
>  To be specific, the repos that I'm including in this are:
>   - libtaskotron
>   - taskotron-trigger
>   - resultsdb
>   - resultsdb_frontend
>   - resultsdb_api
>   - pytap13
>   - fake_fedorainfra
>  
>  The settings that I'm proposing for all those repos are:
>  
>   - use gitflow and set 'develop' as the default branch
>   - host projects under bitbucket/fedoraqa
>     * makes it easier to say "find our projects at this url" instead of
>       "find projects X,Y and Z here. find A and B here"
>   - code submissions and issues/tasks are tracked through phabricator
>  
>  Any objections to doing this to all the repos I mentioned? 
Almost no objections :-)

For pytap13, I think it would make sense to keep the issues in Bitbucket. Once the library
is complete, we won't touch it too much, it's just a utility library with a very
narrow scope. In this case, I think it would be better to keep the issue tracker more
accessible (people are much more likely to create a Bitbucket account than our Phab
account).

[Josef Skladanka]

>   - use gitflow and set 'develop' as the default branch
>   - host projects under bitbucket/fedoraqa
>     * makes it easier to say "find our projects at this url" instead of
>       "find projects X,Y and Z here. find A and B here" 
Absolutely no problem here.

>   - code submissions and issues/tasks are tracked through phabricator
At least for the utility-projects (pytap13 is IMHO the only one though), I'd rather
still have the issues on both Bitbucket and in Phab. The thing is, that since this might
(sometimes) get used out of taskotron/fedoraqa, it seems like too much of a hassle to
request the 'outsiders' to register in our Phab, when the ticket can be posted via
the Bitbucket.

Does it make sense?

J.

[Tim Flink]

On Fri, 4 Apr 2014 08:50:25 -0600
Tim Flink <tflink(a)redhat.com&gt; wrote:


>  To be specific, the repos that I'm including in this are:
>   - libtaskotron
>   - taskotron-trigger
>   - resultsdb
>   - resultsdb_frontend
>   - resultsdb_api
>   - pytap13
>   - fake_fedorainfra
>  
>  The settings that I'm proposing for all those repos are:
>  
>   - use gitflow and set 'develop' as the default branch
>   - host projects under bitbucket/fedoraqa
>     * makes it easier to say "find our projects at this url" instead of
>       "find projects X,Y and Z here. find A and B here"
>   - code submissions and issues/tasks are tracked through phabricator 
From the responses thus far, I have seen no objections other than keep
pytap13 issues in bitbucket (which I agree with).

I'm assuming that the only active project at this exact moment is
libtaskotron, so I'll plan to changing repos around in the next day or
so.

Tim