CodeYourFuture / CodeYourFuture/Changes
Actually build and adopt an attendance register with API
- 主要言語
- JavaScript
- スター
- 3
- フォーク
- 4
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
## I want to do this:
I want to build (or redevelop a good example of) this Final Project and actually adopt it into use.
https://docs.google.com/document/d/1BQd_AA4qz-N1fv83yeyh72QdhSnAzdn6GtwjC6tMwDQ/edit
Loads of people really want this project! It has been built a couple of times but not yet taken forward in a way that can really be useful.
## Here’s why I want to do it:
- We know that attendance is highly correlated with success on our course
- In some schools, we are inconsistent with recording attendance, so we miss trainees who are falling behind or having personal difficulties
- It's laborious for volunteers to manually update attendance in a spreadsheet when we are a community of developers so should not be burdened by this kind of data entry
## Here’s how it serves our goals:
- This would be a decent portfolio piece for our grads
- This would free up our time and be simpler to handle
- This would be easier to make available to a new tracker
- This would be more reliable and therefore more useful to everyone
## This is how much time I can put towards this change:
### already done
- I have written this Final Project briefing
- I have explained the idea to various CYFers who also really want this
### can do
- I'm happy to throw on a nice, accessible and simple front end, so don't get bogged down in that stuff - focus on the function
- I can offer up to 6 121 sessions for development and 3 for testing
## This is the help I need from others to get this done (if any):
- a team of two developers to build this
- a liaison from @CodeYourFuture/cyf-next to make sure the API makes sense
- a tech volunteer to code review
- a product owner to drive adoption
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
リンク先のFinal Projectブリーフィングから始め、提案されている出席登録とその要件を理解してください。このIssueでは、チームがプロジェクトを構築し、cyf-nextのリエゾンとAPIを定義し、シンプルでアクセシブルなフロントエンドを提供し、テストし、導入を支援することが求められています。それ以外に、完了の定義は指定されていません。
索引モデルが issue の本文から書いたものです。
評価
- 領域
- api
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 20/100