Born To Be Open

středa 5. listopadu 2014

No, no, we won't have Beta Council, we're going to have final release from beginning (although implementation details has to be sorted out). It was just a coincidence - Fedora 21 Beta was released the same day as Council elections nomination period opened. Two announcements that had to go out yesterday.

Fedora Council nomination period is open by November 10th. If you're interested in to be a pioneer of the new Fedora and write history as member of the very first Fedora Council, please, add yourself to the Nominations page. If you know anyone, who would suit this role, talk to him, try to convince him to run for the seat. Two seats are available for community Elected Representatives. Another part of the Council is appointed but in a very clever way - by communities to serve specific roles (an Engineering Representative and an Outreach Representative). Then we have two appointed leadership roles - Fedora Project Leader andFedora Community Action and Impact Coordinator. And two more members to help with diversity (Diversity Advisor) and secretary things (me aka Fedora Program Manager) but with limited voting scope. I really like the balance between appointed and elected seats and I hope to see a lot of folks running for Council seat!

Fedora 21 Beta is out. It was fun again, as always but we will work on a (I hope early) present for everyone delivered later this year. There are still a few things, that has to be sorted out but with very positive feedback on Alpha all around the Internet, we're on a good path. Currently, the plan is to release on December 9th.

Make Java 8 (provided by OpenJDK 8 which is java-1.8.0-openjdk) the
default Java runtime. The current default Java runtime (Java 7, provided
by OpenJDK 7, java-1.7.0-openjdk) will be obsoleted and removed.

This is essentially an upgrade to the latest Java and OpenJDK version.

Let's make Fedora more secure by default! Recent systemd versions
provide two per-service switches PrivateDevices?=yes/no and
PrivateNetwork?=yes/no which enable services to run without access to
any physical devices in /dev, or without access to kind of network
sockets. So far this has seen little use in Fedora, and with this Fedora
Change we'd like to change this, and enable these for all long-running
services that do not require device/network access.

This first version will have only the very basic functionality with limited user interface and limited resiliency. Next versions (to be delivered in Fedora 22 time frame) will improve resiliency and user interface significantly.

NFS Ganesha is a user mode file server that supports NFSv3, NFSv4, and NFSv4.1 including pNFS for distributed filesystems. It uses loadable filesystem driver modules to support its backend filesystems. It also integrates 9P.2000L file service

Rejected Changes

There are many known tips and tricks how to make a system more secure,
often depending on the use case for the system. With the OSCAP Anaconda
Addon and the SCAP Security Guide projects, we may allow users choosing a
security policy for their newly installed system.

čtvrtek 13. března 2014

As a follow up to my previous post, we're now getting closer to the Fedora 21 schedule. It's still not there and "no earlier than" type until we collect all proposed Changes (and will take a look on the scope of the release). But it should give you some overview - (no earlier than) October 14th is the date we are aiming for!

Why October? It gives us a bit more time to think about Fedora.next and actually work on it as there are changes planned that needs time to settle down. Also we will get back to May/October release dates and it allows us to sync with a few prominent upstreams (and get out of sync with other top upstreams probably ;-). At least for now :).

One more thing - this is friendly reminder that Change Proposals Submission Deadline is coming pretty soon (three weeks now), so make sure to propose your changes as soon as possible to avoid long queues waiting for FESCo decision (and killing me with wrangling everything day before deadline ;-). Thanks a lot!

pondělí 10. února 2014

Fedora's End of Life process creates a lot of discussion every time the magic script is executed. It's a life! Some folks do prefer notification emails sent from Bugzilla, another half dislike that spam (for Fedora 18 it's eliminated a bit). Clone versus reopen wars. As the script itself is pretty dumb and runs CSV file generated from Bugzilla, races occurs... And of course - the existence of the process itself. We can let bugs open without any attention or we can admit, we don't have enough man power to fix them all. Or both :). It's all up to discussion - we're open to any ideas, it's still open on devel list and FESCo ticket and we're trying to make sure it's not going to eat more kittens than it should.

