From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-webteam/2011-January/000102.html | 111 ++++++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 zarb-ml/mageia-webteam/2011-January/000102.html (limited to 'zarb-ml/mageia-webteam/2011-January/000102.html') diff --git a/zarb-ml/mageia-webteam/2011-January/000102.html b/zarb-ml/mageia-webteam/2011-January/000102.html new file mode 100644 index 000000000..d3e93ff03 --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-January/000102.html @@ -0,0 +1,111 @@ + + + + [Mageia-webteam] Webteam peers, bootstrapping + + + + + + + + + +

[Mageia-webteam] Webteam peers, bootstrapping

+ Maât + maat-ml at vilarem.net +
+ Thu Jan 6 18:23:20 CET 2011 +

+
+ +
Le 06/01/2011 17:44, Romain d'Alverny a écrit :
+> On Thu, Jan 6, 2011 at 15:25, Maât <maat-ml at vilarem.net> wrote:
+>> Le 06/01/2011 14:27, Romain d'Alverny a écrit :
+>>>      - of course, something making push/merge requests possible could
+>>> help (writable only by manager+webmasters, leaving everyone else push
+>>> changes to be merged after review)
+>> Have we designed the standard lifecycles for patches and the standard merge/qualification processes ?
+> Not. We need some practice on this first I guess.
+k
+
+>>>    - some limited commands? what type? rsync/svn/git types?
+>>>
+>> for example : forums we'll be deploying forums versions with git
+> Ok, but that does not necessarily mean access to the server (this can
+> be triggered indirectly).
+Yup but this means coding yet an other specific wrapper ?
+
+
+>>>  * server deployment:
+>>>    - staging from a branch available to all peers
+> That is, ability to sync trunk (or whatever branch) to staging server.
+> That's an option that allows everyone to see up-to-date working apps
+> (and to quickly acknolewge broken ones). Or we can have a cron from
+> VCS to staging.
+>
+> Romain
+This imply limiting ourselves to one trunk and limiting our capacity to thread features developement nope ?
+
+I'd rather see a model with many trunks/tags/branches available for (one for each active dev) and ~user dirs allowing people to switch their personnal instance to the trunk/tag/branch they want to play with...
+
+for a given project we would have a SVN repos organization like that :
+
+$baseurl/$project_root/main/{trunk|tags|branches}
+
+
+$baseurl/$project_root/devs/$nickname/{trunk|tags|branches}
+
+
+$baseurl/$project_root = name of the application
+
+
+$baseurl/$project_root/devs/$nickname => repos dedicated to $nickname developer work
+
+
+$baseurl/$project_root/main => official public repos where "webmasters" merge developpers work
+
+Then for apache testing organization we could have :
+
+http://thesdeverver.mageia.org/manager => where $nickname can log on and click to switch it's own instance to what he wants (application,repository,tag or branch or trunk)
+
+http://the-dev-server.mageia.org/testing/~$nickname/ => where he tests the application he just switched to
+
+what do you think ?
+
+
+
+ + + +
+

+ +
+More information about the Mageia-webteam +mailing list
+ -- cgit v1.2.1