Clojurians Log v2

@seancorfield have you seen https://github.com/rauchg/slackin? http://Functionalprogramming.slack.com has it set up at https://fpchat-invite.herokuapp.com/; it might be reasonable to set something like that up for here, then have http://clojure.org point to that instead. That should help keep the burden on http://clojure.org maintainers low.

@elliot.stern That's what http://clojurians.net was I believe, but we do not have access to that domain right now.

Slack changed the inviter process and our maintainer didn't have time to change the code and just put a redirect to an invite link up as a temporary measure and now we're stuck with it 😐

Do new people still have the ability to come in here?

I was able to ask some coworkers for an invite, about 2 weeks ago.

The problem is that http://clojurians.net is linked all over the place and we cannot update that site right now -- we're still trying to get hold of the person who has the keys to it.

(I wish people would stop bringing it up here -- the admin team all know about the problem and we are trying to fix it but right now there's not much we can do until we can reach the person who set it up)

We've also updated the README on the community-development repo page with that link: https://github.com/clojurians/community-development (per the channel topic here).

at some point waiting is no longer a real option. and i see a possible solution posted here and then someone making sure that people can get in at the moment. all valid concerns to me

It's not a solution unless the new app is accessible to all the admins to maintain and we then have to get all the references updated all over the internet to use the new domain/link.

It has been a very frustrating issue for all the Admins for quite a while.

http://Clojurians.net expires in May, btw

Yeah, just noticed that when I ran whois to try to get an alternative contact email for the maintainer...

We're looking at buying a new domain and making all credentials for it and the account it runs on available to all the Admins so we no longer have the "bus" problem.

Hmm. Reminds me that I should probably put the Clojure cheatsheet data file / PDF/HTML-generating code in clj-commons on Github, and the actual generated HTML pages for browsing...

If it would help for someone (e.g. perhaps me) to write an FAQ on the http://clojurians.net issue that you can link to, let me know. The issue will keep being asked until/unless resolved, no matter what you do.

https://github.com/clojurians/community-development explains it.

Cool. If it helps to have the fuller explanation written up of how we got into this situation, so you can point people at that in near future, I can do that.

I know you are often willing to explain it repeatedly, but if you didn't have to ....

Tomorrow, once DNS has propagated, we'll be posting a new inviter domain everywhere and I'll update the README with it (and http://clojure.org etc).