-
Notifications
You must be signed in to change notification settings - Fork 4
Label Philosophy
Editors: Furkan Kadıoğlu, Velican Ünal
"Effort: High"
This kind of issues approximately takes few hours.
"Effort: Medium"
This kind of issues approximately takes 1 hour.
"Effort: Low"
This kind of issues approximately takes up to 15 minutes.
"Priority: Critical"
This should be dealt with ASAP. Not fixing this issue would be a serious error.
"Priority: High"
After critical issues are fixed, these should be dealt with before any further issues.
"Priority: Medium"
This issue may be useful, and needs some attention.
"Priority: Low"
This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix.
"Type: Documentation"
Issues describe qualification of project and completed tasks' details.
"Type: Meeting"
We need to discuss
"Type: Research"
We need to discuss
"Type: Agenda"
Issues collect suggestions about next meeting.
The status label may apply to both Issues and Pull Requests.
"Status: Available"
No one has claimed responsibility for resolving this issue. Generally this will be applied to bugs and enhancement issues, but may be applied to others.
"Status: Accepted"
It's clear what the subject of the issue is about, and what the resolution should be.
"Status: Blocked"
There is another issue that needs to be resolved first, or a specific person is required to comment or reply to progress. There may also be some external blocker.
"Status: Completed"
Nothing further to be done with this issue. Awaiting to be closed by the requestor out of politeness, or can be closed by a project member.
"Status: In Progress"
This issue is being worked on, and has someone assigned.
"Status: On Hold"
Similar to blocked, but is assigned to someone. May also be assigned to someone because of their experience, but it's recognised they are unable to process the issue at this time.
"Status: Review Needed"
The issue has a PR attached to it which needs to be reviewed. Should receive review by others in the community, and at least one member / comitter. Specifics on when merging PRs is allowed is still up for debate.
"Status: Revision Needed"
At least two people have seen issues in the PR that makes them uneasy. Submitter of PR needs to revise the PR related to the issue.
This project is operated in the context of Cmpe 451
- Ali Meriç Deşer
- Yusuf Mert Bila
- Furkan Kadıoğlu
- Mahmut Uzunpostalcı
- Hasan Öztürk
- Selamettin Dirik
- Meltem Suiçmez (Communicator)
- Abdullah Enes Öncü
- Kartal Kaan Bozdoğan
- Nevzat Ersoy
💻 Project
- Requirements
- User Manual
- User Stories
- Mockups
- Diagrams
- Milestone I Report (CMPE 352)
- Project Plan (CMPE 352)
- API Documentations:
- Milestone 2 Report (CMPE 352)
- Milestone I Report
- Milestone II Report
- Final Report
Meeting 2 (Android) (02.10.19) | Meeting 2 (Frontend) (07.10.19) | Meeting 2 (Backend) |