Power saving settings of GDM in Fedora 20
by Sergio Pascual
Hi,
if I log out of the gnome session, my monitor does not put itself in power
saving mode after a time. It used to do it in F19. I suppose this is
related with the power saving settings of the gdm user, whick spawns the
login screen.
I have updated from F19 to F20 via fedup. I do not know if this affects my
system only, everything updated via fedup or all F20 installs.
Regards, Sergio
9 years, 11 months
Re: Draft Workstation WG Governance Charter
by Josh Boyer
On Wed, Oct 30, 2013 at 3:16 PM, Ray Strode <halfline(a)gmail.com> wrote:
> Hi,
>
> On Wed, Oct 30, 2013 at 9:01 AM, Josh Boyer <jwboyer(a)fedoraproject.org> wrote:
>> The other positions will be filled by general election
>> every two years. As a special exception, four seats will be filled in
>> one year, with those positions chosen at random (unless some number of
>> members decide to step down). Voting will follow the standard Fedora
>> election process and be open to all contributors in the CLA+1 group.
>>
>> In the event that a current member relinquishes their seat, that seat
>> will be filled by the first runner up in the previous election. If
>> that person is not able or willing to fill the seat, it will go to
>> each successive runner up until the seat is filled.
>
> I think, I personally, would rather see the previous working group
> decide new members of the working group. They're the ones doing the
> work, so they should get the most say in the direction the work goes.
> (the whole "fedora is a meritocracy not a democracy" thing).
>
> Put another way: I don't think someone who works on desktop related
> software should have much say in who gets to be put in the cloud
> working group, or vice-versa.
>
> Let the people already doing the work decide the continuing direction
> of the work.
> If things really get off course, fesco can intervene, but I don't
> think that will happen.
Fair. To be honest, the more I think about it the more I dislike the
idea of doing full blown elections. They seem overkill and cumbersome
when it comes to coordinating, etc.
In your opinion, should we have term limits imposed to ensure we have
fresh members coming into the WG? As I said in another email, I think
we should shoot for some continuity while also encouraging new members
to step up.
josh
9 years, 11 months
Draft Workstation WG Governance Charter
by Josh Boyer
Hi All,
Below is a draft governance charter for the Workstation WG. I have
taken much of this from the Cloud WG draft charter (found here:
https://fedoraproject.org/wiki/Cloud_WG) to have some commonality
between groups. I left some of the sections from that off for now, as
I think that is their main landing page and we can fill in those
sections with our relevant details as we go.
Please read it over and provide any feedback or ask any questions you
may have. Thanks!
josh
== Fedora Workstation WG Governance ==
This document describes the governing structure for the Fedora
Workstation Work Group.
=== Membership ===
The Fedora Workstation Work Group has nine voting members, with one
member selected by the Fedora Engineering Steering Committee as the
liaison to FESCo.
Members of the Working Group serve two year terms. At the end of the
two year period, FESCo will either renew the FESCo liaison or appoint
a new one. The other positions will be filled by general election
every two years. As a special exception, four seats will be filled in
one year, with those positions chosen at random (unless some number of
members decide to step down). Voting will follow the standard Fedora
election process and be open to all contributors in the CLA+1 group.
In the event that a current member relinquishes their seat, that seat
will be filled by the first runner up in the previous election. If
that person is not able or willing to fill the seat, it will go to
each successive runner up until the seat is filled. If there are no
candidates available or remaining from the previous election, the Work
Group will fill the seat by selecting a candidate and approving by
majority consensus.
NOTE: Clearly all of the above is open for discussion. I've modelled
it after how FESCo current does their membership to a large degree.
If we want something else, please follow up with alternative
suggestions.
=== Current Members ===
* Josh Boyer (FESCo Liaison)
* Matthias Clasen
* Kalev Lember
* Ryan Lerch
* Jens Petersen
* Christian Schaller
* Owen Taylor
* Lukáš Tinkl
* Christoph Wickert
=== Making Decisions ===
Because Fedora is a global project, members of the working group may
be distributed across multiple timezones. It may be possible to have a
real-time IRC meetings, but in general we will conduct business on the
mailing list.
Many of our decisions can be made through "lazy consensus";. Under
this model, an intended action is announced on the mailing list,
discussed, and if there is no controversy or dissenting views with a
few days, simply done.
For bigger issues, where there may be disagreement, or where there is
long-term impact, or where an action may not easily be undone, we will
[1]... Working group members can vote +1 to approve, -1 to disagree,
or 0 to abstain; five +1 votes are necessary for a measure to pass.
Non-members may comment on the item and (of course) discuss on the
mailing list, but are asked to refrain from putting votes.
[1] NOTE: for the workstation WG, we have the following option for
dispute resolution:
1) Use a trac ticketing system as the cloud WG is doing
2) Come up with an official proposal voting system on the mailing list
(specific "Subject: [Proposal for Vote] ..." or something).
3) Schedule an IRC meeting and do the vote live.
I'm fine with any of these, though I will point out that live meetings
across all of our relevant timezones are difficult. If we choose to
have a trac ticketing system (which can be used for votes and for
people to report issues), I can get that created.
=== Changing these Rules ===
This document will be approved by consensus of the initial Working
Group members and approved by FESCo. After initial ratification, any
substantive changes can be approved by majority vote and sent to FESCo
for acceptance.
9 years, 11 months
Re: Draft Workstation WG Governance Charter
by Josh Boyer
On Wed, Oct 30, 2013 at 10:39 AM, Matthew Garrett <mjg59(a)srcf.ucam.org> wrote:
> On Wed, Oct 30, 2013 at 09:01:52AM -0400, Josh Boyer wrote:
>
>> The Fedora Workstation Work Group has nine voting members, with one
>> member selected by the Fedora Engineering Steering Committee as the
>> liaison to FESCo.
>
> Is the FESCo appointed member one of the nine voting members?
For the initial voting set, yes. Going forward, I've asked FESCo to
clarify that with this ticket to be discussed at today's FESCo
meeting:
https://fedorahosted.org/fesco/ticket/1186
When I asked in IRC, I got different replies from different FESCo
members so they need to clear it up. For now, I'm assuming yes the
liaison will always be a voting member. If that changes, I will
change the draft to reflect that it need not be that way (and probably
flesh out what the role does then).
josh
9 years, 11 months
Meeting Minutes for Workstation WG (2013-10-29)
by Josh Boyer
======================================
#fedora-meeting: Fedora Workstation WG
======================================
Meeting started by jwb at 14:00:02 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-10-29/fedora-worksta...
.
Meeting summary
---------------
* init (jwb, 14:00:03)
* logistics (jwb, 14:05:13)
* desktop(a)lists.fedoraproject.org is the main mailing list for the WG
(jwb, 14:08:29)
* Primary IRC channel will be #fedora-workstation on Freenode (jwb,
14:16:45)
* Next Steps (jwb, 14:20:11)
* ACTION: jwb to send initial draft of governance document to the
mailing list for discussion (jwb, 14:40:56)
* ACTION: cschalle_ to send intial draft of PRD to the mailing list
for discussion (jwb, 14:41:14)
* Open Floor (jwb, 14:45:31)
Meeting ended at 15:04:07 UTC.
Action Items
------------
* jwb to send initial draft of governance document to the mailing list
for discussion
* cschalle_ to send intial draft of PRD to the mailing list for
discussion
Action Items, by person
-----------------------
* cschalle_
* cschalle_ to send intial draft of PRD to the mailing list for
discussion
* jwb
* jwb to send initial draft of governance document to the mailing list
for discussion
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jwb (117)
* juhp (30)
* cwickert (30)
* sgallagh (26)
* mclasen (23)
* hadess (22)
* cschalle_ (22)
* kalev (14)
* ltinkl (12)
* otaylor (11)
* ryanlerch (9)
* zodbot (8)
* halfline (1)
* Kevin_Kofler (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
9 years, 11 months
Agenda for Today's Workstation WG Meeting (2013-10-29 14:00 UTC)
by Josh Boyer
My apologies for the last minute agenda. We'll be holding our initial
WG meeting today at 14:00 UTC in #fedora-meeting on Freenode. We'll
cover the various items below. I will try and keep the meeting under
1 hour.
== Logistics ==
- mailing list(s)
- IRC channel(s)
- Meeting frequency and times
- Trac instance?
== Next Steps ==
- Discussions around the WG governance charter
- PRD
== Open Floor ==
9 years, 11 months
Announcing the Workstation Working Group
by Josh Boyer
The initial Fedora Workstation Working Group has been formed and
ratified by FESCo as of yesterday. FESCo has appointed me as the
coordinator and I am pleased to announce the following people as
members of the initial voting group:
Owen Taylor: He will be able to discuss upstream Gnome plans and adds
a lot of knowledge on desktop interactions.
Kalev Lember: He will be able to provide community focused input and
feedback into what is needed for a successful workstation product.
Christoph Wickert: Long time Fedora member, will bring experience from
both XFCE and LXDE desktop environments. Can help with
inter-operability aspects between DEs, etc.
Lukáš Tinkl: Long time core KDE developer. Will be able to provide
feedback and insight into that DE as well as what that class of user
looks for in a workstation.
Jens Petersen: Will add i8n and developer experience to the team,
helping the workstation product in those areas.
Ryan Lerch: Fedora Design representative. Will help with UI and design
experience.
Matthias Clasen: GNOME desktop team lead. Lots of experience with
Fedora and GNOME in a variety of aspects.
Christian Schaller: Desktop manager and Fedora packager. Brings a good
knowledge of workstation products.
Josh Boyer: Coordinator.
While the above people are the initial voting members, I want to
strongly stress that we are looking for participation from anyone
wishing to produce a high quality Workstation product. This is
especially true if you are a member of another group that will be
impacted, such as QA, rel-eng, etc.
Logistics
We are still working out details on our meeting times and IRC
channels. For the time being, we will be using the
desktop(a)lists.fedoraproject.org for our mailing list. Once we get
further details worked out, we'll announce them here and on that list.
Thanks!
josh
9 years, 11 months
Getting the desktop image size under control
by Matthias Clasen
I've been looking at the desktop image size again this afternoon. We're
still some 7M over. I've found a few things in /usr/share/doc that
should not be there, but that is not quite enough. Since gnome-software
will debut in F20 and allow us to have a reasonable search for
applications, I'm going to suggest that we remove
gnome-boxes
gnome-dictionary
prelink
which will probably get us here. gnome-boxes has been called out as
problematic on the live image before since it being present has
side-effects for network configuration
( https://lists.fedoraproject.org/pipermail/desktop/2013-August/008140.html ).
I'll make these changes soon, unless there is strong opposition. In that
case, please be prepared to suggest alternative cuts.
9 years, 12 months
Fedup to f20 didn't automatically pull down gnome-software
by Ryan Lerch
I recently just did a fedup from f19 to f20, and the new gnome-software
application was not installed after the upgrade.
Is this something that should have occurred? if so, where should i file
this bug?
cheers,
ryanlerch
10 years
