Phabricator/es

Reportar errores/cualquier otra cosa  Reportar problema de seguridad   Solicitar dominio personalizado   Solicitar cambios de configuración

Phabricator es un software de seguimiento de problemas utilizado para tener seguimiento de solicitudes de características, bugs abiertos, etc.

Phabricator is only for technical issues! If you require assistance with something non-technical in nature (i.e. adoption requests, disruptive users, help with CSS, etc.), please ask on the Community noticeboard or Stewards' noticeboard.

Se puede encontrar información técnica aquí.

Creating an account/Logging in
To create an account or log in, please use the following steps:


 * 1) Go to Phabricator.
 * 2) If you are not logged in, click "Log In" at the top right.
 * On the next page, click the "Log In or Register // MediaWiki" button at the bottom right (this logs you in to your Miraheze account).


 * Always click the "Log In or Register// MediaWiki" button at the bottom right. Do not log in straight from Phabricator, that login prompt is not for wiki users.


 * 1) If prompted, sign into your Miraheze account.
 * A prompt appears asking you if you want to allow Miraheze Phabricator to log you in, click "Allow".


 * 1) If you haven't made an account already, you will be asked to confirm your username and add your email.
 * Below are images that may assist you in this process, the images show how each screen/step should look. Each image is labelled what step it corresponds to.



Filing tasks
Once you are logged in, click the links at the top of the page to file tasks. Alternatively, if you click "Maniphest" in the Main Page, a button titled "Create Task" should appear.

When making requests, title them descriptively. For example, if you encounter a bug such as a database error on your wiki, a good title could be "Database errors on "mywiki.miraheze.org".

Unless you have been instructed to, do not assign the task to anyone (including yourself). System administrators assign tasks to other system administrators, users, or even to themselves to help track the task's progress. Additionally, unless the task is an urgent one (such as errors on all wikis, downtime globally, etc.), do not set the priority to "High" or "Unbreak Now!". This does not cause your request to be processed faster. Even if your wiki is inaccessible, you should leave the priority at "Needs Triage" or "Normal" and a system administrator will change it if needed.

Do not fill in "Tags" or change "Subscribers" if you do not know what you are doing. Leave them blank and if needed, someone will change them.

In the description of the task you are creating, be descriptive on the issue or feature you are requesting. If your task is regarding a wiki in particular, please link to it. If the task you are creating is using a template (e.g. Custom domain requests, security issues, etc.), please follow the guidelines laid out on the page.

Once you have filled out your request, a system administrator will process it shortly. Please have patience if your task is not dealt with immediately!

Who can file tasks?
All Miraheze users are free to file bug reports and to give feedback. However, for more sensitive issues such as custom domain requests, article imports, database name changes, changing of restricted settings, among others, only bureaucrats should files those tasks. Even if you are a sysop, it is recommended a bureaucrat files the task.

Solicitudes y reportes

 * Si desea solicitar una extensión y/o un cambio de configuración (¡eso no está en ManageWiki!) para su wiki, por favor usa este formulario.
 * Si desea reportar un error o cualquier otra cosa, por favor usa este formulario
 * Si desea reportar un problema de seguridad por favor usa este formulario

Para obtener más detalles técnicos, consulte Tech:Phabricator.

Tareas de orientación

 * Todas las solicitudes de características y la mayoría de los cambios de configuración se triaje como "Normal" por defecto. No es necesario cambiar la prioridad de la solicitud, ya que no hará que su solicitud sea procesada más rápidamente. Todas las peticiones de características y los cambios de configuración se realizan por orden de llegada, en el que su wiki se configurará cuando todas las peticiones antes de que se completen o se completen con un estándar lo suficientemente bueno como para que sea posible seguir adelante.
 * La prioridad "Alta" se usa cuando un problema está afectando a toda la granja, o causando grandes problemas en un wiki. La prioridad "Unbreak Now" se utiliza cuando hay un problema urgente, o cuando la granja está caída.
 * Las tareas que no son importantes para el funcionamiento directo de Miraheze, son sólo ideas o no se pueden trabajar en la actualidad se deben clasificar como "Baja".

Additionally, there are also statuses on Phabricator:


 * Open: Tasks that are currently waiting on someone to take care of them, or that are in progress.
 * Resolved: Tasks that have been completed.
 * Invalid: Tasks that are inappropriate for Phabricator and the request should have been made somewhere else.
 * Declined: Tasks that either can't be done at this time, won't be done or the conclusion was that it was not needed at the time.
 * Stalled Tasks that are waiting on an external entity to respond before any further action from us can be taken.

Si no está seguro de cómo seleccionar un problema, por favor déjelo como está y un Administrador del sistema lo seleccionará apropiadamente.

Etiquetas/Proyectos

 * Las etiquetas/proyectos se utilizan para organizar las tareas en sus temas relativos. Por ejemplo, una tarea titulada "Solicitud de características por ejemplo.miraheze.org" se colocaría bajo la etiqueta "Configuración", ya que es la etiqueta bajo la que ponemos todas las solicitudes de características y cambios de configuración.
 * Las extensiones que pueden necesitar ser revisadas se colocan bajo la etiqueta Extension-Review.
 * Las tareas que se relacionan con el funcionamiento general de Miraheze y sus servidores se colocan bajo la etiqueta "Operations".
 * Hay un sinnúmero de otras etiquetas que son usadas para una variedad de propósitos. Todos ellos pueden ser vistos aquí: https://phabricator.miraheze.org/project/query/all/

Types
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
 * Groups
 * These represent 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
 * ACLs
 * Similar to groups except these are used for controlling access to certain tasks, with their group membership heavily restricted.
 * Icon: Policy
 * Colour: Red
 * Tags
 * Tags represent common objectives or issues that aren't Project-specific.
 * Icon: Tag
 * Colour: Yellow
 * Goals
 * Goals are most commonly our bi-annual planning period objectives.
 * Icon: Goal
 * Colour: Green
 * User
 * User projects can be used to allow a user to categorise tasks easily 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

Access Policy
This outlines access to certain ACLs and Administrator privileges on Phabricator.

Administrator
Phabricator Administrator is not a powerful tool; however, it has access to certain protected information about user accounts and can see sensitive information such as 2-Factor Authentication Status.

Currently, Phabricator Administrator rights have only been granted to Site Reliability Engineers, who already maintain root access on the relevant Phabricator servers. This policy can be reviewed if a use-case can be presented by any member who is not eligible for the rights currently.

ACL: Security
This ACL allows tasks to be restricted from public view when the contents being public could cause a risk to Miraheze's operations, software security or data protection. This ACL can additionally be used when such information could pose a risk to other services until a reasonable disclosure period has passed - when Miraheze may make such information public.

Membership to the group is restricted to:
 * Site Reliability Engineering
 * Trust and Safety
 * Board of Directors (when they take an active part in compliance/regulatory business of the company)

Anyone, who requires access to a certain task, can be added as a subscriber without ACL membership.

Digests
Digests of Phabricator Search Queries are available using the PhabDigests tool powered by the volunteer MirahezeBots project. This will require your email to be given to volunteers, and the information is not covered under the Miraheze NDA or Privacy Policy. Data stored on this system is subject to a separate privacy policy.

Please contact RhinosF1 or ask in if you would like a digest.

Véase también
vea esta página para más detalles técnicos sobre Phabricator.