The nomination period for FESCo and Environments and Stacks Working
Group Elections is now open.
We will be selecting five seats on FESCo  and four seats on Env and
Stacks Working Group . If you are interested in these roles, please
add yourself to the lists of nominees at  and  before 23:59:59
UTC on January 19, 2015! If you wish to nominate someone else, please
consult with that person ahead of time. If you know someone who would
be a good candidate, now is a great time to make sure they're thinking
If you have questions you'd like asked of candidates, please add them
to the <https://fedoraproject.org/wiki/Elections/Questionnaire> wiki
page. Nominees will answer these questions and the answers will be
published simultaneously on January 26th as part of campaign period.
Questions may be moderated to fit Fedora Magazine interview format.
No FAmSCo elections are held this time as FAmSCo is discussing the
new committee format.
* January 13-19: Nomination period open
* January 20-26: "Campaign" period.
* January 27 - February 03: Voting open
* February 04: Results announcement
devel-announce mailing list
My name is Jakub Jelen and I am from Czech Republic. I'm member of
fedoraproject for a long time, but now will get more active and I will
be responsible for future releases of some security components in
Fedora. I have almost one year experience in Red Hat with helping to
test security components, creating new test cases and communicating
results with developers and testers. But packaging and maintaining is
for me another new challenge. I will be visible in Fedora project under
common name JJELEN.
I'm fan of opensource, linux and stuff like that for a long time. I
didn't contribute much yet, so I hope I will have the opportunity to do
In free time I like to travel, visit different places and meet new
I look forward to future cooperation with you and thanks you all for
It has happened again. :-/
| This message is a notice that Fedora 19 is now at end of life. Fedora
| has stopped maintaining and issuing updates for Fedora 19. It is
| Fedora's policy to close all bug reports from releases that are no
| longer maintained.
As I found it odd, that again I would receive so many bz mails for old
tickets, initially I had started taking a look at some, but there are too
many packaging issues where the packagers don't respond because they
dislike Fedora's packaging guidelines.
It's not managable for me to revisit them all. I also cannot jump in and
take over work, such as resolving implicit conflicts between packages.
Especially for implicit conflicts, a reminder:
Implicit conflicts are _nasty_ and so far are not detected by package
tools prior to the transaction check. What does that mean? Dependency
solving and downloading of possibly huge packages will be done without
indicating a problem, only to fail before installing the packages. All
the user then can do is to try excluding a package somehow, which may be
difficult if it's pulled in as a dependency.
I've also noticed a few version upgrade requests with no response from
the package maintainer -> potentially unmaintained Fedora packages.
This is not encouraging.
I'm maintainer of asciinema package and need some help from more
The upstream was rewritten from Python to Go lang. Because I haven't any
experience with Go packaging, I'll be happy if somebody take a look. Spec
and srpm files are in bugzilla .
The second thing: the upstream project was renamed from asciinema to
asciinema-cli. Should I rename package too and set asciinema pkg as
obsolete? And what about binary - should it be asciinema-cli with symlink
to asciinema or just leave it as it is? I prefer to leave it as asciinema
but I'm not sure if it's ok.