Mailing list: Use the main Fedora Development list, prefixing subject lines with [Modularity]
IRC: #fedora-modularity on FreeNode

Meetings

The Modularity Working Group meets regularly, once per week on Tuesdays in #fedora-meeting-3. Please refer to the Modularity WG calendar for the dates. The meetings are at 15:00 UTC, to get the time for your time zone use:

date -d 'Tuesday 15:00 UTC'

Calendar for the Modularity WG
Modularity Project Issue Tracker, file proposed agenda items here
Planned Agenda Items
Meeting Minutes

Voting Membership

[outdated, see "Voting"]

This is the home for the Fedora Modularity Working Group. To find out what this is all about, please visit the Modularity Documentation Website.

Mission Statement

The goal of the Modularity Working Group is to define and maintain the Fedora Base Module and guidelines and tools for other modules.

This includes releasing the Fedora Base Module in artifact form on a regular schedule — as a Docker base image, as an installable minimal system, and possibly in other ways in the future. This will not be a Fedora Edition, but rather be the thing people constructing custom versions of Fedora can start from — including both advanced end-users and Fedora Spins and Editions. (See interesting background discussion on the Fedora Server mailing list.)

So that modules are useful in the greatest number of situations, are fast to create and to deploy, and have the smallest possible security footprint, the Modularity Working Group will reduce package dependency trees, particularly in the Fedora Base Module.

The Working Group will also produce tooling for module production and maintenance, and guidelines for modules, as the FPC does for RPMs.

The effort will also require help and resources from across Fedora, including Fedora Infrastructure, Release Engineering, QA, Security Team, and more. Representatives of those groups should be included on the new Working Group. Also, proven packagers working as part of this effort will institute weak dependencies in a systematic manner, in cooperation with package maintainers.

Policies

Voting

Once a proposal is created as a ticket in the Modularity project issue tracker, it must be voted on in the ticket within one week.
If at the end of one week there are at least 3 votes for the proposal and 0 votes against in the ticket, it has passed.
If there are any votes against, the proposal is added to the agenda of the next Working Group meeting, where a simple majority vote of those present will decide it. This decision will be recorded in the ticket.
If at the end of one week there are fewer than 3 votes for the proposal in the ticket, it is extended one further week and requires only a single affirmative vote to pass.
If at the end of two weeks there are still no votes for the proposal in the ticket, it fails automatically and the status quo is maintained.

Documents and Stuff

Proposed (outdated, to be discussed and decided upon in issue #119): Modularity_Working_Group/Governance_Charter

WG Meetings & Minutes

The Working Group meets regularly on IRC, see the sidebar for details. If you want to discuss something during a meeting, file an issue against the modularity project on Pagure, and contact someone from the Working Group, so they can put it on the agenda for the meeting.

Find minutes for past meetings on Fedora møte.

Helpful Information

Preparing a meeting

If you're responsible for running the meeting, look here for detailed information.

Commands for chairing a meeting

Use #meetingtopic, not #meetingname
Don't use #meetingname, it changes the log name of the meeting, making past meeting logs hard to discover.

#startmeeting modularity_wg
#meetingtopic Weekly Meeting of the Modularity Working Group

#topic Roll Call
[... wait a while for people to join ...]

#topic Agenda
#info a topic
#info another topic

Don't forget to use #info, #agreed, #link, #idea, #action or other commands often for better meeting minutes. Introduction might be done by .hello mynick.

Search

Modularity Team

Contents