= Proposed Self Contained Change: Fontconfig cache directory change =
https://fedoraproject.org/wiki/Changes/FontconfigCacheDirChange
Change owner(s):
* Akira TAGOH <tagoh AT redhat DOT com>
The fontconfig cache files are placed onto /var/cache/fontconfig now.
this seems incompatible with the ostree model. so this is a proposal
to move it to /usr/lib/fontconfig/cache.
== Detailed Description ==
The fontconfig cache files are placed onto /var/cache/fontconfig now.
this seems incompatible with the ostree model. so this is a proposal
to move it to /usr/lib/fontconfig/cache as proposed at #1377367 [
https://bugzilla.redhat.com/show_bug.cgi?id=1377367 ]
== Scope ==
* Proposal owners: Rebuild the fontconfig package with the changes of
the proposed cache directory.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Greetings,
FAmSCo elections are now open and we're looking for new candidates:
https://fedoraproject.org/wiki/Elections
For FAmSCo we have opened seven seats:
https://fedoraproject.org/wiki/FAmSCo_nominations
The Elections schedule is as follows:
* December 13 - December 19: Nomination period open (closes promptly at
23:59 UTC on December 19th)
* December 20 - January 09: Campaign period. Individual blog posts, etc.
encouraged. We will also have an interview with answers published on the
Fedora Community Blog.
* January 10 - January 16: Voting open (closes promptly at 23:59 UTC on
January 16th)
* January 17: Results announcement
Elections Questionnaire needs more questions for email/Community blog
interviews! If you have anything you would like to ask candidates to
FAmSCo, please add it to the wiki.
https://fedoraproject.org/wiki/Elections/Questionnaire#FAmSCo
Read more about the FAmSCo at:
https://fedoraproject.org/wiki/Fedora_Ambassadors_Steering_Committee
Thanks for your support,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Beginning with Fedora 26, the i686 architecture is officially being
migrated to alternative architecture status. This completes a
transition that began with Fedora 24 where i686 was not being
prioritized at a kernel or Edition image level, and that continued
into Fedora 25 where i686 media was no longer blocking or created in
several Editions.
Specifically, i686 will continue to be built in koji as all
architectures are today under the new definitions of Alternative
Architectures [1], and will also still be present in x86_64 media and
repositories for multilib where applicable. The i686-only repositories
have been migrated off of the primary mirror location and will be
served from the alternative mirror location [2].
Community members that wish to continue development of i686 are
encouraged to form a SIG and collaborate to keep packages building and
well tested on such hardware.
--FESCo
[1] https://fedoraproject.org/wiki/Architectures/RedefiningSecondaryArchitectur…
[2] http://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/
There will be an outage starting at 2016-12-16 16:00 UTC, which will
last approximately 4 hours.
To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2016-12-16 16:00 UTC'
Reason for outage:
We will be moving backend storage for pagure.org to a larger volume and
increasing it's size to handle further growth in the coming year.
Affected Services:
All services on .pagure.org / .pagure.io
Contact Information: infrastructure @lists.fedoraproject.org
Please join #fedora-admin in irc.freenode.net or add comments to the
ticket for this outage above.
It is with great pleasure that the Fedora Project Announces the availability
of the Fedora Docker Layered Image Build Service[0] to the Fedora Contributor
Community!
With this announcement we are opening availability of the Docker Layered
Image Build Service for the Docker Layered Images[1] that the Fedora Cloud
SIG[2] has been the primary maintainers[3] of on GitHub into DistGit as
official components of Fedora. From there we will be extending an invitation
to all Fedora Contributors to maintain Docker Layered Image Containers for
official release by the Fedora Project. Currently this effort is to enable
the Fedora Cloud/Atomic WG[2] goals which target Fedora Atomic Host[4] as a
primary deliverable to power the future of Cloud. This is also to enable the
Fedora Modularity[5] work be delivered as Containers in the future as Fedora
becomes fundamentally more modular in nature.
How do I get started?
Contributors will go through a simliar process as what they currently do
with RPM Review Requests. There will be Container Reviews as well as
Container Guidelines:
https://fedoraproject.org/wiki/Container:Review_Processhttps://fedoraproject.org/wiki/Container:Guidelines
At this time the Cloud/Atomic WG[2] will maintain the Guidelines as well as
the Review Process along with input from all Fedora Contributors. This may
change later with the formation of a Fedora Container Committee (similar to
the Fedora Packaging Committee[6]).
Please note that both the Guidelines and the Review Process are likely to
evolve along with the Container technologies as we move into the future so
we encourage community members to check the documentation for updates.
For more information, please see the following Fedora Community Blog:
https://communityblog.fedoraproject.org/fedora-docker-layered-image-build-s…
[0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
[1] - https://fedoraproject.org/wiki/Cloud
[2] - https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
[3] - https://github.com/fedora-cloud/Fedora-Dockerfiles
[4] - https://getfedora.org/en/atomic/download/
[5] - https://fedoraproject.org/wiki/Modularity
[6] - https://fedoraproject.org/wiki/Packaging_Committee
Greetings,
FESCo and Council elections are now open and we're looking for new
candidates: https://fedoraproject.org/wiki/Elections
For FESCo we have opened five seats:
https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
For Council we have opened one seat:
https://fedoraproject.org/wiki/Council/Nominations
The Elections schedule is as follows:
* December 06 - December 12: Nomination period open (closes promptly
at 23:59 UTC on December 12th)
* December 13 - January 09: Campaign period. Individual blog posts,
etc. encouraged. We will also have an interview with answers published
on the Fedora Community Blog.
* January 10 - January 16: Voting open (closes promptly at 23:59 UTC
on January 16th)
* January 17: Results announcement
The Campaign period has been prolonged, in these Elections, as it is
expected to have people in many countries away from keyboards during
the Christmas period.
Elections Questionnaire needs more questions for email/Community blog
interviews! If you have anything you would like to ask candidates to
FESCo or to Council, please add it to the wiki.
http://fedoraproject.org/wiki/Elections/Questionnaire
Read more about the FESCo at:
http://fedoraproject.org/wiki/Development/SteeringCommittee
and about the Council at: http://fedoraproject.org/wiki/Council
Thanks for your support,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= Proposed System Wide Change: Ruby 2.4 =
https://fedoraproject.org/wiki/Changes/Ruby_2.4
Change owner(s):
* Vít Ondruch <vondruch AT redhat DOT com>
Ruby 2.4 is the latest stable version of Ruby. Many new features and
improvements are included for the increasingly diverse and expanding
demands for Ruby. With this major update from Ruby 2.3 in Fedora 24 to
Ruby 2.4 in Fedora 26, Fedora becomes the superior Ruby development
platform.
== Detailed Description ==
Ruby 2.4 is upstream's new major release of Ruby. Many new features
and improvements are included.
* Introduce hash table improvement (by Vladimir Makarov)
Improve the internal structure of hash table (st_table) by introducing
open addressing and an inclusion order array. This improvement has
been discussed with many people, especially with Yura Sokolov.
* Binding#irb: Start a REPL session similar to binding.pry
While you are debugging, you may often use p to see the value of
variables. With pry you can use binding.pry in your application to
launch a REPL and run any Ruby code. r56624 introduces binding.irb
which behaves like that with irb.
* Unify Fixnum and Bignum into Integer
Though ISO/IEC 30170:2012 doesn’t specify details of the Integer
class, Ruby had two visible Integer classes: Fixnum and Bignum. Ruby
2.4 unifies them into Integer. All C extensions which touch the Fixnum
or Bignum class need to be fixed.
* String supports Unicode case mappings
String/Symbol#upcase/downcase/swapcase/capitalize(!) now handle
Unicode case mappings instead of only ASCII case mappings.
* Performance improvements
Ruby 2.4 also contains the following performance improvements
including language changes:
-- Array#max, Array#min [x, y].max and [x, y].min are optimized to not
create a temporary array under certain conditions.
-- Regexp#match? Added Regexp#match?, which executes a regexp match
without creating a back reference object and changing $~ to reduce
object allocation.
-- Speed up instance variable access
* Debugging
Thread#report_on_exception and Thread.report_on_exception Ruby ignores
exceptions in threads unless another thread explicitly joins them.
With report_on_exception = true, you can notice if a thread has died
due to an unhandled exception.
Thread deadlock detection now shows threads with their backtrace and
dependency Ruby has deadlock detection around waiting threads, but its
report doesn’t include enough information for debugging. Ruby 2.4’s
deadlock detection shows threads with their backtrace and dependent
threads.
== Scope ==
* Proposal owners:
- Finish packaging of Ruby 2.4. Current changes available in
private-ruby-2.4 branch of ruby package in dist-git.
- Rebuilding of Ruby packages providing native extensions (i.e.
packages which depends on libruby).
* Other developers:
Rebuild of packages with binary extensions (i.e. packages which
depends on libruby) will be handled automatically, but some packages
might need fixes/updates to support Ruby 2.4 properly.
* Release engineering:
* Separate Koji tag for package rebuild will be needed.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= Proposed Self Contained Change: Golang buildmode PIE =
https://fedoraproject.org/wiki/Changes/golang-buildmode-pie
Change owner(s):
* Jakub Čajka <jcajka AT fedoraproject DOT org>
Change default build mode of golang in Fedora packaging macros to
buildmode=pie, which results in packages using them to produce
Position Independent Executables. Another part of the change is to
pass the Fedora hardened linker flags to the external linker(regular
system linker). In result reducing exploit-ability of binaries.
== Detailed Description ==
Change default build mode of golang in Fedora packaging macros to
buildmode=pie, which results in packages using them to produce
Position Independent Executables. Another part of the change is to
pass the Fedora hardened linker flags to the external linker(regular
system linker). This will only affect packages that depend on golang
packaging macros for their build. This should be first step towards
mandating this on all packages that provide binaries based on golang
in whole distribution via Go packaging guidelines(which is out of
scope for this change proposal).
== Scope ==
* Proposal owners:
change the Go packaging macros, resolve possible issue encountered
* Other developers:
help with resolving any issues encountered
* Release engineering:
none as mass-rebuild is scheduled
* List of deliverables:
N/A (not a System Wide Change)
* Policies and guidelines:
none
* Trademark approval:
N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= Proposed System Wide Change: Golang 1.8 =
https://fedoraproject.org/wiki/Changes/golang1.8
Change owner(s):
* Jakub Čajka <jcajka AT redhat DOT com>
Rebase of Golang package to upcoming version 1.8 in Fedora 26,
including rebuild of all dependent packages.
== Detailed Description ==
Rebase of Golang package to upcoming version 1.8 in Fedora 26. Golang
1.8 is schedule to be released in Feb. Due to current nature of Go
packages, rebuild of dependent package will be required to pick up the
changes.
== Scope ==
* Proposal owners:
Rebase golang package in f26, help with resolving possible issues
found during package rebuilds.
* Other developers:
fix possible issues
* Release engineering:
As there is scheduled mass-rebuild, nothing should be required.
* List of deliverables: N/A
* Policies and guidelines: N/A
* Trademark approval: N/A
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic