diff options
Diffstat (limited to 'zarb-ml/mageia-webteam/2011-January/000100.html')
-rw-r--r-- | zarb-ml/mageia-webteam/2011-January/000100.html | 137 |
1 files changed, 137 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000100.html b/zarb-ml/mageia-webteam/2011-January/000100.html new file mode 100644 index 000000000..5fd8a1975 --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-January/000100.html @@ -0,0 +1,137 @@ +<!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=%3CAANLkTimfTXnEhsivYnLeXk%3DS5P42mZNEFN%3DOJvj-izP6%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="000098.html"> + <LINK REL="Next" HREF="000101.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-webteam] Webteam peers, bootstrapping</H1> + <B>Romain d'Alverny</B> + <A HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Webteam%20peers%2C%20bootstrapping&In-Reply-To=%3CAANLkTimfTXnEhsivYnLeXk%3DS5P42mZNEFN%3DOJvj-izP6%40mail.gmail.com%3E" + TITLE="[Mageia-webteam] Webteam peers, bootstrapping">rdalverny at gmail.com + </A><BR> + <I>Thu Jan 6 18:05:00 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000098.html">[Mageia-webteam] Webteam peers, bootstrapping +</A></li> + <LI>Next message: <A HREF="000101.html">[Mageia-webteam] Calendar on the website +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#100">[ date ]</a> + <a href="thread.html#100">[ thread ]</a> + <a href="subject.html#100">[ subject ]</a> + <a href="author.html#100">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, Jan 6, 2011 at 15:44, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-webteam">misc at zarb.org</A>> wrote: +><i> Le jeudi 06 janvier 2011 à 14:27 +0100, Romain d'Alverny a écrit : +</I>>><i>  * VCSes: +</I>>><i>    - read access for everyone (peers & non-peers); +</I>><i> the easy part +</I> +Always start with the easy part. + +>><i>    - write access for: +</I>>><i>      - webmasters (specific role, see below) +</I>><i> so we need a group in ldap for that, i guess ? +</I> +Yes. + +><i> For git like all dvcs, we are slightly more free in term of workflow, as +</I>><i> explained for example here +</I>><i> <A HREF="http://doc.bazaar.canonical.com/bzr.1.18-html/en/user-guide/bazaar_workflows.html">http://doc.bazaar.canonical.com/bzr.1.18-html/en/user-guide/bazaar_workflows.html</A> . +</I>><i> +</I>><i> And so I feel that industrialisation of project hosting ( as we are +</I>><i> somehow starting to do ) will be detrimental to the freedom of choice, +</I>><i> and we should agree on a few workflow before starting to deploy too much +</I>><i> things. ( ie, if we do want to automate thing, and that's one of the +</I>><i> sysadmin team goal ). +</I>><i> +</I>><i> Deploying a simple git repository managed like a svn one would be easy +</I>><i> and fast. But that would be marginally better than git-svn. +</I> +Indeed, unless you adapt manually for each project (one with a +gatekeeper merging changes, one with open bar^Waccess, etc.) + +><i> Deploying a full system with workflow delegation is much more difficult, +</I>><i> but that's what we would want. +</I> +Well... I may write it too fast, but I am not sure that, for instance +a gitorious setup (hard part) would prevent several workflows to grow +depending on the team working on it. + +><i> So a compromise would be to decide for 1 simple workflow, use for +</I>><i> everything in the first place, and postpone the deployment of a full +</I>><i> system to later. +</I> +Yes, but what workflow then? + +>><i>  * server logs: +</I>>><i>    - read access to webmasters +</I>>><i>    - some limited commands? what type? rsync/svn/git types? +</I>><i> +</I>><i> Well, limited command could be hard to achieve. I assume that read logs +</I>><i> is just "set permission properly" ( easy to do ). Limitation of command +</I>><i> could be done with sudo, but wouldn't change much if we give access to +</I>><i> shell. +</I>><i> +</I>>><i>  * server deployment: +</I>>><i>    - staging from a branch available to all peers +</I>>><i>    - production push from staging available to webmasters only +</I>><i> +</I>><i> We can : +</I>><i> - use sudo + script + ldap group +</I>><i> - use $VCS based tags/branch + acl ( potentially based on ldap group +</I>><i> again ) +</I> +Hmm, sorry I'm lost here. + +><i> ( and I am picky, but sysadmin is the name of the team +</I>><i> in ldap, I do not know why people say sysadm everywhere, likely because +</I>><i> of the name of the list and irc channel  :/ ). +</I> +Indeed :-p and that's 2 (!) chars less to type. + +><i> So to summarize : +</I>><i> - external people +</I>><i> - webteam members +</I>><i> - webmasters +</I>><i> +</I>><i> So 1st step, adding 2 group to ldap ? +</I> +Yep. webmasters and webpeers (or webteam members). + +Romain +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000098.html">[Mageia-webteam] Webteam peers, bootstrapping +</A></li> + <LI>Next message: <A HREF="000101.html">[Mageia-webteam] Calendar on the website +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#100">[ date ]</a> + <a href="thread.html#100">[ thread ]</a> + <a href="subject.html#100">[ subject ]</a> + <a href="author.html#100">[ 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> |