But let's take a look on EOL from perspective of number of bugs closed. I was running the script from Fedora 14 up to Fedora 18 (with exception of Fedora 15 - Spot was doing it), so it's now possible to draw a simple chart and a lot of people were curios for stats.

As you can see, F14, F16 and F18 looks pretty similar. Approximately 6-7 thousand bugs, with F17 being exception.

I don't have total numbers of bugs right now, would be nice to see comparison but Bugzilla refuses to talk to me... 502... Also I tried to correlate numbers to Abrt bugs - looks consistent, no surprises (if you're interest in, I can share). And I'll let up to you to come with resolution what figure above means for us ;-).

Update: Bugzilla now talks to me again, so here is Total/EOL/Abrt bugs chart.

středa 8. ledna 2014

I got this question several times last few days - "hey, you're the
schedule wrangler, you have to know" - as usually this time, we are
working pretty hard on the next Fedora. And Heisenbug was finished
almost month ago - EOL is nearing. But this time we are in a bit
different situation - there are several working groups trying to
redefine, how Fedora should look like in the future and it does not make
sense to create schedule. We need resolution from this effort. It's
planned for January.

Is Fedora 21 going to be
released in the old model way, or new one? Hard to answer right now. But
there's one date - F21 is not going to be released earlier than in
August (and I'd say late August). See FESCo ticket.
What's the reason? As otherwise we would try to hit May timeframe?
Short answe: we want to give the opportunity to the teams that are
smashed by release windmills to work on tooling. Especially as the
Fedora.next proposal stands on more automation to be able to deliver
more products. Especially for QA and release engineering. Of course this
time could be used by anyone! Also there was FESCo decision
to steer release cycle and cadance at least for short term upcoming
release to stick together. In the future, we can end with different
release schedules for different products but automation and lot of
preparation is prerequisite for it.

Other note -
somehow connected to Fedora 21 release cycle, raised by Sirko. What will
be the code name for Fedora 21. And again short answer: null. Not null
as null string but null. Fedora Board decided to end release names process.
It does not mean "no more release names" but it's up to community or
working groups, if anyone wants to step into the role of Name Wrangler
and helps running this process. Or reform it in any way.

January is going to be very interesting month from the point of future Fedora releases - stay tuned!

Btw.
I can see a lot of people and teams missing information on what's going
on, it's really hard for anyone to follow all working groups and what
they are proposing, what FESCo decides, where's the schedule etc. Too
much happening and I'd really like to see better coordination. As Base
WG member I came with the idea of broader project meeting - WGs and
other teams representatives to brief on status, work on coordination.
Unfortunately, one more meeting during F20 release cycle would mean divorce :), so let me take a look on it again.

pátek 18. ledna 2013

Schedules, features and similar creatures at FUDCon - Day 1

FUDCon is here (and most people are already here, some still lost somewhere in space travelling ;-) and for quite a long time it's being planned as "the FUDCon to solve all our problems" regarding the items listed in topic.

Today's Bar Camp sessions

I can't talk about the first one - actually I'm looking forward to see what's going to be part of this one but I think it could be very nice kickup of discussion for follow up schedule/release hackfest I'd like to run tomorrow.

In the second one (and it's my session) - I'm more going to answer the question how to use schedules we provide, not to answer how/what and when we are going to release (so, sorry - no F19 schedule, not now! ;-). But as a tool - there's still some stuff to be improved - new TaskJuggler, linking to SOPs, move the schedule to more neutral place - so no new URL with new Program Manager ;-). Also a lot of teams are surprised by their own schedule - usually I hear - really? We came with this schedule? So clean up is really needed - nice task for F19!

Hackfest

I do not have more details for hackfest right now, but once it's scheduled - I'll share more :) But it will already a Day 2 (and for one guy the time he will hopefully arrive to FUDCon ;-). We have plenty of topics, a lot of ideas, drafts, proposals appearing for ages - reserve a time!

Really creatures?

But I'm really happy to hear a positive feedback on the first change we implemented for F19 - the announcement on devel-announce (even it makes people to spend more time on devel-announce moderation queue), even here on FUDCon. So I hope we will move with it even more during FUDCon!

Enjoy and feel free to stop me, the guy with the cow (for whose who do not know me ;-).