[CfP] 2nd Call - 2020 Scheme and Functional Programming Workshop

[Jason Hemann]

Hello,

Thank you for your attention, and my apologies for any duplication you
receive. Please find below the Call for Papers for the *2020 Scheme and
Functional Programming Workshop*. The deadline has been extended to *May 31*.
Please also note that the workshop is now to be held *virtual*ly; hopefully
the silver lining is more and wider participation. We look forward to your
submissions.


*Call for Papers*The 2020 Scheme and Functional Programming Workshop is
calling for submissions.

We invite high-quality papers about novel research results, lessons learned
from practical experience in industrial or educational setting, and even
new insights on old ideas. We welcome and encourage submissions that apply
to any language that can be considered Scheme: from strict subsets of RnRS
to other “Scheme” implementations, to Racket, to Lisp dialects including
Clojure, Emacs Lisp, Common Lisp, to functional languages with
continuations and/or macros (or extended to have them) such as Dylan,
ECMAScript, Hop, Lua, Scala, Rust, etc. The elegance of the paper and the
relevance of its topic to the interests of Schemers will matter more than
the surface syntax of the examples used. Topics of interest include (but
are not limited to):

Interaction: program-development environments, debugging, testing,
refactoring
Implementation: interpreters, compilers, tools, garbage collectors,
benchmarks
Extension: macros, hygiene, domain-specific languages, reflection, and how
such extension affects interaction.
Expression: control, modularity, ad hoc and parametric polymorphism, types,
aspects, ownership models, concurrency, distribution, parallelism,
non-determinism, probabilism, and other programming paradigms
Integration: build tools, deployment, interoperation with other languages
and systems
Formal semantics: Theory, analyses and transformations, partial evaluation
Human Factors: Past, present and future history, evolution and sociology of
the language Scheme, its standard and its dialects
Education: approaches, experiences, curricula
Applications: industrial uses of Scheme
Scheme pearls: elegant, instructive uses of Scheme


*Important dates*Submission deadline is 31 May 2020.
Authors will be notified by 12 June 2020.
Camera-ready versions are due 30 June 2020.
All deadlines are (23:59 UTC-12), “Anywhere on Earth”.
Submission Information
Paper submissions must use the format acmart and its sub-format acmlarge.
They must be in PDF, printable in black and white on US Letter size.
Microsoft Word and LaTeX templates for this format are available at:

http://www.sigplan.org/Resources/Author/

This format is in line with ACM conferences (such as ICFP with which we are
colocated). It is recommended to use the review option when submitting a
paper; this option enables line numbers for easy reference in reviews.

We want to encourage all kinds of submissions, including full papers,
experience reports and lightning talks. Papers and experience reports are
limited to 14 pages, but we encourage submitting smaller papers. Lightning
talks are limited to 192 words. Each accepted paper and report will be
presented by its authors in a 25 minute slot including Q&A. Each accepted
lightning talk will be presented by its authors in a 5 minute slot,
followed by 5 minutes of Q&A.

The size limits above exclude references and any optional appendices. There
are no size limits on appendices, but the papers should stand without the
need to read them, and reviewers are not required to read them.

Authors are encouraged to publish any code associated to their papers under
an open source license, so that reviewers may try the code and verify the
claims.

Proceedings will be printed as a Technical Report at the University of
Michigan and uploaded to arXiv.org

.

Publication of a paper at this workshop is not intended to replace
conference or journal publication, and does not preclude re-publication of
a more complete or finished version of the paper at some later conference
or in a journal.

Sincerely,


Jason Hemann, Northeastern University





*Organizing Committee*Michael D. Adams (Program Co-Chair), University of
Michigan
Baptiste Saleil (Program Co-Chair), IBM Canada
Jason Hemann (Publicity Chair), Northeastern University



*Program Committee*Michael D. Adams (Program Co-Chair), University of
Michigan
Baptiste Saleil (Program Co-Chair), IBM Canada
Maxime Chevalier-Boisvert, Université de Montréal
Ryan Culpepper, Czech Technical University
Kimball Germane, University of Utah
Yukiyoshi Kameyama, University of Tsukuba
Andy Keep, Cisco Systems, Inc
Julien Pagès, Université de Montréal
Alexey Radul



*Steering 

[ANN] Deploy tokens for Clojars

[Toby Crawley]

Howdy folks!

Just letting you know that Clojars[1] now allows you to create and use
deploy tokens[2] in place of passwords when deploying. If you don't
deploy OSS projects to Clojars, feel free to stop reading now.

The deploy tokens are to be used in place of a password when
deploying, and can optionally be scoped to only allow deployment of a
single artifact or any artifact within a group[2].

We now consider deploying with your Clojars password deprecated, and
will *disable deploying with a password on or after 2020-06-27*. So
please switch to using deploy tokens as soon as you can, and please
file an issue[3] or get in touch via the #clojars channel on the
Clojurians slack if you encounter any problems.

Also please file an issue[3] if you know of any public documentation
that should be updated to mention deploy tokens.

