diff options
Diffstat (limited to 'zarb-ml/mageia-webteam/attachments/20110211/5be8dbb2/attachment.html')
| -rw-r--r-- | zarb-ml/mageia-webteam/attachments/20110211/5be8dbb2/attachment.html | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/attachments/20110211/5be8dbb2/attachment.html b/zarb-ml/mageia-webteam/attachments/20110211/5be8dbb2/attachment.html new file mode 100644 index 000000000..ac695dcde --- /dev/null +++ b/zarb-ml/mageia-webteam/attachments/20110211/5be8dbb2/attachment.html @@ -0,0 +1,16 @@ +Re,<br><br><div class="gmail_quote">2011/2/11 Romain d'Alverny <span dir="ltr"><<a href="mailto:rdalverny@gmail.com">rdalverny@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +just to lay down a few cross-apps/server issues, related to alpha 1<br> +release reception by the public.<br></blockquote><div><br></div><div>maybe definition of alpha1 may be precised, I suggest : testing the whole infrastructure (building, distribution, mirrors, publication of release_notes / errata / faq / how to become involved identifying what people want to do and can do... giving them proper tools and identifying what could be done).</div> +<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> + * other I may have missed? </blockquote></div><br><div>yep, a real wiki :-) the current one (temporary) not enabling teams to work together at full speed :/ I think to artwork - web team -and even translators (and users).</div> +<div><br></div><div>some time ago I wanted to propose <a href="http://mageiacauldron.tuxfamily.org/MageiaWiki">http://mageiacauldron.tuxfamily.org/MageiaWiki</a></div><div>and I think that <a href="http://mageia.org/wiki/doku.php?id=wiki_requirements">http://mageia.org/wiki/doku.php?id=wiki_requirements</a> is complementary, both could merge ;-)</div> +<div>There's <a href="http://www.mageia.org/wiki/doku.php?id=web:wiki">http://www.mageia.org/wiki/doku.php?id=web:wiki</a> too</div><div><br></div><div>To be fair, I'm a bit biased towards a wiki that promotes self organization as we can see at <a href="http://mageia.org/wiki">http://mageia.org/wiki</a> : I would prefer to have people document, enhance content and explain than discuss endlessly on ML (once a consensus is reached a wiki can document it, with references if needed).</div> +<div><br></div><div>At the moment, we've reached critical mass(*) to begin the release process and alpha needs publishing errata and release notes imho (with common pitfalls, faq, known-workaround...). As an example, have a look at <a href="http://wiki.mandriva.com/en/2010.1_Development">http://wiki.mandriva.com/en/2010.1_Development</a> and <a href="http://wiki.mandriva.com/en/2010.1_Alpha_1">http://wiki.mandriva.com/en/2010.1_Alpha_1</a> then wonder "where do we publish it currently?" in a ML ? (please ask if I'm not suficiently precise, yeah I know that ).</div> +<div>(*) developers can document, marketing could structure it all, artwork team can work on css, translators may be involved too, collaborative work can begin with a focus and anyone wanting to get involved, delegation may begin with simply editing a wiki (easy for anyone imho), this would mean team-building by effective exchanges available to everyone :)</div> +<div><br></div><div><br></div><div>For effective availability, I would see : </div><div>- a basic instance available for testing [<a href="http://dev.wiki.mageia.org">http://dev.wiki.mageia.org</a>] </div><div>- packaging mediawiki (done) and identified plugin (being done) for sysadm satisfaction, let's make available what we use and build teams around it :-) (dev, packaging, testing, using with comm and artwork involved)</div> +<div>- involve people in participation around a tool that permits to publish (with discussion either on wiki or ML), local involvement with translations or initiatives (let's get people not speaking english to involve :p).</div> +<div>- for production <a href="http://wiki.mageia.org">http://wiki.mageia.org</a> in any language, let's choose to go forward and just deploy it then see how people can use it :-) (requiring other plugins to be packaged or working through -discuss ML or with discussion page once created in their own language, that's the purpose of alpha1 imho to test the infrastructure and create team-building)</div> +<div><br></div><div>IMHO, a forum will come when needed, but I think that a wiki can enhance our answers, explaining in 3 lines in a post (on ML currently, on forum later on) what people can find on the wiki far more detailed :-)</div> +<div><br></div><div>At the moment, we have <a href="http://mageia.org/wiki/doku.php?id=policies-review">http://mageia.org/wiki/doku.php?id=policies-review</a> which lists long term documentation that should be translated for anyone to get involved. I'm a bit disappointed that it does not happen on a stabilized plateform with clear license policy and long term enhancements :/</div> +<div><br></div><div>well, I should bring this subject to -discuss but I wanted to have your feedback before it begins for real :-) so WDYT ? maybe a blog post can explain how we are going to deploy alpha1 for this sunday ? who is concerned with iso testing ? who is concerned with wiki testing ? (can we make it with catdap and missing plugins ?) who can be involved and what tasks should be done at the moment (packagers, developers, testers, marketing, communication, mirrors, council, board, translators, triage, sysadm, artwork, moderators, users and anyone that want to follow what is being done?)</div> +<div><br></div><div>I think that an official wiki would get all people to involve, in a long term participation, WDYT ?</div><div>@++</div><div>Ben' aka baud123</div> |