jetta6241/djudge

Automatically exported from code.google.com/p/djudge

djudge's Issues

Judging problems

Need script to judge user submissions.

Original issue reported on code.google.com by [email protected] on 17 Jan 2010 at 9:03

manage user's handles

A user should be able to add or change his handles

Original issue reported on code.google.com by [email protected] on 12 Jan 2010 at 11:40

Code review request

Please review the model changes to the ExternalProblem model.

Original issue reported on code.google.com by [email protected] on 17 Jan 2010 at 6:29

Creating User Model

Sorry for the detailed description which of course happened by mistake.

Here is the issue description:

The user model should be created where user information
and activities are managed.

Original issue reported on code.google.com by [email protected] on 11 Dec 2009 at 4:39

Statistics columns in problems list

Add statistics columns to the list of problems, e.g. no. of submissions, 
correct submissions, etc...

Original issue reported on code.google.com by [email protected] on 20 Jan 2010 at 1:06

Please review and test the login/logout feature

Steps to test the register and login/logout features:

1- The usual validate-syncdb-runserver
2- Go to /judge/register/ and create a new user (no activation step, to be
implemented)
3- Login using your newly registered user at /judge/login/
4- Visit all pages, making sure the session doesn't drop the user somewhere
5- (Optional step) Try to sniff for the password ;)
6- Logout
7- Comment and give feedback

Original issue reported on code.google.com by [email protected] on 13 Dec 2009 at 9:06

modify user information

A user should be able to modify his own data:

1- First name
2- Last name
3- E-mail address
4- University

Original issue reported on code.google.com by [email protected] on 12 Jan 2010 at 11:39

Script Jury review

What can be changed to make it better. (Not accounting for security problems).

Original issue reported on code.google.com by [email protected] on 18 Jan 2010 at 12:00

Admin interface style

The Admin interface looks horrible currently, a new theme needs to be chosen.

Original issue reported on code.google.com by [email protected] on 14 Dec 2009 at 12:23

Clean up the code

Clean up the code by renaming some variables, add comments, get rid of
unnecessary views operations, etc..
Have the code in a good state for development.

Original issue reported on code.google.com by [email protected] on 8 Dec 2009 at 5:17

Modifying the problem model

1- Differentiate between problems hosted in Online Judges and problems  
uploaded by the user and hosted in DJudge (use of model inheritance).

2- Associate with problem hosted in DJudge with a list of input and output
pairs (Input Instance, Output Instance).  

Original issue reported on code.google.com by [email protected] on 30 Dec 2009 at 7:04

Admin media & CSS not found

The admin interface is missing all the css since revision a79b431171.

Original issue reported on code.google.com by [email protected] on 11 Dec 2009 at 3:40

Interface for upload files to the judge

Interface for upload Input/Output files to the judge  

Original issue reported on code.google.com by [email protected] on 30 Dec 2009 at 7:06

An all submissions page showing latest submissions independant of a contest

An all submissions pages similar to the one used on SPOJ
(http://www.spoj.pl/status/) will be very helpful in tracking the overall
activity on the website.

Original issue reported on code.google.com by [email protected] on 26 Jan 2010 at 6:22

您的OJ很出色，我们希望邀请您加入OJ题库共享平台。

您的OJ很出色，我们希望邀请您加入OJ题库共享平台。

我们的项目地址:

http://code.google.com/p/freeproblemset/

目前已有百余道题目可免费下载。

目前有许多开源的ACM/ICPC Online Judge 
系统，都各有特色，他们都有自己独特的
体系结构。

但似乎比较难找的是相应的练习题目，各大学校的OJ都对自己
的题目数据严加保密，
不轻易与人分享。

出题是很辛苦的事情，抄题也是如此，而且抄来的题目数据��
�难制作，标程就更难寻
找，特别裁判更加难上加难。

这个项目希望建立一个交流平台，使得学校之间交流题目更��
�容易。

所以这个项目的目标是，建立一种通用题目交换格式，基于XM
L来实现。

其中包含了：
1、题目
2、测试数据
3、裁判(可选)
4、标程(可选)


目前HUSTOJ已经可以进行题目和测试数据的导出,只要您的平台�
��提供FPS接口，就能
使用所有FPS题库，并制作自己的题库与兄弟院校交流。

期待您的加入，让我们共同建设一个开源题库。

Original issue reported on code.google.com by [email protected] on 16 Apr 2010 at 3:07

solution submission front end

A submission page for coders to submit solutions to a problem

Original issue reported on code.google.com by [email protected] on 14 Jan 2010 at 6:51

User login feature

Implement a user login feature

Original issue reported on code.google.com by [email protected] on 8 Dec 2009 at 1:07

User-Problem Integration

Integrate the user model with the external problem model. The goal is to
have a running judge like the old one. (With contests from UVa and SPOJ).

Note: This is a major change and will be broken down to several issues

Original issue reported on code.google.com by [email protected] on 17 Jan 2010 at 5:30

Problem statement front end

A page for displaying the problem statement of a problem

Original issue reported on code.google.com by [email protected] on 14 Jan 2010 at 6:54

change user password

A user should be able to change his own password

Original issue reported on code.google.com by [email protected] on 12 Jan 2010 at 11:39

• Merged into: #14

redirect the user to verdict after submission

After submission a user is redirected to the main page. This is very
inconvenient, as the user will probably wish to see the result of their
submission. A redirect to a page containing the result is more intuitive.

Original issue reported on code.google.com by [email protected] on 26 Jan 2010 at 10:04

[deleted issue]

[deleted issue]

modify DjudgeProblem model

Need to modify the DjudgeProblem statement to have:
1- Time limit.
2- memory limit.
3- problem statement.
4- sample input.
5- sample output.

Original issue reported on code.google.com by [email protected] on 17 Jan 2010 at 12:34

Seperating the Submissions for the Djudge problems form other submissions

The submissions for the djudge problem should be seperated from the
existing submissions as it needs the source code file and it doesn't need a
judge ID.
This can be accomplished by modifying the problem model

Original issue reported on code.google.com by [email protected] on 17 Jan 2010 at 8:42

[deleted issue]

[deleted issue]

Users list

A list of registered users with statistics, rankings, etc...

Original issue reported on code.google.com by [email protected] on 20 Jan 2010 at 1:03

Require email address for users

The email address should be required and unique with the username/handle.

Original issue reported on code.google.com by [email protected] on 17 Jan 2010 at 1:21

djudge/db folder missing

It should be created and should contain the file 'db.dat' to be seen by
line 22 in settings file:
DATABASE_NAME = os.path.join(SITE_ROOT, 'db/db.dat')  

Original issue reported on code.google.com by [email protected] on 11 Dec 2009 at 3:48

Please review the user model and registration page

The user model is done, along with the registration page. Please review.

Original issue reported on code.google.com by [email protected] on 13 Dec 2009 at 2:13

Enlarging the text fields for the problem statement and the sample IO for Djudge problems

What steps will reproduce the problem?
1.  Log in to the judge
2.  Go to add problem
3.  Check the previous fields

What is the expected output? What do you see instead?

The expected output is bigger fields for specifying the problem statement
and its sample IO.

Later, it needs to be changed to accommodate the presence of pictures with
the problem.

Original issue reported on code.google.com by [email protected] on 17 Jan 2010 at 5:52

Atomizing the features

We are expected to atomize all the features and break it down to tasks. The
end result should be a list of issues on the issue tracker indicating what
to be done next.

Original issue reported on code.google.com by [email protected] on 6 Dec 2009 at 1:52