Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Brief

This space contains information with regards to storage of WARG Information/Data.

Meeting Notes (Meeting Minutes)

  • Every formally scheduled meeting will require meeting minutes in Confluence

    • The naming convention in Meetings Overview should be followed

      • No need to retroactively enforce this scheme as going through previous meeting minutes will take forever. Let’s just try to stick with this going forwards!

    • A link to the meeting minutes should be included in the google calendar description

      • see this leads meeting as an example

      • this helps keep data accessible to members!

    • All meeting minutes will go into the centralized Confluence Space

    • Meeting minutes should contain a somewhat high level summary of what will be discussed in that meeting before the meeting so that attendees know what to expect from the meeting!

    • During the meeting, information should be added to the meeting minutes to document the discussion as it occurs

      • This is done so anyone who missed the meeting can get a summary of what was discussed!

  • Over time we want subteams (and leads meeting) to converge on a meeting minutes format though for now the variety is swag.

Data Handling Summary

  • WARG will be using:

    • Our Website for the onboarding and sponsor pipeline

    • Asana to track:

      • Low Level Tasks

    • Confluence to track:

      • Documentation

        • Essentially anything we want to keep for a long time as reference for WARG members

      • High Level Program Direction

      • Engineering Analysis

        • The exception to this is engineering analysis on other WARG Platforms

      • Meeting Minutes

        • If meeting minutes are desired to be private Confluence has features to accommodate this

    • Google Calendar

    • Discord

      • For communications

      • Private information (passwords) using private channels

      • Relocate “bookshelf” channels to Confluence

    • Onedrive

      • Media

        • Photos and videos for social media

        • Autonomy Model Training Photographs

    • Google Drive

      • Financial ledgers

      • Slide Deck Presentations

    • Other Services

      • Altium 365

      • Github

      • Etc.

  • Do not store any WARG information on personal accounts.

    • If you have concerns with this or any edge cases please ping directors for assistance

  • This migration will be tough as these services are confusing and often difficult to use

    • Please reach out for directors or other leads for guidance as these systems are new for all of us.

    • If systems are not functioning we can absolutely pivot as a team following a lead discussion

  • If possible do not delete general outdated information

    • It’s always good to reference in the future

    • Feel free to delete information that poses privacy concerns, this rule is specific to general information

    • Most modern platforms, including Confluence, offer a simple archiving feature, this is optimal and should be used in most cases

    • If the storage of the data is expensive and not worth it than of course it may make sense to delete though be careful

  • No labels