Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view

This file was deleted.

20 changes: 0 additions & 20 deletions .github/ISSUE_TEMPLATE/choosing-idea-week-1-of-3--dev-tasks.md

This file was deleted.

16 changes: 0 additions & 16 deletions .github/ISSUE_TEMPLATE/choosing-idea-week-1-of-3--manager-tasks.md

This file was deleted.

16 changes: 0 additions & 16 deletions .github/ISSUE_TEMPLATE/choosing-idea-week-2-of-3--dev-tasks.md

This file was deleted.

16 changes: 0 additions & 16 deletions .github/ISSUE_TEMPLATE/choosing-idea-week-2-of-3--manager-tasks.md

This file was deleted.

13 changes: 0 additions & 13 deletions .github/ISSUE_TEMPLATE/choosing-idea-week-3-of-3--dev-tasks.md

This file was deleted.

13 changes: 0 additions & 13 deletions .github/ISSUE_TEMPLATE/choosing-idea-week-3-of-3--manager-tasks.md

This file was deleted.

24 changes: 0 additions & 24 deletions .github/ISSUE_TEMPLATE/creating-idea-week-1-of-5--dev-tasks.md

This file was deleted.

15 changes: 0 additions & 15 deletions .github/ISSUE_TEMPLATE/creating-idea-week-1-of-5--manager-tasks.md

This file was deleted.

16 changes: 0 additions & 16 deletions .github/ISSUE_TEMPLATE/creating-idea-week-2-of-5--dev-tasks.md

This file was deleted.

16 changes: 0 additions & 16 deletions .github/ISSUE_TEMPLATE/creating-idea-week-2-of-5--manager-tasks.md

This file was deleted.

18 changes: 0 additions & 18 deletions .github/ISSUE_TEMPLATE/creating-idea-week-3-of-5--dev-tasks.md

This file was deleted.

16 changes: 0 additions & 16 deletions .github/ISSUE_TEMPLATE/creating-idea-week-3-of-5--manager-tasks.md

This file was deleted.

20 changes: 0 additions & 20 deletions .github/ISSUE_TEMPLATE/creating-idea-week-4-of-5--dev-tasks.md

This file was deleted.

19 changes: 0 additions & 19 deletions .github/ISSUE_TEMPLATE/creating-idea-week-4-of-5--manager-tasks.md

This file was deleted.

13 changes: 0 additions & 13 deletions .github/ISSUE_TEMPLATE/creating-idea-week-5-of-5--dev-tasks.md

This file was deleted.

13 changes: 0 additions & 13 deletions .github/ISSUE_TEMPLATE/creating-idea-week-5-of-5--manager-tasks.md

This file was deleted.

19 changes: 19 additions & 0 deletions .github/ISSUE_TEMPLATE/stage-1--blog--week-1-of-3--dev-tasks.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
name: 'Stage 1 (Blog) Week 1 of 3: Dev Tasks'
about: Stage 1, Week 1 for Devs
title: "[Topic Name] [Project Name] Stage 1 - Week 1 of 3: Dev Tasks"
labels: weekly-dev
assignees: ''

---

- [ ] Proposal
- [ ] Specific Idea
- [ ] Interactive Component
- [ ] Code Deliverables
- [ ] Slide Outline
- [ ] Timing
- [ ] Motivation Behind Project
- [ ] Difficulty/prior experience
- [ ] Technologies that will be used
- [ ] Complete Code Deliverables Planned for Week 1
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
name: 'Stage 1 (Blog) Week 1 of 3: Manager Tasks'
about: Stage 1, Week 1 for Managers
title: "[Topic Name] [Project Name] Stage 1 - Week 1 of 3: Manager Tasks"
labels: weekly-manager
assignees: ''

---

* [ ] Follow-up on proposal, ensure proposal is **detailed** and **specific**
* [ ] Proposals should be labelled with a title of \[Topic\]-\[Workshop Name\]-Proposal.md AND in the [proposals](https://github.com/bitprj/mdx-deck/tree/master/misc/proposals) folder
* [ ] "General Manager Responsibility" [checklist](https://about.bitproject.org/teams/developer-relations/future-workshop-plan/managers-responsibilities#general-weekly-responsibilities-for-managers) should be completed
* [ ] Generate an **Epic** issue on `bitprj/mdx-deck` for _Week 2_ with the following format: \[Topic Name\] \[Workshop Name\] Stage 1 Week \[x\] of \[y\]: Dev Tasks
* [ ] Set label as `weekly`
* [ ] Have appropriate checklist within issue
* [ ] Include deadline in issue
* [ ] Set devs as assignees
* [ ] Link these epics with your project epic \(yes, epics can be linked to epics!\)
19 changes: 19 additions & 0 deletions .github/ISSUE_TEMPLATE/stage-1--blog--week-2-of-3--dev-tasks.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
name: 'Stage 1 (Blog) Week 2 of 3: Dev Tasks'
about: Stage 1, Week 2 for Devs
title: "[Topic Name] [Project Name] Stage 1 - Week 2 of 3: Dev Tasks"
labels: weekly-dev
assignees: ''

---

* [ ] Fully integrate manager’s feedback on Week 1
* [ ] Rough Draft of Blog on conceptual and interactive portions of workshop
* Note that blog should cover the following general sections:
* Idea/Motivation behind project
* Concepts
* Code Walkthrough
* Interactive Component
* [ ] Finish Code Deliverables for Week 2
* [ ] Document how to replicate the running of their code in a README
* [ ] Code should be commented in GitHub for blog viewers
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
name: 'Stage 1 (Blog) Week 2 of 3: Manager Tasks'
about: Stage 1, Week 2 for Managers
title: "[Topic Name] [Project Name] Stage 1 - Week 2 of 3: Manager Tasks"
labels: weekly-manager
assignees: ''

---

* [ ] Ensure feedback from last week is fully integrated
* [ ] Nail down specifics of interactive component with devs
* [ ] Ensure that rough draft of blog is complete, covering the following info
* [ ] Idea/Motivation behind project
* [ ] Concepts
* [ ] Code Walkthrough
* [ ] Interactive Component
* [ ] Run their code for Week 2, ensure that their code can run on your computer and that their README is updated accordingly
* [ ] "General Manager Responsibility" [checklist](https://about.bitproject.org/teams/developer-relations/future-workshop-plan/managers-responsibilities#general-weekly-responsibilities-for-managers) should be completed
* [ ] Generate an **Epic** issue on `bitprj/mdx-deck` for _Week 3_ with the following format: \[Topic Name\] \[Workshop Name\] Stage 1 Week \[x\] of \[y\] Dev Tasks
* [ ] Set label as `weekly-dev`
* [ ] Have appropriate checklist within issue
* [ ] Include deadline in issue
* [ ] Set devs as assignees
* [ ] Link these epics with your project epic \(yes, epics can be linked to epics!\)
Loading