Re: [ANN] Discontinuing 4clojure.com

[C. Tas]

I currently own 4clojure.org which is still linked to on many 
Clojure-specific sites. If anyone is interested in buying it, I'd be happy 
to chat.

Peter Strömberg schrieb am Samstag, 17. Juli 2021 um 21:22:16 UTC+2:

> Thanks, thanks, thanks, for creating and caring about 4clojure for this 
> long, Alan! I can't tell how instrumental it has been on my Clojure 
> journey. Not only for learning the language, also for keeping it fun there 
> in the beginning when I doubted I could learn enough of it to get 
> productive. I'm not sure I would have been a Clojurian today if it wasn't 
> for 4clojure.
>
> Best regards,
> /Peter
>
> Den sön 11 juli 2021 kl 23:38 skrev Alan Malloy :
>
>> 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  *-or- 
 *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 
> ). 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  
>> 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 

CfP deadline extension June 8 - ACM Workshop on Functional Art, Music, Modelling and Design

[Michael Sperber]

===
  10th ACM SIGPLAN International Workshop on
 Functional Art, Music, Modelling and Design
(FARM)
   Call for Papers, Demos, and Performance
   Ljubljana, Slovenia, 16th September 2022
   Deadline: June 8
   https://functional-art.org/2022/
===

Key Dates
-

Submission deadline   June 8
Author notification   July 1
Workshop   September 16

Call for Papers
---

The ACM SIGPLAN International Workshop on Functional Art, Music,
Modelling and Design (FARM) encourages submissions from across art,
craft, and design, including textiles, visual art, music, 3D
sculpture, animation, GUIs, video games, 3D printing and architectural
models, choreography, poetry, and even VLSI layouts, GPU
configurations, or mechanical engineering designs. Theoretical
foundations, language design, implementation issues, and applications
in industry or the arts are all within the scope of the workshop.

In addition to the main workshop, FARM hosts a traditional evening of
performances. Thus, this call encompasses both papers/demos for the
workshop (and its published proceedings) as well as performance
proposals for the evening's event. Authors are invited to make a
single submission for each. Authors may submit both a paper/demo and
performance proposal, but the submissions will be considered
independently.

Note on Finances


Paid registration to the FARM workshop is usually required for paper
and demo submitters, but will be waived for performers.

If you would have financial difficulty attending, you can apply for
conference “PAC” funds. Please get in touch for more information.

Papers
--

Paper submissions are invited in three categories:

- Original research
- Overview / state of the art
- Technology tutorial (especially tools and environments for distributed 
artistic workflow)

Papers must be submitted via HotCRP (https://farm22.hotcrp.com/), and
meet the following requirements:

- 5 to 12 pages
- PDF format
- Adhere to the ACM SIGPLAN template

Accepted papers will be published in the ACM Digital Library as part
of the FARM 2022 proceedings.

Authors are encouraged to submit auxiliary material for publication
along with their paper (source code, data, videos, images,
etc.). Authors retain all rights to the auxiliary material.

Demos
-

Demo submissions should describe a demonstration and its context,
connecting it with the themes of FARM. A demo could be in the form of
a short (10 to 20 minute) tutorial, a presentation of work in
progress, an exhibition of some work, or even a performance.

Demos must be submitted via HotCRP (https://farm22.hotcrp.com/), and
meet the following requirements:

- 500 to 2000 words
- Have a title starting with “Demo: ”
- PDF format
- Adhere to the ACM SIGPLAN template 
(https://www.sigplan.org/Resources/ProceedingsFormat/)

Accepted demos will be published in the ACM Digital Library as part of
the FARM 2022 proceedings.

Performances


FARM seeks proposals for performances which employ functional
programming techniques, in whole or in part. We invite a diverse range
of functionally-themed submissions including music, video, dance, and
performance art. Both live performances and fixed-media submissions
are welcome. We encourage risk-taking proposals that push forward the
state of the art as well as refined presentations of highly developed
practice. In either case, please support your submission with a clear
description of your performance, including how your performance
employs functional programming and a discussion of influences and
prior art as appropriate.

Performance proposals should be emailed to
performa...@functional-art.org, and must include:

- A description of the performance (please be as specific as possible)
- An explanation of the use of functional programming in the work
- A list of technical requirements
- A link to an audio or video example (YouTube, Vimeo, Bandcamp, etc.)

Accepted performances will be presented at the performance evening.

Workshop Organization
-

Workshop Chair: John Leo (Halfaya Research)
Program Chair: Youyou Cong (Tokyo Institute of Technology)
Performance Chair: Luka Frelih (Ljudmila Art & Science Laboratory)
Publicity Chair: Michael Sperber (Active Group GmbH)

Contact
---

For any questions, issues or comments, email
farm-2...@functional-art.org.

-- 
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.goog