ogptoolbox-ui issueshttps://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues2017-05-11T17:08:26Zhttps://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/111Arguments on items deletion2017-05-11T17:08:26ZJohan RicherArguments on items deletionEnable users to argument on item pages in order to delete them (or hide them from search results). Kind of a 'meta-argument': basically the same feature as #92 but on item pages instead of the items themselves. In terms of UX it could be...Enable users to argument on item pages in order to delete them (or hide them from search results). Kind of a 'meta-argument': basically the same feature as #92 but on item pages instead of the items themselves. In terms of UX it could be a Trash/Signal/Alert button that would open a modal window to argument on the deletion, with vote. The vote would impact the score of the item (same as with regular arguments), under 0 the item would be hidden/deleted.
Would be a solution for #110.https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/110To Delete: Spam disguised as Tool2017-05-11T17:01:29ZJohan RicherTo Delete: Spam disguised as Toolhttps://ogptoolbox.org/en/tools/48949https://ogptoolbox.org/en/tools/48949https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/108Consider "Use case" as a relation rather than a property2017-05-02T12:30:55ZJohan RicherConsider "Use case" as a relation rather than a propertyhttps://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/107Duplicate items created if Publish button is clicked twice in rapid succession2017-04-30T22:48:48ZJohan RicherDuplicate items created if Publish button is clicked twice in rapid successionWhen publishing an item (e.g. a tool) with a big image file to upload, the lag can lead the user to click a second time (or more) on the Publish button.
Example:
https://ogptoolbox.org/tools/48508
https://ogptoolbox.org/tools/48509When publishing an item (e.g. a tool) with a big image file to upload, the lag can lead the user to click a second time (or more) on the Publish button.
Example:
https://ogptoolbox.org/tools/48508
https://ogptoolbox.org/tools/48509https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/106Use case not displayed2017-04-30T16:25:58ZJohan RicherUse case not displayedAfter editing an item from 'Platform' to 'Use case', the item is not displayed on the corresponding tool's page.
Use case: https://ogptoolbox.org/en/use-cases/3753
Tool: https://ogptoolbox.org/en/tools/4188
(Related to issue #104)After editing an item from 'Platform' to 'Use case', the item is not displayed on the corresponding tool's page.
Use case: https://ogptoolbox.org/en/use-cases/3753
Tool: https://ogptoolbox.org/en/tools/4188
(Related to issue #104)https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/105Improve security score at Mozilla Observatory2017-04-17T15:47:45ZEmmanuel RaviartImprove security score at Mozilla Observatoryhttps://observatory.mozilla.org/analyze.html?host=ogptoolbox.org
Scan summary: **F**
## Recommended Change
Fantastic work using HTTPS! Did you know that you can ensure users never visit your site over HTTP accidentally?
HTTP Strict T...https://observatory.mozilla.org/analyze.html?host=ogptoolbox.org
Scan summary: **F**
## Recommended Change
Fantastic work using HTTPS! Did you know that you can ensure users never visit your site over HTTP accidentally?
HTTP Strict Transport Security tells web browsers to only access your site over HTTPS in the future, even if the user attempts to visit over HTTP or clicks an http:// link.https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/104Types edition is too complex and too permissive2017-04-30T16:25:58ZEmmanuel RaviartTypes edition is too complex and too permissiveWhen editing an existing card, the only way to edit its sub-types is to go to "Additional information" and edit "Types". This is the first problem: Types should have a more visible "edit" button.
The second problem, is that when editing...When editing an existing card, the only way to edit its sub-types is to go to "Additional information" and edit "Types". This is the first problem: Types should have a more visible "edit" button.
The second problem, is that when editing types, the values are not constrained. For example, see #103https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/101Revamping item pages2017-04-08T23:01:14ZJohan RicherRevamping item pages*Related to: [Revamping forms for item creation](https://framagit.org/ogptoolbox/ogptoolbox-ui/issues/100)*
Starting with a brainstorm: **what should be displayed on a page?** (e.g. the page describing a tool: http://ogptoolbox.org/e...*Related to: [Revamping forms for item creation](https://framagit.org/ogptoolbox/ogptoolbox-ui/issues/100)*
Starting with a brainstorm: **what should be displayed on a page?** (e.g. the page describing a tool: http://ogptoolbox.org/en/tools/47330).
## Questions
* What kind of users do we want to satisfy?
* Which informations have priority?
* How to display the wealth of data that we have without overwhelming the user?
## Ideas/propositions
* Add list of clients with clickable URLs (using information stored in **Client_Web**, **Client_Android**, **Client_iOS**, etc.). Could be part of the 'Use it' button UI [discussed here](https://framagit.org/ogptoolbox/ogptoolbox-ui/issues/98).
* List of **Tags**: [discussion here](https://framagit.org/ogptoolbox/ogptoolbox-ui/issues/57).
* Used for / Used by: [discussion here](https://framagit.org/ogptoolbox/ogptoolbox-ui/issues/80)
* Use cases: [Display the geographic location](https://framagit.org/ogptoolbox/ogptoolbox-ui/issues/93)https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/100Revamping forms for item creation2017-05-25T18:23:14ZJohan RicherRevamping forms for item creation*Related to: [Revamping item pages](https://framagit.org/ogptoolbox/ogptoolbox-ui/issues/101)*
## Current forms:
* [New Tool](http://ogptoolbox.org/en/tools/new)
* [New Use case](http://ogptoolbox.org/en/use-cases/new)
* [New Orga...*Related to: [Revamping item pages](https://framagit.org/ogptoolbox/ogptoolbox-ui/issues/101)*
## Current forms:
* [New Tool](http://ogptoolbox.org/en/tools/new)
* [New Use case](http://ogptoolbox.org/en/use-cases/new)
* [New Organization](http://ogptoolbox.org/en/organizations/new)
* [New Collection](http://ogptoolbox.org/en/collections/new)
## Important:
Each field should have a placeholder to disambiguate its purpose, i.e. what information should be entered.
## Issues/Propositions:
### New Tool
* Users should be allowed to add fields on the fly, in a similar manner to the field editing UI which is available once the item is created.
* Fields that should be on the form by default: **Tags**, **Languages**, **SourceCode** (repository; software only), **help** (help/FAQ/documentation page ), **Client** (supported operating systems), **additionalURL**
* Maybe default fields: **Screenshot**, **Twitter** (might be useful for later Retruco features...), **Facebook**, **EmailContact**, **Start** (first launch/release date)
* Field **License** doesn't seem to work. Information entered here doesn't appear on the item page.
* **Publisher** is not currently a used field; should be replaced by **Developer** (software) and **Provider** (platform).
* **Download link** and **Release date** are not priority information, should be at least moved down the form or added by the user on the fly if desired.
* List of fields should change depending on type (software or platform). E.g. **License** should only appear when 'software' is selected.
### New Use case
* UI should take inspiration from the 'New Collection' form which is a more recent iteration
* Fields that should be on the form by default: **tags**, **Organization** (the one offering the tool to the end user), **Partner** (if applicable, organization helping to make the use case possible, e.g. councelling agency), **Tool(s)**, **User type** (the type of final user(s) using the tool(s) that the use case is describing), **Location** (City/Country/International), **Start** / **Stop** (dates), **additionalURL** (more information, could be a press article)
### New Organization
* Fields that should be on the form by default: **Tags**, **Logo**, **Type** (Non-profit organization, Company, Institution [Local/Regional/National/International])
--------
# Useful resources
- https://framacalc.org/ogptoolbox_tool
- https://framacalc.org/ogptoolbox_outilhttps://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/99Add Mastodon button2017-04-07T13:52:01ZEmmanuel RaviartAdd Mastodon buttonAnother social button...Another social button...https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/98List of instances2017-04-08T20:07:51ZJohan RicherList of instances**Problem**: Self-hosting open source software is difficult. In many cases it's not necessary when free and mutualized instances exist. But how to find them?
**Solution**: With the OGP Toolbox, find the open source software you need, ...**Problem**: Self-hosting open source software is difficult. In many cases it's not necessary when free and mutualized instances exist. But how to find them?
**Solution**: With the OGP Toolbox, find the open source software you need, on its page click "Use it" to get a list of instances/services running the code. Choose one and just use it. VoilĂ !
Instances could be stored as URLs, using a new "instance" field for 'software' items ([tested here](http://ogptoolbox.org/en/tools/47065), under "Additional information").
This solution is not perfect:
* Some instances can be more popular than the software they're based on (e.g. Framasoft services). With this solution, services based on open source software wouldn't have their own page on the OGP Toolbox. They wouldn't exist as "tools" but as instances of a tool. Users will not be able to find them, causing frustration and confusion.
* Sometimes the difference between "use case" and "instance" will be unclear.https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/93Display the geographic location of a use case2017-04-08T23:01:14ZJohan RicherDisplay the geographic location of a use caseSince it's an important contextual information, the Toolbox should highlight the location on a use case's page (using the available "location" field: country, city, region, depending on the use case).
Example: http://ogptoolbox.org/us...Since it's an important contextual information, the Toolbox should highlight the location on a use case's page (using the available "location" field: country, city, region, depending on the use case).
Example: http://ogptoolbox.org/use-cases/45941
Location: United Kingdomhttps://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/92Arguments2017-05-11T17:01:29ZJohan RicherArgumentsEnable users to post arguments (pros / cons) on each tool, as well as vote on them. This dynamic will have an effect on the score of the tool, and thus on the default ranking where applicable (e.g. homepage).
Arguments will be integra...Enable users to post arguments (pros / cons) on each tool, as well as vote on them. This dynamic will have an effect on the score of the tool, and thus on the default ranking where applicable (e.g. homepage).
Arguments will be integrated directly in the Toolbox UI, as part of the description on a tool's page.
The **Arguments** feature will use the **Retruco engine** ([API](https://framagit.org/retruco/retruco-api)), a generic debating tool which focus on the complete expression of arguments and counter-arguments. As part of the Toolbox, an overview/summary of the arguments will be displayed on the tool's page, while the complete mapping of the arguments will be located on Retruco's own separate platform and UI.
Beside making arguments, users will be able to vote on arguments.
**Bots** will make it possible to mass-vote, as long as they respect terms and conditions that will be defined iteratively to avoid abuse. This mechanism will open the possibility for users to vote automatically on arguments related to specific aspects they want to promote (such as FOSS).2017-04https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/91Advanced search2017-03-31T18:18:52ZJohan RicherAdvanced searchEnable users to filter through fields (i.e. tool properties: language, OS, license, etc.) to find specific tools. The same will be possible for use cases and organizations...Enable users to filter through fields (i.e. tool properties: language, OS, license, etc.) to find specific tools. The same will be possible for use cases and organizations...2017-04https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/89Duplicate tags2017-07-20T18:11:17ZJohan RicherDuplicate tags1) Tags for tools and use cases with same label should have the same ID.
Example: currently, tag "budgeting" has two different IDs, making it a duplicate.
2) Tags shouldn't be case sensitive.
Example: [collaborative text editing...1) Tags for tools and use cases with same label should have the same ID.
Example: currently, tag "budgeting" has two different IDs, making it a duplicate.
2) Tags shouldn't be case sensitive.
Example: [collaborative text editing](https://ogptoolbox.org/en/tools/?tagIds=46007) and [Collaborative text editing](https://ogptoolbox.org/en/tools/?tagIds=16861)
"Watchdogging"2017-03Emmanuel RaviartEmmanuel Raviarthttps://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/81Page title and SEO2017-07-20T18:11:17ZJohan RicherPage title and SEOCurrently search engines (e.g. Google) show problems with page titles:
![bugusecase](/uploads/99ee83ec9aa11cc73508241a3bffff27/bugusecase.png)
https://www.google.fr/search?q=participez+nanterre+ogp+toolboxCurrently search engines (e.g. Google) show problems with page titles:
![bugusecase](/uploads/99ee83ec9aa11cc73508241a3bffff27/bugusecase.png)
https://www.google.fr/search?q=participez+nanterre+ogp+toolboxhttps://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/80"Used by"2017-07-20T18:11:17ZJohan Richer"Used by"Currently, a Use case page shows a list of organizations under the "Used by" title
(Example: http://ogptoolbox.org/en/use-cases/45219)
I see two problems to this:
1. The wording is not satisfactory because a Use case is not "used...Currently, a Use case page shows a list of organizations under the "Used by" title
(Example: http://ogptoolbox.org/en/use-cases/45219)
I see two problems to this:
1. The wording is not satisfactory because a Use case is not "used" (unlike a Tool). The title of each list should reflect the type of items on the list (Tool / Use case / Organization).
2. The list includes organizations which do not necessarily use the tool, such as Developer organizations2017-03https://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/79Create SQL dumps for open data2017-03-31T18:18:52ZEmmanuel RaviartCreate SQL dumps for open dataRemove names, password hash & salt.Remove names, password hash & salt.2017-03Emmanuel RaviartEmmanuel Raviarthttps://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/77Notify changes using Matrix/Synapse2017-03-31T18:18:54ZEmmanuel RaviartNotify changes using Matrix/Synapse2017-03Emmanuel RaviartEmmanuel Raviarthttps://framagit.org/ogptoolbox/ogptoolbox-ui/-/issues/76Similar tools2017-03-31T18:18:52ZEmmanuel RaviartSimilar toolsAdd "Similar tools" block to the left part of each tool.Add "Similar tools" block to the left part of each tool.2017-03Emmanuel RaviartEmmanuel Raviart