Hats Off Strangers! The Fedora Board Arrives
Though it has been nearly two months, it seems as though it was just a few days ago that we reported the beginning of the Fedora Project's election season. Seemingly as soon as it began it has concluded, and the newly elected to the Fedora Project Board, as well as the Ambassadors and Engineering Steering Committees, have been announced.
The structure of the Fedora Project Board, for those unfamiliar, is a little bit like Parliament. There are five members elected from the community, not unlike the Commons; four appointed by the Fedora Project Leader/Red Hat, not unlike the Peers; and the Fedora Project Leader, currently Paul Frields, appointed by Red Hat — who holds a rarely-used veto power over all decisions — not unlike the Sovereign.1 Unlike Parliament, though, the Fedora Project Board is perpetual, with staggered terms for both elected and appointed members to insure continuity.
Four seats were open in this election, two elected and two appointed. The first appointed seat was announced by the FPL on December 3, the final day of open nominations: Chris Aillon, a former Board member whose term on the Board ended this past summer, will return to the Board for a two-release term. (Board elections are not held at set intervals, but rather at the conclusion of each successful release. Members hold their seats for whatever length of time is necessary to complete two releases.) The announcement of the second appointed seat is being held over until after the holidays, to allow the FPL to take additional advice on the selection.
The election for the two remaining seats concluded on Saturday, and the results were announced yesterday morning by FPL Paul Frields. Out of a field of seven candidates, the two new elected members are Bill Nottingham and Matt Domsch, both of whom, in an interesting twist, were outgoing members — Nottingham held an appointed seat, while Domsch was previously elected. The full election results follow:
- Bill Nottingham 993
- Matt Domsch 962
- Dimitris Glezos 816
- Michael DeHaan 742
- Jon Stanley 691
- Josh Boyer 685
- David Cantrell 574
The Board race wasn't the only contest on the ballot, however. Both the Ambassadors Steering Committee (FAmSCo) and the Engineering Steering Committee (FESCo) also had seats up for grabs — the Localization Steering Committee was also originally scheduled to hold an election, but decided to extend the term of their current members instead.
In the FAmSCo election, seven seats were up for election, with a slate of ten candidates:
- Max Spevack 917
- Joerg Simon 695
- Francesco Ugolini 684
- Thomas Canniot 561
- Rodrigo Padula 548
- David Nalley 487
- Susmit Shannigrahi 442
- Sandro Mathys 356
- Larry Cafiero 346
- Hector Gonzalez 252
On the FESCo side, five candidates stood for four available seats:
- Josh Boyer 489
- Dan Horák 485
- Jarod Wilson 485
- Jon Stanley 453
- Dominik Mierzejewski 396
We offer our most sincere congratulations to all the newly elected leaders, a digital round-of-applause for everyone who stood for election, and wish everyone at the Fedora Project the best of luck for the coming year.
Justin Ryan is a Contributing Editor for Linux Journal.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide