Op is Op
The following is a (slightly cleaned) dump from our etherpad working notes from our first session. It seems to be a good place to start the wiki for our first edition.
TOPIC Scarcity of Resources - try to make it our own, link it too a more specific perspective on this topic
QUESTIONS/NOTES Can the output reflect this topic? For who is this topic relevant/urgent? which public? Environmental issue - Do we want to do it as cheap as possible? thinking through pollution Empowering for artists/designers etc. - to have access to this resource Imagining a future with no resources, what would the methods and tools are Reference: Steal this Book Abbie Hoffman : Download here a PDF version How to get things for free --- radical survivalist tactics in times of scarcity A case study http://www.refugeephrasebook.de/
STEPS IN PRODUCTION OF BOOK
- 1 Schedule
- 2 Team
- 2.1 Editorial team
- 2.2 DESIGN ONLINE / PRINT / OTHER FORMAT
- 2.3 PRODUCTION & COORDINATION
- 2.4 DISTRIBUTION
- 2.5 COORDINATION
- 2.6 CONTENT
- 3 A Catalog of Workflows
- 4 Opensource References
- 5 TIMELINE
- 6 Pad Paradise
- 7 Presentation of the 31 0CT 2016
- 8 References
The production team met on the 15th of September to organise a rough schedule. Please feel free to comment. Please note : do not make permanent changes so that we can discuss before putting anything in stone.
27th of September concept for design & editorial plan for content
4th of October preliminary design proposal based on concept
25th of October design proposal
15th of November design finished for final Proofing
18th of November going to Printer
2nd of December DEADLINE
6th of December RELEASE PARTY !!!!
Deciding on the editorial content (Content plan?) such as categories and structure, whether there is an editorial, glossary, index, illustrations, photographs, interviews, case studies, and essays. Chosing and enforcing the citation style guide, whether that be Chicago, Harvard, custom... (also known as Consistency). Making descisions on whether we want to commission texts and then providing contributing authors with the "style guide" to explain the style for writing footnotes and/or references. Working out permissions with licenses and finally English editing, Copyediting, proofing. Example style guide INC:  (I believe it is from 2014, might be a bit outdated) An overview of style guides :  (may be less out of date?)
DESIGN ONLINE / PRINT / OTHER FORMAT
Typography organising the visual styles, looking at fonts for both online / offline and open fonts, choosing and enforcing image formats (how should materials be delivered looking at print / online) including resolutions. Platforms / Tools. They will coordinate closely with Production (and visa versa) on design choices in relation to materiality and production processes. Organise layout, and consider whether we need special formats (for instance markdown) for outcome in different formats. Also in case of online deployment are (partly? fully?) responsible for the programming.
Better Gimp : Gimpshop
PRODUCTION & COORDINATION
Working within the budget account for materials, printing, buying domain name (if necessary), and coordinating everything so it is going to be producable within cost and time. Consider things (where appropriate) like hosting, production plan, and timeline, considering the challenges of bringing together multiple sources. Consider questions of scale more than the singular article / item, and questions of production process which will be closely worked out with the design team.
As the production team we suggest to adopt a markdown workflow. Here you can find a Markdown template with some metadata. File:Markdowntemplate.zip
Markdown is a product of internet culture . It uses ad-hoc formatting signs commonly used in e-mail and chat platforms, and further popularized on blogging platforms, to provide a standardized, human-readable, user-friendly and well-structured document format, suitable for long-term storage and as a basic source for conversions to contemporary and future document formats. While its formatting **syntax** is simple, it is also both strict and unambiguous enough to allow multiple writers and editors to work on a single document without unnecessary confusion. Another advantage of Markdown is that it can be written and edited in any software application capable of processing basic text: unlike the proprietary file formats of Microsoft Word or other word processors, Markdown can be opened using a simple text editor.
Why do we recommend Markdown in particular? For certain publishing projects - for example, handbooks or books derived from wikis, it may be worth considering alternatives to Markdown, such as reStructuredText. There are, however, two reasons why we recommend Markdown as a practical tool for electronic and mixed-media publishing:
1. Excellent software support. There are many user-friendly, high quality applications for writing and editing documents in Markdown and for converting Markdown to other formats. While Markdown may be written and edited in any text editor, there are several user-friendly text editing applications that make it easier to edit and immediately view the results, such as Mou, MacDown, Texts, MarkdownPad, UberWriter and MdCharm.
2. The extended version MultiMarkdown provides all the necessary formatting and document syntax needed for text-oriented publishing in the arts and humanities, or the text component (complete with footnotes and bibliographical references) of an exhibition catalog.
However, Markdown/MultiMarkdown is not a magical one-size-fits-all solution. It is particularly well suited for text-oriented documents, but quite limited for creating visually oriented documents, and not really of much use for interactive publishing formats.
Markdown and similar formatting/markup languages are designed for workflows in which there is a clear separation between editorial work (involving writers, translators and editors) and publication design. For publications requiring extensive interaction between writers/editors and visual designers/artists from the very beginning of the authoring process, other tools and workflows are preferable.
Word processing / editing applications for Markdown on Mac
- Mou with features such as live preview, sync scroll, auto save, auto pair, custom themes, CSS, HTML and PDF export, enhanced CJK support, and more. 
- MacDown, released under the MIT License and with a design and setup influenced by Mou. 
- Byword, a user-friendly, distraction-free text writing program with built-in MultiMarkdown support and export to HTML, RTF, PDF -nd Microsoft Word. The program runs on Mac, iPhone and iPad 
- iAWriter, a program-similar to Byword. The program runs on Mac, iPhone and iPad. 
- Scrivener, a word processing application popular among professional writers, available for Mac OS X and Windows. Fully supports MultiMarkdown internally.
Consider secondary stock and alternative means of sourcing Lithuenia - Riso? Print on the edges sustainable printing in both economy and environment groen offerte (printvisie) autobahn made their own paper.
Editorial guidelines Timeline for production value proposition ? community?
This is a sub-role within each group. Team management is organised as a holacracy. Work backwards: We know we have a budget of 1000 and a deadline of 6th of December
Content will be created by any member of any other team. To open up the diveristy of the work, it can be sourced from outside with permission from creators. Everything will be run by the editorial team so that a strong coherent publication can be created.
Giulia Julia Max Clàudia Karina Along with guests writers, authors from outside of the program.
A Catalog of Workflows
Colophon editing texts design printing distribution models coordination production/ budget management list of resources available production timeline
Project Management Software Open Source Team Management system (Likely too complex) : XO Platform Free(ish) Basecamp alternative : Freedcamp Free bittorrent P2P sync system : Syncthing Opensource Dropbox Alternative : OwnCloud Free Slack alternatives Rocket Chat Mattermost Lets Chat
- DL MONDAY 19.09
- PROPOSITIONS ABOUT SCARCITY FOR THE EDITORIAL TEAM
- BOOK LAUNCH 06.12.2016
A collection of our Etherpad notes per team! Everything is nicer in pad paradise :)
https://pad.pzimediadesign.nl/p/specialissue-2016-11-01 OOPS PAD PROBLEMS PERSIST ... SEE: https://pad.bleu255.com/p/specialissue-2016-11-01
RULES IN PROGRESS