36d795f69c
As mentioned in commitbc0f04075, a <select> field which submits its form on change causes many accessibility and usability issues. In this case there was also an incompatibility with the advanced search filter which caused a bug solved in commit541a5fa89. So the question is where to position the filters and how to display them. One factor to take into the account is how relevant these filters are, particularly compared to the links to select the prefered order, since we don't usually give users the choice of both filters and orders. Our filters don't really make sense until the valuation phase starts, since before that phase investments aren't selected nor their feasibility is decided. After that phase, the only phase where citizens are really involved is the final voting; the rest of the phases are done by valuators and administrators. In the final voting, citizens can only vote on selected projects, and that's the default filter during that phase. So these filters are mainly there for information purposes, and not to help citizens in the phases where they're actually involved (accepting projects, selecting projects and balloting). Orders, on the other hand, play a crucial role during the final voting phase. Since citizens might have already voted for a few projects and have, let's say, 100,000€ left, ordering by price allows them to find which projects are within their remaining budget. In conclusion, orders are more important than filters, and so they should have a more prominent place. For consistency with the proposals section, where we've got some links in the sidebar (bottom part of the page on small screens) providing a similar funcionality, like accessing selected proposals or archived or retired proposals, we're moving the investments filters to the sidebar (bottom part of the page on small screens) as well.
CONSUL
Citizen Participation and Open Government Application
This is the opensource code repository of the eParticipation website CONSUL, originally developed for the Madrid City government eParticipation website
Documentation
Check the ongoing documentation at https://docs.consulproject.org to learn more about how to start your own CONSUL fork, install it, customize it and learn to use it from an administrator/maintainer perspective.
CONSUL Project main website
You can access the main website of the project at http://consulproject.org where you can find documentation about the use of the platform, videos, and links to the community space.
Configuration for development and test environments
NOTE: For more detailed instructions check the docs
Prerequisites: install git, Ruby 2.7.4, CMake, pkg-config, shared-mime-info, Node.js and PostgreSQL (>=9.5).
git clone https://github.com/consul/consul.git
cd consul
bundle install
cp config/database.yml.example config/database.yml
cp config/secrets.yml.example config/secrets.yml
bin/rake db:create
bin/rake db:migrate
bin/rake db:dev_seed
RAILS_ENV=test rake db:setup
Run the app locally:
bin/rails s
Run the tests with:
bin/rspec
You can use the default admin user from the seeds file:
user: admin@consul.dev pass: 12345678
But for some actions like voting, you will need a verified user, the seeds file also includes one:
user: verified@consul.dev pass: 12345678
Configuration for production environments
See installer
Current state
Development started on 2015 July 15th. Code was deployed to production on 2015 september 7th to decide.madrid.es. Since then new features are added often. You can take a look at the current features at the project's website and future features at the Roadmap and open issues list.
License
Code published under AFFERO GPL v3 (see LICENSE-AGPLv3.txt)
Contributions
See CONTRIBUTING.md