FAD Goals and deliverables

Tue May 12 22:07:24 UTC 2015

On Tue, May 12, 2015 at 4:40 PM, Paul W. Frields <stickster at gmail.com> wrote:
> On Tue, May 12, 2015 at 12:10:32PM -0500, Dennis Gilmore wrote:
>> On Tuesday, May 12, 2015 01:03:15 PM Paul W. Frields wrote:
>> > On Mon, May 11, 2015 at 02:57:11PM -0500, Dennis Gilmore wrote:
>> > > On Sunday, May 10, 2015 01:28:13 PM Dennis Gilmore wrote:
>> > > > Hi all,
>> > > >
>> > > > As we get closer to the FAD we need to nail down the deliverables and
>> > > > what
>> > > > we want to achieve by the end of the FAD.  I am going to list some of
>> > > > the
>> > > > things I think we need to have done. feel free to discuss and add
>> > > > things.
>> > > > at the ned we will update the wiki with the deliverables.
>> > > >
>> > > > 1) working pungi 4.
>> > > > 2) integrated ability to make atomic installer and pxe to live in pungi
>> > > > 3) mash ported to createrepo_c
>> > > > 4) rawhide looking like a TC/RC
>> > > > 5) bodhi2 able to trigger atomic installer and pxe to live as part of
>> > > > the
>> > > > update push process.
>> > > > 6) livemedia-creator koji integration
>> > > > 7) koji able to manage the url line in kickstarts so that we can do real
>> > > > builds
>> > > > 8) run-root plugin configured
>> > > > 9) Secondary arches working exactly teh same as primary
>> > > > 10) port pungi to dnf
>> > > > 11) make headway and plan to port to python 3
>> > >
>> > > 12) have koji be able to specify the backend for installing packages into
>> > > chroots on a per target basis. we will need to use yum/yum-deprecated for
>> > > most but we will want to use dnf for rawhide and new releases.
>> > > yum-deprecated will be needed when we move builders to f22
>> >
>> > Here are some things that have been under previous discussion some
>> > time but which I don't see on this list:
>> >
>> > * Koji 2 -- What does it look like?  How does it work vs. current
>> >   Koji?  How will it change compose processes?
>> at this point in time it does not exist at all. we can not assume anything
>> about it. I have asked the koji devs to start planning and get moving, but
>> right now thwere is no such thing.
>
> Right, I didn't mean to imply with present tense that I thought it
> did.  I was more asking for some sort of concept, so that as we are
> building tools we aren't setting up for something that has to be
> completely rewritten 12-18 months from now.
>
>> > * Composedb -- Dennis has talked about this many times.  Is it still
>> >   meant to happen?  Is there e.g. a schema design?
>> Mathieu Bridon was tasked with this but AFAIK there is nothing existing for it
>> yet. Again we need to move forward without it :( though it is something that I
>> do really want. Perhaps he can give us an idea where it stands.
>>
>> > I'm not against items in the previous list getting done at the FAD.
>> > But I guess I was asking what will happen wrt. the revolutionary list
>> > beyond discussion (which is what the list is for).  IOW, leaving the
>> > FAD with a vague consensus that "yeah, we'll take care of all that
>> > with composedb, whatever/whenever that is" would be more like kicking
>> > the can down the road.
>>
>> To me they are Bonus things we need. but they do not come out of thin air. I
>> have tried to keep the list to concrete things that by the end of the FAD is
>> complete and will majorly change the way we produce not only rawhide but
>> Fedora.
>
> There are some great things on that list for sure.  One additional
> thing that needs to be reality by the time the FAD is over, if not
> before (and I realize this is already the province of another thread):
>
> * Establishing git repos/branches and a review process so work on
>   tools happens regardless of what stage the release is actually in.
>
> I would encourage looking at how this is done in the fedora-infra
> related projects, especially since it seems Pagure 0.1.x works for
> that purpose.  It's about more than the tool, though, it's also about
> spreading the ability (and responsibility) for code reviews across
> many people so things can always move forward.
>

The Rel-Eng group has been involved in conversations with the Infra
Team about pagure which is more or less what spawned the thread about
the git workflow in the past[0] so we're definitely trying to keep in
alignment there. +1

-AdamM

[0] - https://lists.fedoraproject.org/pipermail/rel-eng/2015-April/019796.html

>
> --
> Paul W. Frields                                http://paul.frields.org/
>   gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
>   http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
>     The open source story continues to grow: http://opensource.com
> _______________________________________________
> rel-eng mailing list
> rel-eng at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/rel-eng