11:10 p.m.
At the usual time and place - #fedora-meeting on freenode, 1500UTC (that's 10AM US
Eastern).
Agenda:
- Fedora 11 Alpha
- status
- review of test procedures / results
- Wiki use
- Guidelines for naming test plans / test cases
- QA team guidelines
- Who gets to vote on decisions? Sponsors?
- How do you get to be a QA team sponsor?
- How do you get to be a QA team member?
- What does being in the QA team require/provide?
- Open floor / misc.
Note that the guidelines being discussed will *not* be final decisions. We're going to
come up with some ideas and propose them to the list for feedback, and vote on them in a
future meeting.
If you've got something to discuss, reply to this mail or come to the meeting.
Thanks!
-w
5:31 a.m.
Will Woods wrote:
At the usual time and place - #fedora-meeting on freenode, 1500UTC
(that's 10AM US Eastern).
So have we moved the meeting time from16:00 back to 15:00?
Agenda:
- Fedora 11 Alpha
- status
- review of test procedures / results
- Wiki use
- Guidelines for naming test plans / test cases
- QA team guidelines
- Who gets to vote on decisions? Sponsors?
- How do you get to be a QA team sponsor?
- How do you get to be a QA team member?
- What does being in the QA team require/provide?
Let's first come up with a QA team made from the community for the
community
before coming up with any guidelines for QA
I want everyone to take a look at http://sqa.net/
and consider the Fedora QA procedure will be moved in that direction.
The idea is that there will be made QA board consisting of one
representing from each SIG
That representative task will be over sighting the QA of his SIG and
this board over sighting the QA of the whole Fedoraproject.
Example for the ART team is the art consistent are there any missing
icons for package etc..
Example for Doc team could be like are documentation up to standard any
man pages missing etc...
Any software related SIG would be responsible for that SIG components
works as advertised and provide the
SQC with test cases test Plans ( or ask them for help to come up with
those test plans test cases )
And so on..
The current QA form will become SQC and the SQC board will consist of
equal number from both Testers and Triagers and
any other team within Fedora that might fall under the definition of SQC
Preferable those representatives will be from different parts of the
world you would not have 2 from triage team from the states
or 2 from testers team from the states in that board.
- Open floor / misc.
This can be added to that meetings agenda.
Redirect all the test related topics that end on devel to the test list.
If developers aren't subscribed to this list they should be.
Improve packagers rawhide/updates testing report
1. They provide bug number of the bug that was fixed ( atleast if that
bug is in our bugzilla )
2. Provide CVE reference if this was a security fix.
3. Enhancements should be described well or an url is provided either on
the form http://www.exampleproject.org/path/to/changlog
or file:///usr/share/doc/<component>/changelog
These are vital information for the SQC process to have.
Ideas to get maintainers/developers to start using the both this list
and fedora-qa tickets system.
Define what services the SQC offerst maintainers and what it expects
from them to improve SQC.
JBG
5:51 a.m.
Jóhann B. Guðmundsson wrote:
Will Woods wrote:
> At the usual time and place - #fedora-meeting on freenode, 1500UTC
> (that's 10AM US Eastern).
>
So have we moved the meeting time from16:00 back to 15:00?
Not sure on the time, Will was either up late or early when he sent that. :)
Leam
9:16 a.m.
On Wed, 2009-02-04 at 11:31 +0000, "Jóhann B. Guðmundsson" wrote:
Will Woods wrote:
> At the usual time and place - #fedora-meeting on freenode, 1500UTC (that's 10AM
US Eastern).
>
So have we moved the meeting time from16:00 back to 15:00?
> Agenda:
>
> - Fedora 11 Alpha
> - status
> - review of test procedures / results
> - Wiki use
> - Guidelines for naming test plans / test cases
>
> - QA team guidelines
> - Who gets to vote on decisions? Sponsors?
> - How do you get to be a QA team sponsor?
> - How do you get to be a QA team member?
> - What does being in the QA team require/provide?
>
Let's first come up with a QA team made from the community for the community
before coming up with any guidelines for QA
I want everyone to take a look at http://sqa.net/
and consider the Fedora QA procedure will be moved in that direction.
The idea is that there will be made QA board consisting of one
representing from each SIG
That representative task will be over sighting the QA of his SIG and
this board over sighting the QA of the whole Fedoraproject.
There are good general quality practices and procedures listed at the
URL provide above. But they also assume a level of resources we don't
yet have. Over time as we gather more contributors, this could be
something to look into.
I do like the idea of outlining a structure so that specialty QA groups
with similar interests can coalesce and provide service to other Fedora
teams. Leam Hall has begun pulling some of this together to flesh out a
new "Join Fedora" QA landing page.
Thanks,
James
9:23 a.m.
James Laska wrote:
On Wed, 2009-02-04 at 11:31 +0000, "Jóhann B. Guðmundsson"
wrote:
> Will Woods wrote:
>
>> At the usual time and place - #fedora-meeting on freenode, 1500UTC (that's
10AM US Eastern).
>>
>>
> So have we moved the meeting time from16:00 back to 15:00?
>
>> Agenda:
>>
>> - Fedora 11 Alpha
>> - status
>> - review of test procedures / results
>> - Wiki use
>> - Guidelines for naming test plans / test cases
>>
>> - QA team guidelines
>> - Who gets to vote on decisions? Sponsors?
>> - How do you get to be a QA team sponsor?
>> - How do you get to be a QA team member?
>> - What does being in the QA team require/provide?
>>
>>
> Let's first come up with a QA team made from the community for the community
> before coming up with any guidelines for QA
>
> I want everyone to take a look at http://sqa.net/
> and consider the Fedora QA procedure will be moved in that direction.
>
> The idea is that there will be made QA board consisting of one
> representing from each SIG
>
> That representative task will be over sighting the QA of his SIG and
> this board over sighting the QA of the whole Fedoraproject.
>
There are good general quality practices and procedures listed at the
URL provide above. But they also assume a level of resources we don't
yet have. Over time as we gather more contributors, this could be
something to look into.
I say look into it now then add those contributes to the resource we have.
I do like the idea of outlining a structure so that specialty QA
groups
with similar interests can coalesce and provide service to other Fedora
teams. Leam Hall has begun pulling some of this together to flesh out a
new "Join Fedora" QA landing page.
Looking forward to the see that page.
JBG
9:38 a.m.
Jóhann B. Guðmundsson wrote:
James Laska wrote:
I say look into it now then add those contributes to the resource we
have.
> I do like the idea of outlining a structure so that specialty QA groups
> with similar interests can coalesce and provide service to other Fedora
> teams. Leam Hall has begun pulling some of this together to flesh out a
> new "Join Fedora" QA landing page.
>
>
Looking forward to the see that page.
JBG
Well, it ain't all that...
https://fedoraproject.org/wiki/Leam
But I'm keeping my thought process on the page, in italics. That way we
can brain-share a bit up front and then remove it later.
Leam/leitz
5562
days inactive
5562
days old
5 comments
4 participants
participants (4)
-
"Jóhann B. Guðmundsson" -
James Laska -
Leam Hall -
Will Woods