On Thu, Mar 03, 2016 at 05:12:12PM +0000, Tristan Cacqueray wrote: > Hi folks, > > During the sprint 2016-09, the Cobra team have been working on: > > * Update RDOPKG and RDOINFO to support migration from gerrithub to > rpmfactory > * Automatic replication all project from rpmfactory to > https://github.com/rdo-packages/ > * Import of rdo-liberty and rdo-kilo branches > * Improve monitoring of SF services using monit, and proposed to add > collectd > * Automatic deployment of koji+sf using nodepool slave and validation > with a simple distgit package test. > * Fix CAUTH to better support single user mail used from multiple auth > backend (e.g. from github or launchpad) > * Add a Mumble service to SF > * SF-2.1.7 release, 2.1.8 already proposed to implement more polishing > > Not related to SF: > * Many OSSA bug triaged (12 new private bugs reported this sprint) > * Swift Mid-Cycle > * Shade review in progress to support Heat (for Ansible module) > * elections.openstack.org domain is getting finalized > > Bluejeans record: https://redhat.bluejeans.com/m/9dPH/ > Review: http://softwarefactory-project.io/etherpad/p/sprint_review > Retro: http://softwarefactory-project.io/etherpad/p/sf-retro-160303 > So I was looking at the retro and the following caught my eye:
> Black Hat: Bad stuff > No time to work on Software Factory. rpmfactoy every day. Personally, you should seriously consider having the Software Factory team step back from the day to day of RPMFactory. I'll probably sound like the bad guy, but you don't want to get bogged down managing Software Factory deployments, you want to actively develop or maintain Software Factory. I understand why you are doing a lot of work with RPMFactory but I think your first priority should be to transition RPMfactory off ASAP and bring new maintainer into the fold to manage it. This new maintainer should be responsible for actively deploying SF. Obviously this will be a huge undertaking for the new maintainer to learn the ins and outs of openstack-infra CI. I've seen this happen a few time with people running openstack-infra CI in house, they become overwhelmed just trying to maintain the CI system and slowly drift farther and farther from upstream. I would hate to see the SF team start maintaining deployments of CI over training others to do the work. As a data point, the HP Gozer team was about 10-12 people strong just maintaining their shadow instance of upstream CI. Upstream openstack-infra has 9 infra-roots (and countless volunteers) keeping upstream CI working. > Regards, > The Cobra team > _______________________________________________ Softwarefactory-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/softwarefactory-dev