We are currently working with GitHub to enable secret scanning[4] for
these tokens. Once that is in place, any token that GitHub discovers
in source code will automatically be disabled and Clojars will email
you about it.

This work is being sponsored by Clojurists Together[5]. Please
consider joining to sponsor this and other OSS work in the Clojure
community if you aren't already a member. If you are already a member:
thank you!

- Toby

[1]: https://clojars.org
[2]: https://github.com/clojars/clojars-web/wiki/Deploy-Tokens
[3]: https://github.com/clojars/clojars-web/issues/new?template=issue.md
[4]: https://developer.github.com/partnerships/secret-scanning/
[5]: 
https://www.clojuriststogether.org/news/clojurists-together-is-funding-clojars/

-- 
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/CAA3HuyZiAFk8Bb4gRjrKuO-fs4psK9TPvR0FZX00w-01ZGhhSQ%40mail.gmail.com.

Re: [ANN] Deploy tokens for Clojars

[Sean Corfield]

Here's a project that is documented to use the Clojars password and is
fairly widely used: https://github.com/slipset/deps-deploy -- all projects
created by clj-new rely on this and all of them will have the same
documentation to use the Clojars password.

Forcing everyone to change their deployment processes across the board
within just over a month seems a bit... aggressive...

On Sun, May 17, 2020 at 1:56 PM Toby Crawley  wrote:

> Howdy folks!
>
> Just letting you know that Clojars[1] now allows you to create and use
> deploy tokens[2] in place of passwords when deploying. If you don't
> deploy OSS projects to Clojars, feel free to stop reading now.
>
> The deploy tokens are to be used in place of a password when
> deploying, and can optionally be scoped to only allow deployment of a
> single artifact or any artifact within a group[2].
>
> We now consider deploying with your Clojars password deprecated, and
> will *disable deploying with a password on or after 2020-06-27*. So
> please switch to using deploy tokens as soon as you can, and please
> file an issue[3] or get in touch via the #clojars channel on the
> Clojurians slack if you encounter any problems.
>
> Also please file an issue[3] if you know of any public documentation
> that should be updated to mention deploy tokens.
>
> We are currently working with GitHub to enable secret scanning[4] for
> these tokens. Once that is in place, any token that GitHub discovers
> in source code will automatically be disabled and Clojars will email
> you about it.
>
> This work is being sponsored by Clojurists Together[5]. Please
> consider joining to sponsor this and other OSS work in the Clojure
> community if you aren't already a member. If you are already a member:
> thank you!
>
> - Toby
>
> [1]: https://clojars.org
> [2]: https://github.com/clojars/clojars-web/wiki/Deploy-Tokens
> [3]: https://github.com/clojars/clojars-web/issues/new?template=issue.md
> [4]: https://developer.github.com/partnerships/secret-scanning/
> [5]:
> https://www.clojuriststogether.org/news/clojurists-together-is-funding-clojars/
>
> --
> 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/CAA3HuyZiAFk8Bb4gRjrKuO-fs4psK9TPvR0FZX00w-01ZGhhSQ%40mail.gmail.com
> .
>


-- 
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- https://corfield.org/
World Singles Networks, LLC. -- https://worldsinglesnetworks.com/

"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)

-- 
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/CAD4thx-VRp3NbVjLrZ5-iihxeO9r66WD%3DqpAhNwj_HQ7Vuq-cg%40mail.gmail.com.

Re: [ANN] Deploy tokens for Clojars

[Erik Assum]

I think I agree with Sean that the time frame is a bit short. One thing is 
making deps-deploy
(and also pomegranate) work with tokens (which I’m confident I can handle).
Another thing is that I would imagine both leiningen and boot would need new
releases and people would need to adopt those releases?

On a positive note, I think the deploy-token per artefact is super for 
clj-commons, since we
then have a way to publish artefacts under the original groupid/artefactid.

Erik.

