Search results: "modularity" (page 1 of 4)

Documentation and Modularity at Flock 2017

If I had to choose one buzzword for Flock 2017 at Cape Cod, it would be ‘modularity’. Modules, module building, module testing, and module explaining seemed to be all over the place. I attended to give a workshop (with Aneta ŠP) about a proposed way to inject new life into the Fedora Documentation Project. Continue reading

Flock interviews: User Feedback on Modularity

As you probably know, there is annual convention called Flock. This year’s is happening in Cape Cod, Hyannis, MA and will begin the morning of Tuesday, August 29. Sessions will continue each day until midday on Friday, September 1.

I have asked all of the session leaders from Flock some questions.

And now you are about to read one of the responses.

User Feedback on Modularity by Mary Clarke

Briefly describe your session:

I will actually have 6, 1-hour sessions during the course of Flock. They will be in the hour before the lunch break and the  hour after the lunch break on Tuesday, Wednesday, and Thursday. The reason we are doing this is that my sessions are not typical talks, in fact, they are not talks at all. You could describe them as focus groups intended to obtain end-user feedback. These sessions are intended to be highly interactive where we will demo functionality and ask for attendees to respond with their thoughts. I have provided more information through my answers below.

Continue reading

What does Factory 2.0 mean for Modularity?

This blog now has a drop-down category called Modularity. But, many arteries of Modularity lead into a project called Factory 2.0. These two are, in fact, pretty much inseparable. In this post, we’ll talk about the 5 problems that need to be solved before Modularity can really live.

Continue reading

Modularity Infrastructure Design

Co-authored by Courtney Pacheco and Ralph Bean

Note: This article is a follow-up to Introduction to Modularity.


Introduction

The purpose of our Modularity initiative is to support the building, maintaining, and shipping of modular things. So, in order to ensure these three requirements are met, we need to design a framework for building and composing the distribution.

In terms of the framework, in general, we are concerned about the possibility of creating an exponential number of component combinations with independent lifecycles. That is, when the number of component combinations becomes too large, we will not be able to manage them. So that we don’t accidentally make our lives worse, we must limit the number of supported modules with a policy and provide infrastructure automation to reduce the amount of manual work required.
Continue reading

Introduction to Modularity

What is Modularity?

Modularity is an exciting, new initiative aimed at resolving the issue of diverging (and occasionally conflicting) lifecycles of different “components” within Fedora. A great example of a diverging and conflicting lifecycle is the Ruby on Rails (RoR) lifecycle, whereby Fedora stipulates that itself can only have one version of RoR at any point in time – but that doesn’t mean Fedora’s version of RoR won’t conflict with another version of RoR used in an application. Therefore, we want to avoid having “components”, like RoR, conflict with other existing components within Fedora.

Although RoR can be thought of as a component, the definition of “component” is actually a work-in-progress. In other words, another example of a component might be a “LAMP module”, where module is defined as a well-integrated and well-tested set of smaller components that provide functionality. The LAMP module would contain the necessary smaller components required to build and deploy a dynamic, high-performance Apache web server that utilizes MariaDB and PHP. Such a module would be completely independent of all other modules.

Continue reading

Modularity Use Case: Application Independence

A modularity use case in Fedora is much like working with legos.We will be writing a series of blog posts regarding the project to help the Modularity effort move forward. Some of the posts will be about “Why?” and some will be about “How?” As the first post in the series, this article is about “Why?

The Rings Proposal and the Modularity Objective are both about big ideas and a long-term vision. And it should be all those things. Grand visions are how Fedora is what it is today.

Continue reading

What I have found interesting in Fedora during the week 39 of 2017

I was asked whether I can share sort of a report about interesting events or issues I was involved in or I noticed in the Fedora project and community which happened during the last week. So here is my first post:

Delayed delivery of Fedora 27 Server

This is actually two weeks old decision made by Fedora Council, however it has an overlap to the last week as well. For those who do not know, Fedora Council has decided to support Modularity initiative driven by Modularity WG and Server SIG to deliver the Fedora 27 Server edition as the Modular one. To give this initiative some spare time to be able to deliver the content in high quality the Fedora 27 Server edition is going to be delivered a bit later then the rest of the Fedora 27 release. During the last week there was done work on scheduling of this edition and the currently planned target date for Fedora 27 Server GA is 2017-11-28 having the rain date planned on 2017-12-12. See the details on Langdon’s personal page.
Beside of the scheduling there is of course hard work in progress, delivering for example lorax templates to be able to build images, and  lot more.

Fedora 27 Beta release is GO

On the Go/No-Go meeting held on Thursday 2017-09-28 the representatives of FESCo, RelEng, QA and PgM has concluded the Fedora 27 Beta build 1.5 is GOLD and can be delivered as the official F27 Beta release.

i10n freeze policies

For some time already there are discussions how to deal with “string freezes” during the Fedora Release Cycle. The last week Randy Barlow, as a FESCo representative, has requested a feedback on the current policies. Please check it out and respond, if you have anything to add.

Flock 2018 Bidding Open

Bex has opened bid process for the next Flock 2018. I am personally glad to see the bid process started so early.

Update of Election Application

Justin has took the initiative and together with Ryan Lerch, working on the UI, have requested a deploy of an Election Application update. Hopefully, we will see more fluent flow of upcoming Elections thanks to this update.

New Election schedule

On Fedora Council we were working on scheduling and overall organization of Elections. Finally, we have a new schedule which, as we believe, helps to solve some of the issues and complaints we were facing during the past election cycles.

Fedora 27 talking points

During the last week we have also realized, we have an issue collecting Talking Points for Fedora 27 release. I would like to ask anyone who can contribute here, to do so. And thanks Gabriele to lead this initiative.

And of course, the list above is not exhaustive and there is much more going on in Fedora community. The list above just summarizing some tasks which has drawn my attention.

Flock 2017 – test, test, test

FLOCK 2017 – Testing Testing Testing

I’ve attended Flock for the first time this year. I’ve didn’t know what to expect there. We’ve had prepared workshop about Meta-Test-Family to present it there.

Continue reading

Flock interview: When to go fully modular?

As you probably know, there is annual convention called Flock. This year’s is happening in Cape Cod, Hyannis, MA and will begin the morning of Tuesday, August 29. Sessions will continue each day until midday on Friday, September 1.

I have asked all of the session leaders from Flock some questions.
And now you are about to read one of the responses.

When to go fully modular? by Adam Šamalík

What does your talk focus on?

It will be in a form of a discussion or BoF. It will focus on the future of Fedora in the Modularity world.

Continue reading

Flock interviews: How do we restore Fedora to factory settings?

As you probably know, there is annual convention called Flock. This year’s is happening in Cape Cod, Hyannis, MA and will begin the morning of Tuesday, August 29. Sessions will continue each day until midday on Friday, September 1.

I have asked all of the session leaders from Flock some questions.
And now you are about to read one of the responses.

How do we restore Fedora to factory settings? by Stephen Gallagher

What is the goal of your session at Flock?

The goal of this session is to discuss some of the less-obvious needs for packaging system services and applications for Fedora in such a way as to make it possible to generate a “gold master” image for containers and virtualization.

Continue reading

Olderposts

Copyright © 2017 Fedora Community Blog

Theme by Anders NorenUp ↑