Talk:Thematic-Making It Public: Difference between revisions

From XPUB & Lens-Based wiki
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
''Page dedicated to brainstorming, planning and preparation of the thematic''
''Page dedicated to brainstorming, planning and preparation of the thematic''
=Publication=
What has been done so far?
What can be done?
Choose a work and produce a translation of it.
Next meeting we should be presented with a few translations. 
==Jan 20==
* no translations
* start the epub from the report produced by steve.
* git rep
* is it something you want to do?
* https://github.com/pietzwart/making-it-public
* Making the epub from the translations and documentation
== division of tasks==
* Natalya: content transformations from videos onto still images ( pixel scan) + code snipets
* Pleun: design 
* Colm: gathering and preface
* Samira: write, editor
* Nadine: coordinator
* Max: translation onto code
* Stone: content translation
* Julia: reflective text (TBA)
* Sara:
==tools==
* Git
* Epub
==Pleun - Index==
http://pzwart1.wdka.hro.nl/~pleun/makeitpublic/ 
=Feedback=
==Stone==
* Not interested in topic. Finds little value in the format?
* Interested in design part, interested, similar to the web-design
* Working on a photobooks and non-the-less experimenting making epub
==Max==
* intense, long days (tiring)
* '''5 days''' could be more appropriate, since they allow the creating work, and for thoughts and work start to alignment
* interested in talks
==Nadine==
* interesting the different perspectives on the same subject
==Colm== 
* topics for the days - titles, texts, talk - realizing how deep each threat of the topic helps.
* confuse: how far they should go? Would like the expected outcome was more clear from the beginning.
==Pleun==
* something happens when you go white far
* wish to have it every month
==natalya==
* look at an object like an epub - from something technical and practical, to a more experimental and exploratory object
==Julia==
* unsure about if 3 days or good, or should go long
* suspicious about the topic - everything around the topic was interesting
* was not clear where the connections were.
* 3 days were about '''ways of doing''', rather than the content.
==Sara==
* intense, but needed, specially after 1 month unemployment
* 1st impression was not of interest, but also because it was a foreign topic
* texts created interested
* pity to have not discussed the texts - since they are ways to process the rest of the readings and talks. Need to approach the text differently.
* Report (Steve) - as way of process
* work in groups and without hierarchies
* necessity for collective thinking -
==Annet==
* necessary to work more with the students for the preparation phase. Talk them more on what to expect.
* guests - what did you feel?
* content - underestimated the context of the content.
* (students were not making the connections, being active withing the text)
----
necessaity to prepare




Line 34: Line 131:


=== Tuesday===  
=== Tuesday===  
* division into 3 teams, each dealing respectively with: Source material, publishing pipeline,   Front-end design
* the same groups as yesterday.
* implement a prototype that puts into practice the necessary tasks
 
Think about the output format the epub.
 
Stipulate a goal for your publication.
 
Address the steps that you'll need to get there.
 
What will be the limitations?
 
 
Homework: Make a written summary  (1 paragraph ) of your publication.
 
 
 
* division into 3 teams, each dealing respectively with: '''Source material''', '''publishing pipeline''',   '''Front-end design'''
* '''implement a prototype''' that puts into practice the necessary tasks


==== Groups and Tasks:====  
==== Groups and Tasks:====  
* Source material
<s>* Source material
** digitization
** digitization
** storage and organization on the wiki
** storage and organization on the wiki
** context, information
** context, information


* Publishing pipeline
* Publishing pipeline
Line 52: Line 163:
** publishable format(s)
** publishable format(s)
** identity of publication(s)
** identity of publication(s)
 
</s>
 
==== Evening:====
Examples 
And independent practice 


=== Wednesday:===  
=== Wednesday:===  

Latest revision as of 10:51, 20 January 2016

Page dedicated to brainstorming, planning and preparation of the thematic

Publication

What has been done so far?

What can be done?

Choose a work and produce a translation of it.

