Technical information can be found here.
Requests and reports[edit | edit source]
- If you want to request an extension and/or configuration change (that is not on ManageWiki!) for your wiki, please use this form.
- If you want to report a bug or anything else please use this form
- If you want to report a security issue please use this form
For more technical details please see Tech:Phabricator.
Triaging tasks[edit | edit source]
- All feature requests and most configuration changes are triaged as "Normal" by default. There is no need to change the priority of the request as it will not make your request be processed faster. All feature requests and configuration changes are done on a first come, first served basis, wherein your wiki will be configured when all requests before it are either completed or completed to a well enough standard that it is possible to move on. There are four different priorities that are used on Phabricator:
- Unbreak Now: Tasks here should be resolved as soon as possible, all other tasks should be dealt with after the ones here are resolved.
- High: Tasks here should ideally be resolved in a few days.
- Normal: Feature requests here should be resolved as soon as someone is able to, and other tasks (such as goals) should be done in the time period that's assigned to them.
- Low: Tasks here are not important to the direct functioning of Miraheze or are just ideas or cannot be worked on currently, and therefore they should be done whenever someone wants to.
Additionally, there are also statuses on Phabricator ("Open", "Denied", "Invalid", "Resolved" and "Stalled"). While the first four are self-explanatory we use Stalled for tasks that are waiting on an external entity to respond before any further action from us can be taken.
If you are unsure about how to triage an issue, please leave it as it is and a System administrator will triage it appropriately.
SRE Duty[edit | edit source]
Site Reliability Engineering Duty is a name assigned to the process of ensuring incoming tasks and problems get resolved in a timely manner or remain tracked week-in-week-out to prevent tasks dropping off everyone's radar.
Read more about SRE Duty here.
Tags/Projects[edit | edit source]
- Tags/Projects are used to organize tasks into their relative topics. For example a task titled "Feature request for example.miraheze.org" would be placed under the "Configuration" tag as this is the tag we put all feature requests and configuration changes under.
- Extensions that may need to be reviewed are added to the "Extensions" project under the "Review Needed" workboard
- Tasks that relate to the general running of Miraheze and its servers is placed under the Site Reliability Engineering tag.
- There are countless other tags that are used for a variety of purposes. They can all be viewed here: https://phabricator.miraheze.org/project/query/all/
Types[edit | edit source]
There are different types of projects/tags that are used on Phabricator. The current configuration is as follows:
- Projects / Components
- These represent the bulk of projects within Phabricator and belong to an area of either software, infrastructure or activity.
- Icon: Project
- Colour: Blue
- These represents entities of people and serve as a common association for tasks which require involvement or engagement from a certain group or for a group who may be a stakeholder in a task's progression.
- Icon: Group
- Colour: Violet
- Similar to groups except these are used for controlling access to certain tasks, with their group membership heavily restricted.
- Icon: Policy
- Colour: Red
- Tags represent common objectives or issues that aren't Project specific.
- Icon: Tag
- Colour: Yellow
- Goals are most commonly our bi-annual planning period objectives.
- Icon: Goal
- Colour: Green
- User projects can be used to allow a user to categorise tasks in an easy way within a project rather than tracking it via other means such as notifications. Useful for monitoring progression of tasks across a workboard.
- Icon: Timeline
- Colour: Checkered