| 1 |
On Tue, Aug 12, 2003 at 09:05:16AM -0400, Kurt Lieber wrote: |
| 2 |
> 1) anything that falls under a *.gentoo.org name needs to maintain the |
| 3 |
> consistent look and feel of the main gentoo.org site. |
| 4 |
> |
| 5 |
> 2) they need to publish their docs using guide-xsl. This is more of a |
| 6 |
> technical requirement since our entire web site is built around AxKit |
| 7 |
> and XML. It also ensures that, if we update the look/feel of the web |
| 8 |
> site in the future, all pages in the *.gentoo.org domain will be updated |
| 9 |
> instantly. |
| 10 |
> |
| 11 |
> 3) they need to reside on a gentoo.org infrastructure server. Again, if it |
| 12 |
> ends in gentoo.org, we need to have control over the security of the |
| 13 |
> server and also have the ability to yank inappropriate content in an |
| 14 |
> emergency. I won't risk having a rogue user get pissed off and posting |
| 15 |
> "gentoo is a bunch of communist pinkos" on their country page. |
| 16 |
|
| 17 |
I agree fully to this. |
| 18 |
|
| 19 |
> That's it. I'm still open to creating those pages on a *country* specific |
| 20 |
> basis, but not a language specific one. (otherwise, how do we handle |
| 21 |
> countries like England, Canada and the US which all speak English) |
| 22 |
|
| 23 |
They use the same documentation, don't they? If the page with the English |
| 24 |
communities mentions the location of each community, then this issue is |
| 25 |
solved. I don't see a reason of having seperate ${COUNTRY}.gentoo.org |
| 26 |
domains just because their communities are located elsewhere... |
| 27 |
|
| 28 |
Wkr, |
| 29 |
Sven Vermeulen |
| 30 |
|
| 31 |
-- |
| 32 |
Save some animals, eat a vegetarian. |
Archives