On Sat, Jul 3, 2010 at 9:06 AM, Chris Tyler <chris@xxxxxxxxxxx> wrote:
> On Fri, 2010-07-02 at 23:23 -0400, Máirín Duffy wrote:
>> On Fri, 2010-07-02 at 23:08 -0400, Chris Tyler wrote:
>> > Consider: we don't want someone from -- oh, let's say Canada -- showing
>> > up, realizing that there's neither a ca.fedoraproject.org nor a
>> > ca.fedoracommunity.org site, and concluding that there's no one involved
>> > with Fedora from her country (you can repeat the exercise with "us" or
>> > any other country code in place of "ca"). At the same time, I really,
>> > really don't want to create a new domain just to "solve" this problem.
>>
>> Is a domain beyond fedoracommunity.org and fedoraproject.org being
>> proposed by anyone? I'm not proposing that.
>>
>> ~m
>
> Sorry, I meant "domain" as in "subdomain":
> foo.fedora{community,project}.org
>
> I see three separate things here; let me sum them up from my POV--
>
> - A discussion about whether foo.fedoracommunity.org should be permitted
> to point to fedoraproject.org/wiki/foo (the original question). The
> argument for this include making it easy to remember where local content
> can be found, the argument against this is that it loses the original
> meaning attached to fedoracommunity.org, that is, local community-run
> websites outside of the scope of the main Fedora project. My opinion is
> that this distinction is significant and should not be lost -- we should
> not point *.fedoracommunity.org to resources within the main
> fedoraproject.org space.
>
> - Paul pointed out during the discussion yesterday that it would also be
> possible to create foo.fedoraproject.org and have it point to a
> particular resource (e.g., wiki landing page). I don't know if this was
> an off-the-cuff observation that this is possible, or a serious proposal
> that we do it. The other possibility, I suppose, would be
> fedoraproject.org/foo, if the intention is simply to create short,
> memorable URLs. Personally, I don't consider these to be a great step
> forward from fedoraproject.org/wiki/foo.
>
I missed this part sorry. Here is my view as an infrastructure person.
Making more top level names is a bad idea for several reasons:
A) It makes infrastructures life a little harder as we are dealing
with DNS changes AND/OR website redirect changes.
B) It makes search engines lives harder because they may never KNOW
about lemuria.fedoraproject.org because there is no reference in the
right spots for it.
C) I have heard that for a branding perspective it weakens the brand
in the mind of the reader. The brands we are trying to promote is
fedoracommunity and fedoraproject. Putting countries, languages,
lefthanded/righthanded before that makes those to seem more important
than the ideas project and community.
Thus from an infrastructure view, I think we would much prefer to deal
with fedoraproject.org/communities/<*> than adding more
<*>.fedoraproject.org names.
That said I think the other issue we want to deal with here is how can
we strengthen fedoracommunity.org so that we can make it usable for
groups that do not have their own infrastructure etc.
--
Stephen J Smoogen.
“The core skill of innovators is error recovery, not failure avoidance.”
Randy Nelson, President of Pixar University.
"We have a strategic plan. It's called doing things.""
— Herb Kelleher, founder Southwest Airlines
_______________________________________________
advisory-board mailing list
advisory-board@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/advisory-board
