MeetingReports

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2012-04-12 21:59:52 →
Size: 6029
Editor: 189
Comment:
← Revision 2 as of 2012-04-12 22:16:41 → ⇥
Size: 4122
Editor: 189-38-251-58
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
=== Trial: A private Live Testing session ===
 * In order to evaluate the effectiveness, problems, strong and week points on this strategy, a trial session will be developed;
 * Implementation difficulties, results and other aspects will be evaluated / fixed by the team before a public set of events is announced;
==== Trial implementation processes and delegation ====
'''"Trial" Live Testing Session Planning'''
||<tablestyle="float:center; width:100%; background:#F1F1DD; color: #000000; margin: 0; padding: 0; border: 0; text-align: left;" rowstyle="margin: 0; padding: 0; border: 0; background: #3C3B37; color: #FFFFFF;" style="text-align: center; width:4%;">~+'''#'''+~||<style="text-align: center; width:10%;">~+'''Activitity'''+~||<style="text-align: center; width:30%;">~+'''Description'''+~||<style="text-align: center; width:10%;">~+'''Delegated to'''+~||<style="text-align: center; width:10%;">~+'''Deadline'''+~||<style="text-align: center; width:36%;">~+'''Status'''+~||
||1||IRC Infrastructure||Get temporary IRC infrastructure and moderation staff for a single trial event.||?||?||?||
||2||Testing Repo||A testing repository must be set exclusively for this session. The developers must have the rights to upload to it in real time during the session.||?||?||?||
||3||ISO||A previously developed ISO must be made, to be used by testers during the session||?||?||?||
||4||Tracker||A Tracker must be accessible by the developer and testers during the session. Results must continue to be available after the session.||?||?||?||
||5||Analysis/Selection||Select bugs and corresponding packages, reach their developers to invite for the trial session||?||?||EVeryone will study and send a list of packages/bugs to Effenberg0x0 before the next meeting. -- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T21:59:52Z)>>||
||6||Content||Create omnibus wiki page to support the session. Link, develop or improve related tutorials. Evaluate how much time it would take to have such a content ready for every session.||?||?||I've been working with Python scripts that auto read/sort/parse LP and update MoinMoin via API (much like Fedora auto-does it, and Ubuntu QA Reports are done). I can take this one. -- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-11T18:54:13Z)>>||
||7||Testers||Select small group (5?) of testers, to participate in the trial session.||Cariboo907||?||Cariboo907 already selected a list of testers and will contact them. -- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T21:59:52Z)>>||
||8||Developers||Select small group (5?) of testers, to participate in the trial session.||?||?||?||		 <<Include(LiveTesting/Resources/NavBar)>>
||<tablestyle="float:right; font-size: 0.9em; width:35%; background:#F1F1DD; margin: 2.5em 0 1em 1em; border: none; border-radius: 10px 10px 10px 10px;" style="margin: 0; padding:0.5em;"><<TableOfContents(6)>>||
= Agenda =
== Apr. 18 2012 ==
'''Suggested Topics:'''<<BR>>
~-Add your suggestion drectly to the bullets below. Please add the ``@SIG``@``macro at the end of the line. When you '''save''' the page, your name/timestamp will be automatically added.-~
 * Check if groups of selected testers (Cariboo907)has accepted to participate.-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * Check and discuss list of target Packages/Bugs sent by team members during the week. Define final list.
 * Confirm who will approach developers for the selected targets (Balloons?) and if help from other member is needed for this task.-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * Decide who will be responsible for creating LiveTesting Page, which contains all the info for the testing session.-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * Decide who will approach IRC Management and get us infrastructure (and, also, if that will be needed in the trial).-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * ToDo: Wait for feedback from developers. Once a developers accepts to take part in the trial, we can proceed to creating the documentation and setting up a date.-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
= Previous Meetings =
== Apr. 12 2012 ==
 * Cariboo907 has selected a group of testers and will approach them. He will communicate us of the status of this process in the next meeting.-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * The group agreed to study and select potential target Packages/Bugs throughout next 7 days so that we a list to evaluate in the next meeting.-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * Once a list of potential target Packages/Bugs is defined, Balloons agreed to reach for developers.-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
== Apr. 4th. 2012 (kickoff) ==
'''References:'''<<BR>>
 * http://meetbot.fedoraproject.org/fedora-bugzappers/2012-03-02/f17-beta-blocker-review-1.2012-03-02-17.00.html-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * https://bugzilla.redhat.com/show_bug.cgi?id=752650-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * http://fedoraproject.org/wiki/Blocker_Bug_FAQ-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * http://meetbot.fedoraproject.org/fedora-bugzappers/2012-03-02/f17-beta-blocker-review-1.2012-03-02-17.00.html-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-mgr-p-tracking-bugs.html-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
 * https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=785053I-- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-12T22:16:41Z)>>
Line 16: Line 28:
=== Endurance and regularity: How to make this strategy sustainable in long-term? ===
 * Previous strategies have failed in Ubuntu;
 * Other similar activities have also been discontinued or abandoned;
 * Why? Failure to get results (bugs fixed)? No interest from developers, testers? Failure to communicate and create awareness over the initiative? Poor and/or non-functional technical resources? Documentation?
