search

cs102-project / LabConnect

LabConnect facilitates communication between students, TA's, tutors, and instructors.
http://labconnect.me
GNU Affero General Public License v3.0
6 stars 0 forks source link

UI Design Report #7

Closed vedxyz closed 3 years ago

vedxyz commented 3 years ago

To be merged on Thursday, 25th March. The mock-up designs shouldn't need many modifications hereon, it might be fine to focus on the report itself. As a precaution, I've made the introduction to the report document by explaining why the interface design of LabConnect cannot practically be illustrated accurately at this stage of development.

Some unrelated suggestions that have been taken care of

P.S. would be cool if we could have a roadmap of sorts made up of GitHub issues, so we could open these PRs and just say "Closes #`issue`." lol. Perhaps the issues themselves could be used as discussion boards for those features/tasks? Anyway, just throwing ideas around. Edit: Talking precisely about what Berkan was doing before: #4 P.P.S. it's also possible to get an issue/PR template going under the `.github` folder, if need be.

whymeeverytime commented 3 years ago

lol

berkan-sahin commented 3 years ago

I think milestones can be more appropriate for what @vedattt is asking. In fact, that's how I made the "roadmap" for the Requirements report phase.

P.S: Milestones can be used in conjunction with issues which are linked w/ PRs for better planning. Issues would have the more general discussion (guys who's going to upload to Moodle etc.) while PRs would have discussion directly related to the report/code at hand.

vedxyz commented 3 years ago

@berkan-sahin Yup, I've ended up connecting things with Projects/Labels/Issues/Milestones, whichever one sticks will be fine I guess. Thanks.

berkan-sahin commented 3 years ago

I uploaded the report to Moodle.

berkan-sahin commented 3 years ago

I removed my submission since the TAs expect @friberk to upload all reports from now on.