#6082 Pagure SOP missing
Closed: Upstream 6 years ago Opened 6 years ago by puiterwijk.

We really should have an SOP for Pagure, and I can't find one.


What all should go into this SOP? Is this something we can tag as easyfix?

Easyfix? surely

as to what:

how to launch an instance either on your own infra or cloud provider.
basic quickstart, including how to enable issues, PRs, access controls, like making/using private tickets
basic debugging steps
how to fork and PR
how to setup /add ssh keys or other auth protocols like freeipa or ipsilon (i.e. fas3)
basic ticket/issue handling ( adding tags, assignees, priority etc)

how to launch an instance either on your own infra or cloud provider.

Not in the scope of the infra doc

basic quickstart, including how to enable issues, PRs, access controls, like making/using private tickets

Not in the scope of the infra doc

basic debugging steps

Ok

how to fork and PR

Not in the scope of the infra doc

how to setup /add ssh keys or other auth protocols like freeipa or ipsilon (i.e. fas3)

Not in the scope of the infra doc

basic ticket/issue handling ( adding tags, assignees, priority etc)

Not in the scope of the infra doc

What you are describing here is a documentation for pagure which exists in http://docs.pagure.org/pagure (and can be improved, for sure), but not what we want in the infrastructure SOP which are more along the lines of:

  • point of contact
  • architecture
  • machines
  • debugging
  • frequently seen problems (and their solution)
    ...

Filed initial PR with:

https://pagure.io/infra-docs/pull-request/45

Lets track there...

:barber:

Metadata Update from @kevin:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata