[cp-global] Restarting the countries and languages discussion
sva at cryptoparty.in
Mon Mar 24 19:28:17 GMT 2014
I was part of that discussion, and already start writing about it, too.
Also I want to bring up a discussion on if all those lists and wikis are
really needed, see the other thread.
Here I propose how the wikis can be done at the backend:
Just namespaces of one dokuwiki, but if/how to implement that our
beloved serveradmin needs to tell :D
In dokuwiki namespaces can be hidden by alias, so e.g.
are the same wiki in the backend:
Every page started under fr.cryptoparty.org would be
wiki.cryptoparty.org/fr:home automagically. If Canada wants to have
ca.fr.cryptoparty.org they just get /fr:ca:home from the wiki. Still
they can hang up the canadian flag there :D
In that case we have the option on a search on all the content of all
the languages and countries but without the help of an external search
engine. Which is wonderful:
A wiki/website is in ideal a place where people just dump things (btw,
anyone explored this etherpad-plugin for dokuwiki already?) But imho the
power of dokuwiki is the _search_, and the "illness" of wikis is that
people have to put efford and time in layout and nice tagging/linking of
the page. So whatever is dumped, with the search you can find it.
For the cases like /fr:ca and /en:ca there might be a redirect possible
to /ca:, right?
So do we have covered all possible cases with such a setup? I hope the
assumption that MLs are mostly used to organizational stuff and
therefore makes the most sense on country/territorium is correct?
Knowledge sharing should really be done via the wiki I believe.
Its important to point out that everyone can get $language and/or
$country and whatever combination. (dokuwiki part I can serve for those
additional rquests, if it works as described) I wonder if it will be
many anyway ;)
And I hope I will finish the mail on the content question soon,
On 25.03.2014 00:13, Kai Engert wrote:
> - drop the idea of country wikis.
> - use language wikis. Use the same set of languages, and the same
> two-letter language codes as used by wikipedia.
> - still use country mailing lists, for regional/local coordination.
> - avoid ambiguity. Don't use two-letter codes for countries.
> Instead, use three-letter codes for countries.
> Longer explanation:
> In today's discussions on the IRC channel, there has been additional
> support for the idea that WIKIs should be LANGUAGE specific (independent
> of region).
> Language-specific Wiki Domain:
> However, mailing LISTS should still be COUNTRY specific (enabling
> regional coordination).
> Country-specific Mailing list:
> (country-id) @ (country-id).cryptoparty.org
> There has been the question, which languages to use, and which codes
> (abbreviations) to use for languages and countries.
> Also, we should avoid ambiguity. We'll require separate domains for
> languages and countries.
> There are many languages in the world. We should restrict the set of
> wikis to the major ones. One suggestion is: Only use languages which are
> big enough to have been assigned a two-letter language code.
> The use of two-letter language codes seems reasonable, because wikipedia
> has used the same approach. If we reuse that principle, people will
> immediately understand it.
> In order to avoid ambiguity, we need different identifiers for country
> subdomains and the country mailing lists.
> The proposal is to use the three-letter country codes.
> Giving an example, let's look at Portual and Brazil, who both use the
> Portuese language. We'd setup the following:
> Only one wiki:
> Two mailing lists:
> bra [at] bra.cryptoparty.org
> prt [at] prt.cryptoparty.org
> This would mean about 250 mailing lists (ISO 3166 ALPHA-3),
> and around 136 wikis (ISO 639-2).
> global mailing list
> global at cryptoparty.is
More information about the global