dev:2017_new_tools
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
dev:2017_new_tools [2018/02/17 07:43] – [GitLab] dyrcona | dev:2017_new_tools [2023/06/22 09:09] – [Con] dyrcona | ||
---|---|---|---|
Line 20: | Line 20: | ||
* The API is hard to use, particularly for command-line applications | * The API is hard to use, particularly for command-line applications | ||
* LP has timeout errors rather more often than one would like | * LP has timeout errors rather more often than one would like | ||
- | * No direct links from the bugs to the commits fixing them. | + | * No direct links from the bugs to the commits fixing them (or viceversa, i.e a "fix bug 123" commit message links LP123 with that branch). |
* Bug search is limited, even with advanced search. | * Bug search is limited, even with advanced search. | ||
* There' | * There' | ||
* There' | * There' | ||
+ | |||
+ | === Huge list of software options out there OSS or not === | ||
+ | * https:// | ||
+ | |||
==== Gitolite ==== | ==== Gitolite ==== | ||
Line 66: | Line 70: | ||
* Ability to report or comment on bugs without requiring a user account | * Ability to report or comment on bugs without requiring a user account | ||
+ | * Better reporting of statistics than is currently available via Launchpad API | ||
===== Options ===== | ===== Options ===== | ||
==== GitHub ==== | ==== GitHub ==== | ||
+ | |||
+ | === Notes === | ||
+ | |||
+ | Options for transitioning from Launchpad to Github: | ||
=== Pro === | === Pro === | ||
Line 76: | Line 85: | ||
* Already being used by DIG for gists. | * Already being used by DIG for gists. | ||
* " | * " | ||
+ | * We can create a [[https:// | ||
=== Con === | === Con === | ||
* Offers no integrated i18n/l10n tools | * Offers no integrated i18n/l10n tools | ||
- | * Private repos are not free (as in beer). | + | * <del>Private repos are not free (as in beer).</ |
* Not F/OSS itself, so we can't host it ourselves if desired. | * Not F/OSS itself, so we can't host it ourselves if desired. | ||
* [[http:// | * [[http:// | ||
+ | * Will necessitate changes in workflow, particularly as regards working repositories. (This could be a good thing!) | ||
+ | * [[https:// | ||
+ | * [[http:// | ||
+ | * [[https:// | ||
+ | * It is a "bad look" for a F/OSS project to use proprietary hosting solutions. | ||
- | ==== GitLab ==== | + | ==== GitLab |
=== Pro === | === Pro === | ||
- | * F/ | + | * We can host it ourselves or host at gitlab.com |
* Includes GitLab CI so we could retire both buildbot + current live testing with full Docker-based CI | * Includes GitLab CI so we could retire both buildbot + current live testing with full Docker-based CI | ||
* Anyone can sign up without administrator intervention. | * Anyone can sign up without administrator intervention. | ||
* Users can be in groups that can all access the same repos. | * Users can be in groups that can all access the same repos. | ||
* Has lots of plugins and applications that could add some of the " | * Has lots of plugins and applications that could add some of the " | ||
+ | * Can integrate with LDAP for community sign-on. | ||
=== Con === | === Con === | ||
- | * Is really a commercial product. The Libre version offers fewer features. | ||
* Offers no integrated i18n/l11n tools | * Offers no integrated i18n/l11n tools | ||
* It won't accept a push of an Evergreen repo because of https:// | * It won't accept a push of an Evergreen repo because of https:// | ||
Line 102: | Line 117: | ||
* We don't have as much control over branch permissions as gitolite offers. This likely means we'll lose the working repository in favor of individual developer repositories. (Note: gitlab used to be based on gitolite but is no longer.) | * We don't have as much control over branch permissions as gitolite offers. This likely means we'll lose the working repository in favor of individual developer repositories. (Note: gitlab used to be based on gitolite but is no longer.) | ||
* [[https:// | * [[https:// | ||
+ | * Anyone with an account can create their own projects/ | ||
+ | * To get many of the best features, we would need a license for the Enterprise Edition. (See https:// | ||
+ | * A self-managed/ | ||
+ | * Going with the community edition will necessitate work flow changes, particularly as regards working repositories. (This could be a good thing!) | ||
- | ==== Phabricator | + | ==== Fork LP ==== |
=== Pro === | === Pro === | ||
- | * Open Source (Apache License 2.0) | + | * We could add what we want without fundamentally changing existing workflows on ourselves |
- | * More to be determined. | + | |
=== Con === | === Con === | ||
- | * No hardware recommendations, | + | * It would be a lot of work |
- | * More TBD | + | |
- | ==== Fork LP ==== | + | |
+ | ==== GOGS ==== | ||
+ | |||
+ | https:// | ||
=== Pro === | === Pro === | ||
- | * We could add what we want without fundamentally changing existing workflows on ourselves | + | * Ridiculously easy to set up |
+ | * GitHub-like features/ | ||
=== Con === | === Con === | ||
- | * It would be a lot of work | + | * May not be robust enough for bug tracking |
+ | |||
+ | |||
+ | ==== Atlassian Open-Source ==== | ||
+ | |||
+ | Atlassian products are free for open-source use on application to them: | ||
+ | https:// | ||
+ | This is used by FOLIO project | ||
+ | |||
+ | === Pro === | ||
+ | |||
+ | * Very feature rich, JIRA for bug tracking is an industry standard tool | ||
+ | * Can be self-hosted | ||
+ | |||
+ | === Con === | ||
+ | |||
+ | * Not open-source | ||
+ | |||
+ | ==== Gerrit ==== | ||
+ | |||
+ | === Pro === | ||
+ | === Con === | ||
+ | |||
+ | |||
+ | ==== savannah.nongnu.org ==== | ||
+ | |||
+ | === Pro === | ||
+ | === Con === | ||
====== Translation tools ====== | ====== Translation tools ====== | ||
If we move to a bug tracking / repository tool that does not include translation support (and most alternatives do not), then we need to consider what we would like to do for translations. | If we move to a bug tracking / repository tool that does not include translation support (and most alternatives do not), then we need to consider what we would like to do for translations. | ||
+ | |||
+ | ===== POEditor.com ===== | ||
+ | |||
+ | https:// | ||
===== Pootle ===== | ===== Pootle ===== |
dev/2017_new_tools.txt · Last modified: 2023/06/22 09:10 by dyrcona