Next meeting we should be presented with a few translations.


Jan 20

  • Making the epub from the translations and documentation


division of tasks

  • Natalya: content transformations from videos onto still images ( pixel scan) + code snipets
  • Pleun: design
  • Colm: gathering and preface
  • Samira: write, editor
  • Nadine: coordinator
  • Max: translation onto code
  • Stone: content translation
  • Julia: reflective text (TBA)
  • Sara:

tools

  • Git
  • Epub


Pleun - Index

http://pzwart1.wdka.hro.nl/~pleun/makeitpublic/


Feedback

Stone

  • Not interested in topic. Finds little value in the format?
  • Interested in design part, interested, similar to the web-design
  • Working on a photobooks and non-the-less experimenting making epub

Max

  • intense, long days (tiring)
  • 5 days could be more appropriate, since they allow the creating work, and for thoughts and work start to alignment
  • interested in talks

Nadine

  • interesting the different perspectives on the same subject

Colm

  • topics for the days - titles, texts, talk - realizing how deep each threat of the topic helps.
  • confuse: how far they should go? Would like the expected outcome was more clear from the beginning.

Pleun

  • something happens when you go white far
  • wish to have it every month

natalya

  • look at an object like an epub - from something technical and practical, to a more experimental and exploratory object

Julia

  • unsure about if 3 days or good, or should go long
  • suspicious about the topic - everything around the topic was interesting
  • was not clear where the connections were.
  • 3 days were about ways of doing, rather than the content.

Sara

  • intense, but needed, specially after 1 month unemployment
  • 1st impression was not of interest, but also because it was a foreign topic
  • texts created interested
  • pity to have not discussed the texts - since they are ways to process the rest of the readings and talks. Need to approach the text differently.
  • Report (Steve) - as way of process
  • work in groups and without hierarchies
  • necessity for collective thinking -

Annet

  • necessary to work more with the students for the preparation phase. Talk them more on what to expect.
  • guests - what did you feel?
  • content - underestimated the context of the content.
  • (students were not making the connections, being active withing the text)




necessaity to prepare



To do

  • send email to all participants with their time.

To Bring in

  • @andre:
    • audio recorder
    • books
    • Film: "The Man Who Wanted to Classify the World"

Planning

Goals for the work sessions

  • conceive and implement an electronic publication for the works developed under the context of the documentation project.
  • discover the works, letting the works talk for themselves, before framing them 
  • organize the works so that an entity (a narrative?) emerges from the publication 

(Possible) Task distribution for Publication

Monday

  • Introduction to the Documentation project at MMDDC
  • Introduction to Hybrid publishing
  • Documentation goals: publicity, funding, process
  • Exploring the documentation materials and their different media( video, photography, text, print) -

(As 1 single group OR 1 group per year for?)

  • Exploring overlaps: funding + process for different purposes
  • Strategies for digitizing off-line content
  • Strategies for common and retrievable storage

Tuesday

  • the same groups as yesterday.

Think about the output format the epub.

Stipulate a goal for your publication.

Address the steps that you'll need to get there.

What will be the limitations?


Homework: Make a written summary (1 paragraph ) of your publication.


  • division into 3 teams, each dealing respectively with: Source material, publishing pipeline,   Front-end design
  • implement a prototype that puts into practice the necessary tasks

Groups and Tasks:

* Source material

    • digitization
    • storage and organization on the wiki
    • context, information
  • Publishing pipeline
    • getting the content from storage (wiki) into its publishable form
    • publishable format(s)
    • translations necessary to represent works under the publishable format
  • Front-end design
    • publishable format(s)
    • identity of publication(s)

Wednesday:

  • Continue to work on Tuesday prototypes
  • results, issues, questions
  • elaborate a proposal a simple for the continuation of the work

Reading groups

===Monday:===  

  • conflict

Tuesday:

  • the web & algorythms as a writing technologies 

Wednesday

Notes

User:Castrobot/Making It Public-Notes