20220508
attendees: @jaseknighter (Jonathan), @eigen (Jordan), @awwaid, @radioedit (Duncan), @ericmoderbacher (Eric), @Alanza (Rylee) @watercolor (Ian?), @tomw, @zbs (Z)
@tomw's mic wasn't working, @zbs arrived for the 2nd part.
- essential feature selection / scope / vision
- prepare for opening the gates to more contributors
- background thinking about aesthetics / publication frequency / nb of pages
would provide mostly editing (proof reading?).
potentially code tutorials about fundamentals.
experienced in editing + writing professionally.
designer by trade.
pretty new to the discord & in this project but is motivated and just wanna be helpful.
no opinion (yet) on what his contribution might be.
good at reading/writing but bad at design.
motivated as not so many similar initiatives (in synth / DIY communities)
does writing/editing for a living.
doesn't touch on the design aspect.
interested in helping out.
did graphic design in college.
proficient w/ Adobe suite, notably InDesign.
motivated by the idea of this zine.
@radioedit: snapshot of the current state of the community
-> in other words: capture the excitement
@radioedit: have it be inspirational, to motivate readers to try new things (scripts they never tried, coding...)
in this fashion feature newly released scripts (@zbs) as well older unknown gems (@radioedit).
@radioedit: more broadly, elevate lesser known stuff from the community (not only scripts, but also music...)
@ericmoderbacher + @radioedit: don't target only the existing community (.i.e lines) but broader appeal: demystify norns & other music-making aspects, empower readers.
@jaseknighter: 1 theme / issue. smoother xp for the reader, based on expectations when seeing the cover. the theme can/must be abstract (echoes the poetry aspect).
-> don't explain everything, leave part of the interpretation to the reader.
@eigen: repeating features between issues
- @jaseknighter: clear tension between poetry & practicality (technical aspects)
- @eigen: balance between subjective (relatable experiences, emotions) & objective (technical stuff)
-> would echo the 2 main sections (PLAY/MAKE), PLAY being more poetical/emotional and MAKE for practical/technical
BUT not a total & clear separation️
-> idea of a "shared interview" between a script author and musician who uses it extensively is the perfect way to link both aspects
it should not look too professional. leave some amateurism as it has 💖.
should not expect to make more than 2 / year related to seasons
would be cool to have it a perpetual project.
even if that kinda sucks, need a relatively small editorial team to converge to a coherent release.
rotation in the editorial team to alleviate the authoritarian aspect.
onboarding new editors should be one main goal.
should provide a template of resources to make a new issue (open source everything).
but for first issue, must also provide some concrete examples: members of the editorial team must also provide content and not just guidelines.
have a queue between issues VS accept everything as we're first & foremost digital?
wants a playground repo for throw-away ideas & WIP articles. to "use the momentum".
-> would act like a mood-board.
reminds him of Make:.
"entry level" can relate to scripting BUT also mic level, using github...
-> could give ideas for articles in the PLAY section
for lots of synth nerds, norns could be intimidating.
this zine could provide small bite at a time, enough to empower readers.
so far assumption for it to be for the community (present or future)
-> part of the audience should be peeps outside of the community
demystifying aspect
publishing software to use?
ok w/ re-learning inDesign if that's what the majority uses, or even step down of the publishing side of things.
for design/prototyping, we could use whatever we want!
-> also have a "tag soup" alongside mood-board, vocab (including poetry) we wanna use in the issue.
- @eigen (Jordan): draft a call for contributors message
- everyone: proofread this message
- Jordan: post it on lines
- everyone: onboard new contributors without suppressing all their ideas but without letting the scope / structure go off track
- Jordan: organize next meeting w/ new contributors