Hi, sorry I have been inactive lately in the Workstation WG: I managed
to attend the last week after a long break.
Now with the end of DST the meeting time becomes 1am for me, which is
not really possible for me... I missed the discussions about the
change of time last time, but I am wondering now if it is possible to
start the meeting earlier in the day (2+ hours earlier would be great
Hi folks, due to travel and various obstacles, we're not able to host a recorded demo this month. Instead we've put together a status report that includes some additional highlights we think you might be interested in. If you have feedback and/or think this works well, I'd love to know b/c I think this vehicle covers more information than a demo alone so I might do both in the future if it's worth it.
Apologies for missing the actual show and tell - if there's anything you'd like to see specifically, I'm sure we can arrange something.
To prepare for the anticipated release of Fedora 25, we have started the
process of drafting the Fedora 25 release announcement and press release.
The release announcement needs the most input. I have based it on the
Fedora 25 beta release announcement and will be going through the document
today to clean up any obvious beta mentions. Members of each workgroup
should focus on:
* Additional features to highlight that were not in the beta announcement
* Important stories that you think this announcement should be telling
* Particular focus on the change from "Cloud" to "Atomic."
The press release is templated from the Fedora 24 press release and will
be revised based on the release announcement.
Therefore, the priority is on the release announcement, and feedback should
be given to that document by close of business (2100 UTC) November 7, 2016.
----- Original Message -----
> On 31 Oct 2016, at 11:41, Richard Hughes <hughsient(a)gmail.com> wrote:
> > On 30 October 2016 at 01:26, Adam Williamson <adamwill(a)fedoraproject.org>
> > wrote:
> >> 1) Both dnf and GNOME Software / PackageKit default to performing
> >> fairly data-hungry transactions in the background, out of the box,
> >> without telling you about it. GNOME's is particularly bad, as it will
> >> happily download available updates in the background, which can be
> >> gigabytes worth of data.
> > If you're on an "unmetered" connection type...
> How does a connection become "unmetered"? It can't just be on interface type,
> as I have metered connections on all interface types, so presumably you use
> some form of web service to distinguish "metered" from "unmetered" based on
> a list of known IP blocks?
> Or do you simply assume that all connections are metered until the user says
They're metered unless you either tag them as unmetered, or hints are provided
to NetworkManager by what you're connected to. For example, Android tethering
is automatically tagged as metered as Android provides a hint in its DHCP