From Fedora Project Wiki

(piratepad.net broke, move our agenda etherpad to board.net)
(reflect name change (working group -> team), update mission statement)
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{side box|
{{side box|


* '''Mailing list:''' Use the main [https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org/ Fedora Devel], prefixing subject lines with <code>[Modularity]</code>
* '''Mailing list:''' Use the main [https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org/ Fedora Development list], prefixing subject lines with <code>[Modularity]</code>
* '''IRC:''' <code>#fedora-modularity</code> on FreeNode
* '''IRC:''' <code>#fedora-modularity</code> on FreeNode


'''Meetings'''
'''Meetings'''


* The Modularity Working Group meets once every two weeks on Tuesdays in <code>#fedora-meeting-3</code>, please refer to the [https://apps.fedoraproject.org/calendar/modularity/ Modularity WG calendar] for the dates. The meetings are at 15:00 UTC, to get the time for your time zone use <code>date -d "15:00 UTC"</code>.
* The Modularity Team meets regularly, once per week on Tuesdays in <code>#fedora-meeting-3</code>. Please refer to the [https://apps.fedoraproject.org/calendar/modularity/ Modularity Team calendar] for the dates. The meetings are at 15:00 UTC, to get the time for your time zone use:
* [https://apps.fedoraproject.org/calendar/modularity/ Calendar for Modularity WG]
* [https://board.net/p/modularity-wg-agendas Meeting Agendas]
'''Voting Membership'''


* [[User:mikedep333|Mike DePaulo]]
date -d 'Tuesday 15:00 UTC'
* [[User:tflink|Tim Flink]]
* [[User:Ausil|Dennis Gilmore]]
* [[User:harald|Harald Hoyer]]
* [[User:sct|Stephen Tweedie]]
* [[User:langdon|Langdon White]]
* [[User:cydrobolt|Chaoyi Zha]]


}}
* [https://apps.fedoraproject.org/calendar/modularity/ Calendar for the Modularity Team]
* [https://pagure.io/modularity/issues Modularity Project Issue Tracker], file proposed agenda items here
* [https://pagure.io/modularity/report/meeting_agenda Planned Agenda Items]
* [https://meetbot.fedoraproject.org/sresults/?group_id&#61;modularity&type&#61;team Team Meeting Minutes] - [https://meetbot.fedoraproject.org/sresults/?group_id&#61;modularity_wg&type&#61;team Working Group Archive]


'''The Usual Suspects'''


This is the home for the Modularity Working Group...
Because of the informal structure of this team (see the [[Modularity_Team/Governance_Charter|Governance Charter]]), here is a list of people who participate regularly in case you need to contact someone "from the team":


* [[User:asamalik|Adam Šamalík]]
* [[User:langdon|Langdon White]]
* [[User:nphilipp|Nils Philippsen]]
* [[User:psabata|Petr Šabata (contyk)]]
* [[User:sgallagh|Stephen Gallagher]]


= Mission Statement =
}}


This is the home for the Fedora Modularity Team. To find out what this is all about, please visit the [https://docs.pagure.org/modularity/ Modularity Documentation Website].


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
= Mission Statement =
[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 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 goal of the Modularity Team is to '''develop and maintain guidelines and tooling for module production and maintenance''' in Fedora.


 
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 are welcome and invited to participate in the work of the Team.
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 =
= Policies =


* [[Modularity_Team/Governance_Charter|Modularity Team Governance Charter]]


= Documents and Stuff =
= Team Meetings & Minutes =
 
Proposed: [[Modularity_Working_Group/Governance_Charter]]
 
See [[Modularity]]
 
= How to Get Involved =
 
== Contributing ==
 
If you are interested in joining the working group, see [[Modularity_Working_Group/Initial_Nominations]] (open until April 18).
 
 
We are still working through this, however, if you would like to see where we are or add user stories or issues please check out the [[Modularization/Planning|Planning]] page.
 
IRC Channel: #fedora-modularity
 
== Tooling Prototypes ==
 
* [[Modularity_Working_Group/prototype/pungi|pungi]] prototype for modularity - For building composes
* [[Modularity_Working_Group/prototype/productmd|productmd]] prototype for modularity - Compose metadata
 
= Release Planning =
 
* [[Modularity_Working_Group/releases/Flock_2016_Release|Flock 2016 Release Features]]
 
=== Status Reports ===


* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/UTNLVDK6TPGWKZHANSFAPJQLZFYLSI3X/ March 11, 2016]
The Team meets regularly on IRC, see the sidebar for details. If you want to discuss something during a meeting, file an issue against the [https://pagure.io/modularity/issues <code>modularity</code>] project on Pagure, and contact someone from the team, so they can put it on the agenda for the meeting.


= Meeting Minutes =
Find minutes for past meetings on [https://meetbot.fedoraproject.org/sresults/?group_id=modularity-team&type=team Fedora møte]. We also have an [https://meetbot.fedoraproject.org/sresults/?group_id=modularity_wg&type=team archive of meeting minutes] from when the Modularity Team was still called a "Working Group".


&nbsp;
== Helpful Information ==
{|
|-
! Date
! Agenda
! Blog Summary
! Mailing List Thread
! Minutes
! Raw Logs
|-
| May 12, 2016
|
* review meeting time
* review package lifecycle diagrams
* demos: where, when, how update
* open floor
| None
| None
| TBD
| TBD
|-
| May 05, 2016
|
* review package lifecycle diagrams (lead by threebean):
* demos: where, when, how (lead by cpacheco)
* mention / review whenisgood results
* open floor
| None
| None
| [https://meetbot.fedoraproject.org/teams/modularity_wg_weekly_meeting/modularity_wg_weekly_meeting.2016-05-05-15.02.html Minutes]
| [https://meetbot.fedoraproject.org/teams/modularity_wg_weekly_meeting/modularity_wg_weekly_meeting.2016-05-05-15.02.log.html Raw log]
|-
| April 28, 2016
|
* Announce new modularity voting members
* Discuss meeting time
* review metadata proposal from contyk & new cards from sct
* discuss open bzs (dnf, anaconda)
* status updates
* discuss future outreach
| None
| None
| [https://meetbot.fedoraproject.org/teams/modularity-wg/modularity-wg.2016-04-28-15.01.html Minutes]
| [https://meetbot.fedoraproject.org/teams/modularity-wg/modularity-wg.2016-04-28-15.01.log.html Raw log]
|-
| April 14, 2016
|
* governance approval
* minor change to infrastructure
* onboarding
* onboarding path
* update on membership
* reviewing other progress
* open floor
| None
| None
| [https://meetbot.fedoraproject.org/teams/modularity_wg/modularity_wg.2016-04-14-15.01.html Minutes]
| [https://meetbot.fedoraproject.org/teams/modularity_wg/modularity_wg.2016-04-14-15.01.log.html Raw log]
|-
| April 07, 2016
|
* governance
* what to deliver? When? (cont'd)
| None
| None
| None
| [https://meetbot.fedoraproject.org/teams/modularity_wg/modularity_wg.2016-04-07-15.01.log.html Raw log]
|-
| March 31, 2016
|
* context setting
* number of voting members & terms of service
* meeting times?
* what to deliver? When?
* how to do stuff
| None
| None
| [https://meetbot.fedoraproject.org/teams/modularity_wg/modularity_wg.2016-03-31-15.02.html Minutes]
| [https://meetbot.fedoraproject.org/teams/modularity_wg/modularity_wg.2016-03-31-15.02.log.html Raw log]
|-
|}


=== Preparing a meeting ===


[https://meetbot.fedoraproject.org/sresults/?group_id=modularity_wg&type=team All meeting minutes ...]
If you're responsible for running the meeting, look [[Meeting_Preparation|here]] for detailed information.


= Helpful Information =
=== Commands for chairing a meeting ===
=== Commands for chairing a meeting ===


{{admon/caution|Use <code>#meetingtopic</code>, not <code>#meetingname</code>|Don't use <code>#meetingname</code>, it changes the log name of the meeting, making past meeting logs hard to discover.}}
{{admon/caution|Use <code>#meetingtopic</code>, not <code>#meetingname</code>|Don't use <code>#meetingname</code>, it changes the log name of the meeting, making past meeting logs hard to discover.}}


<pre>#startmeeting modularity_wg
<pre>#startmeeting modularity
#meetingtopic Weekly Meeting of the Modularity Working Group
#meetingtopic Weekly Meeting of the Modularity Team
#chair cydrobolt dgilmore haraldh langdon mikedep333 sct tflink


#topic Roll Call
#topic Roll Call

Revision as of 12:50, 23 January 2019

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

Meetings

  • The Modularity Team meets regularly, once per week on Tuesdays in #fedora-meeting-3. Please refer to the Modularity Team 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'

The Usual Suspects

Because of the informal structure of this team (see the Governance Charter), here is a list of people who participate regularly in case you need to contact someone "from the team":


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


Mission Statement

The goal of the Modularity Team is to develop and maintain guidelines and tooling for module production and maintenance in Fedora.

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 are welcome and invited to participate in the work of the Team.

Policies

Team Meetings & Minutes

The Team 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 team, so they can put it on the agenda for the meeting.

Find minutes for past meetings on Fedora møte. We also have an archive of meeting minutes from when the Modularity Team was still called a "Working Group".

Helpful Information

Preparing a meeting

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

Commands for chairing a meeting

Stop (medium size).png
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
#meetingtopic Weekly Meeting of the Modularity Team

#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.