Re: Brainstorming "ComposeDB"

[Tim Flink]

On Wed, 5 Aug 2015 15:11:17 -0400
Ralph Bean <rbean(a)redhat.com&gt; wrote:

>  On Tue, Aug 04, 2015 at 10:04:51AM -0400, Ralph Bean wrote:
>  > On Mon, Aug 03, 2015 at 10:00:46AM -0400, Ralph Bean wrote:
>  > > On Tue, Jul 28, 2015 at 03:19:28PM -0400, Ralph Bean wrote:
>  > > > If there's anyone interested in spending an hour brainstorming
>  > > > the requirements for a Fedora "composedb" system, we should get
>  > > > together on a video call before Flock.  Here's a whenisgood
>  > > > link so we can figure out a common time:
>  > > > 
>  > > >     http://whenisgood.net/7pinhrc
>  > > > 
>  > > > I'll send out some call details after we get a time nailed
>  > > > down.  If you can't make it, we'll make sure produce some good
>  > > > notes and email those back to the list aftewards.
>  > > 
>  > > I got four responses so far.  Any other takers?
>  > 
>  > Okay, let's shoot for tomorrow, Wednesday August 5th at 16:00UTC /
>  > 12:00EDT.
>  > 
>  > I'll give out a bluejeans link in #fedora-releng around then.
>  
>  
>  It went well!  Here are some notes from the conversation:
>  https://fedoraproject.org/wiki/ReleaseEngineering/ComposeDB 
FWIW, we (Taskotron devs) are also interested in many of the topics
listed in the wiki page. There are certainly bits that still need to be
figured out, though.

On a side note, if you think that Taskotron might work well for the
bits that our production deployment isn't secure enough for, it might
be worth talking about another instance that is secure enough. We
already have 3 instances (dev, stg, prod) so the roles are relatively
flexible and those playbooks will be maintained for the foreseeable
future.

I wonder if it'd be worth trying to sync up a little bit at Flock to
see how far out all this is and where there's overlap so both groups
don't end up implementing some of the same bits :)

Tim