Wow, a lot of questions.
I'll try and answer my views on some of them below:
On 2014-09-30 15:58, Bob Brighton wrote:
As per Stef Walter's suggestion that I ask these questions here
(rather than on github), please find below my "Product Management"
What is this project's relationship with Project Atomic?
Colin Walters, who's deeply involved in Atomic used to be on the Cockpit
I want Cockpit to be able to run on Atomic systems, and be able to
handle things like it's specific OS upgrade model. Cockpit will need to
be modular enough that for more traditional distributions can use
another upgrade method with packages and all. I think the UX will be
fairly similar though.
I find docker containers interesting and useful in general, also for
running under more traditional distros. So any Atomic work will benefit
the more traditional distros too.
Do you have any goals to explicitly support other distributions
(Ubuntu, SUSE etc.)?
I want Cockpit to shine regardless where it runs. Or rather, to make
whatever Cockpit runs on to shine thanks to Cockpit.
I hope that Cockpit is useful enough to others to package and
Current version (on Fedora 21) is 0.25-1, what is the criteria for
At the very least to with confidence be able to recommend someone to run
it in actual production.
How is the project team structured? Do you each have formal roles and
I'll introduce myself.
I'm a designer. I sketch out the UI's, do UI reviews, graphics and
good at programming)