Fork me on GitHub
#community-development
<
2019-06-28
>
plexus08:06:16

Yup, we're working on that and coming back ๐Ÿ™‚ and we're still logging. Hang in there! https://clojureverse.org/t/clojurians-log-working-on-a-relaunch-cloud-sponsor-exoscale/4158

๐Ÿ‘ 1
plexus08:06:26

A few volunteers are rebuilding the infrastructure using Terraform/Ansible, progress here: https://github.com/clojureverse/nebula we're getting pretty close, but people do this when they have time which tends to be a few hours on weekends, so... it'll be ready when it's ready.

yogidevbear08:06:18

That's awesome news. Thanks for the update @plexus ๐Ÿ‘

plexus08:06:25

Special thanks to @dorab and @rahul080327!

mario-star 1
andy.fingerhut22:06:30

I was checking whether Clojurians Slack had a channel related to the Atom editor, and found one called #atom that I'm not sure is relevant. When I go to that channel in Slack (web browser interface), it says that it is archived. I am not familiar with that term for Slack. Is it roughly "no longer a channel anyone should use"?

andy.fingerhut22:06:25

Looks like I guessed pretty close. According to Slack docs: "The channel isnโ€™t open for new activity, but the history is retained" https://get.slack.help/hc/en-us/articles/201563847-Archive-a-channel

andy.fingerhut22:06:45

Of course I realize the history here is about 10K messages total across all channels, so unsurprising there is nothing to view in the history

seancorfield22:06:35

Use #chlorine for Chlorine questions and #protorepl for ProtoREPL questions.

seancorfield22:06:53

To avoid confusion, I have deleted the #atom channel (it was archived ages ago -- it was created by mistake).

seancorfield22:06:01

Our policy is generally to archive "bad" channels first, after posting a message indicating why it is being archived and where folks should go instead, then after a few days, we usually remember to go back and delete the channel. But sometimes we forget.