To get involved with the Modularity Working Group, please follow the following steps for becoming a part of the team.
There’s no dedicated mailing list yet and everything regarding this topic should be discussed on the general Fedora Development list. Most of us also hang out on the #fedora-modularity channel on Freenode.
Formal meetings are held once a week by the Modularity Working Group. See the Fedocal to find out when the group is meeting.
We will use agile software development methods for Modularity, more specifically: a hybrid of Scrum and Kanban adapted to the constraints we have in Fedora. For instance, not all contributors can commit to be involved like a regular, full-time employee, meaning that rigid use of 2-week-long Scrum Sprints can be an obstacle to participating for some people.
If you’re not familiar with agile development or the methods we use, here are some links to get you started:
Agile development methods often come with their own lingo that can be confusing to the “uninitiated”—like “epic”, “sprint” (or “iteration”), “spike”. Many of the terms used are explained over at the Agile Dictionary.
We manage the project using Taiga on Fedora Infrastructure, one instance for individual sprint work items and another for higher-level stuff (“epics”).
We currently host all of our code at Pagure — the infrastructure, the client-side tooling, metadata specification drafts and even a couple of proof-of-concept modules. Repositories typically start with the fm- prefix and are open to all members of the Pagure @modularity group.
In order so that our code base is always clean and maintainable, we have to enforce certain rules on how code is written or formatted, how changes are broken up into commits and how pull requests are handled.