Env and Stacks Elections - June 2015 - Results
by Jan Kurik
Greetings, all!
The elections for Env and Stacks - June 2015 have concluded, and the results
are shown below.
Env and Stacks is electing 5 seats this time.
A total of 71 ballots were cast, meaning a candidate
could accumulate up to 426 votes (71 * 6).
The results for the elections are as follows:
# votes | name
- --------+----------------------
307 | Honza Horak (hhorak)
262 | Nick Coghlan (ncoghlan)
219 | Václav Pavlín (vpavlin)
197 | Jens Petersen (petersen)
175 | Jan Kaluza (jkaluza)
- --------+----------------------
154 | Stuart Campbell (sic)
Congratulations to the winning candidates, and thank you all
candidates for running this elections!
--
Jan Kuřík
8 years, 3 months
FESCO Elections - June 2015 - Results
by Jan Kurik
Greetings, all!
The elections for FESCo - June 2015 have concluded, and the results
are shown below.
FESCo is electing 4 seats this time.
A total of 90 ballots were cast, meaning a candidate
could accumulate up to 540 votes (90 * 6).
The results for the elections are as follows:
# votes | name
- --------+----------------------
363 | Stephen Gallagher (sgallagh)
294 | Josh Boyer (jwboyer)
293 | Dennis Gilmore (ausil)
274 | Haïkel Guémar (hguemar)
- --------+----------------------
177 | Germano Massullo (germano)
159 | David King (amigadave)
Congratulations to the winning candidates, and thank you all
candidates for running this elections!
--
Jan Kuřík
8 years, 3 months
F23 Self Contained Change: Astronomy Spin
by Jan Kurik
= Proposed Self Contained Change: Astronomy Spin =
https://fedoraproject.org/wiki/Changes/Astronomy_Spin
Change owner(s): Christian Dersch <lupinix at mailbox dot org >
A Fedora Spin providing a complete toolchain for both amateur and professional astronomers.
== Detailed Description ==
In both amateur and professional astronomy and astrophysics Linux is a very popular operating system. More and more data analysis is performed using Python, especially the astropy project is a quite new effort providing a professional toolchain. The Astronomy Spin provides a complete scientific Python environment (2 and 3) as well as the AstrOmatic software. For observational astronomy, KStars provides a complete solution for astrophotography using the INDI library. In addition to an astronomical collection of packages the spin also adds a menu for astronomy to make work more comfortable.
== Scope ==
* Other developers: N/A (not a System Wide Change)
* Release engineering: Add spin to spin-kickstarts, ensure spin has been tested, and release with rest of spins
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: Requested
--
Jan Kuřík
8 years, 3 months
Koschei - new Fedora infrastructure service
by Mikolaj Izdebski
I'm glad to announce that as of yesterday Koschei production instance
has been moved Fedora infrastructure and now it can be considered as
officially-supported Fedora service.
Koschei is a continuous integration service for Fedora packages.
Koschei is aimed at helping Fedora developers by detecting problems as
soon as they appear in rawhide - it tries to detect package FTBFS in
rawhide by scratch-building them in Koji. More information can be
found at Fedora Wiki [1].
Interested parties can be automatically notified when Koschei detects
change in package FTBFS status. In order to subscribe to email or IRC
notifications you can follow instructions at [2].
At the time of writing, Koschei monitors about 20 % of all Fedora
packages, but anyone with FAS account can add packages they are
interested in. See [3] for details how to add packages to Koschei.
I would like to thank everybody who helped to make Koschei at Fedora
infrastructure possible, especially Kevin Fenzi, who sponsored Koschei
request for resources and assisted us with the migration.
[1] https://fedoraproject.org/wiki/Koschei
[2] https://fedoraproject.org/wiki/Koschei#Notifications
[3] https://fedoraproject.org/wiki/Koschei#Adding_packages
--
Mikolaj Izdebski
8 years, 3 months
F23 System Wide Change: jQuery
by Jan Kurik
= Proposed System Wide Change: jQuery =
https://fedoraproject.org/wiki/Changes/jQuery
Change owner(s): T.C. Hollingsworth <tchollingsworth at gmail dot com>
jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript.
Traditionally, a copy of jQuery has been included with every web application that requires it. This change will migrate many of those applications to a shared system copy of jQuery. Both the 1.x branch of jQuery that supports Internet Explorer 6 and the 2.x branch of jQuery that only works with modern web browsers will be provided.
== Detailed Description ==
Traditionally, a copy of jQuery has been included with every web application that requires it. This change will migrate many of those applications to a shared system copy of jQuery.
The following packages are available in Fedora 21 and later and EPEL 6 and later:
* js-jquery - The latest version of the jQuery 2.x branch, suitable for web applications that are only compatible with modern web browsers that fully support modern web standards.
* js-jquery1 - The latest version of the jQuery 1.x branch, suitable for web applications that endeavor to be compatible with older web browsers such as Internet Explorer 6.
* js-jquery-migrate - The jQuery migrate plugin, which is a compatibility shim that enables web applications that depend on older versions of jQuery to work with the latest version, so that they can be ported away from old, unsupported jQuery versions that may potentially have security issues.
Some new packages are already beginning to use the system version of jQuery with little trouble, so for Fedora 23 we're going to open the doors to converting existing packages. We'll send announcements explaining how to unbundle existing packages. We'll also find all the packages we can that are bundling jQuery and inform maintainers about them, via e-mail only at this time. (We'll save the mass bug filing for F24 to allow maintainers to have a go at it voluntarily first. :-)
== Scope ==
* Migrating Web Applications
-- Web applications that depend on modern versions of jQuery will simply be ported to use the systemwide version instead,
-- Web applications that use older versions of jQuery (> 1.6.4 but <1.9) will be ported to use jquery-migrate and the systemwide version of jQuery. Packagers will be encouraged to work with upstream to migrate to the latest version of jQuery without jquery-migrate, since using this plugin re-enables misfeatures rightly removed from jQuery core that are XSS holes waiting to happen.
-- Maintainers of web applications that use extremely old versions of jQuery (< 1.6.4) will be strongly encouraged to work with upstream to migrate to the latest versions of jQuery and update their packages. However, current Fedora policy regarding bundled libraries permits these packages to be grandfathered in, so I am unable to force any action here.
-- Preliminary repoqueries have been performed to identify potentially affected packages, see the dependencies section for more details.
* Migrating documentation frameworks
-- Certain documentation frameworks, such as python-sphinx, ship copies of jQuery as well. These frameworks will be modified to use a symlink or other means so that they too can use the new systemwide versions.
* Release Engineering
-- No special attention required.
--
Jan Kuřík
8 years, 3 months
F23 Self Contained Change: io.js Technology Preview
by Jan Kurik
= Proposed Self Contained Change: io.js Technology Preview =
https://fedoraproject.org/wiki/Changes/iojs
Change owner(s): T.C. Hollingsworth <tchollingsworth at gmail dot com>
io.js is an npm compatible platform originally based on Node.js™ that supports version 6 of the ECMAScript standard and additional features, developed with an open governance model. io.js will be offered as an optional replacement for `/usr/bin/node` on Fedora systems as a Technology Preview. node.js will remain the default implementation of `/usr/bin/node` in Fedora 23.
== Detailed Description ==
io.js is an npm compatible platform originally based on Node.js™ that supports version 6 of the ECMAScript standard and additional features, developed with an open governance model. For more information about io.js and the differences between node.js, visit the io.js website.
io.js will support the same set of binary modules currently supported by node.js on Fedora. It is expected to be obsoleted by a future version of the `nodejs` package, as these two projects have announced their intention to merge.
We will support both parallel-installation of the iojs interpreter alongside the existing node.js interpreter, and permit replacement of `/usr/bin/node` with io.js in an additional package. All existing noarch nodejs-* packages will work with both interpreters. (Though obviously you'll have to specify iojs if you haven't installed it the /usr/bin/node support package.) Seperate nodejs-* and iojs-* will be provided for binary modules.
== Scope ==
* Proposal owners:
-- Package and build a special v8 package for io.js only.
-- Package and build iojs
-- Update nodejs guidelines for multiple interpreters
-- Rebuild modules with above changes
-- Anything that needs updates for Node.js 0.12 will need it for io.js too.
* Other developers:
-- Anything that needs updates for Node.js 0.12 will need it for io.js too.
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines:
-- Updates to the node.js guidelines and packaging infrastructure to permit building binary modules for multiple interpreters will be necessary. (These are also necessary to allow for a nodejs010/nodejs012 split in EPEL, so will get done anyway.)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
8 years, 3 months
F23 Self Contained Change: npm 2
by Jan Kurik
= Proposed Self Contained Change: npm 2 =
https://fedoraproject.org/wiki/Changes/npm2
Change owner(s): T.C. Hollingsworth <tchollingsworth at gmail dot com>
Fedora 23 features npm 2, the latest version of the package manager for node.js and other JavaScript platforms.
== Detailed Description ==
While npm 2 is a major version number update, it contains little in the way of major changes. The version bump was necessitated by an API change permitting arguments to be passed to scripts executed by `npm run`. Another major change is to the way 0.x.y versions are compared by the semver library used by npm. For more information on all the changes, see the upstream release announcement. There are few end-user facing changes, beyond the addition of a couple features to the CLI.
== Scope ==
* Proposal owners:
-- Update all of nodejs-* basically
-- Update npm of course
* Other developers:
-- I might have to ask a couple other maintainers if they're okay with me updating their packages. They usually are. :-)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines:
-- Some minor updates to the Node.js guidelines are planned, however they are just Nice To Have for the purposes of this specific change.
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
8 years, 3 months
F23 Self Contained Change: Local Test Cloud
by Jan Kurik
= Proposed Self Contained Change: Local Test Cloud =
https://fedoraproject.org/wiki/Changes/Local_Test_Cloud
Change owner(s):
* Mike Ruckman <roshi at fedoraproject dot org>
* Kushal Das <kushaldas at gmail dot com>
testcloud is a small tool to download and boot cloud images locally.
== Detailed Description ==
testcloud was created because manually booting a cloud image locally can be a pain. It handles downloading the image, spoofing cloud-init metadata as well as providing an ssh_config to easily connect to the booted instance. What was usually several different steps to get an image to boot locally is now just one:
testcloud instance create <name of instance> -u <url for qcow2 image>
It currently supports only the Fedora Cloud Base image, and work is ongoing to support the Atomic host image.
== Scope ==
* Proposal owners: Mike Ruckman, Kushal Das to implement proposed change
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
--
Jan Kuřík
8 years, 3 months
F23 Self Contained Change: Node.js 0.12
by Jan Kurik
= Proposed Self Contained Change: Node.js 0.12 =
https://fedoraproject.org/wiki/Changes/NodeJS012
Change owner(s): T.C. Hollingsworth <tchollingsworth at gmail dot com>
Fedora 23 will be updated to Node.js 0.12, the latest release of the platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications.
== Detailed Description ==
Node.js has seen many changes between v0.10 and v0.12. There is a listing of changes documented on the wiki. Note that this release includes API updates that may require dependency updates. Following are some highlights:
* Streams 3
The Streams implementation now works the way you thought it already should, without introducing any changes to the API. Basically this means no more getting stuck in "old mode", there are only streams that are flowing or not.
Streams now support the use of cork and uncork mechanisms to prevent flushing writes out to the system if an application is going to be performing many writes in a row. There is an implicit uncork performed when you end a writable stream.
* HTTP
maxSockets are no longer limited to 5. The default is now set to Infinity with the developer and the operating system given control over how many simultaneous connections an application can keep open to a given host.
Proper KeepAlive support means that sockets will stay open until they timeout at the configured time, are closed by the remote side, or the process exits. Developer's no longer have to make sure requests have been pipelined to keep the socket open, or use an alternative module to get that support.
Developers can also now explicitly flushHeaders to ensure time to first byte is low and proxied connections are held open.
* Cluster
Now has two modes of operation, the new default is a round robin distribution mechanism where the master accepts new connections and distributes them to your workers. If you want you can still opt back into the old method where your workers are responsible for acception connections.
* TLS
We have the new TLSWrap mechanism under the hood, this eliminates quite a few of the hops back and forth between JavaScript and our C++ implementations.
Added APIs for asynchronous SNI callbacks, OCSP stapling, and storage events.
* Buffer
We use a more accurate mechanism for allocating memory for buffers now, which means you'll see less overhead and impact from holding onto to small slices of Buffers. This reduces the amount of memory pressure on the system, which means GC runs are quicker, which means Node.js is on CPU less, and thus lower latency for your applications.
* child_process
spawnSync/execSync have been added to facilitate synchronous child processes, warning your node process won't make forward progress while waiting for the child to exit, caveat emptor!
* Crypto
Added APIs for loading custom engines for use with compiled in OpenSSL.
More APIs support supplying the pass phrases.
Added APIs for RSA public/private key encryption/decryption.
* VM
The module is now based on the Contextify module, which shares values from the sandbox to avoid missing changes inside the execution from appearing in the parent context.
Initial support for ECMAScript Internationalization API 1.0 (ECMA-402)
By default, Node.js v0.12.0 binaries are shipped with ECMA-402 support, but only for the English language. In other words, the ECMA-402 API is working as you would expect, but only data for the English language is included. You can find more info on how to include more languages in the Wiki.
These are just some of the changes you can find in this release of v0.12, and it's thanks to the hard work of the community and the members of team curating Node.js.
We are also pleased to report that this release of Node.js has tests passing on all of our supported platforms. On the one hand, this seems obvious (what are tests for if not to verify before you release it?!), but this is actually the first release of Node.js that has operated under this constraint. Requiring that all tests pass before releasing Node.js marks an important development for the project, and is essential for building a solid path moving forward.
== Scope ==
* Proposal owners:
-- Update v8
-- Update nodejs
-- Rebuild all binary modules, apply patches as necessary
-- Update npm
* Other developers:
-- Other Node.js packagers' attention may be required if the update causes issues for their packages.
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines:
-- Some minor updates to the Node.js guidelines are planned, however they are just Nice To Have for the purposes of this specific change.
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
8 years, 3 months