== Next steps ==
'''Primary'''
 * Team meeting to evaluate this doc (April, 4th, 2100UTC) - '''OK''';
 * '''Next Team meeting''': Mature strategy and delegate tasks (April, 11th, 2100UTC);
 * Plan and host trial session - ?
'''Secondary'''
 * '''Next Team meeting''': Evaluate results, improve process and delegate new tasks (April, 18th, 2100UTC);
 * Communicate Ubuntu Governance Boards and obtain approval;
 * Request support from IRC Team leadership;
 * Inform QA-Related Teams and confirm support for upcoming sessions;
 * Develop and send "open invitation" to developers, via proper channels;
 * Evaluate potential packages and contact developers;
 * Define dates;
 * Publicize to community;
== Agenda - Next Team Meetings ==
Insert topics directly in the bullets below or mail Effenberg0x0 [at] Ubuntu.com if you'd like me to do it. '''Please sign your bullets with ``@``SIG``@`` at the end. It automatically adds your name and timestamp to your comments (when the page is saved, not when previewed), so we can keep track of who said what and when.'''
=== Apr. 15th. 2012 ===
 *
 *
 *
 *
 *
 *
=== Apr. 11th. 2012 ===		 = Other suggested topics =
Line 46: Line 31:
 * Mature strategy and delegate tasks -- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-06T23:52:38Z)>>
 * TASK: Everyone will study and suggest a list of packages/bugs, send them to Effenberg0x0 before next meeting.
 *
 *
 *
=== Apr. 4th. 2012 (kickoff) ===
Topics discussed at this meeting are being summarized and will be inserted here by Apr. 9th, 2012 (Monday) -- [[LaunchpadHome:effenberg0x0]] <<DateTime(2012-04-05T06:43:01Z)>>
'''References:'''<<BR>>
 * http://meetbot.fedoraproject.org/fedora-bugzappers/2012-03-02/f17-beta-blocker-review-1.2012-03-02-17.00.html
 * https://bugzilla.redhat.com/show_bug.cgi?id=752650
 * http://fedoraproject.org/wiki/Blocker_Bug_FAQ
 * http://meetbot.fedoraproject.org/fedora-bugzappers/2012-03-02/f17-beta-blocker-review-1.2012-03-02-17.00.html
 * http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-mgr-p-tracking-bugs.html
 * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244
 * https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=785053I

About
IconsPage/picto_articles_48.png

• Home
• About the Project

DocsIconsPage/picto_articles_48.png

• Project Specifications
• Meeting Reports, ToDo and Agenda

Live TestingIconsPage/picto_articles_48.png

• Sessions Schedule
• Sessions Reports

ContactIconsPage/picto_articles_48.png

• Contact the Team

Click here to access full instructions for the current Live Testing Session.

Agenda

Apr. 18 2012

Suggested Topics:
Add your suggestion drectly to the bullets below. Please add the @SIG@macro at the end of the line. When you save the page, your name/timestamp will be automatically added.

  • Check if groups of selected testers (Cariboo907)has accepted to participate.-- effenberg0x0 2012-04-12 22:16:41

  • Check and discuss list of target Packages/Bugs sent by team members during the week. Define final list.

  • Confirm who will approach developers for the selected targets (Balloons?) and if help from other member is needed for this task.-- effenberg0x0 2012-04-12 22:16:41

  • Decide who will be responsible for creating LiveTesting Page, which contains all the info for the testing session.-- effenberg0x0 2012-04-12 22:16:41

  • Decide who will approach IRC Management and get us infrastructure (and, also, if that will be needed in the trial).-- effenberg0x0 2012-04-12 22:16:41

  • ToDo: Wait for feedback from developers. Once a developers accepts to take part in the trial, we can proceed to creating the documentation and setting up a date.-- effenberg0x0 2012-04-12 22:16:41

Previous Meetings

Apr. 12 2012

  • Cariboo907 has selected a group of testers and will approach them. He will communicate us of the status of this process in the next meeting.-- effenberg0x0 2012-04-12 22:16:41

  • The group agreed to study and select potential target Packages/Bugs throughout next 7 days so that we a list to evaluate in the next meeting.-- effenberg0x0 2012-04-12 22:16:41

  • Once a list of potential target Packages/Bugs is defined, Balloons agreed to reach for developers.-- effenberg0x0 2012-04-12 22:16:41

Apr. 4th. 2012 (kickoff)

References:

Other suggested topics

  • Discuss previous attempts, linked at the topic "Ubuntu Previous Attempts" in this document (see index). They were completely unknown to me. Why did they fail? What can we learn from them? -- effenberg0x0 2012-04-05 06:59:22

  • Infrastructure: A more "in-depth" look at Fedora's implementation revealed to me some infrastructure we currently do not have: Special repos for Live Testing ISOs, Testing Builds of packages updated during the session, a tracker updated in real time during the session, with testing results of session participants, a system to host each tester hardware profile (relevant for developers to evaluate each test result vs hardware tested). -- effenberg0x0 2012-04-05 06:59:22

LiveTesting/MeetingReports (last edited 2012-04-12 22:24:57 by 189)