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.
JavaScript Ruby CSS HTML
Latest commit b04ba86 Sep 24, 2016 @Winbobob Winbobob Show review submissions.
Failed to load latest commit information.
app Show review submissions. Sep 24, 2016
bin Add the Rails 4 bin directory Dec 15, 2014
config add bidding functionality and ui Sep 23, 2016
db Add 'grade_for_reviewer' and 'comment_for_reviewer' to 'participants'… Sep 12, 2016
doc routes.rb changed Oct 27, 2013
hooks Add pre-commit git hook: Aug 7, 2016
lib Refactoring Changes from local repo Mar 21, 2016
public Remove addElement May 10, 2016
spec Move spec/has_paper_trail_spec.rb -> spec/models/has_paper_trail_spec… Sep 15, 2016
vendor Remove graphviz from vendor/plugins. Sep 17, 2016
.bowerrc Update jQuery-UI, using Bower for Bootstrap rather than Gem Jul 23, 2015
.codeclimate.yml Update .codeclimate.yml Jul 10, 2016
.coveralls.yml Add coveralls for code coverage Jan 6, 2014
.gitignore Update .gitignore to ignore javascript downloaded by bower. Sep 18, 2016
.rspec Reverting changes to make the build pass Mar 29, 2016
.rubocop.yml Update course and class length restrictions in rubocop.yml Jul 10, 2016
.travis.yml Update .travis.yml Sep 17, 2016
Capfile Use Rubocop to do auto-correction. Jun 11, 2016
Gemfile 'hoptoad_notifier' is deprecated, use 'airbrake' instead. Sep 15, 2016
Gemfile.lock 'hoptoad_notifier' is deprecated, use 'airbrake' instead. Sep 15, 2016
Guardfile Use Rubocop to do auto-correction. Jun 11, 2016 Update Aug 10, 2016
Rakefile routes.rb changed Oct 27, 2013
bower.json Change jquery verion for compatiable reason. Sep 22, 2016 Use Rubocop to do auto-correction. Jun 11, 2016
prototype.js Integrated React.js into Rails, remove prototype.js Jun 8, 2015


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.


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.


  • 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. :-)