8:58 a.m.
As per Stef Walter's suggestion that I ask these questions here (rather
than on github), please find below my "Product Management" questions:
1. Does RedHat (project owner/sponsor etc.) dictate or offer guidelines
for the product and project team on: Product Management, Project
Goals, Function/Features, Time-scales/Budget, Methods, Technologies
or Standards used etc.?
2. What is this project's relationship with Project Atomic?
3. Do you have any goals to explicitly support other distributions
(Ubuntu, SUSE etc.)?
4. Do you have any marketing goals / how do you measure (marketing)
success? (Downloads, Forks, Servers being managed,
conferences/presentation/interviews given, contributors, github
watchers, technologies being managed etc.)?
5. Current version (on Fedora 21) is 0.25-1, what is the criteria for
release 1.0?
6. How do you get RedHat, other projects, users and other stakeholder
input into the Project/Roadmap?
7. How is the project team structured? Do you each have formal roles
and responsibilities?
8. How do you decide on type (hard coded HTML/CSS or CMS etc.) of the
project's public web site, its functions (simple, static, one page -
to elaborate social/community site) and what information is
contained in the project website v what is on github/github
wiki/issues etc.?
9. What plans do you have to educate/train the intended audience on the
install/configure/use etc. (YouTube videos, manuals, wiki, user
forum etc.)?
10. Are you incentivised to generate revenue (or additional resources)
by offering consultancy, support or additional features through
“feature sponsorship” etc.?
Thanks
BB
10:01 a.m.
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"
questions:
What is this project's relationship with Project Atomic?
Colin Walters, who's deeply involved in Atomic used to be on the Cockpit
team.
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
redistribute it.
Current version (on Fedora 21) is 0.25-1, what is the criteria for
release 1.0?
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
responsibilities?
I'll introduce myself.
I'm a designer. I sketch out the UI's, do UI reviews, graphics and
implement some html+css (and sometimes javascript, but I'm not really
good at programming)
- Andreas
3494
days inactive
3494
days old
cockpit-devel@lists.fedorahosted.org
1 comments
2 participants
participants (2)
-
Andreas Nilsson -
Bob Brighton