зеркало из https://github.com/microsoft/Reactors.git
remove templates that were moved to ReactorPlanning
This commit is contained in:
meaghanlewis
Родитель
c5acf26961
Коммит
a76a668d31
|
|
@ -1,57 +0,0 @@
|
||||||
---
|
|
||||||
name: Digital Event Tracking Issue
|
|
||||||
about: For a single Global Digital Reactor Event
|
|
||||||
title: Date - Title
|
|
||||||
labels: 'global-twitch-event'
|
|
||||||
assignees: ''
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
# Event Information
|
|
||||||
| Category | Details |
|
|
||||||
|-----------|---------|
|
|
||||||
| Reactor Topic | <Topic from one of the 9 Reactor topics> |
|
|
||||||
| Monthly Topic (if applicable) | <Topic taken from [Azure Dev Marketing](https://aka.ms/DevEdCalFY21H1)> |
|
|
||||||
| Weekly Topic (if applicable) | <Topic decided by RCT if relevant> |
|
|
||||||
| Stream Topic | <2-5 words describing the topic> |
|
|
||||||
| Stream Date | <Month ##, ###> |
|
|
||||||
| Stream Time | <12h PT> |
|
|
||||||
| Stream Duration | <minutes> |
|
|
||||||
| Title | <150 characters or less > |
|
|
||||||
| Description | <500 characters or less> |
|
|
||||||
| Speaker | <Name or GitHub alias> |
|
|
||||||
| Moderator | <Name or GitHub alias> |
|
|
||||||
| SharePoint ID | |
|
|
||||||
|
|
||||||
Additional Resources:
|
|
||||||
<Additional resources that can be linked from social media for promotion or added to the description of VOD>
|
|
||||||
|
|
||||||
|
|
||||||
# Event Checklist
|
|
||||||
|
|
||||||
## 10 Weeks Prior
|
|
||||||
- [ ] Reactor Content Team (RCT) or Speaker opens a new issue for an upcoming stream filling in the Event Information table. Both RCT and Speaker are marked as assignees.
|
|
||||||
- [ ] RCT and Speaker discuss details of the event in the comments of this issue. RCT adds a _confirmed-event_ label and _global-twitch-event_ tag to the issue and adds event to the __Global Live Streams__ project. Issue will appear in the __Upcoming Streams__ column
|
|
||||||
- [ ] Speaker adds a _ready-for-marketing-edit_ label so the RCT can review title and description
|
|
||||||
|
|
||||||
## 8 Weeks Prior
|
|
||||||
- [ ] RCT does a review of title and description
|
|
||||||
- [ ] RCT moves the issue to the __Ready for SharePoint__ column
|
|
||||||
- [ ] RCT informs the Reactor Marketing Team of the new event information
|
|
||||||
- [ ] RCT provides speaker with assets (e.g. slides, overlays) and the survey data for the event
|
|
||||||
- [ ] RCT moves the issue to the __Stream Preparation In Progress__ column
|
|
||||||
|
|
||||||
## 2 Weeks Prior
|
|
||||||
- [ ] Speaker opens a PR with the new content for the stream, adds it to the same project chosen above, and adds the _content-development_ and _global-twitch-event_ tag to the PR. PR will appear in the __Stream Preparation In Progress__ column.
|
|
||||||
- [ ] Speaker adds to the same PR a modification to the [Streaming README](https://github.com/microsoft/Reactors/tree/main/Online)
|
|
||||||
- [ ] Speaker adds the RCT assigned to the issue as the reviewer when it is ready for review/merge
|
|
||||||
- [ ] RCT reviews, approves, and merges the changes and the PR moves to the __Stream Complete__ column
|
|
||||||
|
|
||||||
## 1 Week Prior
|
|
||||||
- [ ] Speaker and Moderator test setup for streaming (instructions coming soon)
|
|
||||||
- [ ] RCT checks in with the speaker and moves the issue to the __Ready to Stream__ column
|
|
||||||
|
|
||||||
## During and After Stream
|
|
||||||
- [ ] Speaker and Moderator run the stream
|
|
||||||
- [ ] RCT submits recording to be uploaded to the Reactor YouTube and to be made available on LearnTV
|
|
||||||
- [ ] RCT moves issue to the __Stream Complete__ column
|
|
||||||
|
|
@ -1,55 +0,0 @@
|
||||||
---
|
|
||||||
name: In-Person Event Tracking Issue
|
|
||||||
about: For a single Local in-person Reactor Events
|
|
||||||
title: Date - Topic - Location
|
|
||||||
labels: 'in-person-local-event'
|
|
||||||
assignees: ''
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
# Event Information
|
|
||||||
| Category | Details |
|
|
||||||
|-----------|---------|
|
|
||||||
| Reactor Topic | <Topic from one of the 9 Reactor topics> |
|
|
||||||
| Monthly Topic (if applicable) | <Topic taken from [Azure Dev Marketing](https://aka.ms/DevEdCalFY21H1)> |
|
|
||||||
| Weekly Topic (if applicable) | <Topic decided by RCT if relevant> |
|
|
||||||
| Stream Topic | <2-5 words describing the topic> |
|
|
||||||
| Stream Date | <Month ##, ###> |
|
|
||||||
| Stream Time | <12h Local Time> |
|
|
||||||
| Stream Duration | <minutes> |
|
|
||||||
| Location | <Reactor Location> |
|
|
||||||
| Title | <150 characters or less > |
|
|
||||||
| Description | <500 characters or less> |
|
|
||||||
| Speaker | <Name or GitHub alias> |
|
|
||||||
|
|
||||||
Additional Resources:
|
|
||||||
<Additional resources that can be linked from social media for promotion>
|
|
||||||
|
|
||||||
|
|
||||||
# Event Checklist
|
|
||||||
|
|
||||||
## 10 Weeks Prior
|
|
||||||
- [ ] Reactor Content Team (RCT) or Speaker opens a new issue for an upcoming event filling in the Event Information table. Both RCT and Speaker are marked as assignees.
|
|
||||||
- [ ] RCT and Speaker discuss details of the event in the comments of this issue. RCT adds a _confirmed-event_ label and adds event to the __In-Person Local Events__ project. Issue will appear in the __Upcoming Events__ column
|
|
||||||
|
|
||||||
## 8 Weeks Prior
|
|
||||||
- [ ] RCT does a review of title and description
|
|
||||||
- [ ] RCT moves the issue to the __Ready for Marketing__ column
|
|
||||||
- [ ] RCT informs the Reactor Marketing Team of the new event information
|
|
||||||
- [ ] If content is Reactor provided, RCT adds links to content to the [In-Person README](https://github.com/microsoft/Reactors/tree/master/In-Person%20Events)
|
|
||||||
- [ ] RCT provides speaker with assets (e.g. slides, overlays) and the survey information
|
|
||||||
- [ ] If content is Reactor provided, RCT meets with Speaker to review content
|
|
||||||
- [ ] RCT moves the issue to the __Event Preparation In Progress__ column
|
|
||||||
|
|
||||||
## 2 Weeks Prior
|
|
||||||
- [ ] If content is Speaker provided, Speaker opens a PR with the new content for the event to the [In-Person README](https://github.com/microsoft/Reactors/tree/master/In-Person%20Events), adds it to the same project chosen above, and adds the _content-development_ and _in-person-local-event_ tags to the PR. PR will appear in the __Event Preparation In Progress__ column
|
|
||||||
- [ ] Speaker adds the RCT assigned to the issue as the reviewer when it is ready for review/merge
|
|
||||||
- [ ] RCT reviews, approves, and merges the changes and the PR moves to the __Event Complete__ column
|
|
||||||
|
|
||||||
## 1 Week Prior
|
|
||||||
- [ ] RCT connects Speaker with local Reactor PM
|
|
||||||
- [ ] RCT checks in with the speaker and moves the issue to the __Event Ready__ column
|
|
||||||
|
|
||||||
## During and After Stream
|
|
||||||
- [ ] Speaker runs the event
|
|
||||||
- [ ] RCT moves issue to the __Event Complete__ column
|
|
||||||
|
|
@ -1,53 +0,0 @@
|
||||||
---
|
|
||||||
name: Local Digital Event Tracking Issue
|
|
||||||
about: For a Local digital Reactor Event
|
|
||||||
title: Week - Topic
|
|
||||||
labels: 'local-teams-event'
|
|
||||||
assignees: ''
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
|
|
||||||
# Event Information
|
|
||||||
| Category | Details |
|
|
||||||
|-----------|---------|
|
|
||||||
| Reactor Topic | |
|
|
||||||
| Monthly Topic (if applicable) | |
|
|
||||||
| Weekly Topic (if applicable) | |
|
|
||||||
| Workshop Topic | |
|
|
||||||
| Workshop Duration | |
|
|
||||||
| Title | |
|
|
||||||
| Description | |
|
|
||||||
|
|
||||||
# Workshop details
|
|
||||||
| Date | Local Start Time | Location | Speaker | SharePoint ID |
|
|
||||||
|----- |------------------|-----------|----------|--------------|
|
|
||||||
|
|
||||||
|
|
||||||
# Event Checklist
|
|
||||||
|
|
||||||
## 10 Weeks Prior
|
|
||||||
- [ ] Reactor Content Team (RCT) opens a new issue for an upcoming local workshop filling in the Event Information and Workshop details tables. RCT member who owns content (content owner) this week will be the assignee.
|
|
||||||
- [ ] RCT and content owner discuss details of the event in the comments of this issue. RCT adds a _confirmed-event_ label and _local-teams-event_ tag to the issue and adds event to the __Local Live Streams__ project. Issue will appear in the __Upcoming Streams__ column
|
|
||||||
- [ ] Confirm instructor for weekly workshops
|
|
||||||
|
|
||||||
## 8 Weeks Prior
|
|
||||||
- [ ] RCT does a review of title and description
|
|
||||||
- [ ] RCT moves the issue to the __Ready for Marketing__ column
|
|
||||||
- [ ] RCT informs the Reactor Marketing Team of the new event information
|
|
||||||
- [ ] RCT moves the issue to the __Content Preparation In Progress__ column
|
|
||||||
|
|
||||||
## 5 weeks Prior
|
|
||||||
- [ ] Content owner opens a PR with the new content for the workshop, adds it to the same project chosen above, and adds the _content-development_ and _local-teams-event_ tag to the PR. PR will appear in the __Content Preparation In Progress__ column.
|
|
||||||
- [ ] Content owner adds to the same PR modification to the [Streaming README](https://github.com/microsoft/Reactors/tree/main/Online)
|
|
||||||
- [ ] RCT reviews, approves, and merges the changes and the PR moves to the __Ready to Stream__ column
|
|
||||||
- [ ] RCT shares content with the vendor/instructor
|
|
||||||
- [ ] RCT provides vendor/instructor with assets (e.g. slides, overlays) and the survey data for the event
|
|
||||||
- [ ] RCT ensures that instructors have received an invite to the workshops and that PM team works with instructors to get setup in Teams
|
|
||||||
|
|
||||||
## 1 Week Prior
|
|
||||||
- [ ] Check-in with vendor/instructor that they are prepared for the workshop
|
|
||||||
|
|
||||||
## During and After Stream
|
|
||||||
- [ ] Instructor (and optional moderator) run the stream
|
|
||||||
- [ ] RCT moves issue to the __Stream Complete__ column
|
|
||||||
|
|
@ -1,53 +0,0 @@
|
||||||
---
|
|
||||||
name: New Content Tracking Issue
|
|
||||||
about: For Reactor workshops, streams, and Microsoft Learning Paths
|
|
||||||
title: Topic
|
|
||||||
labels: 'content-development'
|
|
||||||
assignees: ''
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
# Content Information
|
|
||||||
| Category | Details |
|
|
||||||
|-----------|---------|
|
|
||||||
| Reactor Topic | <Topic from one of the 9 Reactor topics> |
|
|
||||||
| Title | <150 characters or less > |
|
|
||||||
| Description | <500 characters or less> |
|
|
||||||
| PreReqs | <Describe what prior knowledge attendees should have> |
|
|
||||||
| Relevant Resources | <Include links to other relevant resources> |
|
|
||||||
| Author | <Name or GitHub alias> |
|
|
||||||
|
|
||||||
Outline:
|
|
||||||
<Please include an outline of the content>
|
|
||||||
|
|
||||||
|
|
||||||
# Content Checklist
|
|
||||||
## Proposal: [Due: INSERT DEADLINE DATE HERE]
|
|
||||||
- [ ] Reactor Content Team (RCT) or Writer opens a new issue for an upcoming content filling in the Content Information table.
|
|
||||||
- If RCT initiated the issue, RCT finds and assigns a Writer to the issue
|
|
||||||
- If Writer initiated the issue, an RCT member will be assigned to the issue
|
|
||||||
- Both RCT and Writer should be marked as assignees
|
|
||||||
- [ ] RCT and Writer discuss details of the content in the comments of this issue. RCT adds issue to the __Content Development__ project. Issue will appear in the __Proposed Content__ column
|
|
||||||
|
|
||||||
## Content Development
|
|
||||||
### Setup: [Due: INSERT DEADLINE DATE HERE]
|
|
||||||
- [ ] RCT creates a folder for the content to live
|
|
||||||
- [ ] Writer opens a PR with a README for the content that includes the information from this issue
|
|
||||||
- [ ] Writer adds PR to the __Content Development__ project and PR will be moved tot he _In progress_ column
|
|
||||||
- [ ] Writer assigned RCT to be the PR reviewer and adds a _draft_ label to the PR
|
|
||||||
|
|
||||||
### Draft Review: [Due: INSERT DEADLINE DATE HERE]
|
|
||||||
- [ ] Writer adds a _ready-for-review_ label (keeping the _draft_ label) to the PR and tags the reviewer in the comments
|
|
||||||
- [ ] RCT conducts review
|
|
||||||
- [ ] Writer removes both the _draft_ and _ready-for-review_ labels and incorporates feedback
|
|
||||||
|
|
||||||
### Final Review: [Due: INSERT DEADLINE DATE HERE]
|
|
||||||
- [ ] Writer adds a _ready-for-review_ label to the PR and tags the reviewer in the comments
|
|
||||||
- [ ] Writer conducts an overview pilot of content for RCT
|
|
||||||
- [ ] RCT conducts review (if back and forth needs to happen, it does)
|
|
||||||
- [ ] RCT approves and merges PR
|
|
||||||
|
|
||||||
## Content Sharing: [Due: INSERT DEADLINE DATE HERE]
|
|
||||||
- [ ] RCT adds the new content to the Content README (Coming soon)
|
|
||||||
- [ ] RCT informs Reactor Program Management and Reactor Marketing Teams of new content
|
|
||||||
- [ ] RCT plans pilot event for this content
|
|
||||||
Загрузка…
Ссылка в новой задаче