Differences

This shows you the differences between two versions of the page.

--- dev:2017_new_tools [2018/11/06 13:32] – add POEditor option bshum
+++ dev:2017_new_tools [2023/06/22 09:10] (current) – [Con] dyrcona
@@ Line 20: / Line 20: @@
   * The API is hard to use, particularly for command-line applications
   * 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.  Most effective way to search is to start opening a new bug.
   * There's no way to edit, delete, or suppress a comment, which is a problem if somebody has inadvertently left in patron or a description of a security exploit.
   * There's no way to update a bug without triggering an email, which is a problem for batch updates.
+=== Huge list of software options out there OSS or not ===
+  * https://github.com/Kickball/awesome-selfhosted#project-management
 ==== Gitolite ====
@@ Line 71: / Line 75: @@
 ==== GitHub ====
+=== Notes ===
+Options for transitioning from Launchpad to Github:  https://lp2gh.readthedocs.io/en/latest/moving_issues.html?highlight=import
 === Pro ===
@@ Line 86: / Line 94: @@
   * [[http://where.coraline.codes/blog/my-year-at-github/|Antisocial Coding: My Year At GitHub]]
   * Will necessitate changes in workflow, particularly as regards working repositories. (This could be a good thing!)
+  * [[https://www.zdnet.com/article/github-starts-blocking-developers-in-countries-facing-us-trade-sanctions/|GitHub starts blocking developers in countries facing US trade sanctions]]
+  * [[http://techrights.org/2020/11/03/github-is-social-control/|GitHub is social control]]
+  * [[https://sfconservancy.org/blog/2022/jun/30/give-up-github-launch/|SFC Gives Up on Github]]
+  * It is a "bad look" for a F/OSS project to use proprietary hosting solutions.
 ==== GitLab Community Edition ====
@@ Line 109: / Line 121: @@
   * A self-managed/self-hosted solution would still require some administrator overhead, perhaps as much as gitolite.
   * Going with the community edition will necessitate work flow changes, particularly as regards working repositories. (This could be a good thing!)
+  * Using dual-licensed products with a full feature proprietary release and less powerful free release is a bad look for a F/OSS project.
 ==== Fork LP ====
@@ Line 156: / Line 169: @@
+==== savannah.nongnu.org ====
+=== Pro ===
+=== Con ===