Skip to content
This repository

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Fix code that removes previously reviewed submissions from

the set of candidate submissions to review.
latest commit 70cbec04c8
Ed Gehringer efg authored April 15, 2014
Octocat-spinner-32 app Fix code that removes previously reviewed submissions from April 15, 2014
Octocat-spinner-32 config Use standard route for student_team/update April 03, 2014
Octocat-spinner-32 db Clean up foreign keys so that users can be deleted March 31, 2014
Octocat-spinner-32 doc routes.rb changed October 27, 2013
Octocat-spinner-32 features Attempt to fix travis build February 10, 2014
Octocat-spinner-32 lib Upgrade deprecated code February 17, 2014
Octocat-spinner-32 public Merge branch 'master' into e915 January 30, 2014
Octocat-spinner-32 script Merge branch 'master' into e907 January 06, 2014
Octocat-spinner-32 spec Remove failing tests February 10, 2014
Octocat-spinner-32 test E1402. Fix review strategies April 01, 2014
Octocat-spinner-32 vendor Decrease warnings, remove some failing tests February 10, 2014
Octocat-spinner-32 .coveralls.yml Add coveralls for code coverage January 06, 2014
Octocat-spinner-32 .gitignore Use the gitignore from master January 30, 2014
Octocat-spinner-32 .rspec Refactor content_pages_controller a bit and begin to test August 15, 2013
Octocat-spinner-32 .ruby-version Add a name specifier to a late_policies remove_index migration January 30, 2014
Octocat-spinner-32 .travis.yml Update the travis config script to copy the *.yml.example db file December 17, 2013
Octocat-spinner-32 Capfile routes.rb changed October 27, 2013
Octocat-spinner-32 Gemfile Remove redundant rspec-rails gems from gemfile February 10, 2014
Octocat-spinner-32 Gemfile.lock Update automated_metareview gem February 10, 2014
Octocat-spinner-32 Guardfile Decrease warnings, remove some failing tests February 10, 2014
Octocat-spinner-32 README Update README December 10, 2013
Octocat-spinner-32 README.md Update the code coverage badge to use the master branch. February 11, 2014
Octocat-spinner-32 Rakefile routes.rb changed October 27, 2013
Octocat-spinner-32 config.ru routes.rb changed October 27, 2013
Octocat-spinner-32 rails3_todo.txt Update deprecated ActiveRecord calls February 17, 2014
Octocat-spinner-32 tags Clean up foreign keys so that users can be deleted March 31, 2014
README.md

Expertiza

Build Status Code Climate Coverage Status

Peer review system

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities.

Setup

NCSU VCL image

The expertiza environment is already set up in NC State's VCL image "Ruby on Rails". If you have access, this is quickest way to get a development environment running for Expertiza. See the Expertiza wiki on developing Expertiza on the VCL.

Using the VCL is the quickest way to get started, but you may find it awkward developing on a remote machine with network lag and having to reinstall gems every time you connect. Installing locally can be a pain though too. Life is full of tradeoffs. :-) The good news is that you can start on one environment, push your work to git, and switch to another environment if you don't like the one you started with.

Installing locally

See the Expertiza wiki for setup instructions. Please update the wiki with corrections or additional helpful information.

Contributing

  • Fork the expertiza project
  • Create a new branch for your contribution with a descriptive name
  • Commit and push until you are happy with your contribution - follow the style guidelines below
  • Make sure to add tests for it; the tests should fail before your contribution/fix and pass afterward
  • Send a pull request to have your code reviewed for merging back into Expertiza

Style Guidelines

We've had many contributors in the past who have used a wide variety of ruby coding styles. It's a mess, and we're trying to unify it.

All new files/contributions should:

  • Use unix line endings (Windows users: configure git to use autocrlf)
  • Indent with 2 spaces (no tabs; configure your editor) both in ruby and erb
  • Follow the Ruby Style Guide style for syntax, formatting, and naming

When editing existing files:

  • Keep the existing tabbing (use tabs instead of spaces in files that already use tabs everywhere; otherwise use spaces)
  • Keep the existing line ending style (dos/unix)
  • Follow the Ruby style Guide on code you add or edit, as above

Please do no go crazy changing old code to match these guidelines; it will just create lots of potential merge conflicts. Applying style guidelines to code you add and modify is good enough. :-)

Something went wrong with that request. Please try again.