On Tue, 2016-03-15 at 14:11 -0400, Matthew Miller wrote:
On Tue, Mar 15, 2016 at 12:30:18PM -0400, Matthias Clasen wrote:
>
>
https://fedoraproject.org/wiki/Workstation/AtomicWorkstation
> has some answers to your questions.
It does, thanks. I did look at that before but had forgotten some of
it -- and it's a really nicely done document, so that's on me. Thanks
for the reminder.
However, when it gets to the "applications" and "developer needs"
portions, it's more about possibilities and plans than concrete
steps,
which is where I'm worried about the practical aspects.
If we're going to make this as a prototype/demo/toy for F25, with a
goal further out, that's not a problem. But if we want to deliver all
of that by then, we really need to step up in resources. Take a look
at
https://fedoraproject.org/wiki/ReleaseEngineering/PriorityPipeline —
support for ostree-based Workstation is there, but there's nothing
for
application delivery as xdg-apps or the "different installation
mechanism" mentioned in Owen's doc.
I hope my initial mail did not give the impression that 'we have it all
perfectly planned out and all the work is done, lets just ask for the
rubberstamp'. Figuring out all the required pieces and collecting them
on a Change page is supposed to be the result of discussing this in the
WG, not the input to that discussion...
>
> As for closer alignment with Atomic, I have heard both your opinion
> (yes, make this part of the atomic umbrella) and the opposite (no,
> atomic is already too much of a grab bag of stuff). I personally
> think
> aligning with Atomic is the right idea.
Yeah, I hear the grab-bag thing too. I don't think we should put
anything under the name _without_ also have the alignment with
technology. And, the other way around, it's a good idea to align the
technology even if we don't use the name.
Of course, thats why there is 'ostree' in the subject line of the
initial email. We are planning on using rpm-ostree and the regular
Workstation content rpms for this (in fact, David King is already
prototyping this).