summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20100922/000766.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-discuss/20100922/000766.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-discuss/20100922/000766.html')
-rw-r--r--zarb-ml/mageia-discuss/20100922/000766.html306
1 files changed, 306 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20100922/000766.html b/zarb-ml/mageia-discuss/20100922/000766.html
new file mode 100644
index 000000000..eb906be27
--- /dev/null
+++ b/zarb-ml/mageia-discuss/20100922/000766.html
@@ -0,0 +1,306 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-discuss] Thank you - Merci - Danke - Gracias - Grazie - Obrigado - &#1089;&#1087;&#1072;&#1089;&#1080;&#1073;&#1086;
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%0A%20%3D%3Futf-8%3Fq%3FThank_you_-_Merci_-_Danke_-_Gracias_-_%3F%3D%0A%20%3D%3Futf-8%3Fb%3FR3JhemllIC0gT2JyaWdhZG8gLSDRgdC/0LDRgdC40LHQvg%3D%3D%3F%3D&In-Reply-To=%3Ci7dqe8%24uv3%241%40dough.gmane.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000759.html">
+ <LINK REL="Next" HREF="000774.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-discuss] Thank you - Merci - Danke - Gracias - Grazie - Obrigado - &#1089;&#1087;&#1072;&#1089;&#1080;&#1073;&#1086;</H1>
+ <B>Marc Par&#233;</B>
+ <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%0A%20%3D%3Futf-8%3Fq%3FThank_you_-_Merci_-_Danke_-_Gracias_-_%3F%3D%0A%20%3D%3Futf-8%3Fb%3FR3JhemllIC0gT2JyaWdhZG8gLSDRgdC/0LDRgdC40LHQvg%3D%3D%3F%3D&In-Reply-To=%3Ci7dqe8%24uv3%241%40dough.gmane.org%3E"
+ TITLE="[Mageia-discuss] Thank you - Merci - Danke - Gracias - Grazie - Obrigado - &#1089;&#1087;&#1072;&#1089;&#1080;&#1073;&#1086;">marc at marcpare.com
+ </A><BR>
+ <I>Wed Sep 22 22:54:31 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000759.html">[Mageia-discuss] Thank you - Merci - Danke - Gracias - Grazie - Obrigado - &#1089;&#1087;&#1072;&#1089;&#1080;&#1073;&#1086;
+</A></li>
+ <LI>Next message: <A HREF="000774.html">[Mageia-discuss] Thank you - Merci - Danke - Gracias - Grazie - Obrigado - &#1089;&#1087;&#1072;&#1089;&#1080;&#1073;&#1086;
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#766">[ date ]</a>
+ <a href="thread.html#766">[ thread ]</a>
+ <a href="subject.html#766">[ subject ]</a>
+ <a href="author.html#766">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le 2010-09-22 16:04, Michael Scherer a &#233;crit :
+&gt;<i> Le mercredi 22 septembre 2010 &#224; 12:11 -0400, Marc Par&#233; a &#233;crit :
+</I>&gt;&gt;<i> Le 2010-09-22 10:41, Michael Scherer a &#233;crit :
+</I>&gt;&gt;&gt;<i> Le mardi 21 septembre 2010 &#224; 16:53 -0400, Marc Par&#233; a &#233;crit :
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> Would it make sense to also have a section for &quot;mageia&quot; domain owners to
+</I>&gt;&gt;&gt;&gt;<i> track domain owners who are willing to cooperate? You will eventually
+</I>&gt;&gt;&gt;&gt;<i> have to do this anyway. I would also consider this also a type of offer
+</I>&gt;&gt;&gt;&gt;<i> of cooperation and help.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Personally, I think we should not collect all domain names to give them
+</I>&gt;&gt;&gt;<i> to the association :
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> The offer was to pass on the domain if the Mageia project wanted to have
+</I>&gt;&gt;<i> it. It adds flexibility
+</I>&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> 1) each domain name will need admin time. Either to manage ( ie, set up
+</I>&gt;&gt;&gt;<i> vhost, setup the zone, add a entry to the zone etc ), or to renew. While
+</I>&gt;&gt;&gt;<i> renewing 1 domain name every year is easy, renewing 10 or 20 on 10 to 20
+</I>&gt;&gt;&gt;<i> different resellers, for different prices and so on will be quite
+</I>&gt;&gt;&gt;<i> annoying.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> When passing off a domain, the reseller is transferred. You then
+</I>&gt;&gt;<i> consolidate all under on reseller. I do this all the time.
+</I>&gt;<i>
+</I>&gt;<i> Well, depending on the domain, I am not sure that all of them can be
+</I>&gt;<i> transferred everywhere.
+</I>&gt;<i>
+</I>&gt;<i> For example, .ie is restricted as Colin Guthrie explained to me for the
+</I>&gt;<i> 10 years of Mandriva. And it seems that you cannot buy .ie at gandi.net,
+</I>&gt;<i> which is the reseller we have used.
+</I>&gt;<i>
+</I>&gt;<i> So I do not know if they can manage every type of TLD.
+</I>
+If you register with a larger reseller, they will have offices in most
+countries to get around this. They then offer you an account that
+consolidates all domains. The contact information is then coordinated
+from this account.
+
+&gt;<i>
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> 2) this will also generate work for people in charge of comptability,
+</I>&gt;&gt;&gt;<i> and we know that people doing the work of a CFO are a scarce ressources
+</I>&gt;&gt;&gt;<i> ( CFO may not be the proper word, but I didn't found better ).
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> You set a pointer to the main site and there is no need to use the other
+</I>&gt;&gt;<i> domain names if you do not wish.
+</I>&gt;<i>
+</I>&gt;<i> I mean administrative work, like taking care of the bill, reporting them
+</I>&gt;<i> on the financial report, etc.
+</I>&gt;<i>
+</I>&gt;<i> I never managed a association as a treasurer, so I do not know how much
+</I>&gt;<i> paperwork is really required, or if this is really annoying, but all the
+</I>&gt;<i> one that I know are always already overworked, so I am sure that less
+</I>&gt;<i> work is better.
+</I>&gt;<i>
+</I>
+It is really not that much of a burden. You can coordinate the billing
+periods with your reseller. They will be more than happy to help you
+with this.
+
+&gt;<i>
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> If we use for http :
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> 4) too much domain will be a pain from a ssl point of view. If we start
+</I>&gt;&gt;&gt;<i> to need ssl for a site, and there is 10 Vhost for it, we will just have
+</I>&gt;&gt;&gt;<i> 10 time the work to renew certificates.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Not applicable if you redirect the domains. You would then only have to
+</I>&gt;&gt;<i> establish certificates for those domains that you intend to use.
+</I>&gt;<i>
+</I>&gt;<i> I beg to differ.
+</I>&gt;<i>
+</I>&gt;<i> For a http redirect, this will require first to connect using https then
+</I>&gt;<i> send the redirect at http level, so a valid certificate is needed before
+</I>&gt;<i> the redirect.
+</I>&gt;<i>
+</I>&gt;<i> If you speak of a &quot;dns redirect&quot;, you can either use a A record, in
+</I>&gt;<i> which case the issue would still be valid since browser will ask for the
+</I>&gt;<i> certificate of the first domain name, not the redirected one. Or you can
+</I>&gt;<i> use a CNAME record, in which case, the issue is the same.
+</I>&gt;<i>
+</I>&gt;<i> Maybe I forgot something or overlooked it however, but I am quite
+</I>&gt;<i> confident of this. And since this will be different TLDs, you cannot use
+</I>&gt;<i> a wildcard certificate.
+</I>&gt;<i>
+</I>&gt;<i> Of course, a solution would be to basically use the same certificate
+</I>&gt;<i> everywhere and let warnings appear, this is not a big issue.
+</I>
+Your reseller and/or hosting service would most likely help you out with
+this as well.
+
+&gt;<i>
+</I>&gt;<i>
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> 5) too much domain will also requires more work for simple http, since
+</I>&gt;&gt;&gt;<i> we will have lots of them.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Not applicable if you set a pointer. This will also depend on the amount
+</I>&gt;&gt;<i> of website developers help who have signed up.
+</I>&gt;<i>
+</I>&gt;<i> Well, it mostly depend on the number of vhost needed. For exemple, if we
+</I>&gt;<i> want to have blog.example.fr redirect to blog.example.org, we need to
+</I>&gt;<i> create a vhost with the redirection. Te issue can be alleviated by using
+</I>&gt;<i> some mod_rewrite tricks.
+</I>&gt;<i>
+</I>&gt;<i> But yes, for the case you gave of simple http redirect, this is not
+</I>&gt;<i> tricky to handle.
+</I>&gt;<i>
+</I>&gt;<i> But it depend on what will be needed. Worst case would be to have
+</I>&gt;<i> conditional vhost for each domain ( like only have a blog on some
+</I>&gt;<i> subdomain and not others ).
+</I>
+The hosting service I use give you unlimited redirects and domain
+parking. -- 123ehost.com. It works well and quite painless. These are
+set up in minutes.
+
+&gt;<i>
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> 6) too much different url will just mean more confusion. I may also fear
+</I>&gt;&gt;&gt;<i> this could be seen by major search engine as unethic SEO, and thus be
+</I>&gt;&gt;&gt;<i> punished ( since link farm is a commonly used technic to try to hijack
+</I>&gt;&gt;&gt;<i> some keywords ). But Google, Yahoo and Bing systems are closed source,
+</I>&gt;&gt;&gt;<i> so I do not know.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> This is not unethic as all business on the internet do this as common
+</I>&gt;&gt;<i> practice. Try to type in URL's for any major corporation, or Yahoo!,
+</I>&gt;&gt;<i> Google, Bing etc.
+</I>&gt;<i>
+</I>&gt;<i> Well, yahoo.fr and yahoo.com do not give the same server, and there is
+</I>&gt;<i> some high level redirection. So does Dell ( 2 differents sites ), Apple
+</I>&gt;<i> ( not the same server, not the same page, redirection to .com with a
+</I>&gt;<i> url ), Microsoft ( does like Apple ), Renault ( not the same ip, some
+</I>&gt;<i> wierd redirection ), Peugeot.
+</I>&gt;<i>
+</I>&gt;<i> Ie, among the test i did, only Google and Bind do have the same page
+</I>&gt;<i> across various urls.
+</I>&gt;<i>
+</I>&gt;<i> So my own understanding is that they appear to be different entities to
+</I>&gt;<i> most search engines.
+</I>
+Due to the load on their services, as well as different national
+conditions put on these companies (RIM and problems with their
+BlackBerry servers in UAE and India etc is a good example), to them, it
+makes sense to have separate servers. However, Mageia would not suffer
+at the outset from such a load and if it did, you could then make
+allowances for this.
+
+&gt;<i>
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> If we use for mail :
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> 7) too much domain will simply mean more spam. If we offer multiple
+</I>&gt;&gt;&gt;<i> email ( like &quot;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">example at mageia.org</A>, and .de, and .fr and .cn, and so on ),
+</I>&gt;&gt;&gt;<i> email will simply appear in more list, and therefore be more spammed.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Domains do not have to be activated for mail. If a domain is not
+</I>&gt;&gt;<i> activated for mail service then the mail bounces back to the sender.
+</I>&gt;&gt;<i> This is done all of the time.
+</I>&gt;<i>
+</I>&gt;<i> Well, that why I have said &quot;if we use it for mail&quot;.
+</I>&gt;<i>
+</I>&gt;<i> And I see at least 1 person using the domain name he bought and offered
+</I>&gt;<i> us to use ( see Tom&#225;&#353; Kindl on
+</I>&gt;<i> <A HREF="http://mageia.org/wiki/doku.php?id=ressources">http://mageia.org/wiki/doku.php?id=ressources</A> ).
+</I>&gt;<i>
+</I>
+This is easily set up. Mageia devs and core groups (once formally
+established) are more than welcome to have a &quot;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">____ at mageia.ca</A> mail
+account if they want one. I will set that up for them along with POP,
+SMTP and Webmail.
+
+&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> 9) and of course, too much domain name, like for websites will mean more
+</I>&gt;&gt;&gt;<i> confusion.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> It means less confusion. mageia.org will lead to main site; mageia.ca
+</I>&gt;&gt;<i> does lead to main site; magiea.nl would lead to main site; mageia.net
+</I>&gt;&gt;<i> would lead to main site; mageia.info would lead to main site ... How
+</I>&gt;&gt;<i> would this be confusing?
+</I>&gt;<i>
+</I>&gt;<i> I was not clear, I was speaking of mail address ( if we use them ).
+</I>&gt;<i> And so this would bring confusion because people often rely on the mail
+</I>&gt;<i> to see if someone is a official developer or not. Hence, if we use the
+</I>&gt;<i> domain for mail, people will use them to post on ml, I assume people
+</I>&gt;<i> will use them.
+</I>&gt;<i>
+</I>&gt;<i> Of course, as you said, we can also decide to not use it.
+</I>&gt;<i>
+</I>&gt;&gt;<i> By doing business the way that you advocate, you actually lower the
+</I>&gt;&gt;<i> fidelity that one would assume of a serious group.
+</I>&gt;<i>
+</I>&gt;<i> We are not creating a business, but a free software project, IIRC. So
+</I>&gt;<i> some concepts may not be applicable directly. And I think that part of
+</I>&gt;<i> the fidelity would be earned with local user group with their own
+</I>&gt;<i> identity and presence, and likely their own choices, independances and
+</I>&gt;<i> domain names.
+</I>
+If you are looking for foundation grants or government grants, they will
+want to see a business model. They will not lend money to Mageia on
+loose terms. Would you? The core group will have no choice but to adopt
+a business plan if they really want the project to reach their
+advertised goals. Ask any arts group that has applied for grants.
+
+&gt;<i>
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> So
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> 10) by registering every possible variation, we are acting selfishly
+</I>&gt;&gt;&gt;<i> toward others netizens.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> You have already covered these points up above with #9. #10 is not a new
+</I>&gt;&gt;<i> point.
+</I>&gt;<i>
+</I>&gt;<i> No, 10 is for the paragraph about &quot;lack of good domain name on the
+</I>&gt;<i> internet&quot; before, based on the problem about finding a name, and about
+</I>&gt;<i> being nice with other people who may use the name in unrelated way.
+</I>&gt;<i>
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> The only answer I got was about security. But seriously, security of
+</I>&gt;&gt;&gt;<i> what ? Protecting from people doing phishing ? Bank already fail at
+</I>&gt;&gt;&gt;<i> this, and you think we can ?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Who mentioned security? This is all about flexibility.
+</I>&gt;<i>
+</I>&gt;<i> First time I mentioned the issue 2 days ago. But I think this was on
+</I>&gt;<i> irc, since I cannot find anything in the mailling list archives :/
+</I>
+No worry there, there are already speculators who have gobbled up the
+&quot;Mageia&quot; domain permutations that they think will stick, hoping that the
+Mageia project will bring great success. This, hoping to cash out later
+on. I even sent a note out to Anne on Sunday night letting her know that
+the sites were being bought out at a feverish pace.
+
+This is why I think that a further name change later on may be in the
+cards if we find that the &quot;Mageia&quot; domain situation is untenable.
+&gt;<i>
+</I>&gt;<i> ( if someone can confirm that I didn't dream... )
+</I>&gt;<i>
+</I>
+
+</PRE>
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000759.html">[Mageia-discuss] Thank you - Merci - Danke - Gracias - Grazie - Obrigado - &#1089;&#1087;&#1072;&#1089;&#1080;&#1073;&#1086;
+</A></li>
+ <LI>Next message: <A HREF="000774.html">[Mageia-discuss] Thank you - Merci - Danke - Gracias - Grazie - Obrigado - &#1089;&#1087;&#1072;&#1089;&#1080;&#1073;&#1086;
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#766">[ date ]</a>
+ <a href="thread.html#766">[ thread ]</a>
+ <a href="subject.html#766">[ subject ]</a>
+ <a href="author.html#766">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
+mailing list</a><br>
+</body></html>