I don't know which groups are competing, but I can vouch for the 4ever constellation. Not only are they highly trustworthy, but also known for getting shit done, and as stayers.
On Wed, 14 Jul 2021 at 08:50, Alan Malloy <malloyal...@gmail.com> wrote: > There have been a number of requests on this thread for me to transfer the > 4clojure.com domain name to a designated successor. I'm open to that in > principle, but there are a couple issues. > > 1. I don't actually own the 4clojure.com domain name. That belongs to > 4clojure's founder, dbyrne, who has been renewing it and pointing it at my > server. I imagine he will be happy to transfer it, but there might be > organizational hiccups I'm not aware of. If a successor is chosen, we can > loop him in then. > 2. I wouldn't want to transfer the domain to someone who turns out to > be unable to use it - maybe setting up a copy of 4clojure is harder than > one might imagine, since it's all 10-year-old technology. If any of the > prospective new owners already have a copy of 4clojure running under a > different domain name, I'd love to see it. Of course, the 4ever-clojure > guys have already done this. > 3. This is more of a "me" problem because my interaction with the > Clojure community for years has just been the tiny IRC room and Stack > Overflow, but so far all the offers to take on the mantle have come from > people and companies I've never heard of. Maybe you're all pillars of the > community now, but I just don't know it. I'd hate to give the name over to > a group planning to do something nefarious with collected email addresses, > for example. I feel like kinda a jerk for asking, since it's not like I was > the greatest maintainer, but I don't suppose there are any old-time > Clojurists who can vouch for any of these groups? Feel free to email me > privately (amalloy@ the domain in question, for now!) if you'd prefer > not to be on record as favoring one of these groups over the others. > > > On Monday, July 12, 2021 at 9:13:09 PM UTC-7 brando...@gmail.com wrote: > >> Thank you Alan for all the work and time put into 4clojure, and thank >> those of you who've started and contributed to 4ever-clojure! >> >> Cheers, >> Brandon >> >> On Sun, Jul 11, 2021 at 2:38 PM Alan Malloy <mallo...@gmail.com> wrote: >> >>> I've also exported the problem data: >>> https://drive.google.com/file/d/1hHrygxAs5Do8FpHC9kphYnmyTwZvISnb/view?usp=sharing >>> . >>> >>> On Sunday, July 11, 2021 at 2:22:33 PM UTC-7 Alan Malloy wrote: >>> >>>> I'm happy to see this project, and I think exporting some data is a >>>> reasonable compromise. Rather than re-learn how to do any fancy mongodb >>>> stuff to make it into "pretty" json, I've just done a raw JSON export of >>>> the solutions collection, which is world-readable at >>>> https://drive.google.com/file/d/1UQHznThT_eVTBjmLGz3yME8L3teGygUs/view?usp=sharing. >>>> I'm contemplating doing a partial export of the users collection too: I >>>> could connect usernames to IDs without including the email addresses or >>>> passwords, which would let you rebuild most of the user information. But >>>> I'm not totally sure this is a good idea: some people may not want their >>>> usernames shared, or associated with their solutions. Does anyone in this >>>> thread have an opinion? >>>> >>>> On Tuesday, July 6, 2021 at 9:58:29 AM UTC-7 oxa...@gmail.com wrote: >>>> >>>>> Thank you Alan for all your contributions :) >>>>> >>>>> Hosting things and maintaing them is really hard. We, the LambdaIsland >>>>> team, are already maintaining clojurians-log and clojureverse and it's >>>>> definitely not easy! >>>>> >>>>> With a wonderful idea from @borkdude and his `sci` library, I built >>>>> "4ever-clojure": a completely static version of 4clojure which runs using >>>>> cljs + sci. It interprets the code in the browser itself. >>>>> >>>>> It's live at: 4clojure.oxal.org (Source code at: >>>>> https://github.com/oxalorg/4ever-clojure I'm planning to move it >>>>> under the clojureverse github org) >>>>> >>>>> I have 2 asks from you if it is feasible: >>>>> 1. An export of all solutions (only solutions, no user data needed) - >>>>> the community is already coming up with some amazing ideas of hooking up >>>>> user solutions to automatically commit to a Github repo >>>>> 2. Possibility of transfering *4clojure.com <http://4clojure.com> *-or- >>>>> *4clojure.org <http://4clojure.org> *over to us so that we can host >>>>> 4ever-clojure there (instead of on a separate domain) >>>>> >>>>> Thanks! >>>>> - Mitesh >>>>> >>>>> On Tuesday, July 6, 2021 at 5:56:10 PM UTC+5:30 Srihari Sriraman wrote: >>>>> >>>>>> Hey Alan, we really like 4clojure. We've suggested using it for >>>>>> training most people at nilenso and we're very thankful to you and all >>>>>> the >>>>>> contributors for that! >>>>>> We (nilenso) would be up for picking up the hosting costs, and also >>>>>> some other operations or development work if needed. >>>>>> >>>>>> It would be even better if we could work together and turn this into >>>>>> a community owned project (ex: clojurists together >>>>>> <http://clojuriststogether.org>). That might also assuage your >>>>>> concerns about data ownership. >>>>>> >>>>>> The questions, and solutions that the community has put together on >>>>>> 4clojure over the last decade are very valuable as a learning tool. >>>>>> Perhaps >>>>>> we can find a way to keep them around without attributing them to a user? >>>>>> One idea might be to deactivate all existing accounts, and remove the >>>>>> user >>>>>> data (email, passwords, other PII) etc while keeping the questions and >>>>>> solutions from those users. >>>>>> >>>>>> We would be sad to see 4clojure go away, hope we can find a way for >>>>>> it to live on. >>>>>> >>>>>> Cheers, >>>>>> Srihari >>>>>> >>>>>> On Tuesday, July 6, 2021 at 1:12:44 PM UTC+5:30 Robert P. Levy wrote: >>>>>> >>>>>>> Hi Alan, >>>>>>> >>>>>>> Just as a thought. If it's minimal work on your end (eg. if the >>>>>>> folks from Roam research who chimed in above pick it up) why not clear >>>>>>> the >>>>>>> password hashes and let the new maintainer handle the communication that >>>>>>> passwords need to be reset? >>>>>>> >>>>>>> Rob >>>>>>> >>>>>>> On Sun, Jul 4, 2021 at 1:26 PM Alan Malloy <mallo...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> TL;DR: Turning off 4clojure.com by the end of July 2021 >>>>>>>> >>>>>>>> Hello, 4clojure problem solvers. You've probably noticed SSL errors >>>>>>>> on 4clojure.com over the last week. The old decrepit system >>>>>>>> 4clojure runs on has finally gotten out of date enough that I can't >>>>>>>> even >>>>>>>> figure out how to get it recent enough that SSL certs will auto-renew >>>>>>>> anymore. >>>>>>>> >>>>>>>> In principle I could start from scratch on a new server and move >>>>>>>> 4clojure over, but I won't. 4clojure has been piggybacking along on a >>>>>>>> server that I use for personal reasons, and over the years I have less >>>>>>>> and >>>>>>>> less reason to keep paying for that server - it's now pretty much just >>>>>>>> 4clojure costing me an embarrassing amount of money every month >>>>>>>> because I >>>>>>>> haven't wanted to disappoint the community by shutting it down. This >>>>>>>> SSL >>>>>>>> thing is just what made me finally pull the trigger. >>>>>>>> >>>>>>>> I don't have a specific EOL date in mind, but sometime near the end >>>>>>>> of the month, since that's the billing cycle. Until that time, 4clojure >>>>>>>> still works, as long as you don't mind clicking through the security >>>>>>>> warnings - it really is still me hosting the site, and since the >>>>>>>> connection >>>>>>>> is still HTTPS (albeit with an invalid cert) I think that means your >>>>>>>> data >>>>>>>> is still safe. If you have solutions to problems you're proud of, >>>>>>>> you've >>>>>>>> still got some time to print them out and put them up on your >>>>>>>> refrigerator. >>>>>>>> >>>>>>>> I'm not seeking new maintainers. I'd feel uncomfortable handing >>>>>>>> over a database with so many email addresses and password hashes in it >>>>>>>> to >>>>>>>> anyone. The service has had a good run - just over a decade since the >>>>>>>> first >>>>>>>> release >>>>>>>> <https://github.com/4clojure/4clojure/commit/ff457d0b3b5f5e5a74316a1747809c25b84b3b5e>. >>>>>>>> I hope you enjoyed it during that time. >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "Clojure" group. >>>>>>>> To post to this group, send email to clo...@googlegroups.com >>>>>>>> Note that posts from new members are moderated - please be patient >>>>>>>> with your first post. >>>>>>>> To unsubscribe from this group, send email to >>>>>>>> clojure+u...@googlegroups.com >>>>>>>> For more options, visit this group at >>>>>>>> http://groups.google.com/group/clojure?hl=en >>>>>>>> --- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "Clojure" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to clojure+u...@googlegroups.com. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/clojure/385cdef8-fa40-47ba-b5b1-0b3a7cc34935n%40googlegroups.com >>>>>>>> <https://groups.google.com/d/msgid/clojure/385cdef8-fa40-47ba-b5b1-0b3a7cc34935n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> >>>>>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to clo...@googlegroups.com >>> Note that posts from new members are moderated - please be patient with >>> your first post. >>> To unsubscribe from this group, send email to >>> clojure+u...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/clojure?hl=en >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to clojure+u...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/clojure/4d635947-7097-4310-a6dd-c53d9d45b72fn%40googlegroups.com >>> <https://groups.google.com/d/msgid/clojure/4d635947-7097-4310-a6dd-c53d9d45b72fn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/clojure/b55a789b-7063-47bb-9b14-275d4a0e38c7n%40googlegroups.com > <https://groups.google.com/d/msgid/clojure/b55a789b-7063-47bb-9b14-275d4a0e38c7n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/CAMX9Yz_0J8GN9%2BOLcf%2B%3DBbLK9HC86sUizOdjrXtVMtQQDC_Pfw%40mail.gmail.com.
