You have been invited to the following event.
Title: Fedora Release Tools Demo (Live Broadcast)
The hangout will be broadcast live & posted:
Q&A - #fedora-meeting
Purpose: The purpose of a demo is to show our stakeholders what we
completed this iteration, get feedback from them about the changes & set
some context and expectation with them about our direction.
Demo agenda & previous demos can be viewed here:
- Koji signed repos
Signed repos changes in staging instance
- Layered Images
Distgit & pkgdb changes to support containers
Large set of Pungi changes since last demo
Updates to spin kickstarts files
Koji uses livemedia-creator to create livecds instead of
Tunir test automation to verify AMIs in EC2
BugYou official release, docs publication & autocloud plugin
When: Tue Jan 19, 2016 12pm - 1pm Eastern Time
Where: Hangout on Air / YouTube live stream
* acarter(a)redhat.com - organizer
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
desktop(a)lists.fedoraproject.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
Forwarding this invitation could allow any recipient to modify your RSVP
response. Learn more at
Sorry I forgot to post this hear before now, I'm still catching up after
the holidays. I've been a little quiet hear lately, other than my little
rant about chrome, lol. I'm planning to be a lot more active in the
fedora community than I have been, mostly because I like fedora's stance
on free software, and because you guys really take accessibility
seriously. Back on point, the espeak <http:// espeak.sf.net> text to
speech synthesizer was forked about a month ago by reece dunn, the
developer of espeak for android. I have already gotten this added to the
manjaro linux distro, which my linux distribution, sonar, is based on.
The new program is called espeak-ng, the ng standing for next
generation. I would like to eventually get the espeak package in fedora
changed to espeak-ng. There is a problem though. Espeak-ng has not yet
had a formal release. Reece is planning to release one "soon", although
no definite date on when "soon" is, so I'm not sure when to file a
ticket for this. You can check espeak-ng out at,
http://github.com/espeak-ng/espeak-ng.git. The fork was done mainly
because multiple people, me included, have tried getting in touch with
espeak's main developer, johnathan duddington, some going as far as to
get his home address in the UK and his phone number, both of which no
longer seem to be valid. Internally there have been a ton of changes
that make espeak-ng better, most of them well over my head. Espeak-ng
now uses the standard autotools build system, and autodetects your audio
environment so there's no need to specify this stuff in the spec file.
It uses a c99 compiler, whatever in the world that is, lol. My questions
are these. Should I wait until espeak has had a formal release, which
will start out at 1.49.0, continuing the espeak release numbering
scheme, before requesting a package review? I'll need to see if I can
build an rpm spec file that will successfully build and compile first.
I'm not very experienced in this, and as some of you will remember, had
a hard time figuring out on the irc channels. Second, if espeak-ng is
adopted, could this be backported to all supported fedora releases? I'm
not sure if espeak itself, not espeak-ng, will see any further
development, but I doubt it. I'm still new at packaging things for
fedora, so I apologize for all the questions. Espeak-ng will of course
maintain the same license as espeak itself, which is gpl3 or later. I
wouldn't recommend packaging espeak-ng for fedora just yet, since it's
in a state of flux at the moment and sometimes won't build. Any help
would really be appreciated. I am a member of fedora, although I'll have
to try to remember my account info to log in, if I need to file
anything. Any wiki docs would help too, since i don't want to burden
anyone with info that's already available elsewhere that I can read.
Thanks for reading
The Fedora 24 schedule  is winding up, and it's time we started
thinking about what we'd want to have a test day for. There are several
changes accepted already for F24, and the window for proposals is still
open so more may come. You can find the list of accepted Changes here:
Please take some time and look through the list and see if there's
anything you'd be interested in testing - or if there's something you
think should get some testing that isn't in the ChangeSet!
For those of you not familiar with them, a test day is an online event
aimed at testing a specific feature of an upcoming Fedora release. By
utilizing IRC for organization/coordination and a Wiki page for
instructions and results, test days are easy to organize. Anyone can
request to host a test day or request that the QA team help you out
with the organization of the test day. A test day can be run for any
feature or area of a distribution that focused testing would be useful
for. More information on test days can be found here:
To propose a test day, file a ticket on the QA Trac. A full explanation
can be found here:
The SOP for hosting a test day is here:
Traditionally test days have been held on Thursdays, but if you'd
prefer to have it on another day that's fine too. We're pretty
flexible, but having plenty of lead time helps to get the word out.
Just put in your ticket the date or time-frame you'd like, and we'll
figure it out from there.
If you have any questions about test days or the process, please don't
hesitate to contact me or any other QA Team member in #fedora-qa on
Freenode or respond on the test list.
Thanks and happy testing!
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2016-01-06/workstation.20...
Note that we did not have a quorum, so no firm decisions, but I took
some minutes to reflect consensus for the group that showed up.
* * *
#fedora-meeting: Workstation WG
Meeting started by stickster at 15:00:10 UTC. The full logs are
* Roll call (stickster, 15:00:16)
* stickster reverses order of agenda since aday is here (stickster,
* Default installed apps (stickster, 15:08:03)
-- proposed upstream moduleset changes (stickster, 15:11:14)
* Photos is still missing some arguably important core features. While
we don't necessarily need parity to make a default app switch,
consensus is that Photos is not yet meeting a minimum bar to make it
a comfortable default, but probably will be in GNOME 3.22/F25
* Music is in a similar situation (stickster, 15:23:05)
* Shotwell has an additional issue -- not maintained any longer (at
least main fork). Meeting attendees seemed to agree it's worth
taking on the risk of bugs/issues, rather than switching the default
prematurely. (stickster, 15:25:57)
* IDEA: After F24/F25 branching, switch default in Rawhide (pre-F25)
to Music + Photos, with time to revert later if upstream (3.22)
isn't judged ready; F24 defaults (Shotwell, RB) stay same as F23 for
now (stickster, 15:31:43)
* Removing empathy seems to be the general consensus as well, nothing
controversial. Note that mcatanzaro has a patch prepared that will
remove configuration of accounts in g-c-c (making them disappear in
that view to avoid confusion) (stickster, 15:50:48)
* AGREED: (non-voting) General consensus with mcatanzaro's proposal to
keep Workstation default apps aligned with core moduleset upstream,
modulo specific changes (right now, Rhythmbox + Shotwell)
* Missing dnf-langpacks (stickster, 15:52:37)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1286527
* seems to be excluded due to "-@standard" declaraction in
fedora-live-base.ks (stickster, 15:59:51)
* IDEA: mcatanzaro suggests just adding to workstation comps to
compensate (stickster, 16:00:09)
* ACTION: stickster reply on list to Parag to see if we can get fixed
Meeting ended at 16:01:26 UTC.
* stickster reply on list to Parag to see if we can get fixed
Action Items, by person
* stickster reply on list to Parag to see if we can get fixed
People Present (lines said)
* stickster (69)
* mcatanzaro (66)
* aday (19)
* zodbot (10)
* mclasen (9)
* rdieter (6)
* mclasen___ (1)
* aday_ (1)
* linuxmodder (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
Since we moved from yum-langpacks to dnf-langpacks package and yum
to dnf package in Fedora 22+ comps files, we have lost langpacks
plugin in Workstation Live iso. Till Fedora 21 we were having
yum-langpacks package available in Workstation Live iso.
I am not sure what has changed when we moved from yum to dnf but
we need this dnf-langpacks package to be added in the Workstation Live
iso. I have requested this addition against spin-kickstarts package.
Can Workstation WG discuss on this and add dnf-langpacks to
Hi Fedora desktop users and testers,
I'm pushing a git snapshot of Shotwell into F23 and F22 in order to fix
a serious security issue ("Shotwell does not verify TLS certificates").
Upstream is no longer active and I do not expect any further upstream
releases unless someone from the community steps up to maintain it,
hence the decision to package a git snapshot.
What is the impact of the issue? If you ever used any of the publish
functionality (publish to Facebook, publish to Flickr, etc.), your
passwords may have been stolen; changing them is not a bad idea.
What is the risk of the update? Regressions. The easiest way to
validate TLS certificates was to upgrade WebKit; it seems to work but I
don't have accounts with the online services it supports, so I don't
know if photo publishing still works properly on all the services. I've
turned off autokarma so these will spend a full week in updates-
The updates are:
Hope you had a good holiday season.
I propose again some changes to the default apps for F24:
* Empathy - remove without replacement. I use it myself, but I think
I'm a minority -- we don't need to have a chat app installed by default
anymore, since not many people are using the chat protocols supported
by Empathy nowadays. A prominent exception is IRC, but that's only
popular for Fedora/FLOSS developers, not for software developers in
general. Empathy's UI is also looking quite dated. As part of this, we
would remove chat integration from the Online Accounts panel in system
settings. (This is easy; I've already done it for an unrelated
project.) If you want Empathy you can still install it.
* Shotwell -> GNOME Photos. Photos works well for me, and Shotwell is
unmaintained upstream for almost a year now. I'm going to package a git
snapshot for us to get in some security fixes, since I don't expect an
upstream release anytime soon. If you want Shotwell for more advanced
features, you can still install it.
* Rhythmbox -> GNOME Music. I'm using it every day. It works great and
doesn't look like a database frontend. If you want Rhythmbox you can
still install it. There are a couple rough edges left, but it's much
nicer than Rhythmbox overall. One blocker, though: this would need to
be conditional on getting GNOME#747953 (information leak via plain text
HTTP connection) fixed first.
Very odd bug on F23 on the GNOME Wayland session that results in a total
system crash, I have to power cycle the machine in order to reset. When
I'm in overview mode and move windows such as terminals from one monitor to
the other or one workspace to the other I get this crash. See attached
below for bug links.
Do you have any information on this or whether a fix can be backported to
F23 from upstream?
Thank you for any help you can provide!