90 lines
3.3 KiB
Markdown
90 lines
3.3 KiB
Markdown
# About LRR
|
|
|
|
LRR (Lab Report Repository) is an online software application for posting assignments, submitting assignments and marking (re-marking) assignments.
|
|
|
|
This software was originally developed by by Mahomed Nor, a postgraduate student in the Department of Computer Science at the Zhejiang Normal University,
|
|
while he was taking his graduate course **Advanced Software Engineering** (http://lanlab.org/course/2018f/se/homepage.html).
|
|
|
|
|
|
|
|
# Mission
|
|
|
|
Our mission is to make the learning experience great for tens of thousands of students around the world.
|
|
|
|
|
|
|
|
# Current Status
|
|
|
|
This software has been actively used by students who took or are taking courses taught by Hui. There are more than 200 student accounts created since its first launch.
|
|
|
|
A running instance of this software is at http://118.25.96.118/nor/
|
|
|
|
There are about 40 bugs (most being CRITICAL) that remain unresolved before LRR can hit its beta release. See the section *The Bug Tracker* for more details.
|
|
|
|
Currently, there are a few groups (formed by students who are taking Software Project Management) working on these bugs.
|
|
|
|
|
|
|
|
# The Original GitHub Repo
|
|
|
|
The original GitHub Repo is at https://github.com/EngMohamedNor/LabReportRepo
|
|
|
|
|
|
|
|
|
|
# The Bug Tracker
|
|
|
|
Most bugs of this software have been reported on the LRR bug tracker: http://118.25.96.118/bugzilla/describecomponents.cgi?product=Lab%20Report%20Repository%20%28nor%20houzi%29
|
|
|
|
|
|
|
|
# TODO
|
|
|
|
- [SOLVED] A new user could not login immediately after sign up.
|
|
|
|
- *Receiving email for password resetting*. Password resetting link is not always sent successfully.
|
|
|
|
- *How assignements should be stored?* Creating sub-directories on all student submissions course-code/semester/section-number. (/student-number/course-code/semester/section-number/assignement-title/submission.txt)
|
|
|
|
- *Feature request*. Editing the assignment title after uploading a new assignment (instructor).
|
|
|
|
|
|
We welcome your participation in this project. Your participation does not have to be coding. You could help us on ideas, suggestions, information, etc.
|
|
|
|
|
|
*Last modified on 22 March 2020*
|
|
|
|
|
|
|
|
# How to Contribute
|
|
|
|
You need to be an invited member of *Lan Laboratory* before you can push your feature branch or bugfix branch to the central reops at https://github.com/lanlab-org
|
|
|
|
Send Hui (lanhui at zjnu.edu.cn) an email message including your GitHub account name so that he could invite you to be a member of *Lan Laboratory*.
|
|
|
|
Currently, there are 9 members in *Lan Laboratory* (https://github.com/orgs/lanlab-org/people).
|
|
|
|
You will use the feature-branching workflow (see below) when
|
|
interacting with the central repo. The main point of this workflow is
|
|
that you work on a branch on your local drive, push that branch to the
|
|
central repo, and create a Pull Request (i.e., Pull Me Request) at
|
|
GitHub for other people to review your changes. When everything is
|
|
OK, then you could merge your changes to the master branch in the
|
|
central repo.
|
|
|
|
I believe that *code review* at the Pull Request stage is a very important activity for effectively improving both code quality and team quality.
|
|
|
|
|
|
## The feature-branching workflow
|
|
|
|
Check the section **The feature-branching workflow** in the following link:
|
|
|
|
https://github.com/spm2020spring/TeamCollaborationTutorial/blob/master/team.rst
|
|
|
|
|
|
|
|
# Contributor List
|
|
|
|
*Please put your name and student number below*.
|
|
|