Proposal: spins-kickstarts workflow changes

[Kevin Fenzi]

Greetings. 

I am sending this to the devel and spins lists. Feel free to forward to
other places people who might be affected by it should see it. 

Some history: 

We setup the spin-kickstart project on fedorahosted a long time ago. 
At the start it was just the various spins and it's trac instance was
used in the new spins workflow. Then, it was a handy place to put the
dvd iso kickstart that releng made also. Then over time we added cloud
and docker and everything else that used a kickstart to it. In the
start we added some bugzilla components for the various spins for end
user bugs, and used the trac for workflow things. Over time due to
all the images there lots of people have been given commit access to
the repo. Then the spins sig went quiet and we have sort of been limping
along since then with trac tickets not getting to anyone who cares,
etc. 

I'd like to propose the following plan of action: 

* Setup a new project at pagure.io called just kickstarts or
  releng-kickstarts or something. (Bikeshed alert).

* Setup tags for all the various groups that have kickstarts. ie,
  'xfce' 'docker' 'cloud' 'atomic' 'workstation'
etc. And get someone
  from each of those groups to actually watch the tags or someone to CC
  on who will actually look at those tagged issues. 

* Reduce the number of commiters a bunch and ask people to submit PR's
  when they want a change. This will allow releng/qa to control changes
  when in freeze. ie, we can require a freeze break and point to the
  PR/bug with the exact change and merge it when it's approved. 

* Copy the git repo over to it from fedorahosted. Close that repo. 

* Mass close all the fedorahosted trac tickets and close trac to new
  ones with a note to file new issues in pagure. ( 21 tickets
  currently): https://fedorahosted.org/spin-kickstarts/report/1

* Close the "LiveCD*" components in bugzilla to new bugs and close any
  existing ones with a note to refile at pagure. (18 bugs currently):
 
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASS...

* Adjust koji config to pull from pagure.io instead of fedorahosted. 

Thoughts? Additional steps? Better plans?

kevin

[Zach Villers]

+1 for moving forward and involving pagure. I'm not experienced enough to
pick out any issues, but will help however I can.
On Fri, Feb 19, 2016 at 2:37 PM Kevin Fenzi <kevin(a)scrye.com&gt; wrote:

>  Greetings.
>
>  I am sending this to the devel and spins lists. Feel free to forward to
>  other places people who might be affected by it should see it.
>
>  Some history:
>
>  We setup the spin-kickstart project on fedorahosted a long time ago.
>  At the start it was just the various spins and it's trac instance was
>  used in the new spins workflow. Then, it was a handy place to put the
>  dvd iso kickstart that releng made also. Then over time we added cloud
>  and docker and everything else that used a kickstart to it. In the
>  start we added some bugzilla components for the various spins for end
>  user bugs, and used the trac for workflow things. Over time due to
>  all the images there lots of people have been given commit access to
>  the repo. Then the spins sig went quiet and we have sort of been limping
>  along since then with trac tickets not getting to anyone who cares,
>  etc.
>
>  I'd like to propose the following plan of action:
>
>  * Setup a new project at pagure.io called just kickstarts or
>    releng-kickstarts or something. (Bikeshed alert).
>
>  * Setup tags for all the various groups that have kickstarts. ie,
>    'xfce' 'docker' 'cloud' 'atomic' 'workstation'
> etc. And get someone
>    from each of those groups to actually watch the tags or someone to CC
>    on who will actually look at those tagged issues.
>
>  * Reduce the number of commiters a bunch and ask people to submit PR's
>    when they want a change. This will allow releng/qa to control changes
>    when in freeze. ie, we can require a freeze break and point to the
>    PR/bug with the exact change and merge it when it's approved.
>
>  * Copy the git repo over to it from fedorahosted. Close that repo.
>
>  * Mass close all the fedorahosted trac tickets and close trac to new
>    ones with a note to file new issues in pagure. ( 21 tickets
>    currently): https://fedorahosted.org/spin-kickstarts/report/1
>
>  * Close the "LiveCD*" components in bugzilla to new bugs and close any
>    existing ones with a note to refile at pagure. (18 bugs currently):
>
>
> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASS...
>
>  * Adjust koji config to pull from pagure.io instead of fedorahosted.
>
>  Thoughts? Additional steps? Better plans?
>
>  kevin
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  http://lists.fedoraproject.org/admin/lists/[e-mail]
>

