arc/docs/fcas/solution_examples.rst

.. _solution_examples.rst:

Examples of Contributor Actitivies
==================================

Below is an extensive compilation of sample activities that qualify as "contributions"
and can be systematically monitored. These activities involve engaging with services
responsible for publishing messages on the Fedora Messaging bus. For better
organization, these examples can be categorized according to the specific services they
are associated with. It is important to recognize that this list is not exhaustive, and
there may be additional examples beyond those provided here.

COPR
----

Application identifier - ``Copr``

**Tasks**
    - Creating/modifying/deleting package namespaces or primitives
    - Pushing/updating/removing builds/tests for the primitives

**Notes**
    - If "Person X" were to add "Person Y" in the namespace, "Person X" is the reason
      why that message was created on the messaging bus and hence, only "Person X" would
      be said to have done a "contribution activity" and while "Person Y" was involved
      here, they would not be said to have done a "contribution activity" in this case.

Ansible
-------

Application identifier - ``ansible``

**Tasks**
    - Creating/modifying/deleting pull requests to the repository
    - Making/updating/removing issue tickets on the repository

**Notes**
    - If "Person X" were to be assigned an issue ticket by "Person Y", "Person Y" is the
      reason why that message was created on the messaging bus and hence, only "Person
      Y" would be said to have done a "contribution activity" and not "Person X" even
      when they were involved in this case.

Bodhi
-----

Application identifier - ``bodhi``

**Tasks**
    - Creating/modifying/deleting new updates for the packages
    - Giving karma to a testing package

**Notes**
    - If "Person X" were to give a negative karma to a release of a package that belongs
      to "Person Y", "Person X" is the reason why that message was created on the
      messaging bus and hence, only "Person X" would be said to have done a
      "contribution activity" and while "Person Y" was involved here, they would not be
      said to have done a "contribution activity" in this case.

Discourse
---------

Application identifier - ``discourse``

**Tasks**
    - Creating/modifying/deleting new threads on the forum
    - Reacting to the existing threads

**Notes**
    - If "Person X" were to be tagged in a comment post made by "Person Y", "Person Y"
      is the reason why that message was created on the messaging bus and hence, only
      "Person Y" would be said to have done a "contribution activity" and not "Person X"
      even when they were involved in this case.

Fedora Account System
---------------------

Application identifier - ``FAS``

**Tasks**
    - Creating and modifying new accounts on the system
    - Adding and removing accounts from groups

**Notes**
    - If "Person X" were to add "Person Y" to a FAS group - being the sponsor of the
      same group, "Person X" is the reason why that message was created on the messaging
      bus and hence, only "Person X" would be said to have done a "contribution
      activity" and while "Person Y" was involved here, they would not be said to have
      done a "contribution activity" in this case.

Fedora Calendar
---------------

Application identifier - ``fedocal``

**Tasks**
    - Creating/modifying/deleting of events on the calendar
    - Transfer of events from one account to another

**Notes**
    - If "Person X" were to be given the ownership of a calendar event by "Person Y",
      "Person Y" is the reason why that message was created on the messaging bus and
      hence, only "Person Y" would be said to have done a "contribution activity" and
      not "Person X" even when they were involved in this case.

Fedora Build System
-------------------

Application identifier - ``koji``

**Tasks**
    - Creating and deleting jobs for builds and testing
    - Succeeding and failing of the aforementioned jobs

**Notes**
    - If "Person X" were to create a build job for a package owned by "Person Y",
      "Person X" is the reason why that message was created on the messaging bus and
      hence, only "Person X" would be said to have done a "contribution activity" and
      while "Person Y" was involved here, they would not be said to have done a
      "contribution activity" in this case.

Notifications
-------------

Application identifier - ``koji``

**Tasks**
    - Creating/modifying/deleting rules from the dashboard
    - Changing tracking rules and owners for an existing rule

**Notes**
    - If the activities done by "Person X" were to be tracked by "Person Y", "Person Y"
      is the reason why that message was created on the messaging bus and hence, only
      "Person Y" would be said to have done a "contribution activity" and not "Person X"
      even when they were involved in this case.

Pagure
------

Application identifier - ``pagure``

**Tasks**
    - Creating/modifying/deleting repositories or groups
    - Making pull requests against an existing repository

**Notes**
    - If "Person X" were to make a pull request against a repository owned by "Person
      Y", "Person X" is the reason why that message was created on the messaging bus and
      hence, only "Person X" would be said to have done a "contribution activity" and
      while "Person Y" was involved here, they would not be said to have done a
      "contribution activity" in this case.

Elections
---------

Application identifier - ``elections``

**Tasks**
    - Casting and changing vote for a preferred candidate during nomination
    - Creating/modifying/deleting nominees from the stand

**Notes**
    - If "Person X" were to be voted for by "Person Y", "Person Y" is the reason why
      that message was created on the messaging bus and hence, only "Person Y" would be
      said to have done a "contribution activity" and not "Person X" even when they were
      involved in this case.

Package Sources
---------------

Application identifier - ``distgit``

**Tasks**
    - Creating/modifying/deleting repositories or groups
    - Making/updating/removing pull requests on the repository

**Notes**
    - If "Person X" were to be created a namespace for by a package sponsor "Person Y",
      "Person X" is the reason why that message was created on the messaging bus and
      hence, only "Person X" would be said to have done a "contribution activity" and
      while "Person Y" was involved here, they would not be said to have done a
      "contribution activity" in this case.