Search results

=== Standaard Handelings Procedures === ...systeem kan worden gevonden op de [[Infrastructure/Tickets|Infrastructure Tickets Wiki Pagina]].

...ou are already a Fedora contributor, for your own package use the standard procedures https://fedoraproject.org/wiki/Package_maintenance_guide for requesting a n # Look to see if there are any existing tickets for this package to be branched into EPEL. This can help find if there are

== Runbooks / Standard Operating Procedures == When all the tickets are over, go for Open floor

...L) and as always, the problem of refunds is recurrent (for example see the tickets [https://pagure.io/ambassadors-latam/tasks/issue/381] [https://pagure.io/am ...mplementary rules for events organizations/coordinations, funding request, tickets management process, and similar tasks.

...cture is a Fedora Account and a signed [[Legal:FPCA| FPCA]]. A number of tickets can be found in the Infrastructure pagure.io instance: [https://pagure.io/f * Developing and enforcing procedures and policy for Fedora Infrastructure

...format for each coast as follows; Meeting Name, Roll Call, Announcements, Tickets, and Open Floor. Any changes to these guides will require FAmNA voting procedures for approval.

...s already have different, mostly well documented, SOPs (standard operating procedures) for joining their respective SIG. The infrastructure team is a great examp ...w_issue ticket] if you need help from Fedora Join or help us with existing tickets by visiting our [https://pagure.io/fedora-join/Fedora-Join repository].

...L) and as always, the problem of refunds is recurrent (for example see the tickets [https://pagure.io/ambassadors-latam/tasks/issue/381] [https://pagure.io/am ...mplementary rules for events organizations/coordinations, funding request, tickets management process, and similar tasks.

...s already have different, mostly well documented, SOPs (standard operating procedures) for joining their respective SIG. The infrastructure team is a great examp ...w_issue ticket] if you need help from Fedora Join or help us with existing tickets by visiting our [https://pagure.io/fedora-join/Fedora-Join repository].

* Ambassadors Standard Operating Procedures [http://lists.fedoraproject.org/pipermail/ambassadors/2011-February/017066. | '''New tickets''' || '''Open Tickets''' || '''Sponsored ''' || '''Rejected''' || '''Month'''

...om the Fedora Infrastructure team and make sure that we have processes and procedures that are as light as possible while still giving us a consistent way to pus Proposal: that we use bz to handle both work tickets and email "support" requests sent to webmaster@fp.o.

* poelcat filed tickets with RHT Engineering Operations for 'rawhide rebase' and 'Fedora 8 EOL warn | style="color: #42427e" | btw I filed the tickets with rht eng-ops and made sure they can run them

=== development/13 bug procedures === ..." | we're going to want to keep a good mapping of potential fixes to bodhi tickets

...t some time documenting necessary bits into a series of standard operating procedures (SOPs) https://docs.fedoraproject.org/en-US/ask-fedora-sops/ ...tion on the discussions and process that we followed, you can read all the tickets related to Ask Fedora on pagure: https://pagure.io/fedora-join/Fedora-Join/

...siempre, los problemas de reembolsos están presentes (por ejemplo ver los tickets [https://pagure.io/ambassadors-latam/tasks/issue/381] [https://pagure.io/am ...ando las reglas actuales se logrará mejorar el tiempo de aprobación de los tickets y su calidad para optimizar el gasto (gasto mejor orientado).

=== Fedora-qa F15 TRAC tickets === ...ing up the Fedora 15 fedora-qa TRAC milestone in preparation for Fedora 16 tickets

# Start picking up tickets in the above milestones ...ckage repos. So as always, you can update to rawhide using the documented procedures

...le, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approv ...esktop accordingly to connect to the server using the respective standard procedures

* f13 to create the various action tickets for the Beta release. ...le="color: #407a40" | lets move that topic later, after we get through the tickets.

* If no additional feedback, jlaska will create tickets and a draft retrospective SOP this week * Testers needed to help document test procedures (test cases / matrix) and run tests