MeetingSummarySpec

Differences between revisions 2 and 3
Revision 2 as of 2006-11-07 21:54:10
Size: 2179
Editor: pool-129-44-212-45
Comment:
Revision 3 as of 2006-11-07 22:01:59
Size: 2160
Editor: pool-129-44-212-45
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 A Calendaring, A Logging, and A Summary Que component.
  * '''Calendaring
''' accessible from the team's page. Sets up an IRC meeting noting: ''Team'', ''Date'', ''Network'', ''Channel'', ''Start time'', ''End time'', ''Grace time'', and ''Related Distribution''.
  * '''Logging''' would use the Calendaring Component to implement a capture of the IRC meeting. This capture would be placed in Related Distribution Que and read-only on the Teams page.
  * Related Distribution Que page would be used by a Meeting Summary group to draft a summary based on the IRC log captured. The draft of the meeting summary then would be posted on that Teams page.
  * A member of the Teams Page with a draft summary would then approve the summary by signing with their PGP key. This would be like any other group approving minutes.
  * '''Calendar''' accessible from the team's page. Sets up an IRC meeting noting: ''Team'', ''Date'', ''Network'', ''Channel'', ''Start time'', ''End time'', ''Grace time'', and ''Related Distribution''.
  * '''Logging Script''' would use the ''Calendaring Component'' to implement a capture of the IRC meeting. This capture would be placed in ''Related Distribution'' que and read-only on the Teams page.
  * '''Summary Que''' based on ''Related Distribution'' would be used by a 'Distro Summary group' to draft a summary of the log captured. The draft of the meeting summary then would be posted on the page for Team who had the meeting.
  * ''Approval'' by a member of the Team of a draft summary would be done by signing with their PGP key. This would be like any other group approving minutes.

Summary

The Ubuntu community should be able to easily learn about what each team and committee are doing. A form of public disclosure of discussion and activity should be made. Each team and committee should have their meetings documented and available on wiki.ubuntu.com.

Currently there is ["MeetingLogs"] that is documenting meetings held on freenode's #ubuntu-meeting channel. Most meetings are taken from Fabbione's [http://people.ubuntu.com/~fabbione/irclogs/ IRC log site] due to the fact that meeting times fail to coincide with the current maintainer of Meetinglogs. Some meetings are not being held in #ubuntu-meeting, which make it more difficult to maintain.

Meeting Logs are just the IRC traffic during the meeting. The conversations can be difficult to follow when replies come out-of-sync and contain back-traffic of non-pertitent communication.

Recomendation

  • After much thought... I propose developing an extension for Launchpad.
    • Calendar accessible from the team's page. Sets up an IRC meeting noting: Team, Date, Network, Channel, Start time, End time, Grace time, and Related Distribution.

    • Logging Script would use the Calendaring Component to implement a capture of the IRC meeting. This capture would be placed in Related Distribution que and read-only on the Teams page.

    • Summary Que based on Related Distribution would be used by a 'Distro Summary group' to draft a summary of the log captured. The draft of the meeting summary then would be posted on the page for Team who had the meeting.

    • Approval by a member of the Team of a draft summary would be done by signing with their PGP key. This would be like any other group approving minutes. The Summary group will be able to place the logs and official summaries on the Meeting Logs and Summaries wiki page.

This seems a little involved, but I feel it uses resources the best. This method is extendable to all distros on Launchpad as well, which make the feature more useful.

Anyone interested in helping or commenting contact AusImage.


CategorySpec

MeetingSummarySpec (last edited 2008-08-06 16:23:49 by localhost)