[Dan Book]

This sounds like a good step to me. I am used to the pull request workflow
though.

On Fri, Feb 19, 2016 at 5:55 PM, Zach Villers <zachvatwork(a)gmail.com&gt; wrote:

>  +1 for moving forward and involving pagure. I'm not experienced
> enough to
>  pick out any issues, but will help however I can.
>  On Fri, Feb 19, 2016 at 2:37 PM Kevin Fenzi <kevin(a)scrye.com&gt; wrote:
>
> > Greetings.
> >
> > I am sending this to the devel and spins lists. Feel free to forward to
> > other places people who might be affected by it should see it.
> >
> > Some history:
> >
> > We setup the spin-kickstart project on fedorahosted a long time ago.
> > At the start it was just the various spins and it's trac instance was
> > used in the new spins workflow. Then, it was a handy place to put the
> > dvd iso kickstart that releng made also. Then over time we added cloud
> > and docker and everything else that used a kickstart to it. In the
> > start we added some bugzilla components for the various spins for end
> > user bugs, and used the trac for workflow things. Over time due to
> > all the images there lots of people have been given commit access to
> > the repo. Then the spins sig went quiet and we have sort of been limping
> > along since then with trac tickets not getting to anyone who cares,
> > etc.
> >
> > I'd like to propose the following plan of action:
> >
> > * Setup a new project at pagure.io called just kickstarts or
> >   releng-kickstarts or something. (Bikeshed alert).
> >
> > * Setup tags for all the various groups that have kickstarts. ie,
> >   'xfce' 'docker' 'cloud' 'atomic'
> 'workstation' etc. And get someone
> >   from each of those groups to actually watch the tags or someone to CC
> >   on who will actually look at those tagged issues.
> >
> > * Reduce the number of commiters a bunch and ask people to submit PR's
> >   when they want a change. This will allow releng/qa to control changes
> >   when in freeze. ie, we can require a freeze break and point to the
> >   PR/bug with the exact change and merge it when it's approved.
> >
> > * Copy the git repo over to it from fedorahosted. Close that repo.
> >
> > * Mass close all the fedorahosted trac tickets and close trac to new
> >   ones with a note to file new issues in pagure. ( 21 tickets
> >   currently): https://fedorahosted.org/spin-kickstarts/report/1
> >
> > * Close the "LiveCD*" components in bugzilla to new bugs and close any
> >   existing ones with a note to refile at pagure. (18 bugs currently):
> >
> >
> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASS...
> >
> > * Adjust koji config to pull from pagure.io instead of fedorahosted.
> >
> > Thoughts? Additional steps? Better plans?
> >
> > kevin
> > --
> > devel mailing list
> > devel(a)lists.fedoraproject.org
> > http://lists.fedoraproject.org/admin/lists/[e-mail]
> >
>
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  http://lists.fedoraproject.org/admin/lists/[e-mail]
>
>

[Colin Walters]

On Fri, Feb 19, 2016, at 02:37 PM, Kevin Fenzi wrote:

>  * Setup tags for all the various groups that have kickstarts. ie,
>    'xfce' 'docker' 'cloud' 'atomic' 'workstation'
> etc. And get someone
>    from each of those groups to actually watch the tags or someone to CC
>    on who will actually look at those tagged issues.  
I'm not familiar with tags, and how different groups would interact with the
single git repo, but I'm sure I can figure it out over time.

Basically, sounds good to me.

[Corey Sheldon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

feel free to CC me  on that, I work kk4ewt  on the updated respins ( re
spun with kernel drops in stable) and as a ambassador I evangelize each
one  (minus gnome -- sorry not my taste :) ).    co 
corey84(a)fedoraproject.org || irc:linuxmodder

On 02/20/2016 09:16 AM, Colin Walters wrote:
>  > > On Fri, Feb 19, 2016, at 02:37 PM, Kevin Fenzi wrote: >
> >> * Setup 
tags for all the various groups that have kickstarts. ie, >> 
 'xfce'
