From Fedora Project Wiki

(Commands for chairing a meeting)
(bi-weekly → once every two weeks)
Line 6: Line 6:
 
'''Meetings'''
 
'''Meetings'''
  
* The Modularity Working Group meets bi-weekly 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 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>.
 
* [https://apps.fedoraproject.org/calendar/modularity/ Calendar for Modularity WG]
 
* [https://apps.fedoraproject.org/calendar/modularity/ Calendar for Modularity WG]
 
* [http://piratepad.net/modularity-wg-agendas Meeting Agendas]
 
* [http://piratepad.net/modularity-wg-agendas Meeting Agendas]

Revision as of 13:07, 6 March 2017

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

Meetings

Voting 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

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 Planning page.

IRC Channel: #fedora-modularity

Tooling Prototypes

  • pungi prototype for modularity - For building composes
  • productmd prototype for modularity - Compose metadata

Release Planning

Status Reports

Meeting Minutes

 

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 Minutes 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 Minutes Raw log
April 14, 2016
  • governance approval
  • minor change to infrastructure
  • onboarding
  • onboarding path
  • update on membership
  • reviewing other progress
  • open floor
None None Minutes Raw log
April 07, 2016
  • governance
  • what to deliver? When? (cont'd)
None None None 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 Minutes Raw log


All meeting minutes ...

Helpful 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_wg
#meetingtopic Weekly Meeting of the Modularity Working Group
#chair cydrobolt dgilmore haraldh langdon mikedep333 sct tflink

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