Forges » History » Version 7
Denis 'GNUtoo' Carikli, 04/07/2020 05:00 PM
| 1 | 1 | Denis 'GNUtoo' Carikli | h1. Forges |
|---|---|---|---|
| 2 | |||
| 3 | 5 | Denis 'GNUtoo' Carikli | h2. Requirements |
| 4 | 1 | Denis 'GNUtoo' Carikli | |
| 5 | 5 | Denis 'GNUtoo' Carikli | * Fully free software |
| 6 | * Low resource usage |
||
| 7 | * Javascript requirements: |
||
| 8 | ** Friendly upstream that could accept patches to make all features work without JavaScript |
||
| 9 | ** If possible don't depend on JavaScript |
||
| 10 | ** if possible the JavaScript has to be compatible with LibreJS |
||
| 11 | * Workflow requirements: |
||
| 12 | ** Have the ability to tell users about sending patches to the mailing list |
||
| 13 | ** Friendly upstream that can accept patches for integrating it with a mailing based workflow. |
||
| 14 | 7 | Denis 'GNUtoo' Carikli | * Have it packaged in a distribution we can use in the FSF VMs to reduce maintenance cost |
| 15 | 5 | Denis 'GNUtoo' Carikli | |
| 16 | h2. Possible forges |
||
| 17 | |||
| 18 | h3. Gitlab |
||
| 19 | |||
| 20 | 3 | Denis 'GNUtoo' Carikli | It has some big dependency on Javascript, |
| 21 | from our FOSDEM 2020 report that is not yet released: |
||
| 22 | <pre> |
||
| 23 | They used a framework that did most of the work on the server side, |
||
| 24 | but at some point they switched to a framework that does JavaScript |
||
| 25 | on the client side. |
||
| 26 | |||
| 27 | Accepting patches to fix that would require to double the UI work for |
||
| 28 | everything, but it might be possible to do server side rendering for |
||
| 29 | JavaScript. The issue is that it cannot make requests from buttons |
||
| 30 | like that, so in addition to the page rendering that could happen |
||
| 31 | through server-side JavaScript, introspection could be used to |
||
| 32 | rewrite the buttons. |
||
| 33 | </pre> |
||
| 34 | |||
| 35 | It also hide buttons, which is awful for users as they don't understand what is going on. |
||
| 36 | |||
| 37 | 1 | Denis 'GNUtoo' Carikli | Packages: ? |
| 38 | 3 | Denis 'GNUtoo' Carikli | |
| 39 | 5 | Denis 'GNUtoo' Carikli | h3. Pargure |
| 40 | 1 | Denis 'GNUtoo' Carikli | |
| 41 | *Website*: https://pagure.io/pagure |
||
| 42 | *Command line tools* : https://pagure.io/pag-off |
||
| 43 | |||
| 44 | Features: |
||
| 45 | * "The buttons seem to be greyed out when they cannot be used":https://pagure.io/pagure/pull-request/4786 This is much better than Gitlab where the buttons like "Send pull request" completely disappear if the feature is deactivated. Having button like that disappearing is really bad as users struggle to understand what they are doing wrong and can't contribute, when in fact the feature is simply deactivated without any way that shows it. |
||
| 46 | 3 | Denis 'GNUtoo' Carikli | * It's compatible with LibreJS but still requires JavaScript for some functionalities. Upstream seem friendly and is probably very interested in getting patches to make it possible to enable to use all features without any JavaScript. For that the few features that depends on it would need to be modified to work without Javascript as well. |
| 47 | 1 | Denis 'GNUtoo' Carikli | * There is some interest in bridging a mailing based workflow to pargure: https://pagure.io/pagure/issue/15 |
| 48 | 3 | Denis 'GNUtoo' Carikli | |
| 49 | 6 | Denis 'GNUtoo' Carikli | Packages: "currently packaged in Debian SID":https://packages.debian.org/sid/pagure, in "a PPA":https://packages.ubuntu.com/focal/pagure, might be packaged in other distributions |
| 50 | 3 | Denis 'GNUtoo' Carikli | |
| 51 | Contacts: #pagure on Freenode and/orthe pagure-devel@lists.pagure.io mailing list |