> On 18 May 2020, at 06:25, Sean Corfield  wrote:
> 
> Here's a project that is documented to use the Clojars password and is fairly 
> widely used: https://github.com/slipset/deps-deploy 
>  -- all projects created by clj-new 
> rely on this and all of them will have the same documentation to use the 
> Clojars password.
> 
> Forcing everyone to change their deployment processes across the board within 
> just over a month seems a bit... aggressive...
> 
> On Sun, May 17, 2020 at 1:56 PM Toby Crawley  > wrote:
> Howdy folks!
> 
> Just letting you know that Clojars[1] now allows you to create and use
> deploy tokens[2] in place of passwords when deploying. If you don't
> deploy OSS projects to Clojars, feel free to stop reading now.
> 
> The deploy tokens are to be used in place of a password when
> deploying, and can optionally be scoped to only allow deployment of a
> single artifact or any artifact within a group[2].
> 
> We now consider deploying with your Clojars password deprecated, and
> will *disable deploying with a password on or after 2020-06-27*. So
> please switch to using deploy tokens as soon as you can, and please
> file an issue[3] or get in touch via the #clojars channel on the
> Clojurians slack if you encounter any problems.
> 
> Also please file an issue[3] if you know of any public documentation
> that should be updated to mention deploy tokens.
> 
> We are currently working with GitHub to enable secret scanning[4] for
> these tokens. Once that is in place, any token that GitHub discovers
> in source code will automatically be disabled and Clojars will email
> you about it.
> 
> This work is being sponsored by Clojurists Together[5]. Please
> consider joining to sponsor this and other OSS work in the Clojure
> community if you aren't already a member. If you are already a member:
> thank you!
> 
> - Toby
> 
> [1]: https://clojars.org 
> [2]: https://github.com/clojars/clojars-web/wiki/Deploy-Tokens 
> 
> [3]: https://github.com/clojars/clojars-web/issues/new?template=issue.md 
> 
> [4]: https://developer.github.com/partnerships/secret-scanning/ 
> 
> [5]: 
> https://www.clojuriststogether.org/news/clojurists-together-is-funding-clojars/
>  
> 
> 
> -- 
> 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/CAA3HuyZiAFk8Bb4gRjrKuO-fs4psK9TPvR0FZX00w-01ZGhhSQ%40mail.gmail.com
>  
> .
> 
> 
> -- 
> Sean A Corfield -- (904) 302-SEAN
> An Architect's View -- https://corfield.org/ 
> World Singles Networks, LLC. -- https://worldsinglesnetworks.com/ 
> 
> 
> "Perfection is the enemy of the good."
> -- Gustave Flaubert, French realist novelist (1821-1880)
> 
> -- 
> 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 
> 
> --- 
> 

Re: [ANN] Deploy tokens for Clojars

[Erik Assum]

D’oh, please disregard. After reading the docs, I see that no changes would be 
needed, apart from updating the docs.

Mea culpa, sorry for the noise.

Erik.

> On 18 May 2020, at 07:38, Erik Assum  wrote:
> 
> I think I agree with Sean that the time frame is a bit short. One thing is 
> making deps-deploy
> (and also pomegranate) work with tokens (which I’m confident I can handle).
> Another thing is that I would imagine both leiningen and boot would need new
> releases and people would need to adopt those releases?
> 
> On a positive note, I think the deploy-token per artefact is super for 
> clj-commons, since we
> then have a way to publish artefacts under the original groupid/artefactid.
> 
> Erik.
> 
>> On 18 May 2020, at 06:25, Sean Corfield > > wrote:
>> 
>> Here's a project that is documented to use the Clojars password and is 
>> fairly widely used: https://github.com/slipset/deps-deploy 
>>  -- all projects created by clj-new 
>> rely on this and all of them will have the same documentation to use the 
>> Clojars password.
>> 
>> Forcing everyone to change their deployment processes across the board 
>> within just over a month seems a bit... aggressive...
>> 
>> On Sun, May 17, 2020 at 1:56 PM Toby Crawley > > wrote:
>> Howdy folks!
>> 
>> Just letting you know that Clojars[1] now allows you to create and use
>> deploy tokens[2] in place of passwords when deploying. If you don't
>> deploy OSS projects to Clojars, feel free to stop reading now.
>> 
>> The deploy tokens are to be used in place of a password when
>> deploying, and can optionally be scoped to only allow deployment of a
>> single artifact or any artifact within a group[2].
>> 
>> We now consider deploying with your Clojars password deprecated, and
>> will *disable deploying with a password on or after 2020-06-27*. So
>> please switch to using deploy tokens as soon as you can, and please
>> file an issue[3] or get in touch via the #clojars channel on the
>> Clojurians slack if you encounter any problems.
>> 
>> Also please file an issue[3] if you know of any public documentation
>> that should be updated to mention deploy tokens.
>> 
>> We are currently working with GitHub to enable secret scanning[4] for
>> these tokens. Once that is in place, any token that GitHub discovers
>> in source code will automatically be disabled and Clojars will email
>> you about it.
>> 
>> This work is being sponsored by Clojurists Together[5]. Please
>> consider joining to sponsor this and other OSS work in the Clojure
>> community if you aren't already a member. If you are already a member:
>> thank you!
>> 
>> - Toby
>> 
>> [1]: https://clojars.org 
>> [2]: https://github.com/clojars/clojars-web/wiki/Deploy-Tokens 
>> 
>> [3]: https://github.com/clojars/clojars-web/issues/new?template=issue.md 
>> 
>> [4]: https://developer.github.com/partnerships/secret-scanning/ 
>> 
>> [5]: 
>> https://www.clojuriststogether.org/news/clojurists-together-is-funding-clojars/
>>  
>> 
>> 
>> -- 
>> 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/CAA3HuyZiAFk8Bb4gRjrKuO-fs4psK9TPvR0FZX00w-01ZGhhSQ%40mail.gmail.com
>>  
>> .
>> 
>> 
>> -- 
>> Sean A Corfield -- (904) 302-SEAN
>> An Architect's View -- https://corfield.org/ 
>> World Singles Networks, LLC. -- https://worldsinglesnetworks.com/ 
>> 
>> 
>> "Perfection is the enemy of the good."
>> -- Gustave Flaubert, French realist novelist (1821-1880)
>> 
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email