Post-Alignment Issues

[ehmatthes]

This is an issue to collect things that should be done after the alignment (#41) to the Great Schools Partnership model.

• [x] Schools need an owner?
• [ ] Identify and implement the first real milestone: using the project to manage competencies that will see actual use.
• [ ] Implement a full email-based registration system. This will allow password resets, and communication with people interested in the project.
• [ ] Include links to GSP documents. Include them in the project itself?
• [ ] Reach out to GSP. Make sure this is welcome; make sure no licensing issues.
  • Most of their work is clearly marked CC, I'm pretty sure this won't be an issue.
• [ ] Implement a more efficient data structure, such as MPTT. This should be a high priority, because it simplifies all subsequent work.
  • This may need to come before a more proper forking implementation?
• [x] Reevaluate whether "School" is the appropriate container for a set of standards. Could be "Organization". Could simply allow an alias for what kind of organization/ container user is representing.
• [x] Make a plan for improving test coverage. At this stage, there's value in working with the project before testing fully. But a baseline level of test coverage will become critical quickly.
• [ ] Update to Bootstrap 3.
• [ ] Further simplify homepage. The detailed discussions of the problems addressed by OC should be moved to separate pages.
• [ ] Update /docs directory.
• [x] Simplification: should there be a base class for taxonomy elements, pulling alias, description, etc.?
• [ ] Update urls.py to match 1.8 conventions.
• [ ] Revise helper functions in views.py.
  • Move to a separate module?
  • as the model gets refined and confirmed, it will be easier to settle on a small set of non-redundant helper functions
• [ ] Break sa_summary into overall summary page, and individual pages for the general subject area competencies, and subdiscipline area competencies?
• [ ] Test if user allowed to edit school should be a function.
• [ ] Function to get school for any given competency element.
• [ ] Links to delete elements. #121
• [ ] Can probably use one form to cover new_gs and new_sda_gs.
  • [ ] One template also. See docs.

[ehmatthes]

• [ ] Record history of each element.
  • [ ] Before updating a record, move the current text to a CompetencyAreaHx object.
  • [ ] Display link to hx for every element on the edit_sa_summary page. Links to a page showing the edit history for that element.
  • [ ] Link next to each entry to restore to that version.
• [ ] Allow order of elements to be modified. #126
• [ ] Only display edit link if user has permission to edit the school/ element.
• [ ] Create a sample school that's public, using existing gsp docs. #75
• [ ] Address grade level issues.
• [ ] Give the user a way to edit their profile.
• [x] Give users the ability to make their schools public.
• [x] Give school owners/ admins the ability to add users to their schools.
  • May want to give users the ability to request privileges for a school.
  • May want to give school owners/ admins the choice of making their school open to editing requests.
• [ ] Clean up register form.
  • [ ] Use bootstrap for forms.
  • [ ] Informational text is distracting.
  • [ ] Does it respond to errors appropriately?
• [ ] Any need to clarify the open licensing of the site's content, for contributors?

[ehmatthes]

• [x] Clean the codebase
  • [x] Remove unused pages from urls, views, and templates.
  • [x] Remove unused helper functions from views.py.
  • [x] Remove unused tests.
• [ ] Refactor
  • Focus on obvious refactors; this is a quick refactor to remove elements that will confuse potential contributors.
  • [ ] get_school() method on most models
  • [ ] some new helper functions
  • [x] migrate db to new taxonomy Sticking with original taxonomy, but allowing aliases
  • [ ] ca -> gs
  • [ ] eu -> pi
  • [ ] lt -> lo
• [x] Write initial tests.
  • Should be able to whip out a quick comprehensive test that establishes a baseline level of testing.
  • This should definitely come after cleaning the codebase and some obvious refactoring.
  • [x] Start a list of highest priority tests to write.