Using Django's auth views and maybe Class Based Views equivalents if you can find good ones, implement the views for :

• User creation by the admin, providing the e-mail of the user, who will received an e-mail with a link to create their password
• Activation - deactivation of Singer profile
• Lost password management
• Custom user model with all the needed info ? (if necessary)

Mainly, test what the Poireau Notebook does.

Also, test that loading the pages when logged out (except Login page) redirects to login.

• Allow basic instruments (piano, ...), but also percussions to work on the rythm
• Allow tempo modification
• Allow relative volume modification between parts.

We could generate a "Learning package" with exercises : The song with your voice, the song with your voice and the other voices lower, the "normal" song, the song without your voice, the song with holes and you're supposed to continue alone for ten seconds etc.

If you specify some measures you want to work specifically, you may generate a loop of n times theses measures specifically.

Find a way to set the volume independently for each part in the generated sound file. That may be by editing the musicxml and making sure it is taken into account by musicxml2ly. Another lead is to see if it's possible to do it from the .ly file. Finally, maybe it's doable from the generated midi file.

We may attach a property ("volume") on xml_parts in Song, and Song.export may use it to set the volume properly at export time.

Then we'll be able to generate songs with all but one part with a lower volume.

This is the only editable thing in Part. It's logical to edit all the sections for all the parts in a Song simultaneously. A little bit of logic could help providing a default section for a part from its name ("Bass" usually is linked to Bass ...). We could examine all other parts named identically and if they're always linked to the same section, this should be the default choice.

This feature allows users to create and manage surveys for all users of one or several given "main section"

This feature contains:

• A view to list all the existing surveys (with links to each survey, and a link to create a new survey)
• A view to create, modify or delete a survey
• A view to answer the survey, update an answer and see the responses of all the participants
• A script to remind regularly the users until they have answered the survey

The method is already there but it should be made into a View with 2 steps :

• See all the changes that will be done
• Validate and do the changes

In order to do that, the discover method has an argument commit. If false, nothing is changed, but the return value helps figuring out what changes will be done, and then if commit= True, changes are made.

Create basic ModelForms and Views for Detail, Creation, List, Update (and Deletion when applicable ?) for :

• Songs
• Parts
• Singers
• Sections

Some highly specialized views like Auto-Song Creation from Dropbox exploration or assignement of singers to their parts in songs will be done in their own ticket. This is for the simple views.

Idea : use Selectize to improve display of ChoiceFields.

Create the base HTML template for the views.

Using Bootstrap 3 (and Django Bootstrap 3), create a html file in common/templates/base.html that will be the base for all (or most) pages. This invloves choosing how the menu will appear etc.

Currently, Lylipond creates a .midi file from the .xml. The midi file defines notes, but has to be associated with instruments to create a real sound. On method is to use FluidSynth in association with a SoundFont (sf2) file. Try different methods (ideally using a python library, and if not possible, using a executable in python) to implement this in the Song.export method (that may need refinement in terms of defining its inputs and outputs).

We could generate an mp3 file on the server or generate a midi and play it through midi.js or use vecFlow (which would also let us show the partition) or...?

2 views :

• From a Singer : for each song, specifies his/her parts (useful when adding a new member)
• From a Song : for each singer, specifies their parts (useful when adding a new song)

Default choices can be inferred via part.section and singer.main_section

A way for users to sugest new songs to work on. Features include :

• Anyone (logged) can add a new suggestion and edit their suggestions
• Anyone can comment any suggestion (not anonymously)
• Anyone can vote +1 or -1 or 0 on any song. This is anonymous but we keep track of user's votes. Yes, the admin may know who voted for what but it's ok.
• The only votes considered are those of active users.
• The total (sum of 0, +1 and -1) on each song is displayed. Songs are sorted by tuple (DidIAlreadyVoteForThat, score (desc)),
• Voting is done through an ajax call to enable quick voting
• A suggestion is composed of :
  • The name of the song
  • The person who suggested it
  • the date of suggestion
  • Up to 3 youtube videos embedded, with suggestion of having the original song, the most interesting performance they can find and, if it exists an arrangement for choir or something.
  • A free (markdowned) text box for the rest
  • and the score and the voting panel (something like this : http://getbootstrap.com/components/#btn-groups-sizing)
• Optionnal : when voted, a suggestion moves to the bottom part of the list

Each user is able to say how much they master a given song (I don't sing it / I don't know it / I know it / I master it). In the song list, songs are sorted with the ones that need the more work first.

Could use this : https://github.com/janslow/gandi-mail-forwarders-cli or Gandi's api directly