Projects/Memopol/Roadmap : Différence entre versions

De La Quadrature du Net
Aller à la navigationAller à la recherche
m
 
(28 révisions intermédiaires par 5 utilisateurs non affichées)
Ligne 1 : Ligne 1 :
 
{{Infobox Version|en=Projects/Memopol/Roadmap|fr=Projects/Memopol/Roadmap/fr}}
 
{{Infobox Version|en=Projects/Memopol/Roadmap|fr=Projects/Memopol/Roadmap/fr}}
  
= Roadmap =
+
This is the roadmap for the third version of Memopol.
  
Actually, a new version is in development mode. There are plenty of things to do. The idea is to make each main point a little workshop in order to make them open to everyone.
+
Each part can be worked on at the same time as each section is a small project in itself.
  
 +
== Urgent ==
  
 +
Required skills : Administration
  
== Interface design ==
+
* Take the current website offline - WIP
 +
* Create a link to access ML dev
 +
* Create a discussion on ML pour public discussions
  
First page is slow, shows no direct information, as some redundant access...
+
== Website Administration ==
  
 +
Required skills : Django administration, Database,
  
=== Eliminate useless pages/views ===
+
* 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.. )
  
* First tabs "Geographical Map" / "List of committees" / "Parliament hemicycle" should be deleted. Menus on top permit the same access.
+
== Home Page ==
* The map should be kept but modified in order to be faster to load and show direct information (average score of each countries)
 
  
 +
Required skills : Design, Data visualisation
  
=== Modify pages ===
+
* 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
  
* Search bar should be put on top in order to let room to more important information
+
== MEP's record ==
* Scores tab of each MEP shows a complex image. Should be simpler. Plus, this image is recalculated each time shown. Should be cacheable.
 
* CV tab for each MEP is not always formated. Try to get this page more easy to read.
 
  
=== Show score of each "scorable object" ===
+
Required skills : Design, Data visualisation, Python, Django, Database
  
Each "scorable object" should have a score :
+
* Global view of the MEP
* Committee
+
* Global score
* MEP
+
** Update the scoring ( from a % to an absolute score )
* Country
+
** Systeme of awards / medals / achievments
* Political Group
+
* Public positions
* National party
+
** 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 ==
  
=== Make the score more understandable, easy to read ===
+
Required skills : Python, Django, Database
  
An infinite debate about score is always on. You could discuss about it or try to make a mock-up of what you would like it to be...
+
* 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)
 +
* Get a list of user-case about filtering
  
 +
== Miscellaneous ==
 +
* 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)
  
=== Use some sort of medals/trophies to show best/worse MEPs ===
+
[[Category:Memopol]]
 
 
Some kind of trophies or medals could be obtained by MEPs when they do something very good (or very bad).
 
 
 
 
 
=== Show trend based on latest votes ===
 
 
 
A trend should be shown for the latest votes in order to be able to see what direction the MEP/Country/Political group/Committee is taking
 
 
 
 
 
 
 
==  Optimize / Accelerate loading ==
 
 
 
 
 
=== The map ===
 
 
 
Actual map is heavy and tends to make first page slow. Changing it is mandatory.
 
 
 
 
 
=== List of MEPs ===
 
 
 
List of MEPs could be very long. A quick search in it with some Ctrl+F is usefull, but as the list is slow to load, the loading has been cut into endless loading, making the Ctrl+F research impossible.
 
 
 
List of MEPs should be faster in order to avoid this.
 
 
 
 
 
 
 
== Show important information in priority ==
 
 
 
 
 
=== The map ===
 
 
 
It must show some information about countries scoring: average score of each country's MEP.
 
 
 
 
 
=== Each MEP must have their important information on the first tab ===
 
 
 
* On the MEP's profile, the badge should be reduced
 
* Contact informations should be moved on a Contact tab
 
* Public positions should be directly visibles (anchor name in order to let other websites link to them)
 
 
 
 
 
 
 
== Simplify the search engine ==
 
 
 
 
 
=== Looooong urls ===
 
 
 
Some simple requests can create too much long URL in return => impossible to re-use/distribute them easily
 
 
 
 
 
=== Use simple filters ===
 
 
 
Be able to use filters should improve the use of the List of MEPs.
 
 
 
 
 
 
 
== Test ==
 
 
 
Tests are actually just a little part of Memopol, making it "not 100% stable". If you like to write tests and/or break code, you should add some in our actual tests.
 
 
 
 
 
 
 
 
 
== Clearly separate and standardize different parts of Memopol ==
 
 
 
This huge work is actually in Bram's hand. You are more than welcome to help him :
 
 
 
* Memopol-core => Main part of Memopol, linking all other parts of it in one usable piece
 
* Memopol-representative => Standardisation of the datas of each representative of a parliament (European, Italian, French, etc...)
 
* Memopol-XX => Where XX represents a parliament
 
 
 
 
 
 
 
== Other possible things not clear at the moment ==
 
 
 
* Easiest translation for admins
 
* Easiest transaltion for users => flag to click
 
* Global comprehension: Visitors are not lawyers or specialists
 
* Data porn: free our datas in a reasonable way (csv, database dump, etc...)
 
* FAQ: every one can have questions (scoring explication could be a good point too)
 
* CSV (and other formats) export for Data love
 

Version actuelle datée du 16 août 2015 à 10:51


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[modifier]

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[modifier]

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[modifier]

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[modifier]

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[modifier]

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[modifier]

  • 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)