phabricator is yet another webapp to maintain. Every now and then an update breaks it such as recently an update broke something which worked for a long time: the outbound mailer. Other issues with phabricator: we require 3 user accounts. Forums, wiki, and issue tracker. The latter is certainly the most underused where the fewest people sign up. Also other issues.
Often we have a forum subject with the “real” discussion and then a phabricator ticket as reminder to actually implement what was being discussed, some duplication. The main feature used by phabricator: issue tracking, open/close status and tags. So I was wondering if discourse is capable to replace phabricator.
I just noticed we have “only” 100 open tickets.
Correction: I just noticed we have “only” 220 open tickets.
https://phabricator.whonix.org/maniphest/query/open/
So even a manual migration is realistic. Wondering to just close the stale / unrealistic ones. The tracker could use a spring clean anyhow.
The good thing is the forum search allows to search for multiple tags which all have to be matched at the same time.
EDIT:
- Tags were heavily modified just now: https://forums.whonix.org/tags
- New change related to discourse forum tags:
- Discourse forums tags are now only changeable by Whonix discourse moderators
discourse does not yet support following which tags where changed
Added here just now:
https://www.whonix.org/wiki/Reporting_Bugs#Issue_Tracker
- Old legacy issue tracker: In not so long ago past issues were posted on Whonix ™ phabricator [archive].
- Migration: Issues are in a slow process of being migrated [archive].
- New issue tracker: Whonix ™ discourse forums [archive].
backlog 1 [archive] / backlog 2 [archive]
Previously there were no guidelines / rules on how to use discourse forum tags. Anyone could create them / add them / change them. [10]
Discourse forums tags are now only changeable by Whonix ™ discourse moderators [archive].
Search query examples:
- all
status_open_issue_todo
issues [archive]- all
status_closed_issue_implemented
issues [archive]status_open_issue_todo
component_security
related enhancement requests (TODO) [archive]status_closed_issue_implemented
component_security
related enhancement requests (done) [archive]status_open_issue_todo
component_research
tasks [archive]- list of all forum tags [archive]
You can create a comment in a separate post such as:
Please open.
Please close.
Please re-open.
Please add tag
testers-wanted
.Please remove tag
component_security
.If appropriate, the tag will be changed by a forum moderator. Such comments might be deleted if inappropriate, duplicated or for brevity of the discussion (such as in case the status was only not updated due to as mistake).
If a forum thread is not tagged with
whonix-15
(the current stable release of Whonix ™) at time of writing towhonix-16
(the next Whonix ™ release) then it is not on the roadmap. In result chances the issue will be resolved (feature implemented, research/task done, or bug fixed) is lower. Please abstain from debating priorities which issue is more/less important or when it should be implemented. (reasons)Tags should not be appended to every discussion or question about the related subject.
The goal of forum tags is to maximize Whonix ™ forum’s usefulness as a roadmap and issue tracker for Whonix ™ project developers.