fedora-commops

#181 Document CommOps administration and workflow
Closed: moved by jflory7. Opened by jflory7.

Closed: moved
Reopen Issue

Summary

Add a new page to CommOps documentation about our administration to run CommOps and workflow for Pagure issues / IRC meetings / mailing list / etc.

Background

In 2015, we trialed a new workflow for CommOps and it's mostly stuck since then. Some minor changes have happened over time (Trac retirement, new labels / tags, etc.), but it is mostly in memory, not documented. It would be helpful for other CommOps team members and future team leads to have both this workflow and a high-level overview of administrating CommOps documented. It can live with our other documentation on docs.fp.o.

Details

The form for this can be a new page in our CommOps documentation. It should explain the following topics (in any order):

  • How our IRC meetings run
  • How our Pagure repo is configured (tags, priorities, milestones)
  • Choosing what platform to communicate on (Pagure, mailing list, IRC)
  • What to do after a new release (Mindshare seat, possibly a check-in on yearly goals)
  • [new] Explaining our annual goals for each year (??)
  • How to update the FAS groups (commops, community-blog)

And possibly more…

Outcome

Easier to understand how CommOps functions, begin to document parts of our workflow so others can understand and participate easier, encourage wider adoption of practices if others find it useful and clear

tusharkumar2020 commented

Hello @jflory7 ,

Please let me know if I can pursue this task as it will help me learn more.
tusharkumar2020 commented

Dropping this task as the expectation is to receive inputs from CommOps team and administration teams.
tusharkumar2020 commented

Current status pending.

Hi @tusharkumar2020, thanks for your interest on this! However, it is a difficult task for a newcomer. This issue is focused on better documenting the way Fedora CommOps has run over the last 4-5 years. Historical context will make this issue way easier I think.

Did you see some of the other issues tagged as "help wanted"? These are great places to start!

https://pagure.io/fedora-commops/issues?status=Open&tags=help+wanted

Metadata Update from @jflory7:
- Issue set to the milestone: None (was: Fedora 30 (to May 2019))

Moved to GitLab

On May 16th, 2024, this repository was migrated from Pagure to GitLab, including all closed and open issues. This Pagure repository is being retired and set to read-only. We are committed to reviewing tickets on GitLab that are still open to determine whether or not they should be moved to the team's active planning repository.

If you want this issue to be followed up in 2024, please comment on the corresponding GitLab issue and let us know you are still interested in seeing it completed or implemented.

Find the new home for CommOps

See the repository below for the imported issues:

https://gitlab.com/fedora/commops/archive/

This specific issue can be found below:

https://gitlab.com/fedora/commops/archive/-/issues/181

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

team - commops type - docs

None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.