GSoC 2015 - Interface Improvements to CritiqueBrainz

Hello everyone,

I am planning to apply for the CritiqueBrainz GSoC task this year.

I've picked out a few things that'll be a part of my proposal:


Moderation Interface (CB-157)
-----------------------------

Reviews can be reported currently but there's no way of taking any action on
those reports, so we'll have to create a UI (that'll only be visible to
moderators) where from the reviews can be hidden or removed.

A user posts a review, someone else reports it. A moderator logs in  
(how will
the mods be decided?), goes to the reports page and takes one  of the
following actions:

Hide:   The review will not be visible to anyone and the author will be
         notified of it. The author can then edit the review to remove any
         problems with it. After the edit, a moderator will have to 
'pass' the
         review for it to visible again.

Delete: The review will be removed and the author will be notified.


UI For Revisions (CB-29)
------------------------

A new revision is created for every edit of a review, but there's no UI for
viewing older revisions. So this will involve creating a UI similar to
Mediawiki's History page that'll list past revisions (their votes etc) and
will also allow the authors to revert back to an older version.


Markdown Editor (CB-95)
-----------------------

Adding a WYSIWYG editor will help those new to Markdown write better 
reviews.
I found this plugin: http://www.codingdrama.com/bootstrap-markdown/ and we
can easily modify it to suit our needs.


Embedded Players
----------------

CB-152 - Add other embedded players (Bandcamp, Soundcloud, others?) for
releases that are linked to them.

CB-146 - Add a player on the 'Write Review' page as people might be 
interested
in listening to the song while they're reviewing them.

CB-135 - Add a user preference for region of spotify player.


Sort Order
----------

CB-126 - Sort reviews by popularity on release group page.

CB-80 - Albums have no discernible sort orders.

Add multiple 'Sort By' options to these pages.


The problem is that all these tasks combined are still not big enough to be
considered for the three month GSoC period. I could add other issues 
into the
list like CB-80, CB-36, CB-120, CB-123 but that won't really make much
difference as all these issues are quite trivial.

I could also try adding more MB entites, but am not too sure about which of
those would make sense as a part of CB. 'Label', 'Recording' and 'Events'?

Does anyone have other ideas in mind?

-

dufferZafar