summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2011-March/003231.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-March/003231.html')
-rw-r--r--zarb-ml/mageia-sysadm/2011-March/003231.html146
1 files changed, 146 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-March/003231.html b/zarb-ml/mageia-sysadm/2011-March/003231.html
new file mode 100644
index 000000000..b59f4865c
--- /dev/null
+++ b/zarb-ml/mageia-sysadm/2011-March/003231.html
@@ -0,0 +1,146 @@
+<!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=%3C1301597259.10310.293.camel%40akroma.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="003230.html">
+ <LINK REL="Next" HREF="003232.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-sysadm] ML request for QAteam</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20ML%20request%20for%20QAteam&In-Reply-To=%3C1301597259.10310.293.camel%40akroma.ephaone.org%3E"
+ TITLE="[Mageia-sysadm] ML request for QAteam">misc at zarb.org
+ </A><BR>
+ <I>Thu Mar 31 20:47:39 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="003230.html">[Mageia-sysadm] ML request for QAteam
+</A></li>
+ <LI>Next message: <A HREF="003232.html">[Mageia-sysadm] ML request for QAteam
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3231">[ date ]</a>
+ <a href="thread.html#3231">[ thread ]</a>
+ <a href="subject.html#3231">[ subject ]</a>
+ <a href="author.html#3231">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le jeudi 31 mars 2011 &#224; 17:41 +0200, Romain d'Alverny a &#233;crit :
+&gt;<i> On Thu, Mar 31, 2011 at 14:02, Michael Scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>&gt; wrote:
+</I>&gt;<i> &gt; For the name, well, I am not much satisfied with qateam, as I find this
+</I>&gt;<i> &gt; to be quite non descriptive for people who are not previous mandriva
+</I>&gt;<i> &gt; people ( ie for almost everybody except a few ).
+</I>&gt;<i> &gt; So I am sure that we can find a better and more descriptive name, or at
+</I>&gt;<i> &gt; least try to find a better one.
+</I>&gt;<i>
+</I>&gt;<i> qateam =&gt; QA team, as there's one in the project? (such as could be
+</I>&gt;<i> webteam@, secteam@, commteam@, etc.?
+</I>&gt;<i>
+</I>&gt;<i> I would find this more descriptive as to the purpose/role of the list
+</I>&gt;<i> (team list) than just qa@, web@, security@ which would be, in turn,
+</I>&gt;<i> more descriptive of a contact email address.
+</I>
+I would also find more descriptive the purpose rather than the group
+name. For example, -dev instead of packagersteam@, ie focused on
+activity ( developping ) rather than the team naming ( packagers ). This
+would be imho be clearer if we want to foster cross team activities.
+
+&gt;<i> Or maybe <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">qa-team at ml.mageia.org</A> then?
+</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
+ldap group mga-foo ( which is used to define a team so far for all
+others teams ). We could also use team.mageia.org ( but that would make
+thing more complex as not not all groups are a team ).
+
+I think we can all agree that the canonical list of member of a team is
+in a ldap group for all teams ( because that's what we did so far for
+web application integration, catdap integration, sympa integration,
+epoll integration, etc ).
+
+So if the qa team is the list of people in the ldap group mga-qa,
+it is confusing to refer to a 2nd group ( the list of people who
+subscribed to the ml, and who would be ) as qateam.
+
+
+&gt;<i> (yes, it comes out too from years of practice of this naming scheme at
+</I>&gt;<i> Mandriva where, well, these were internal list names/aliases - but
+</I>&gt;<i> here it would be public as team's lists are :-p ).
+</I>
+On mandriva qateam alias/ml, who was behind ?
+
+While I was not here so I am maybe wrong, I suspect the aliases matched
+exactly the internal organisation.
+
+Here, I do not know exactly because Damien ask for a public list, and to
+me that mean a list were anybody can subscribe and post, but maybe he
+mean a list that anybody can read ( something like council ).
+
+So in the hypothesis that the list is not restricted to members of the
+team, the name would be misleading.
+
+If the list is restricted, i think we would need a unrestricted list.
+( hence another name would be chose ).
+
+
+I would also add that it seems that people on the wiki
+( <A HREF="http://mageia.org/wiki/doku.php?id=qateam">http://mageia.org/wiki/doku.php?id=qateam</A> ) have a different view of
+QA than what is written as a description ( and the purpose is the same
+as others team like debian one <A HREF="http://wiki.debian.org/qa.debian.org/">http://wiki.debian.org/qa.debian.org/</A>
+and ubuntu <A HREF="https://wiki.ubuntu.com/QATeam/">https://wiki.ubuntu.com/QATeam/</A> ).
+
+And the ratio of people saying &quot;automation tool&quot; vs &quot;test packages&quot; on
+<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
+automation, 53 for &quot;testing&quot; ).
+
+So while the plan for qateam is also to do automation ( and I have been
+working on making easy to install virtual machines also for that this
+night ), I think that most people on the wiki page are here to do tests.
+
+
+Moreover, those historically interested in QA ( such as me see
+<A HREF="http://www.zarb.org/~misc/slides/cooker.sxi,">http://www.zarb.org/~misc/slides/cooker.sxi,</A> nanar, pterjan, etc ) will
+likely discuss the matter either on -dev ( for feedback on technical
+level ) and then on -sysadmin ( for deployment ). I do not think a 3rd
+list would bring much.
+
+
+So maybe the list name should reflect more closely the activity ?
+Something like <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">distribution-testers at ml</A> ( or a shorter name like
+distro-test@ ) would be a more suitable ?
+
+I add distribution because if we decide to do more than a distribution,
+this would be clearer in the long run.
+
+Maybe I am also thinking too much of course.
+--
+Michael Scherer
+
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="003230.html">[Mageia-sysadm] ML request for QAteam
+</A></li>
+ <LI>Next message: <A HREF="003232.html">[Mageia-sysadm] ML request for QAteam
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3231">[ date ]</a>
+ <a href="thread.html#3231">[ thread ]</a>
+ <a href="subject.html#3231">[ subject ]</a>
+ <a href="author.html#3231">[ 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>