Opened 5 months ago

Last modified 5 weeks ago

#2416 new task

transfer of domains from planet.federal.com

Reported by: jive Owned by: sac@…
Priority: normal Milestone:
Component: Systems Admin Keywords:
Cc:

Description

We would like to accept the following domains from planet.federal.com:

  • fedgeoday.com - osgeo.us
  • geogig.org - locationtech
  • geonode.org
  • geoscript.org - locationtech
  • geoserver.org
  • geowebcache.com
  • geowebcache.net
  • geowebcache.org
  • qgis.us - qgis.org

Change History (17)

comment:1 Changed 5 months ago by rjhale1971

The QGIS.us group (which I'm a member of) is interested in the QGIS.us domain - or at least getting it transferred. It's been a bit of a handicap working around a locked domain and github as the hosting solution. If there's anything I can do to help I'm at your disposal as are the other people on the "board" - Kurt Menke and Michelle Tobias.

comment:2 Changed 5 months ago by geomenke

+1 for me, especially for qgis.us.

comment:3 Changed 5 months ago by MicheleTobias

+1 for me too, especially qgis.us since this would make keeping our website up to date easier.

comment:4 Changed 5 months ago by wildintellect

I think we can make this happen fairly easily.

Transfer instructions: https://www.pairdomains.com/kb/posts/293

Looks like we can initiate the transfers, but someone on Planet Federal will get notified to approve. Do you have a point of contact on the Planet Federal side? So we know who will be approving the transfers. Can maybe get a dump of current settings? Or can someone map out the IP for each? Are there MX or other record types we'll need to put in place?

Question, for geogig and geoscript.org(which does not seem to be in use). Is there a reason OSGeo is being asked to take these instead of LocationTech? (Eclipse Foundation)?

comment:5 Changed 5 months ago by jive

Point of contact is Torben, who can check in on this ticket.

This is just the list we think may of interest to the open source community as a whole. I made suggestions of organizations (osgeo.us and locationtech) who may be interested.

We should reach out to appropriate parties, for example the geonode psc may be interested in geonode.org

comment:6 in reply to:  1 Changed 4 months ago by jive

Replying to rjhale1971:

The QGIS.us group (which I'm a member of) is interested in the QGIS.us domain - or at least getting it transferred. It's been a bit of a handicap working around a locked domain and github as the hosting solution. If there's anything I can do to help I'm at your disposal as are the other people on the "board" - Kurt Menke and Michelle Tobias.

Is the qgis.us group a legal entity, or do we go talk to qgis.org association?

comment:7 in reply to:  5 Changed 4 months ago by jive

Replying to jive:

We should reach out to appropriate parties, for example the geonode psc may be interested in geonode.org

Appropriate parties have been contacted.

comment:8 Changed 4 months ago by pcav

I believe QGIS.org is the best home for it. Please let us know how to proceed.

comment:9 Changed 4 months ago by jive

Opened a bug ticket (https://bugs.eclipse.org/bugs/show_bug.cgi?id=560743) to communicate with Eclipse Foundation.

comment:10 Changed 2 months ago by gsteinmon

Hello folks,

I am the president of the OSGeo US chapter and I would like to know how to transfer the fedgeoday.com to our dns service.

Thank you for your assistance.

-Guido

comment:11 in reply to:  description Changed 8 weeks ago by gsteinmon

Hey folks, is there anything I can do to help make this process move forward, it's been quiet for another two weeks.

-Guido

Replying to jive:

We would like to accept the following domains from planet.federal.com:

  • fedgeoday.com - osgeo.us
  • geogig.org - locationtech
  • geonode.org
  • geoscript.org - locationtech
  • geoserver.org
  • geowebcache.com
  • geowebcache.net
  • geowebcache.org
  • qgis.us - qgis.org

comment:12 Changed 7 weeks ago by wildintellect

Guido,

When you say us, do you mean QGIS Web team (Swiss Org), or OSGeo SAC? Also the biggest hold up is we don't know who the contact at Planet Federal is that needs to be available to approve the transfer request.

-Alex

comment:13 Changed 7 weeks ago by rjhale1971

Any word on where this stands? It just rolled back up on my spreadsheet of 'things to do'

comment:14 Changed 7 weeks ago by wildintellect

Ok to clarify, this is the plan, please comment if this any of these dont' look right.

current domain -> suggested new manager

  • fedgeoday.com -> osgeo.us (osgeo dns)
  • geonode.org -> geonode or osgeo?
  • geoserver.org -> geoserver or osgeo?
  • geowebcache.com -> geowebcache/geoserver or osgeo?
  • geowebcache.net -> geowebcache/geoserver or osgeo?
  • geowebcache.org -> geowebcache/geoserver or osgeo?

  • geogig.org -> locationtech
  • geoscript.org -> locationtech

  • qgis.us -> qgis.org

Next steps, we need confirmation of the correct new homes, question marks need to be resolved by contacting PSC of projects. @jive can you provide SAC with the Planet Federal contact so we can make sure the transfers don't get rejected.

comment:15 Changed 7 weeks ago by jive

I have sent an introduction via email.

  • geoserver and geowebcache go to OSGeo (there is no distinct geoserver entity).
  • I would assume geocode also goes to OSGeo (but you could ask their PSC).

comment:16 Changed 5 weeks ago by jive

We have reports of:

GeoServer? website is giving me security certificate issues across all my browsers. Seems that the certificate is for some flavour of github.com rather than geoserver.org.

Further discussion:

Certificate is valid for the domain name github.com and its subdomains. The website domain name being "geoserver.org" this triggers the browsers: "The servers name "geoserver.org" does not match the certficate's name: www.github.com, *github.com, etc.

Checking settings:

GH Pages Repo I'm seeing these warnings:

The custom domain for your GitHub? Pages site is pointed at an outdated IP address. You must update your site's DNS records if you'd like it to be available via your custom domain. For more information, see

Enforce HTTPS — Unavailable for your site because your domain is not properly configured to support HTTPS

So when we have control over the geoserver.org domain perhaps we can address this.

comment:17 Changed 5 weeks ago by wildintellect

I looked into this the other day. I believe you are correct that simply updating the github DNS IPs will fix it. It's related to how github rolled out https for custom domains.

Note: See TracTickets for help on using tickets.