SC Book Second Edition Open Call

Dear All,

It's been ten years of the first edition of the SC Book; thank you to all w=
ho contributed and to all who bought it, read it in a university library, o=
r took it to the top of Everest in the name of art.=20

MIT Press have now given us permission to develop a second edition. We're h=
oping to do this in the next year and are writing to update you all about t=
his.

Many of the original chapters will stay (with small updates), but we are an=
ticipating some structural changes to reflect the large development in plat=
form and GUI capabilities in the last decade. We are writing to individual =
chapter authors alongside this email concerning these matters.=20

Here, we wanted to re-iterate the open call we made some months back. Now i=
s the time to let us know if there is some chapter about SC you think reall=
y should be in the new edition (and whether you are proposing you write it!=
).=20

As well as more standard chapters, there will also be some shorter artist s=
tatements from SC practitioners (like the shorter features in the Processin=
g Book, or the artists' statements in the Cambridge Companion to Electronic=
 Music). We hope to make these as diverse as possible, and happy to hear an=
y suggestions, whether self nominations or those you think we should reach =
out to. Similarly, we are hoping that the second edition will reflect the i=
ncreased and growing diversity of the SC community, and welcome proposals f=
rom the widest range of potential authors.

The deadline for any new materials will be the end of 2021 for draft materi=
al, before a back and forth with the editors in early 2022.=20

In order to keep things manageable for establishing the contributor list fo=
r the second edition, please get in touch with Scott as lead editor by July=
 14th in order to be considered. ([email protected]) If you are proposi=
ng a chapter, a short (say 100 word) summary of the chapter setting out the=
 proposed contents would be helpful. Bear in mind that one important consid=
eration is usefulness to others, so if you want to write about an obscure b=
it of code used only in a personal project, this is less likely to be picke=
d up than discussing a more general library or facilities. Similarly, if yo=
ur chapter overlaps with an existing topic, do consider proposing co-author=
ship rather than duplication.

We apologise in advance that we will be working within a limited word budge=
t, and whilst the second edition will be a bit larger than the first, we wo=
n't be able to feature everything proposed.=20

All going well, we hope to get SC Book 2.0 with MIT Press in the first half=
 of next year, and given MIT Press reviews and publishing delays, this prob=
ably means 2023 at the earliest for the actual book. But if we can move qui=
ckly, we do hope to do this much faster than with the original text (which =
took 5 years to go from proposal to print).=20

btw, the code examples for the second edition will move to a github reposit=
ory, and we'll update people about that in due course.=20

Best wishes,

Scott and Nick=

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/