Difference between revisions of "Projects/Memopol/Roadmap"

From La Quadrature du Net
Jump to navigationJump to search
(Miscellaneous)
m
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Infobox Version|en=Projects/Memopol/Roadmap|fr=Projects/Memopol/Roadmap/fr}}
 
{{Infobox Version|en=Projects/Memopol/Roadmap|fr=Projects/Memopol/Roadmap/fr}}
  
This is the roadmap for the third version of the Memopol.
+
This is the roadmap for the third version of Memopol.
  
 
Each part can be worked on at the same time as each section is a small project in itself.
 
Each part can be worked on at the same time as each section is a small project in itself.
Line 37: Line 37:
 
* Global view of the MEP
 
* Global view of the MEP
 
* Global score
 
* Global score
** Update the scoring ( from a % to a absolute score )  
+
** Update the scoring ( from a % to an absolute score )  
** Systeme of badges / medales
+
** Systeme of awards / medals / achievments
 
* Public positions
 
* Public positions
** Work on the public positions ( how to get them and their presentation )
+
** Data structure / representation
*** Make a structure for the position ( under the form of a base/object )
+
*** Create a standard like the infobox on wikipedia which is easy to use and re-use (thinking... optional)
**** Create a standard like the infobox on wikipedia which is easy to use and re-use (thinking... optional)
+
*** Create a management of the notation associated to a position (thinking... optional)
**** Create a management of the notation associated to a position (thinking... optional)
+
** Moderation of a posted public positions
**** Moderation of a posted public positions
+
** Note (= score) the public positions (thinking... optional)
*** Note the public positions (thinking... optional)
+
** Importation
 
* Data visualisation
 
* Data visualisation
 
** Global score
 
** Global score
Line 57: Line 57:
 
Required skills : Python, Django, Database
 
Required skills : Python, Django, Database
  
* Make the search engine simpler yet powerfull  
+
* Make the search engine simpler yet powerfull (tips: [http://www.elasticsearch.org/ Elasticsearch] as a backend, use in conjonction with [http://www.elasticsearch.org/overview/kibana Kibana] for data visualisation)
 
* Filter the MEPs ( like in Dynamic filters within LibreOffice Calc)  
 
* Filter the MEPs ( like in Dynamic filters within LibreOffice Calc)  
 
* Get a list of user-case about filtering
 
* Get a list of user-case about filtering
Line 63: Line 63:
 
== Miscellaneous ==
 
== Miscellaneous ==
 
* Discuss the migration to Python 3 / Django 1.7
 
* Discuss the migration to Python 3 / Django 1.7
** Strong arguments for Python 2.7 with django 1.7
+
** '''Strong arguments for Python 2.7 with django 1.7 (migrations !)'''
 
* FAQ (skills: writing, design)
 
* FAQ (skills: writing, design)
 
** Make the website so easy the FAQ becomes useless ( with a small explanation next to the votes, etc... )
 
** Make the website so easy the FAQ becomes useless ( with a small explanation next to the votes, etc... )
Line 73: Line 73:
 
* '''make the install super easy !'''
 
* '''make the install super easy !'''
 
** Test the install (skills: not too much knowledge in Python/Django in order to have better feedback)
 
** Test the install (skills: not too much knowledge in Python/Django in order to have better feedback)
 +
 +
[[Category:Memopol]]

Latest revision as of 11:51, 16 August 2015


This is the roadmap for the third version of Memopol.

Each part can be worked on at the same time as each section is a small project in itself.

Urgent[edit]

Required skills : Administration

  • Take the current website offline - WIP
  • Create a link to access ML dev
  • Create a discussion on ML pour public discussions

Website Administration[edit]

Required skills : Django administration, Database,

  • Management of votes (updates, recommendations, etc...)
  • Management of MEPs (updates, adding trophies)
  • Management of public positions of the MEPs (moderation maybe here)
  • Management of decorations (Medals, Trophies, etc.. )

Home Page[edit]

Required skills : Design, Data visualisation

  • Complete redesign
  • Multiples entry points for each type of user
  • Display the informations on the home page
  • Make it clear and visible that each and everyone can help out by adding public positions

MEP's record[edit]

Required skills : Design, Data visualisation, Python, Django, Database

  • Global view of the MEP
  • Global score
    • Update the scoring ( from a % to an absolute score )
    • Systeme of awards / medals / achievments
  • Public positions
    • Data structure / representation
      • Create a standard like the infobox on wikipedia which is easy to use and re-use (thinking... optional)
      • Create a management of the notation associated to a position (thinking... optional)
    • Moderation of a posted public positions
    • Note (= score) the public positions (thinking... optional)
    • Importation
  • Data visualisation
    • Global score
    • Score in relation with the groupe, the MEPs...
    • Create graphs that are beautiful ( data viz )
    • Evolution of the position of a MEP
  • Widget easily re-usable somewhere else

Search Engine[edit]

Required skills : Python, Django, Database

  • Make the search engine simpler yet powerfull (tips: Elasticsearch as a backend, use in conjonction with Kibana for data visualisation)
  • Filter the MEPs ( like in Dynamic filters within LibreOffice Calc)
  • Get a list of user-case about filtering

Miscellaneous[edit]

  • Discuss the migration to Python 3 / Django 1.7
    • Strong arguments for Python 2.7 with django 1.7 (migrations !)
  • FAQ (skills: writing, design)
    • Make the website so easy the FAQ becomes useless ( with a small explanation next to the votes, etc... )
  • Api (skills: tastypie)
    • Re-usable data
    • representative format for people, datas, scores, etc...
  • Code testing (skills: Python, Django)
  • Document the code ( in the source and on the git ) (skills: writing)
  • make the install super easy !
    • Test the install (skills: not too much knowledge in Python/Django in order to have better feedback)