OpenSUTD Term 5 release planning
===

###### tags: `OpenSUTD`

Planning slides [here](https://docs.google.com/presentation/d/1S1pSdvzt0TYugBxL9uXFfpIacOgyXbGymKtAALyvkvs/edit#slide=id.g4a15e9887e_1_11)

## Visual Identity
Common Artifacts:
- Gitter/Discord Channels to open source our conversations
- Branding, "pricing plans" to give something for everyone
<img src="https://i.imgur.com/OWvLjuJ.png" width="400">
<img src="https://i.imgur.com/8v4Y589.png" width="400">
- Student starter pack
- Project References for students with easy downloadability
- Fifth Row pulse check slides and manual for Exco
- Upload notes and organically have it spread. Probs & Stats/ Coding Notes
- someone reported issue of the course names being too long, and unable to clone repo. no one made the pull request yet
- Freshmore notes from Tee meng & GA in form of jupyter notebook: https://github.com/09x09/le_notebooks
- Freshmore HASS notes
- *Notes formatting* converging in a single model for people to utilise as a standard

**Coherence in identity**

## Stakeholders we need to consider

|Stakeholder|Concern|
|--|--|
|ILP/Early Mat|Onboarding Process, getting buy-in. Alpha testing|
|Pillar Reps|Ensure Pillar projects are in. Notes production and sharing|
|Fifth Row Leaders|Fifth Row publicity through static pages, hosting Fifth Row repositories, surviving pulse check, common admin pitfalls|
|Profs|Github Classroom?|
|Staff|Policy Documents for Student spaces, Discovery Week|

**Get buy-in long before we actually need it**

## Open Regulation
### Student Activity Centre "Constitution"

Concept: think of it as a user manual ([Valve's Handbook](https://steamcdn-a.akamaihd.net/apps/valve/Valve_NewEmployeeHandbook.pdf))
**Align student perceptions with the design intent of the space. Ensure sustainability usage**

eg.
If you have a need to store items short-term for your project, Contact ROOT SI with the following information:
- Start Date
- End Date
- Disposal Date
- What item you are storing
- Picture of item and its location in SAC

## Open Regulation
### Living Lab
Policies not yet done up; Projects hosting
Make perception for living lab as a 'lab' and not 'computer hosting'
**Align student perceptions with the design intent of the space. Ensure sustainable usage**

## "R&D"
- Explore upcoming github functionality? Things have changed significantly since MSoft
- Prioritize comms efforts and port over into a channel
- Automation - a phase 2 for the overall workflow
- Github Classroom - use for IAP? let people come to it
- shell script - problems with repos and submodules? - how do we take advantage of the Git structure?
- presets?

**Key is to keep things simple and efficient**

## Release prep
Target audience for Alpha: pre-mat/ILP students
Full Release on Discovery Week, around May after Orientation

### What needs to happen
- 5th row support for OpenSUTD - pulse check, etc. ensure that incentives are aligned, good fifth rows will want to publicise their work
- Organise into pillar type, give a number code
- Consider having shell scripts to mass download

## Landing Page release
Landing page must encompass our visual identity and be coherent

### What needs to happen
- Format content for our stakeholders according to stakeholder needs
- A 'web' format?
- The Academically oriented?
- The fifth-row leader?
- OPENSUTD pricing plan??

## Work Streams
Detailed Objectives and Key Results

### Visual Identity
Objectives:
1. Coherence throughout all OpenSUTD material
2. Principles of OpenSUTD has to be self-evident when interacting with its material

Key Results:

### Open Regulation
Objectives:
1. Our shared spaces are used according to its design intent
2. Students know where to refer if they have questions on how the spaces are used
3. Students can contribute to improving the space with a clear and transparent suggestion process

Key Results:

### R&D
Objectives:
1. Inform the technical and design decisions of OpenSUTD
2. Explore functionalities that contribute to improving the ease of use of OpenSUTD
3. Web app?

Key Results:

### Release
Objectives:
1. Execute the OpenSUTD release successfully
2. Align with Discovery Week
3. Measure the success of our efforts for OpenSUTD based on direct feedback from the alpha test

Key Results:

**Key Questions**
Teams and roles: how do we organise our collaborators?
By job function?
Organic teams?
Pick our initial teams and then let the organic growth take over?
Need to grow our teams: search for that initial seed with initiative, and inculcate them with our processes
Possible need for greater numbers right now in core team to push issues forward and make OpenSUTD work
Seeming lack of people with initiative each year?

# Timeline

5-6 Feb - CNY
22nd Feb - **Townhall**
23-24th Feb - Open House
19-21 Apr - Good Friday/ Easter
2/3 May - Finals
May - Discovery Week
May - Aug - Review usage of OpenSUTD during Summer
Sept - Dec - 3.007, Term 4 Projects