'docker' 'cloud' 'atomic' 'workstation' etc. And get
someone >>   from
each of those groups to actually watch the tags or someone to CC >>   on
who will actually look at those tagged issues. > > I'm not familiar with
tags, and how different groups would interact with the > single git
repo, but I'm sure I can figure it out over time. > > Basically, sounds
good to me. > -- > devel mailing list > devel(a)lists.fedoraproject.org >
http://lists.fedoraproject.org/admin/lists/[e-mail]

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJWyHjIAAoJEHeOgyS7CC5mo9gP/1aE2LXHP7nR2HBHbBauZ4nX
> 4szkLqio7zsRlaaRDmqexguNL4N5rm5V4HCvH48+GvhQRVJ82ZUbzzfbLEaz7tD/
> iozQ0bTiE23Lm+WU+0UXq4QPqDBPt1sfC3lPLbMZ3Sn11CZl+FryQ2MoChXtgmFz
> wFOw4zkjXwyuheGoT+ZtIRBkCz8rvd/qRpKQ/02lGqhXWuQmxzFr74C3hXdNszQc
> pe34hLTw/8h7VfpQatptDp20FwXXv1y5D2oEi6zV4IZ95vJTB1VV5mwaniHGD8GM
> XkJBY7GNB9hrdtCJHmDmvMiDW4JKlYc2ry0Z84WezaW1fHHTTI51RbZwomsoD65L
> HQhIVENROxiyMvyYHljkH7zTWBKleyTSgQQMzUHM5Kjiq+DALVE9v9OqxTd8lTon
> TqAcpp7A16/PXuxS4XKjfaiJW0mNVnjbQ9BaEOrQxBcXjbVCc230iekFxl0Zvpy7
> dQZAN/jPEzAUsHFtqTSDXz9dt0X67Vg2DJcGzA0w2RlZ6zRarcNQ3couM14t1PML
> gTRTOyqWzFivwG4C7mrZSq/RVKi7OS1dCXksAcReDAVcIV9JtiAdgkXEsieHbNZG
> Sq/PdPw8Q81WeA1muydexu0Q9ujb5JXL/2LfrfElSUQSgPtO+DmkhkUo8Fk5PKtP
> qCkd/7WWe+zjHQLmiazA
> =NOex
> -----END PGP SIGNATURE-----

[Adam Miller]

On Fri, Feb 19, 2016 at 1:37 PM, Kevin Fenzi <kevin(a)scrye.com&gt; wrote:
>  Greetings.
>
>  I am sending this to the devel and spins lists. Feel free to forward to
>  other places people who might be affected by it should see it.
>
>  Some history:
>
>  We setup the spin-kickstart project on fedorahosted a long time ago.
>  At the start it was just the various spins and it's trac instance was
>  used in the new spins workflow. Then, it was a handy place to put the
>  dvd iso kickstart that releng made also. Then over time we added cloud
>  and docker and everything else that used a kickstart to it. In the
>  start we added some bugzilla components for the various spins for end
>  user bugs, and used the trac for workflow things. Over time due to
>  all the images there lots of people have been given commit access to
>  the repo. Then the spins sig went quiet and we have sort of been limping
>  along since then with trac tickets not getting to anyone who cares,
>  etc.
>
>  I'd like to propose the following plan of action:
>
>  * Setup a new project at pagure.io called just kickstarts or
>    releng-kickstarts or something. (Bikeshed alert).
>
>  * Setup tags for all the various groups that have kickstarts. ie,
>    'xfce' 'docker' 'cloud' 'atomic' 'workstation'
> etc. And get someone
>    from each of those groups to actually watch the tags or someone to CC
>    on who will actually look at those tagged issues.
>
>  * Reduce the number of commiters a bunch and ask people to submit PR's
>    when they want a change. This will allow releng/qa to control changes
>    when in freeze. ie, we can require a freeze break and point to the
>    PR/bug with the exact change and merge it when it's approved.
>
>  * Copy the git repo over to it from fedorahosted. Close that repo.
>
>  * Mass close all the fedorahosted trac tickets and close trac to new
>    ones with a note to file new issues in pagure. ( 21 tickets
>    currently): https://fedorahosted.org/spin-kickstarts/report/1
>
>  * Close the "LiveCD*" components in bugzilla to new bugs and close any
>    existing ones with a note to refile at pagure. (18 bugs currently):
>   
> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASS...
>
>  * Adjust koji config to pull from pagure.io instead of fedorahosted.
>
>  Thoughts? Additional steps? Better plans? 
Seems like a logical plan that would offer us a lot of improvements
over the current workflow. Sounds great! +1

-AdamM

>
> kevin
>
> --
> devel mailing list
> devel(a)lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/[e-mail]
>