Greetings.
With our driving force leaving us (thanks for all your work sgallagh!) I figured it might be good to discuss a few things.
First: Meetings.
With adding new folks, is the current meeting time still good? Or should we look at a new one?
I'd like to propose that we do a rotating chair/organizer like FESCo does. This means that each meeting we pick the next meeting organizer and they are responsible for gathering agenda items and inviting anyone that needs to be invited and running the meeting. It's really not that difficult, but if we rotate it around it keeps any one person from burning out.
Second: Plans.
F24 is pretty much in the can (of course we need to maintain things and fix bugs and help test, but we aren't going to be doing any new development on it now).
What do people want to focus on for f25? or beyond? There are a number of things we could work on:
* More roles
* Layered docker images (once those are all setup to build/work)
* Your big plan here.
Thoughts? ideas? Dreams?
kevin
On 05/03/2016 12:03 PM, Kevin Fenzi wrote:
Greetings.
With our driving force leaving us (thanks for all your work sgallagh!) I figured it might be good to discuss a few things.
First: Meetings.
With adding new folks, is the current meeting time still good? Or should we look at a new one?
I'd like to propose that we do a rotating chair/organizer like FESCo does. This means that each meeting we pick the next meeting organizer and they are responsible for gathering agenda items and inviting anyone that needs to be invited and running the meeting. It's really not that difficult, but if we rotate it around it keeps any one person from burning out.
Second: Plans.
F24 is pretty much in the can (of course we need to maintain things and fix bugs and help test, but we aren't going to be doing any new development on it now).
What do people want to focus on for f25? or beyond? There are a number of things we could work on:
More roles
Layered docker images (once those are all setup to build/work)
Your big plan here.
Thoughts? ideas? Dreams?
kevin
server mailing list server@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org
Kevin et. al,
The current time works for me (most weeks), however I am flexible to a new time. As to the rotating chair idea I like it for 2 main reasons
1) it helps prevent burnout as you mentioned.
2) It helps foster SIG member involvement and familiarity with the duties and not getting comfy in the back seat per say.
Subject: Meetings and plans
Greetings.
With our driving force leaving us (thanks for all your work sgallagh!) I figured it might be good to discuss a few things.
First: Meetings.
With adding new folks, is the current meeting time still good? Or should we look at a new one?
The current time works for me.
I'd like to propose that we do a rotating chair/organizer like FESCo does. This means that each meeting we pick the next meeting organizer and they are responsible for gathering agenda items and inviting anyone that needs to be invited and running the meeting. It's really not that difficult, but if we rotate it around it keeps any one person from burning out.
Sounds good.
Second: Plans.
F24 is pretty much in the can (of course we need to maintain things and fix bugs and help test, but we aren't going to be doing any new development on it now).
What do people want to focus on for f25? or beyond? There are a number of things we could work on:
- More roles
I also have an interest here.
Layered docker images (once those are all setup to build/work)
Your big plan here.
Automated testing is high on my list as well as continous integration. Getting code into an installable image or an update fast.
Thoughts? ideas? Dreams?
kevin [attachment "attvg26x.dat" deleted by Michael J Wolf/Rochester/IBM] _______________________________________________ server mailing list server@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org
On Wed, 2016-05-04 at 16:59 -0500, Michael J Wolf wrote:
- Your big plan here.
Automated testing is high on my list as well as continous integration. Getting code into an installable image or an update fast.
I'm already working on automating the validation testing. 6 of the validation tests are already automated, now. I'm aiming to have all the tests besides AD automated (via openQA) by Final.
I'm fine with the rotating chair idea, though my involvement is mainly supposed to be to represent QA.
On 05/03/2016 11:03 AM, Kevin Fenzi wrote:
Greetings.
With our driving force leaving us (thanks for all your work sgallagh!)
+1^1000000000000
I figured it might be good to discuss a few things.
First: Meetings.
With adding new folks, is the current meeting time still good? Or should we look at a new one?
Time is fine (at the moment)
I'd like to propose that we do a rotating chair/organizer like FESCo does. This means that each meeting we pick the next meeting organizer and they are responsible for gathering agenda items and inviting anyone that needs to be invited and running the meeting. It's really not that difficult, but if we rotate it around it keeps any one person from burning out.
I would be OK with this.
Second: Plans.
F24 is pretty much in the can (of course we need to maintain things and fix bugs and help test, but we aren't going to be doing any new development on it now).
What do people want to focus on for f25? or beyond? There are a number of things we could work on:
- More roles
More roles is always good. Someone really needs to pick up the rolekit torch and run with it - I can only wish that I had the ability to do so, and it is my main goal for learning Python so I can do just this.
Layered docker images (once those are all setup to build/work)
Your big plan here.
Stephen had a goal of rolekit integration into Cockpit - a GUI driven rolekit. This, I feel, should be our next major target, but it likely won't happen without the aforementioned rolekit developer.
Thoughts? ideas? Dreams?
kevin
server mailing list server@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org
On Tue, May 03, 2016 at 10:03:37AM -0600, Kevin Fenzi wrote:
- More roles
Here's my take, for what it's worth. I like the idea of roles, but for it to really be successful, there should be roles for 90%* of what people want to deploy a Fedora server for, and incentive in the remaining 10% to start collaborative work on creating new roles.
I'm not sure exactly how we get there, though.
* or other arbitrary threshold — enough so that the assumption can be "there's probably a role for that".
Hello all,
I've been subscribed to this mailing list for a long time but have been struggling to find the time to step up and start actively contributing (or even supporting) in any way. Anyway, to the point (I'll introduce myself etc in another mail), is there interest in a Virtual Host role available (outside of just, dnf installgroups) that can be used for either as an independent hypervisor or managed by oVirt?
If not, this will be an area of interest for me to work on.
With regards to meetings - I'm assuming that I can join and contribute despite not being a listed member? I couldn't find much information for newbs specific to server-wg on the wiki.
Cheers, Tim
On 10 May 2016 at 14:21, Matthew Miller mattdm@fedoraproject.org wrote:
On Tue, May 03, 2016 at 10:03:37AM -0600, Kevin Fenzi wrote:
- More roles
Here's my take, for what it's worth. I like the idea of roles, but for it to really be successful, there should be roles for 90%* of what people want to deploy a Fedora server for, and incentive in the remaining 10% to start collaborative work on creating new roles.
I'm not sure exactly how we get there, though.
- or other arbitrary threshold — enough so that the assumption can be
"there's probably a role for that".
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ server mailing list server@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org
On Tue, May 10, 2016 at 02:28:17PM +0200, Timothy Rees wrote:
I've been subscribed to this mailing list for a long time but have been struggling to find the time to step up and start actively contributing (or even supporting) in any way. Anyway, to the point (I'll introduce myself etc in another mail), is there interest in a Virtual Host role available (outside of just, dnf installgroups) that can be used for either as an independent hypervisor or managed by oVirt? If not, this will be an area of interest for me to work on.
Sounds very interesting to _me_ at least, and in line with what I was just saying. :)
With regards to meetings - I'm assuming that I can join and contribute despite not being a listed member? I couldn't find much information for newbs specific to server-wg on the wiki.
Yes, absolutely you can. The basic structure (not just for Server but roughly in general) is that we have a broader SIG (special interest group) which is informal and anyone can join, and a more formal WG (working group) which is responsible to meet regularly and has voting power for hard decisions which require a vote. The WG _should_ represent the core of people who are actually active and doing things, so membership is reevaluated periodically — and it's generally the case that active SIG members will have the opportunity WG members eventually if they want to.
If you want, you can add your name to the SIG "Fan Club" list at https://fedoraproject.org/wiki/SIGs/Server — or, you can just start working. (Hmmm. That page could stand to be updated to clarify what I just said above, for that matter.)
On 05/10/2016 08:28 AM, Timothy Rees wrote:
Hello all,
I've been subscribed to this mailing list for a long time but have been struggling to find the time to step up and start actively contributing (or even supporting) in any way. Anyway, to the point (I'll introduce myself etc in another mail), is there interest in a Virtual Host role available (outside of just, dnf installgroups) that can be used for either as an independent hypervisor or managed by oVirt?
Yes, absolutely. As much as a year ago, I proposed[1] that we should add virt-manager functionality into the Cockpit project. From there, it was suggested that the best approach might actually be for us to work up a role that installed oVirt and for Cockpit to be able to link over to the oVirt UI.
No work (that I am aware of) has actually been done on this yet, but it keeps coming up periodically[2].
If not, this will be an area of interest for me to work on.
If this is something you're interested in, I recommend that we get you and Marek Libra (CCed) in a conversation together. Perhaps we can turn this into an actual project with enough interested people.
With regards to meetings - I'm assuming that I can join and contribute despite not being a listed member? I couldn't find much information for newbs specific to server-wg on the wiki.
Yes! The Server SIG is open to all. There is a governing body called the Server Working Group that exists to make decisions (and resolve conflicts), but anyone who wants to work on the Fedora Server is certainly welcome in the SIG. (And as Matthew noted, people who are doing actual work usually end up being invited to the Working Group when a seat opens up.)
[1] https://github.com/cockpit-project/cockpit/issues/2099 [2] https://lists.fedorahosted.org/archives/list/cockpit-devel@lists.fedorahoste...
server@lists.fedoraproject.org