An interesting proposal! Thanks Jef.
I also wonder about how we handle when something that wants to use this
process interacts with existing stable part of the project, but I
suppose we could take those sorts of things on a case by case basis.
and/or try and come up with ways to avoid such entanglements if we can.
How would these sandboxed projects infrastructure be handled?
I don’t think we want to just tell them to build things on their own
dime, but also don’t want to provide them fully staffed and resourced
infrastructure (unless requirements are small). I could see a middle
ground, perhaps leveraging communishift + aws resources (thanks amazon!)
and having the sandboxed project manage things themselves?
I can see this adding load/process to fesco, but perhaps it would be
ok, depending on how many projects were going at once. Would handling
the process here be something the Fedora Operations Architect would take
on? The process of requesting checks/keeping docs flowing/etc I could
see being a lot of work and get off track if someone wasn’t keeping it
flowing along.
Finally, do you know/have some things that might be good candidates for
this sort of process? I would think that if we have some things saying
they would use this process would be very helpful to trying to adjust
the process along with avoiding ‘if you build it they will come’
syndrome. Also, examples might help people see where this process would
be useful/better than not having it at all.
kevin