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,
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.
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
-*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)
We welcome your participation in this project. Your participation does not have to be coding. You could help us on ideas, suggestions, information, etc.
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 when interaction 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.
I believe that *code review* is a very important activity for effectively improving code quality and promoting participation.
## The feature-branching workflow
Check the section **The feature-branching workflow** in the following link: