Fedora Community Conduct Reminder
by Josh Boyer
The Board was recently notified of a serious violation of our Code of
Conduct made on the development list last week. Physical threats of
violence are an egregious offense and may result in further censure or
disciplinary action. While we look into the matter further, we would
like to remind everyone that threats of any nature are not appropriate
and will not be tolerated in our community. Fedora is a welcoming
project and while debates may be heated, they should never be hostile.
The Board
9 years, 10 months
Fedora 18 End of Life
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
As of 14th January 2014, Fedora 18 has reached its end of life for
updates and support. No further updates, including security updates,
will be available for Fedora 18. A previous reminder was sent on
December 18th [0].
Fedora 19 will continue to receive updates until approximately one
month after the release of Fedora 21. The maintenance schedule of
Fedora releases is documented on the Fedora Project wiki [1]. The
Fedora Project wiki also contains instructions [2] on how to upgrade
from a previous release of Fedora to a version receiving updates.
Cheers,
Dennis
[0]
https://lists.fedoraproject.org/pipermail/announce/2013-December/003189.html
[1]
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Sche...
[2] http://fedoraproject.org/wiki/DistributionUpgrades
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJS1ayyAAoJEH7ltONmPFDRr+sP/jP6cyvPiV15obiZALPvsTXq
lciq4XmDeHNW10zk/aXRJg7TZBI9WHjEHhg7USSlOJoSbfKrylLCniWrx/S+Czyw
wIO0sfE8xxc2zWdJAyb+lBBXcnBHrA1kyWJPoeYidb/xrv4TEIXcCft06ntVzOns
DIhaMrGE2HkwDiUH/J+GJ06E00EmJCxm7y+UFX59OHE3stKbo9MxefjP8A3X1Qqv
/Pnl8awJXVxq92co0oO2DFPGJ3NPMn4iKvZnERRwjb+/H/oNbYZwl6eQ4yClBxbE
jAIgNd3mwMMp6V1hU4fngfxUyz27EEb1FfhqzfGZVQANwi5xtMrvLCFZWqDZ41NQ
NkcQjfkqw6/NAXL+MPEKCKQkUSCHxBWtL+J+DF+kEGr7jarXKw/sAyHFaLNEhKS5
TKZuh1Fay8rWmqlOhaTtICK4NV8g03ql75KcKivK7Q4nJCb8wWIyfQp97fiqAFav
iE6+/SzHdGEAaBAymf0cxO8AUmIgmGXRNzDRn8fEQQOj9okOfbzOeRs0f/RbGCLs
RdSUCup/QSq/4W2Laoyh+/iEgFCZcmTIc3ShItEbuVrrW87+5wf6WKH55DO55nM+
JAuKshpZcW9n+fo9WnPgI8xsuUSh4+ZbXe7nO6cOnHy/zOfCV2k1O/Uay3aGMPvF
LLITN5Ux1HHtSVBvor3G
=VpxD
-----END PGP SIGNATURE-----
9 years, 11 months
Adjustments to _hardened_build and %configure macro in rawhide
by Kevin Fenzi
Greetings.
Packages currently using the _hardened_build macro that also use
libtool may have been built only with "partial" RELRO instead of full
RELRO protections.
https://fedoraproject.org/wiki/Security_Features_Matrix#Built_with_RELRO
A workaround has been added today to the redhat-rpm-config package in
rawhide to fix this issue. Maintainers are encouraged to check their
_hardened_build packages to confirm that they rebuild correctly with
full RELRO protections. Additionally since this change is in the
%configure macro used by many packages, maintainers that find
regressions due to this change should file bugs on the
redhat-rpm-macros package or note them in
https://bugzilla.redhat.com/show_bug.cgi?id=978949
You can check your package for RELRO by unpacking it and running the
hardening-check tool from the hardening-check package over it's
libraries.
Thanks,
kevin
9 years, 11 months
rawhide evolution-data-server/libcamel soname version bump
by Milan Crha
Hello,
I'm just updating evolution-data-server to 3.11.4 in rawhide, which
includes a soname version bump for libcamel (it happened before 3.11.3,
but that version didn't reach Fedora rawhide for some reason).
I'll rebuild all affected packages I have commit rights for.
Bye,
Milan
9 years, 11 months
EPEL 7 Development
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All,
Yesterday we opened up epel7 for people to request branches and
contribute to there is a FAQ[1]. The things to note at this point in
time. epel7 is working like rawhide with daily automated composes, we
will endevour to sign all packages but as with any disjointed process
there could be packages missed. The git branch, tagging in koji and
packagedb all use epel7, to support this we needed a minor change to
fedpkg you will need to make sure you have fedpkg-1.15-1 installed, its
currently in updates-testing for fedora 19 and el6 and was not
backported to fedora 18.
you can request your package be branched for epel by filling in the
table at the request page[2]. The list will be processed regularly you
will get emails from packagedb when it is done, additionally you can
also use bugzilla but thats a little more tedious and results in extra
bugzilla noise. closer to going stable we will shut off request via the
wiki.
To see if a package you are interesting in maintaing the full list of
package names in the public beta is also in the wiki[3].
Thanks to everyone that helps with epel7
Dennis
[1] https://fedoraproject.org/wiki/EPEL/epel7beta-faq
[2] https://fedoraproject.org/wiki/EPEL/epel7/Requests
[3] https://fedoraproject.org/wiki/EPEL/epel7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJS0cOXAAoJEH7ltONmPFDRhPUQAJ9k0o3s64jp2BqdJqWSOVsQ
QXRVbpJT7hFleXMT5hBgnKPKK0xdpd4VNAA7bIJ9DI/VlJWKvLZSzmMWI/vEa0Ql
ZjB7ORRyrxcnJIJAtZbhChl1oj4AWRCpBjVe7HiKtGD41nL6LOYdr9KpEO1C5oYT
dM0Uw57SASO1a6p6VN3YGKk9AITmDZm3I30ZeQDBJ/YpbwVmnpyUeJTorTYmgOd7
q5cL8ahC1UhkJ6GOGkiKQSWxwlBpRk0YPXgjf52XqQ5+EEqwIskMye6jOwr4sRKq
8tjYtgXVt1fB83/GaG/wtox4+qft7SKLFqDnn3Z2MQ1s9gmH//iaJ41qIq86hDeE
ChovlehbrAiRR3wmBBxvrRPmh5V5k2HDbMCGU49ONTfkdyzD1q+mVsWWpvR4mGej
nKb6dVX2O64HRKpwARaVgGVAwDRKULMWckQmTIpXbksN3aF4BSn+oNTMK7+jYQ2h
WfOvs0cihd5N2zFjp6m4rrewcjxbava82QUMqErbiEXYMXvs8O8NSH8+NJVJyIW4
v3Gdq9RnZTxGIsECTrChC6waa6endqNJ4DP5KczV0kO4SMfXKRuyNQhA08m48nRH
bYcvaRnLO5LbhSKoNWwrjHw3JokkKjPqyOh33ZvEy5mAgALS0Agp9S5UjbkpS4c4
3RyEMRBvFJVxLE23JOX1
=he3l
-----END PGP SIGNATURE-----
9 years, 11 months
Fedora Server PRD Draft and call for participation
by Stephen Gallagher
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The first deliverable that the Fedora Server Working Group was tasked
with was the production of a Product Requirements Document. This
document is intended to provide a high-level view of the goals and
primary deliverables of the Fedora Server distribution. A great deal
of discussion has gone on during the weekly Working Group meetings as
well as on the mailing list.
At this time, the deadline for the delivery of the PRD is rapidly
approaching. Originally it was due to be delivered for ratification on
Monday, January 13th, but at the FESCo meeting on Wednesday, it was
agreed to delay this deadline by a single week. The primary reason for
this delay was so that the Fedora Cloud and Fedora Server groups could
have some last discussions about overlap and respective areas of
responsibility.
This past Tuesday, we had an all-day PRD hackfest in IRC and have come
up with a fairly strong draft[1]. It is not yet complete (notably,
there remains a FIXME under "Misc. Concerns" and some ambiguity around
the Use Cases), but I believe that it is close enough to its final
form (as envisioned by those people that have contributed to it), that
we should expose this document to the wider world and ask for input
before submitting it to the Fedora Engineering Steering Committee and
Fedora Advisory Board a week from Monday.
Please read through the PRD draft and provide feedback of any sort. If
you see that we have missed or misrepresented any of our statements,
we would very much like to hear this soon.
[1]
https://fedoraproject.org/w/index.php?title=Server/Product_Requirements_D...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlLQUp4ACgkQeiVVYja6o6O8IwCcCIaNJEr919QgyB3XJC+2Ynqf
6PcAoJ2BpgMwi1NzdG2XBZ0nyEzlh9XZ
=DINq
-----END PGP SIGNATURE-----
9 years, 11 months
Fedora 21 election season has begun!
by Christoph Wickert
My fellow Fedorians,
It's time for the Fedora 21 elections. In fact, we are already a little
late: First Fedora 20 was delayed and then we had the holiday season, so
we needed to adjust the schedule a little.
== Election Schedule ==
The Fedora 21 election schedule looks as follows:
* January 8 - 13: Nomination Period
(closes promptly at 23:59:59 UTC on January 13)
* January 8 - 13: Questionnaire form open for the community to
submit questions for the candidates.
* January 13 - 18: Candidates Questionnaire. Results will be
posted to the wiki prior to the first townhall
* January 18 - 23: Townhalls
* January 23 - 30: Voting Period
(closes promptly at 23:59:59 UTC on January 30)
* January 31: Announce Results
== Fedora Board, FESCo, and FAmSCo Elections ==
This election cycle will fill the following seats for a one-year period:
* Fedora Board: 2 elected seats (2 additional seats will be
appointed according to schedule)
* FESCo (Fedora Engineering Steering Committee): 4 elected seats
* FAmSCo (Fedora Ambassadors Steering Committee): 3 elected seats
Full information about the committee elections, including the elections
schedule, and links to where one may nominate, can be seen here:
https://fedoraproject.org/wiki/Elections
== Nominations ==
Nominations are NOW OPEN until 23:59:59 UTC on January 13. I encourage
everyone to consider serving in an elected seat, or to encourage others
that they feel would represent Fedora well to run for election.
== Election questionnaire ==
Additionally, the elections questionnaire is NOW OPEN for adding
questions which will be posed to candidates for the listed groups.
Questions may be added until 23:59:59 on January 13 at
https://fedoraproject.org/wiki/Elections/Questionnaire
Following the closing of the questionnaire, candidates will be asked to
answer questions relevant to the position for which they are seeking
election.
Further information regarding each body's election follows below.
== Fedora Board ==
This election cycle will fill three elected seats for the Board (seats
E3, E4, and E5). Two appointed seats (A3 and A4) will also be filled
this cycle.
https://fedoraproject.org/wiki/Board_nominations
https://fedoraproject.org/wiki/Board/Elections
https://fedoraproject.org/wiki/Board/History
== FESCo ==
This cycle will see candidates elected to five open seats in the Fedora
Engineering Steering Committee. For information on the nominations and
elections, please refer to:
https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
https://fedoraproject.org/wiki/FESCo_election_policy
== FAmSCo ==
This election cycle will see candidates elected to fill four open seats
on the Fedora Ambassadors Steering Committee. For more information,
please refer to:
https://fedoraproject.org/wiki/FAmSCo_nominations
https://fedoraproject.org/wiki/FAmSCo_election_rules
https://fedoraproject.org/wiki/FAmSCo_elections
== Help us! ==
In order to make these elections a success, we need your help:
* First and foremost, we need you to vote.
* Tell others community members to vote.
* Ask questions in the elections questionnaire.
* Run for one of the elected bodies. With the new working groups
and CentOS as our new family member, we have exciting times
ahead. You can shape the future of Fedora and it's community!
* Encourage others that they feel would represent Fedora well to
run for election.
* Attend the townhall IRC meetings and ask the candidates your
questions.
* Volunteer to host the townhalls. We strive to have two meetings
for each body, that means six in total. I would appreciate your
help.
If you want to help out of have any further questions, please don't
hesitate to contact me.
Best regards,
Christoph Wickert
9 years, 11 months