Scheme.org: Protecting Scheme's name for the next 20 years
Lassi Kortela
(22 Nov 2020 21:54 UTC)
|
Re: Scheme.org: Protecting Scheme's name for the next 20 years
Amirouche Boubekki
(24 Nov 2020 16:37 UTC)
|
Re: Scheme.org: Protecting Scheme's name for the next 20 years Lassi Kortela (24 Nov 2020 11:37 UTC)
|
Re: Scheme.org: Protecting Scheme's name for the next 20 years
(no sender)
(01 Dec 2020 18:39 UTC)
|
Who owns Scheme?
Lassi Kortela
(01 Dec 2020 17:33 UTC)
|
Re: Who owns Scheme?
John Cowan
(26 Dec 2020 05:49 UTC)
|
Re: Scheme.org: Protecting Scheme's name for the next 20 years
Arthur A. Gleckler
(01 Dec 2020 18:45 UTC)
|
Re: Scheme.org: Protecting Scheme's name for the next 20 years
Amirouche Boubekki
(24 Dec 2020 16:59 UTC)
|
Re: Scheme.org: Protecting Scheme's name for the next 20 years
Lassi Kortela
(27 Dec 2020 14:02 UTC)
|
Re: Scheme.org: Protecting Scheme's name for the next 20 years Lassi Kortela 24 Nov 2020 11:37 UTC
> That is a great idea! Thanks for working on this. Thanks! Welcome aboard. > Will the scheme.org domain work like https://js.org/ ? Indeed, JS.org looks like it works on a similar principle: projects can get subdomains. It's not clear how many projects they host. Seems like their criteria for granting subdomains are quite lax (i.e. doesn't have to be a big, well-known project). IMHO it would be a good idea to list all our subdomains on the Scheme.org front page. That means there should be some criteria of notability for establishing a subdomain. Otherwise we could eventually wind up with things like subdomains for individual Scheme libraries, of which there are hundreds. (Though perhaps there could be a lib.scheme.org subdomain and individual libraries could have nested subdomains foo.lib.scheme.org if they want to.) It would probably be polite to give each Scheme implementation a direct subdomain of scheme.org if they want one. Other than that, the standards (r5rs, r6rs, r7rs, srfi) are obvious candidates. What about well-known tools like Akku and Snow?