summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-webteam/2011-January/000097.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-webteam/2011-January/000097.html')
-rw-r--r--zarb-ml/mageia-webteam/2011-January/000097.html123
1 files changed, 123 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000097.html b/zarb-ml/mageia-webteam/2011-January/000097.html
new file mode 100644
index 000000000..6ac753f0b
--- /dev/null
+++ b/zarb-ml/mageia-webteam/2011-January/000097.html
@@ -0,0 +1,123 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-webteam] Webteam peers, bootstrapping
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Webteam%20peers%2C%20bootstrapping&In-Reply-To=%3C4D25D0E9.3060704%40vilarem.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000096.html">
+ <LINK REL="Next" HREF="000099.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-webteam] Webteam peers, bootstrapping</H1>
+ <B>Ma&#226;t</B>
+ <A HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Webteam%20peers%2C%20bootstrapping&In-Reply-To=%3C4D25D0E9.3060704%40vilarem.net%3E"
+ TITLE="[Mageia-webteam] Webteam peers, bootstrapping">maat-ml at vilarem.net
+ </A><BR>
+ <I>Thu Jan 6 15:25:45 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000096.html">[Mageia-webteam] Webteam peers, bootstrapping
+</A></li>
+ <LI>Next message: <A HREF="000099.html">[Mageia-webteam] Webteam peers, bootstrapping
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#97">[ date ]</a>
+ <a href="thread.html#97">[ thread ]</a>
+ <a href="subject.html#97">[ subject ]</a>
+ <a href="author.html#97">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le 06/01/2011 14:27, Romain d'Alverny a &#233;crit :
+&gt;<i> On Thu, Jan 6, 2011 at 13:19, Michael Scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-webteam">misc at zarb.org</A>&gt; wrote:
+</I>&gt;&gt;<i> Le jeudi 06 janvier 2011 &#224; 12:09 +0100, Romain d'Alverny a &#233;crit :
+</I>&gt;&gt;&gt;<i> What do peers have that non-peers do not?
+</I>&gt;&gt;&gt;<i> [...]
+</I>&gt;&gt;<i> How are access to $VCS will be handled ?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> The possibility of having access to server to either read logs or run
+</I>&gt;&gt;<i> some limited commands was also asked, how would it articulate with this
+</I>&gt;&gt;<i> scheme ?
+</I>&gt;<i> I had written a &#167; about it but thought it was too early here. Anyway,
+</I>&gt;<i> here are my thoughts:
+</I>&gt;<i>
+</I>&gt;<i> * VCSes:
+</I>&gt;<i> - read access for everyone (peers &amp; non-peers);
+</I>&gt;<i> - write access for:
+</I>&gt;<i> - webmasters (specific role, see below)
+</I>&gt;<i> - app manager, who should in turn be able to provide a write
+</I>&gt;<i> access to other peers (developers), on demand? if that's possible
+</I>&gt;<i> - or for all peers, with each developer/app manager having a
+</I>&gt;<i> careful look at what happens.
+</I>Indeed integration and merging need to be controlled by a restricted number of people
+
+but we could also provide branches or repos with write access to developpers (subversions sub-repos are perfect for that unless we decide to use things like git or mercurial)
+
+but if i'm not mitaken there is nothing available offering such a fine grained access control :-/
+
+&gt;<i> - or maybe it can be app-specific (depending on the app-criticity)
+</I>&gt;<i> - of course, something making push/merge requests possible could
+</I>&gt;<i> help (writable only by manager+webmasters, leaving everyone else push
+</I>&gt;<i> changes to be merged after review)
+</I>&gt;<i>
+</I>Have we designed the standard lifecycles for patches and the standard merge/qualification processes ?
+&gt;<i> * server logs:
+</I>&gt;<i> - read access to webmasters
+</I>&gt;<i> - some limited commands? what type? rsync/svn/git types?
+</I>&gt;<i>
+</I>for example : forums we'll be deploying forums versions with git
+&gt;<i> * server deployment:
+</I>&gt;<i> - staging from a branch available to all peers
+</I>??
+&gt;<i> - production push from staging available to webmasters only
+</I>ok
+&gt;<i> Webmasters are necessarily peers; they do master the whole websites,
+</I>&gt;<i> deploy into production with the assistance of app developers (in
+</I>&gt;<i> short, with sysadm, they are the ones having the production-push
+</I>&gt;<i> button and the ability to check on logs). Of course, this requires
+</I>&gt;<i> webmasters &amp; sysadm to go along well.
+</I>yup
+&gt;<i> So sysadm would have at least a
+</I>&gt;<i> consultative say on who can become a webmaster.
+</I>&gt;<i>
+</I>agreed
+&gt;<i> At this time, this role is managed by (non-sysadm people): me and
+</I>&gt;<i> damsweb for blog/www (editorial stuff), I believe all the rest is
+</I>&gt;<i> pushed by sysadm at this time.
+</I>&gt;<i>
+</I>&gt;<i> Advice?
+</I>&gt;<i>
+</I>&gt;<i> Romain
+</I>OK with the schema but i wonder how we'll manage ACL part without pain :-/
+
+Ma&#226;t
+
+
+
+</PRE>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000096.html">[Mageia-webteam] Webteam peers, bootstrapping
+</A></li>
+ <LI>Next message: <A HREF="000099.html">[Mageia-webteam] Webteam peers, bootstrapping
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#97">[ date ]</a>
+ <a href="thread.html#97">[ thread ]</a>
+ <a href="subject.html#97">[ subject ]</a>
+ <a href="author.html#97">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-webteam">More information about the Mageia-webteam
+mailing list</a><br>
+</body></html>