Excerpts from Michael K. Johnson's message of 2014-03-18 11:40:57 +0100:
> Just to be clear, there are definitely people in the Fedora community
> who know what we are doing.

are there people discussing what we are doing?

> My intent has been the usual open source way: get something minimally working
> before advertising.  Not keeping quiet, just not advertising until there is
> something that people would want to test.

i am fully on board with that.

> If the f20 import isn't up and running in two months, I'll be surprised
> and sad.
> So there should be something to say.

indeed, my thoughts too.

> > the deadline to submit a talk is the 20th of march noon EST!
> > http://tinyurl.com/FUDConAPAC2014CFP
> > 
> > i can probably work out a presentation in the next two months, but i would 
> > need
> > help making a submission. (an outline of what to talk about would help a 
> > lot, i
> > can work out an abstract based on that)
> 
> I'm afraid that this is where I fall down.  I'm not sure I'll be
> much help.

uhm, on the contrary it appears. what you wrote is almost as good as an 
abstract in itself :-)

[ text snipped ]

i'd just like to copy-paste this text as a whole into the submission form :-)

> In summary, I see several points of potential interest to the Fedora
> community:
> 
> * Enabling Fedora users to consume Fedora using a rolling model.
> 
> * Demonstrating a new way to build a Fedora remix, one that takes
>   advantage of the rolling model and helps the remixes stay current.
> 
> * Contributing to upstream quality by catching certain classes of
>   bugs prior to release.
> 
> * Using Conary's extensive package build automation to make it easier
>   to build better packages for Fedora.

can you elaborate how we would do that?
a recipe that depends on and invokes rpm build tools and spits out an
encapsulated rpm instead of a native conary package?

well, i suppose it would be a factory that can handle all rpm packages
otherwise a packager would have two, the conary recipe and the rpm spec to
manage for each package.

> Does that seem like something you would feel comfortable talking to?

it does very much so.

the summary is just the kind of outline i was looking for.
i found nothing that i could add or remove from it or from the text.
i'd present the talk as made by the foresight development team with me just
acting as a speaker.

greetings, martin.

-- 
eKita                   -   the online platform for your entire academic life
hackerspace beijing     -                                    http://qike.info
-- 
chief engineer                                                       eKita.co
pike programmer      pike.lysator.liu.se    caudium.net     societyserver.org
BLUG secretary                                                 beijinglug.org
foresight developer  foresightlinux.org                            realss.com
unix sysadmin
Martin Bähr          working in china        http://societyserver.org/mbaehr/

_______________________________________________
Foresight-devel mailing list
[email protected]
https://lists.foresightlinux.org/mailman/listinfo/foresight-devel

Reply via email to