Meeting Minutes

Attendees

• Fabian Hauser, fhauser
• Raphael Zimmermann, rzimmerm
• Prof. Dr. Farhad Mehta, MeF

Agenda

1. Present current Project status
2. Discuss results of language evaluation
3. Discuss revised concept and requirements
4. Date and time for next meeting

Discussion / Decisions

1. Present current Project status
   • We are mostly on plan
   • Exception: We stopped with research and focussed on describing the requirements in depth.
2. Discuss results of language evaluation
   • Using Rust is fine, MeF notes that it's our decision in the end.
   • The argumentation seems reasonable.
   • MeF thinks it is a good idea to try it out quickly to fail fast.
   • Ocaml, Java or Python might be a fallback in the worst case
3. Date and time for next meeting
   • The next meeting takes place on 20.10.2017 at 16:00 at MeFs office.
4. Discuss revised concept and requirements
   • MeF gives general feedback of the document so far:
     • The format and layout is fine
     • The requirements are fine, although we should clarify that requirements are vague on purpose (wishlist)
     • A simple formal description is missing
       • Add diagrams and a more high level description (e.g. using the C4 Model)
       • What are the responsibilities of each component? How are paths/file names and versions stored?
       • This must be priority no. 1 for our next steps.
     • Discussion of n-replication vs. m-replication is not coherent (storage is relatively cheap!)
       • Discuss this as well as other possible strategies using the morphological box technique
     • Remove examiner from the title sheet
   • Present the refined concept to MeF. The following points come up:
     • Discuss hash-collisions: Is it even possible? How to handle it? (30' research)
     • Is Git really no option as a storage / transport backend / protocol? (30' research)
     • Discuss the reason for time in the system and potential risks of it
       • What about infinite expiration
       • Why not "mark as not so important" so we can clean things up if we come close to the storage capacity

Open issues

open issues must be completed before the next meeting

• Clarify that requirements are vague on purpose (REDPRO-68)
• Remove examiner from the title sheet (REDPRO-67)
• Create diagrams for better understanding the concept. (REDPRO-62, REDPRO-63, REDPRO-64)
• Describe the responsibilities of each component (REDPRO-63)
• Discuss possible strategies using the morphological box tequnique (REDPRO-69)
• Discuss hash-hollisions (REDPRO-70)
• Clarify if git is an possible storage backend (REDPRO-71)
• Discuss the need of physical time in the system and potential risks of it (REDPRO-72)

Upcoming absences

• Raphael Zimmermann, Friday 27. October.

Next meeting

• The next meeting takes place on 20.10.2017 at 16:00 at MeFs office