m (Mattdm moved page Modules Working Group to Modularity Working Group: Color of bikeshed settled once and for all) |
(permanent bikeshed paint) |
||
| Line 6: | Line 6: | ||
'''Meetings''' | '''Meetings''' | ||
* The | * The Modularity Working Group meets weekly on ? in #fedora-meeting. The meetings are at ??:00 UTC on odd weeks and at ?:00 UTC on even weeks. To get the time for your time zone, use <code>date -d "??:00 UTC"</code> and to get the week number, use <code>date +"%V" </code>. | ||
* [[https://meetbot.fedoraproject.org/sresults/?group_id= | * [[https://meetbot.fedoraproject.org/sresults/?group_id=modularity&type=team meeting logs]] | ||
'''Membership''' | '''Membership''' | ||
| Line 17: | Line 17: | ||
This is the home for the | This is the home for the Modularity Working Group... | ||
| Line 23: | Line 23: | ||
The goal of the | 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 | 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 | ||
[http://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/message/K45OPPE5GN3V4MME5FTN7NM6PNESWA5L/ background discussion on the Fedora Server mailing list]].) | [http://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/message/K45OPPE5GN3V4MME5FTN7NM6PNESWA5L/ 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 | 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 Working Group will also '''produce tooling for module production and maintenance, and guidelines for modules''', as the FPC does for RPMs. | ||
| Line 48: | Line 48: | ||
= Helpful Information = | = Helpful Information = | ||
=== Commands for chairing a meeting === | === Commands for chairing a meeting === | ||
#startmeeting | #startmeeting Modularity (YYYY-MM-DD) | ||
#meetingname | #meetingname modularity | ||
#chair ..... | #chair ..... | ||
#topic Welcomes and Hellos | #topic Welcomes and Hellos | ||
Revision as of 16:21, 15 March 2016
Meetings
Membership
|
This is the home for the Modularity Working Group...
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
Documents and Stuff
See Modularization
Tasklist/How to get involved/Contact Us
Which features were started, where is help needed can be found here: Tasklist
Helpful Information
Commands for chairing a meeting
#startmeeting Modularity (YYYY-MM-DD) #meetingname modularity #chair ..... #topic Welcomes and Hellos ... #topic ... ... #endmeeting
Don't forget to use #info, #agreed, #link, #idea, #action or other commands often for better meeting minutes. Introduction might be done by .hellomynameis mynick.