julian
November 13, 2023, 1:26pm
1
Here a suggestion which I think is a good one:
opened 10:15PM - 16 Oct 23 UTC
enhancement
## Motivation
Currently the most official URL is supercollider.github.io whic… h is owned by GitHub - but there are also other URLs
* scsynth.org
* sccode.org
* https://depts.washington.edu/dxscdoc/
* supercollider.sourceforge.net
* ... ?
This is per-se not a problem as it allows for a de-centralization which I greatly appreciate, yet it would maybe also help newcomers to have an official entrypoint and also provide a trusted URL for binaries, something which I think supercollider.github.io aims to be (and does a great job at this IMO).
The official URL could and should still link to the websites above, such as the current github.io site does.
This has been come up within #6108
## Description of Proposed Feature
Instead of relying on a URL which is not owned by any maintainer, there should be a URL which has the `supercollider` name in it.
This would allow to
* create a stable home for years to come (see `sourceforge.supercollider.net`)
* host e.g. official docs (see #6108 ) via `docs.new-super-official-collider.org`
* provide "official" links to outside resources such as the discourse forum via `forum.newsuper-official-collider.org` which redirects to `scsynth.org`
* have "official" supercollider mail domains (in case they are necessary)
* and reduce the dependency on GitHub.
## Plan for Implementation
* [ ] Agree if there should be an official URL
* [ ] Agree on a URL/TLD - I think this could be a live vote during a dev meeting b/c otherwise some people/bots would maybe take prior action and reserve the URL we want
* [ ] Someone orders this URL (I would be up for that if it is not too expensive, but I am also happy if other people would be up for that)
* [ ] `github.io` URL gets replaced by the new URL - the `github.io` can redirect to the new URL (the github pages workflow would not change in this regard, so the change does not introduce any external hosting, only an URL)
2 Likes
agree! ‘supercollider.online’ would be great and thank you to @dscheiba for registering!
…my one concern - what happens to this domain if Dennis is abducted by aliens or otherwise disappears? How do we keep it “in the community”?
1 Like
I’d hope you’d search for me :o
On the other hand, the domain is managed via OVH, which allows to set up an IAM management - so although I would own the domain, it would be possible for others to manage it as well. If one of the maintainers has an OVH account, I am happy to give them full access to the domain, allowing them to configure it to their liking.
With this access it is also possible to approve an outgoing transfer which transfers the ownership of a domain (IIUC).
4 Likes
scztt
November 13, 2023, 7:32pm
4
The scsynth.org forum is already hosted on a digitalocean instance. We could do something through them?
1 Like
In order to get things running I created a PR to move the official website to the proposed https://supercollider.online domain (currently the domain is not working b/c it is already setup to replace github.io address)
supercollider:main ← capital-G:new-domain
opened 08:21AM - 29 Nov 23 UTC
Also see
* https://scsynth.org/t/moving-the-supercollider-webpage/
* https:/… /github.com/supercollider/supercollider/issues/6114
Although GitHub is a convenient platform for developers, SuperCollider should not be too tied to GitHub.
In particular, any external communication should always be independent of GitHub or any other coding platform, as history has shown for example via <https://supercollider.sourceforge.net/>. Using a self-owned and platform independent domain creates a more resilient address for the SuperCollider community.
Setting up a domain is an easy task and does not consume too many resources, so I decided to donate an official domain to SuperCollider called <https://supercollider.online> (I also bought the address <https://supercollider.dev> as a "backup").
I am happy to share any admin rights of the URL with the maintainers through OVH IAM management (see scsynth post), in order to be more resilient if, for example, I will be absent from the community indefinitely.
There are already some other websites which are operating under this domain, such as
* https://docs.supercollider.online/ - see https://github.com/capital-G/sc-docs
* https://baryon.supercollider.online/ - see https://github.com/capital-G/baryon
* https://quarks.supercollider.online/ - see https://github.com/capital-G/quarks-web -will soon be deprecated soon in favor of baryon
I already setup the A record for the domain, so that once the branch is deployed the website would be available under <https://supercollider.online>.
If deployed, the "old" domain <https://supercollider.github.io/> will automatically redirected to the new domain <https://supercollider.online>, see https://capital-g.github.io/quarks-web/ which now redirects automatically to https://quarks.supercollider.online/
Feel free to discuss here or on GitHub any blockers, worries or support of this delicate action
3 Likes
