diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-March/003232.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2011-March/003232.html | 161 |
1 files changed, 161 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-March/003232.html b/zarb-ml/mageia-sysadm/2011-March/003232.html new file mode 100644 index 000000000..72d1bf796 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-March/003232.html @@ -0,0 +1,161 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] ML request for QAteam + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20ML%20request%20for%20QAteam&In-Reply-To=%3CAANLkTinOdPr-wiQYMOEZX393QM1B-DB2JkzSMVM5NXJ1%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003231.html"> + <LINK REL="Next" HREF="003228.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] ML request for QAteam</H1> + <B>Romain d'Alverny</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20ML%20request%20for%20QAteam&In-Reply-To=%3CAANLkTinOdPr-wiQYMOEZX393QM1B-DB2JkzSMVM5NXJ1%40mail.gmail.com%3E" + TITLE="[Mageia-sysadm] ML request for QAteam">rdalverny at gmail.com + </A><BR> + <I>Thu Mar 31 21:33:44 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003231.html">[Mageia-sysadm] ML request for QAteam +</A></li> + <LI>Next message: <A HREF="003228.html">[Mageia-sysadm] NFrance and Mageia forums hosting +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3232">[ date ]</a> + <a href="thread.html#3232">[ thread ]</a> + <a href="subject.html#3232">[ subject ]</a> + <a href="author.html#3232">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, Mar 31, 2011 at 20:47, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>> wrote: +><i> Le jeudi 31 mars 2011 à 17:41 +0200, Romain d'Alverny a écrit : +</I>><i> I would also find more descriptive the purpose rather than the group +</I>><i> name. For example, -dev instead of packagersteam@, ie focused on +</I>><i> activity ( developping ) rather than the team naming ( packagers ). This +</I>><i> would be imho be clearer if we want to foster cross team activities. +</I> +Well, there was a plan to have both activities (packaging and +development). It happens that, for now, packaging is the focus. And +packaging and developing are two separate activities, and having +devteam@ and packteam@ for instance, could make sense as well. + +So the point is not here. + +>><i> Or maybe <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">qa-team at ml.mageia.org</A> then? +</I>><i> +</I>><i> But we do have <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">foo at group.mageia.org</A> for that, to send a email to the +</I>><i> ldap group mga-foo ( which is used to define a team so far for all +</I>><i> others teams ). We could also use team.mageia.org ( but that would make +</I>><i> thing more complex as not not all groups are a team ). +</I>><i> +</I>><i> I think we can all agree that the canonical list of member of a team is +</I>><i> in a ldap group for all teams ( because that's what we did so far for +</I>><i> web application integration, catdap integration, sympa integration, +</I>><i> epoll integration, etc ). +</I> +Yes, but we discussed (several months ago) too to remind that it's not +because one is (or is not) a team member that it would necessarily be +subscribed to the team list; that should not be a bijective +relationship. + +><i> So if the qa team is the list of people in the ldap group mga-qa, +</I>><i> it is confusing to refer to a 2nd group ( the list of people who +</I>><i> subscribed to the ml, and who would be ) as qateam. +</I> +There's the informal team list, where non-peers can subscribe and +participate. That's the mailing-list (communication/collaboration +goals). + +And there's the formal team, made of peers only. That's the LDAP group +(credential/recognition goal). + +These are two distinct sets that don't match exactly with each other. + +>><i> (yes, it comes out too from years of practice of this naming scheme at +</I>>><i> Mandriva where, well, these were internal list names/aliases - but +</I>>><i> here it would be public as team's lists are :-p ). +</I>><i> +</I>><i> On mandriva qateam alias/ml, who was behind  ? +</I>><i> +</I>><i> While I was not here so I am maybe wrong, I suspect the aliases matched +</I>><i> exactly the internal organisation. +</I> +Far from that. Cross-teams information + +><i> Here, I do not know exactly because Damien ask for a public list, and to +</I>><i> me that mean a list were anybody can subscribe and post, but maybe he +</I>><i> mean a list that anybody can read ( something like council ). +</I>><i> +</I>><i> So in the hypothesis that the list is not restricted to members of the +</I>><i> team, the name would be misleading. +</I> +We have already <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">mageia-webteam at mageia.org.</A> That's the team discussion +list, and it is open to everyone (lurkers included). Only a little +subset of its subscribers are team peers. And that is perfectly fine. + +The only best convenient alternative approach I could see at this time +would be setting up a Wordpress blog + P2 theme + posting access to +everyone - and limit afterwise to subscribed users in case of detected +abuse (but that's not even considered, no need for it). + +If we were to move the Web team ml to ml.mageia.org (I guess that will +happen some day) it should not strictly tie ml membership to team +membership - these are two different things. + + +><i> If the list is restricted, i think we would need a unrestricted list. +</I>><i> ( hence another name would be chose ). +</I> +I don't think Damien meant for a restricted list. + +><i> I would also add that it seems that people on the wiki +</I>><i> ( <A HREF="http://mageia.org/wiki/doku.php?id=qateam">http://mageia.org/wiki/doku.php?id=qateam</A> ) have a different view of +</I>><i> QA than what is written as a description ( and the purpose is the same +</I>><i> as others team like debian one  <A HREF="http://wiki.debian.org/qa.debian.org/">http://wiki.debian.org/qa.debian.org/</A> +</I>><i> and ubuntu <A HREF="https://wiki.ubuntu.com/QATeam/">https://wiki.ubuntu.com/QATeam/</A> ). +</I>><i> +</I>><i> And the ratio of people saying "automation tool" vs "test packages" on +</I>><i> <A HREF="http://mageia.org/wiki/doku.php?id=qateam">http://mageia.org/wiki/doku.php?id=qateam</A> is quite clear ( 1 people for +</I>><i> automation, 53 for "testing" ). +</I> +But that should not prevent the QA team to be further designed and +built for both practices (and still bear the "QA" name, as that's what +it is about). + +Testers are testers, but maybe not necessarily meant to be QA team +peers that _organize_ and coordonate things - it's not because it does +not stand out yet that a QA team can't be setup at all as such (look +at marketing and communication teams - they are not there yet, but +that doesn't prevent to work for it slowly). + + + +Have a great week-end, + +Romain +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003231.html">[Mageia-sysadm] ML request for QAteam +</A></li> + <LI>Next message: <A HREF="003228.html">[Mageia-sysadm] NFrance and Mageia forums hosting +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3232">[ date ]</a> + <a href="thread.html#3232">[ thread ]</a> + <a href="subject.html#3232">[ subject ]</a> + <a href="author.html#3232">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |