DIP-14: Posters

[VMLVaske]

No description provided.

[ligi]

saying this with the editor's hat on (formal foo):

• Correct markdown (e.g. headers with ##, header surrounded by ---)
• syntax check
• filename is DIP-X.md (with X being the correct DIP number)
• header contains (in this order)
  • DIP
  • Title
  • Status
  • Theme(s)
  • Tag(s)
  • Author(s)
  • Resources Required (optional)
  • Discussion-to (with link to devcon forum)
  • Created (in the format year-month-day e.g 2020-4-20)
• contains these sections:
  • Abstract
  • Rationale
  • Implementation
  • Operational Requirements & Ownership
• PR title prefixed with DIP-X

saying this personally:
really like the idea and want to see this implemented! Not also is it great for the reasons you mentioned - but it also can be a great platforms for projects where no member wants to be on stage.
I think DIP wise just the Implementation section must be reworked to really answer how it will be made happen. Currently it is more rationale what is in implementation IMHO. We need to answer:

• how will curation happen (I think the biggest issue to solve) we most likely will use pretalx for the talks/workshops. Maybe we can add "posters" as a track? cc @BettinaBF
• How/When will the posters be printed? If devcon will do it - what does it cost?
• what happens after the conference with the posters?

[VMLVaske]

Changed spelling

[ligi]

Thanks. The last checkbox I am missing is the created header. Then editor-wise it is OK to merge.

[VMLVaske]

Sorry for the delay! Added the creation-header-column :D

[ligi]

Thanks & no worries.
Just bringing this to our standard format and then I would merge