This example builds the following physical hierarchy over the course of several operations: /data/ /projects/ /project-1/ task-43/ task-48/
6/26/2022Attendees Justin B Jackson M Josh C elf Pavlik Eric P Agenda
6/26/2022Recap -- how resource metadata evolveveve Justin: Aaron and i started it in NH ... last two substantive issues: ... .. exposure of metaddata to clients ... .. linking back from metadata resources
6/26/2022Justin Introduction Extremely tight on time, this will be tightly moderated, important to get as much feedback as possible Only those on the agenda will be queued to speak, and only during the allotted time. Editors may ask for clarification after each block. Clarifying questions should be queued for efficiency, and may be taken offline due to time constraints. Primary role of the editors today is to listen to you, and learn which features or issues are important. Consequently, having a good record is paramount. Scribes will do our best to keep up, but we'll also ask that the implementers help us to review the minutes afterwards and make sure they are an accurate reflection of what was reported. Also we're learning the best way to structure sessions like this, so we'd really love to know what you thought of this format, or how we could optimize it moving forward. JD Topics Justin
6/26/2022or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up