This is the continuation of part four of a series based on talks at February at DevConf in the Czech Republic. Last week, I was going to cover all of the reports from each of the Working Group liaisons but that turned out to be quite a wall of text, so I’m going to do them one by one, with Marcela Mašláňová from the Environments and Stacks Working Group this week.
You should start with Part I, ”Why?”, and if you enjoy the general concepts of “logical progression” and “putting the horse before the cart”, I suggest following that with Part II, “What’s Happening?” and then Part III, “Governance, Progress, and More Ideas”.
You can watch the video on YouTube, but you may find the text more helpful. I’ve summarized and paraphrased instead of just transcribing. And, since it has been three months, I’ve gotten updates from each speaker.
Working Group Report Video
Environment and Stacks: Marcela Mašláňová
Marcela explains that, like Base Design, Environments and Stacks is not a product in itself. It exists to serve the other products, and it does this through new or improved methods for developing, testing, packaging, and deploying software for the Fedora community.
One part of this is thinking about is improvements to Fedora developer’s lives, and what is missing there, so an early focus is improved documentation for Koji (the Fedora package build system) and for COPRs (our system which lets developers easily manage and host their own small package repositories).
Another big area is SCLs. This stands for “Software CoLlections” — a way of packaging specific versions of languages like Ruby or Python into the /opt directory, where they don’t interfere with a system version of that same language (more at the Software Collections “upstream” web site). This is very different from any previous way of packaging things in Fedora, so the group is working with the the Fedora Packaging Committee (FPC) to develop guidelines for providing these within the distribution. Both the Cloud and Workstation groups have asked for this as important for their audiences. (And an update on this: the Ruby 1.9.3 collection, with Rails 3.2.8, will be the first available.)
The next area is the “Fedora Ugly” or “Fedora Incubator” repository, which I spoke about briefly at the end of my talk (see Part III, “Governance, Progress, and More Ideas”… scroll down to the last section). This is a space within Fedora for packages which, for whatever reason, do not meet the standards of the main repository. The two big big updates on this are that first, the naming has been settled and the repository will be the “Fedora Playground”, and second, this has been officially approved by FESCo (the Fedora Engineering Steering Committee) and will be a feature in Fedora 21 this October. More details can be found on the Fedora project wiki.
Marcela says that the group has many plans and future ideas. There are many possible improvements for automated packaging, reviews, and QA; improvements in build systems; better integration of services; and more and better documentation. What can be done for the Fedora 21 timeframe must necessarily be a smaller scope, so SCLs and the Playground are the first focus. In the future, this will expand as the needs of the other working groups and the associated products develop.
Visit the Env and Stacks page on the Fedora Project wiki for further information, including the mailing list and IRC meeting times.
Watch for more of Part IV Next Week
Coming up, the summaries from product-based working groups: Server, Workstation, and Cloud. Since these are shorter than the earlier parts of this series, I’m going to try to do them at a slightly faster pace than only one a week; we’ll see how that goes. In any case, once the summary presentations are done, it’s on to Q&A.
As before, let’s continue this conversation in comments and replies, and in addition to responding, I’ll distill that into a final Q&A post at the end of this series (separate from the summary of the questions at the conference).