aismail / vmgui Goto Github PK

This file contains all the python dependencies needed to run the current project.
You can create one with

$ pip freeze > requirements.txt

To install the deps needed after you clone the project, you run:

$ pip install 

It is very important when starting an app to create a requirements.txt file and to maintain it, whenever a new lib is added, it must be added to the requirements file.

Assignment
- subject_id
- name
- text (html) - markdown
- attachments (URLs uploaded somewhere else, for example skeleton starting point, example inputs, etc.)
- deadline

• FARA zile de vacanta sau alte complicatii
• FARA depunctari momentan

Move this aismail/vmgui to vmchecker/vmchecker-ui

• - Add aismail to vmchecker-ui-admins
• - Grant commit access to everyone involved
• - Move repo
• - Update test server
• - ???
• - Profit!

• @AndreiDuma
• read [1]
• read [2]

@bogdanbresug

• read [1]
• read [2]

@bgdnc

• read [1]
• read [2]

[1] http://gitimmersion.com/
[2] https://github.com/aismail/vmgui/blob/master/CONTRIBUTING.md

@bogdanbresug What's gunicorn? A fancy of web server.

Let's not put questions in commit messages. Instead let's add an issue with the question tag and people will answer it.

• delete everything
• use factories to create entitites (need UserFactory)

SubmissionComments:
- submission_id
- filename (optional)
- line_no (optional)
- comment_no
- comment (sanitized html)

Is is possible for the teacher to define extra fields for a submission?

Example:

The teacher wants to know how much time a student worked on a homework.
The teacher sets up the assignment, and mentions that he wants to get the number of hours.
When submitting, the student will be required to enter the number of hours.

Note:

This is low priority. Just something to think about, 
and maybe plan for towards the end of the project.

Needed:

• get all subjects (for their names, on the dashboard page)
• get a subject by ID (for the subject full page view)

When deploy-ing, extra steps to be taken:

• additional stuff added to requirements.txt should be installed
• the gunicorn server should be restarted
• syncdb not interactive should be done, to redo the extra tables created.
• an initial dump of data should exist in repo, and be loaded in DB

Currently, files uploaded via a submission go to the vmchecker/vmc_backend/files/ which is kind of a hidden location. Should we change it or leave it like that?

There are files that do not pass pep 8 validation. We should write valid code, right?
You can either use pep8 command from cli or use pep8 plugin for vim.
Do you think it would be a good idea to create an issue for every file so we can track easier the process?

Not entering a line_no when creating a new SubmissionComment returns the following error:

IntegrityError at /admin/vmc_backend/submissioncomment/add/
vmc_backend_submissioncomment.line_no may not be NULL

Solution here (also a good read)
https://code.djangoproject.com/wiki/NewbieMistakes

inspiration: https://github.com/rosedu/wouso/blob/master/wouso/core/user/tests.py

We have to keep in mind that the DB should be kept across several years.
If last year's student checks vmchecker, he should see all of last year's assignments and submission. However, these should not be visible for this year's students (or could be visible, but separated). Should we add a school_year field to the AssignmentModel?
Feel free to comment on the idea.

inspiration: https://github.com/rosedu/wouso/blob/master/wouso/core/user/tests.py

It's not yet implemented.

Should we limit the size and type of uploaded submissions?

You could get this from the number of comments that reference the Submission.
Remove the comment_count field, and add related_name='comments' to submission_id = models.ForeignKey(Submission)
Remove comment_no = models.IntegerField() as it's also not needed

You can then retrieve the number of comments by using submission.comments.all().count()

I created some factories for the models that generate some random entries and I want someone to check them. I was also not sure how to generate a random file for this field inside the SubmissionModel:

content = models.FileField(upload_to='vmc_backend/files')

Thank you. :)

403 forbidden

Write tests.

Submission
- student_id
- assignment_id
- uploaded_at
- graded (true/false)
- comment_count (a-la-github)
- content

Subjects
- name
- description
- link
- contact_person_email

Should we impose a size and type limit on uploaded submissions?

In the former implementation of vmchecker's UI, a submission could have multiple types. For example, it's usually a zip archive, but it could also be the md5 hash of a VERY large archive, that would be uploaded later on.
This is a MUST HAVE feature for v1.0 of the new UI.

• get UsersToSubjects related to a given user (filter by user_id) - needed for the Dashboard page

CC @andreip

Also write a short guide.

• create a Submission via POST (this will be probably the only case where we need to POST data to the application from the JS dashboard, other editing/creating cases will be handled from the Django admin directly)
• get submissions of a student for a given assignment (needed on the assignment full page view, to display the submissions of the student for that assignment next to the assignment itself)

Make sure the UI and DB support internationalization (translation into other languages).
More info here:
https://docs.djangoproject.com/en/1.0/topics/i18n/

UsersToSubjects:
- subject_id
- user_id
- role (user can be teacher for one course, student for another)
- UNIQUE_TOGETHER(subject_id, user_id)

1. Dashboard - view subjects + your role in them + link to courses
   • SELECT * FROM UsersToSubjects WHERE user_id = :user_id
   • GET /api/v1/subjects/?user_id={{user_id}}
   • DashboardController + Subject Widget
2. View an individual subject:
   • SELECT * FROM Subjects WHERE id = :id
   • SELECT * FROM Assignments WHERE subject_id = :id
   • GET /api/v1/subjects/:id
   • GET /api/v1/assignments/?subject_id=:id
   • SubjectController + SubjectWidget (description, etc.) + AssignmentWidget (cu link spre assignment)
     Obs: editare de assignments facem din Django Admin pt. inceput
3. View an individual assignment:
   • SELECT * FROM Assignments WHERE id = :id
   • SELECT * FROM Submission WHERE assignment_id = :id and student_id = :current_user_id
   • GET /api/v1/assignments/:id
   • GET /api/v1/submissions/?assignment_id=:id
   • POST /api/v1/submissions/:id/download (gimme the tarball nigga)
   • AssignmentController + FullAssignmentWidget + SubmissionWidget + DownloadSubmissionWidget

• get assignments by subject id (for subject full page view)
• get assignment by id (for assignment full page view)
• tests

• Add auth tests for each resource
• Add auth to each resource

1st test case

create 2 subjects, 3 homeworks linked to the 2 subjects
perform API call
test that the expected homeworks are present.

2nd test case

create 2 subjects, 1 homework linked to 1 subject
perform API call filtered by subject_id
test that there are no results returned

grupa (sau ceva mai generic care e sinonim cu grupa)

Write tests.