Closed coke closed 3 years ago
@timo, @rba - any concerns on the site hosting if we make this change?
A correction, please: it has to be under rakudo org ownership, not Raku.
Disagree - rakudo ownership currently implies that committers to the site have a Contributer License Agreement, and I'd rather not require that for website maintenance.
This is solvable via splitting the rakudo org into teams. The one with commit bit into rakudo repo would have to hava CLA signed to join. This could be discussed and decided on problem-solving.
But I strongly against moving rakudo.org into Raku because this would make rakudo more equal than any other implementation. Or we take the responsibility of hosting all websites of all possible implementations which would imply commercial ones in theory.
The goal of this ticket was merely to follow all the other repositories out of "perl6" to "Raku".
I don't disagree in theory that it might show rakudo as "more equal". In practicality? There's no other compilers at the moment to worry about (https://raku.org/compilers).
I'd think we'd also be happy to share the Raku org for other OS language implementations if they wanted. I do disagree that it would imply any sort of responsibility to a commercial product.
TL;DR - Sure, OK.
I think this repo here should really be moved over to the https://github.com/rakudo organization. It took me quite some time to finally find the source of https://rakudo.org/ to apply some fixes / additions :|
It probably should. But I do not currently have enough rights to do so.
This is now done.
This is now done.
THANK YOU and who ever else was involved!!!!
Likely would have to coordinate with a site infrastructure update to pull from the new remote (even though a redirect will be available for a while)