Postponing UI design for August 31st.
diff --git a/MelangePlan0310.wiki b/MelangePlan0310.wiki index 7592585..1aa8992 100644 --- a/MelangePlan0310.wiki +++ b/MelangePlan0310.wiki
@@ -10,11 +10,11 @@ * Testing, Sverre suggesting getting more time for it. Chong Liu's work should help. || *Short Name* || *Description* || *Schelduled* || *Priority* || *Primary Contributors* || -|| Design UI Prototypes || Design and prototype new UI designs for Melange || 16 August || High || Mario Ferraro || +|| Design UI Prototypes || Design and prototype new UI designs for Melange || 31 August || High || Mario Ferraro || || User Interface Discussion || Discussion and choosing of the new interface || 6 September || High || All || || User Interface Implementation|| Implementation of the new user interface. || TBD || High || || ||Internal User ID as a reference||Currently, we use email address as user ID, but then if that changes we don't have a correct reference to the user anymore and we have to fix things manually. This means to update current user models in the datastore and changing the current calls to getUserForCurrentAccount to work with the ID|| ||Medium|||| -|| JavaScript Refactoring || Refactor Melange JavaScripts to their separate module. || TBD || Medium || Mario || +|| JavaScript Refactoring || Refactor Melange JavaScripts to their separate module. || TBD || Medium || Mario Ferraro || ||Per Org URL for Applying||The current StudentApplication uses the student as scope. This gives non-shareable URL’s for organizations to apply on. Unless changing the datamodel to become based around Orgs becomes viable for GSoC10 (a lot of dependencies with access and accepting/rejecting applications), a good solution would also be to introduce a URL that is not user-dependent but Organization dependent.|| ||Low|| || ||Use HTTPS protocol for certain pages||This means enabling HTTPS for a certain set of pages such as edit pages for roles. See also Issue 445.|| ||Low|| || ||Enhance Notifications||This includes posting the complete notification in the email sent to the user and perhaps add the possibility to read them using an RSS feed (NewsFeed framework from James Levy)|| ||Low|| || @@ -31,4 +31,4 @@ || GHOP Task workflow || Run the current workflow from the point that a task is published till the completion of a Task. Includes, allowing uploads to be made as part of a WorkSubmission, checking access to make sure that a mentor/org admin can't claim a task and someone who has claimed a task or is a Student can't become a Org Admin/Mentor. || TBD || High || TBD || || GHOP statistics || Page to gather GHOP Statistics, might make use of the work from Mario and Daniel. Most importantly we need to know who completed what amount of tasks on a overall and per-org basis.|| TBD || High || TBD || || GHOP Task pages || Besides the per-task page there are a few more important pages to be checked/fixed/implemented. Namely the org home page with a lists of their tasks, a page with all tasks for a single program and a page for listing "My tasks" showing either the ones you have claimed or are mentoring. || TBD || High || TBD || -|| GHOP Testing period || Similar to the GSoC testing period we will run GHOP through its paces publicly during this time. || TBD || High || TBD || +|| GHOP Testing period || Similar to the GSoC testing period we will run GHOP through its paces publicly during this time. || TBD || High || TBD || \ No newline at end of file