To be honest, I'm not super excited about this; it seems more confusing than helpful. But I could be convinced. :)

What's the advantage of a name like wiki.fedoraloves.net over fedoraproject.org/wiki? Is the idea that every name in this domain would be a redirect? Who will manage the redirects (and make sure they keep working)?

@mattdm I'm gonna convince you :p

We have http://redhatloves.net and it would be awesome if we had similar redirect for Fedora. And it looks cool on slides.

What's the advantage of a name like wiki.fedoraloves.net over fedoraproject.org/wiki?

Those Subdomains do not have any real meaning to be honest, I just thought that it could be useful one day, e.g. I will want to point someone to our mailing list to subscribe, I can just point them to list.fedoraloves.net instead of looking for this giant link: lists.fedoraproject.org/admin/lists/dotnet-sig.lists.fedoraproject.org

Is the idea that every name in this domain would be a redirect? Who will manage the redirects (and make sure they keep working)?

Yes, it serves only as redirect to actual Fedora pages or resources related to .NET Core. As it is right now I manage (I don't really need to transfer it to under Fedora budget unless legally necessary. This is both my job as RH's .NET Engineer and my passion as Fedora's dotnet SIG) this with these technical details:

• DNS at cloudflare points to my own server where I run multiple services useful for open source projects, such as web or app hosting, etherpad, webmail, some bots and communication stuff, openshift, ...
• This server has a simple vhost that redirects everything to the developer portal using mod rewrite...

(This will be followed by tshirts and stickers with similar theme to our Red Hat ones...)

Dump question: is Fedora supporting .NET core the same way as RedHat does?

If you bought the domain you have to sign the license agreement anyway:
https://fedoraproject.org/wiki/Trademark_license_agreement

is Fedora supporting .NET core the same way as RedHat does?

I'm not sure I understand the question. Taken literally, no we do not provide any support :P

If it's in Fedora the same way it is in Red Hat, then no, it's work in progress. Red Hat does not have as strict packaging rules as Fedora, therefor it's much easier to get the job done, while in Fedora we keep getting stuck on having to use prebuilt pieces. The ability to build from source is almost there..

Red Hat has the dotnet packages in Software Collections and it is part of the Developer program stuff. We can use Microsoft-built rpm on Fedora right now and we are working on a new dirty package for upcoming netcore 2.0 release at least for Copr, however we hope that proper package is not that far off either.

I'd rather see the domain point to a specific page in our existing infrastructure that onboard people. This way we don't have to maintain lots of parallel linking infrastructure. It also has the added bonus of quickly introducing the person to the Fedora Project and not leaving them segregated.

I'd rather see the domain point to a specific page in our existing infrastructure that onboard people.

I'm not trying to onboard contributors, that would come at later time, after they become a user in the first place. I'm trying to throw easily accessible guide-type-of-stuff at potential users, .net developers - only very few actually use Linux, and even those that deploy on Linux usually develop on Windows.

I'd rather see the domain point to a specific page in our existing infrastructure that onboard people.

I'm not trying to onboard contributors, that would come at later time, after they become a user in the first place. I'm trying to throw easily accessible guide-type-of-stuff at potential users, .net developers - only very few actually use Linux, and even those that deploy on Linux usually develop on Windows.

Then, if the TM usage is approved, let's delete everything but the redirect to developers.fedoraproject.org. It still accomplishes the goal of pushing them toward the larger Fedora project as users.

Yup, and on another thought, we could have join.fedoraloves.net point to the SIG's join page, as far as onboarding goes... thoughts @bex?

Yup, and on another thought, we could have join.fedoraloves.net point to the SIG's join page, as far as onboarding goes... thoughts @bex?

I am generally not in favor of this as it feels fragile. I'd rather see a blurb on developers.fp.o that encourages people to join the SIG if they wish to contribute to Fedora.

This URL should try to "get out of the way" as soon as possible, I think.

I am generally not in favor of this as it feels fragile. I'd rather see a blurb on developers.fp.o that encourages people to join the SIG if they wish to contribute to Fedora.

Oh yes, there is a page about both mono sig, and dotnet sig. =)

Part of my problem here is that I might be old-school enough on the Internet that it takes a lot of thinking for me to associate the .net TLD (for Internet infrastructure and ISPs!) with .NET. When I see "fedoraloves.net" I don't read "Fedora Loves .NET!". I read "Fedora Loves! (and dot .com was taken)".

Is this just me? Am I too old for this? :)

I am on the same boat as @mattdm . My first thought, before I read the explanation about .NET, was that it is going to be an extension of diversity activities focusing on LGBT community. I am afraid I will not be the only one who parse the domain name in this way. Personally, I will be more happy with a less confusing domain name even I do not have an exact proposal what the domain name should be like.

I have to point out that this domain name and the whole effort follows already-done-before, and set in stone redhatloves.net and also fedora loves python, etc...

Part of my problem here is that I might be old-school enough on the Internet that it takes a lot of thinking for me to associate the .net TLD (for Internet infrastructure and ISPs!) with .NET. When I see "fedoraloves.net" I don't read "Fedora Loves .NET!". I read "Fedora Loves! (and dot .com was taken)".
Is this just me? Am I too old for this? :)

I might be old school too, but it took me quite a while to understand that. Having a domain with Fedora inside should be an exception by itself, getting one just to redirect it to the more well known developer.fp.o website, is rather useless.

Part of my problem here is that I might be old-school enough on the Internet that it takes a lot of thinking for me to associate the .net TLD (for Internet infrastructure and ISPs!) with .NET. When I see "fedoraloves.net" I don't read "Fedora Loves .NET!". I read "Fedora Loves! (and dot .com was taken)".
Is this just me? Am I too old for this? :)

I don't think this is an age issue. I don't think anyone on this thread except @rhea is in the actual target audience. I am OK with the domain name as a redirector because I believe it will resonate with the target audience, based on @rhea's knowledge.

The idea is to use this to redirect to various .NET content? If that's what's proposed, I'm good with that. So, wiki.fedoraloves.net would point to https://fedoraproject.org/wiki/DotNet, not https://fedoraproject.org/wiki as I had initially thought you meant?

@mattdm yes, but Brian suggested to drop the subdomains, since the dev portal as target of the main domain, already contains a link to it (on the sig page) and encourages contribution.

Note that the contents of the developer portal are still work in progress and we are working on a lot more content to expand these basics.

@mattdm yes, but Brian suggested to drop the subdomains, since the dev portal as target of the main domain, already contains a link to it (on the sig page) and encourages contribution.

I am also still of this opinion :)

Okay, discussed this in the meeting. We're okay with this with a single redirect and no subdomains as Brian suggests. Please arrange to sign the trademark agreement (contact legal@fedoraproject.org and you can reference this approval) and if you want Fedora to own the domain see https://fedoraproject.org/wiki/Local_community_domains#Self-purchased_domain for transfer information.

Sorry being so late to the game here.. However, being a dotnet developer for a long time, I got it immediately when I saw the redhat version. I am also old and am STILL bothered that you can register a .net as a non-ISP. However, I still get the joke :)

re-closing after @langdon's comment.