%YAML 1.2
---
name: Fedora Apps
data:
  description: >
    This is a landing page for Fedora Apps.  Fedora Infrastructure is
    huge; this page details only the public facing portion of
    it all.  Explore!
children:
  - name: Accounts
    data:
    description: >
      Tools for everybody -- use these things to manage your Fedora
      Account.
    children:
      - name: FedoraPeople
        data:
          url: https://fedorapeople.org
          user_url: https://{user}.fedorapeople.org
          status_mappings: [people]
          description: >
            Being a community member you gain access to fedorapeople which
            provides you with a space on the web where you can upload
            files to share them with the community.
      - name: Fedora Accounts
        data:
          url: https://accounts.fedoraproject.org/
          user_url: https://accounts.fedoraproject.org/user/{user}
          source_url: https://github.com/fedora-infra/noggin/
          bugs_url: https://github.com/fedora-infra/noggin/issues/
          docs_url: https://noggin-aaa.readthedocs.io/en/latest/
          sops:
            - https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/fas-notes.html
            - https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/fas-openid.html
            - https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/accountdeletion.html
            - https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/nonhumanaccounts.html
          status_mappings: [fas]
          description: >
            Fedora Accounts. Update your profile
            information and apply for membership in groups.
      - name: Notifications
        data:
          icon: fedmsg.png
          url: https://notifications.fedoraproject.org/
          source_url: https://github.com/fedora-infra/fmn/
          bugs_url: https://github.com/fedora-infra/fmn/issues/
          docs_url: https://fmn.readthedocs.io/
          sops: [https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/fmn/]
          status_mappings: [fedmsg]
          description: >
            Centrally managed preferences for Fedora Infrastructure
            notifications to your inbox, irc client, and mobile device.
      - name: Badges
        status_mappings: [badges]
        data:
          icon: badges.png
          url: https://badges.fedoraproject.org
          user_url: https://badges.fedoraproject.org/user/{user}
          source_url: https://github.com/fedora-infra/tahrir/
          bugs_url: https://github.com/fedora-infra/tahrir/issues/
          docs_url: https://tahrir.readthedocs.org/en/latest/
          sops: [https://infrastructure.fedoraproject.org/infra/docs/badges.rst]
          description: >
            An achievements system for Fedora Contributors!  "Badges"
            are awarded based on activity in the community.  Can you
            unlock them all?
            You can export your badges to Mozilla's
            Open Badges
            Infrastructure
  - name: Content
    data:
    description: >
      Tools for wordsmiths -- the apps that store and archive the troves
      of content that Fedora authors produce.  Blog posts, the wiki, and
      more..
    children:
      - name: Ask Fedora
        data:
          icon: ask_fedora.png
          url: https://ask.fedoraproject.org/
          source_url: https://github.com/askbot/askbot-devel
          bugs_url: https://github.com/askbot/askbot-devel/issues/
          docs_url: http://askbot.org/doc/index.html
          sops: [https://infrastructure.fedoraproject.org/infra/docs/askbot.rst]
          status_mappings: [ask]
          description: >
            Any question at all about Fedora?  Ask it here.
      - name: The Wiki
        data:
          icon: mediawiki.png
          url: https://fedoraproject.org/wiki
          user_url: https://fedoraproject.org/wiki/User:{user}
          source_url: https://www.mediawiki.org/
          bugs_url: https://www.mediawiki.org/wiki/Phabricator#Get_started
          docs_url: https://www.mediawiki.org/wiki/Sysadmin_hub
          sops: [https://infrastructure.fedoraproject.org/infra/docs/wiki.rst]
          status_mappings: [wiki]
          description: >
            Maintain your own user profile page, contribute to
            documents about features, process, and governance.
      - name: Fedora Magazine
        data:
          icon: magazine.png
          url: https://fedoramagazine.org
          docs_url: https://codex.wordpress.org/
        # We don't have a SOP for the magazine yet.
        # https://pagure.io/fedora-infrastructure/issue/5149
        # sops:
        #    - put the url here
          description: >
            Fedora Magazine is a WordPress-based site which delivers all
            the news of the Fedora Community. (It replaces the previous
            Fedora Weekly News.)
      - name: The Planet
        data:
          icon: planet_logo.png
          url: http://fedoraplanet.org
          docs_url: https://www.intertwingly.net/code/venus/
          sops:
            - https://infrastructure.fedoraproject.org/infra/docs/planetsubgroup.rst
          description: >
            The planet is a blog aggregator, a space accessible to you
            as a community member where you can express your opinion and
            talk about what you are doing for Fedora.
      - name: Docs
        data:
          url: https://docs.fedoraproject.org
          status_mappings: [docs]
        # TODO - add the docs_url.  I asked pete travis for info on this
        # docs_url: put the url here
        # TODO - add a sop.
        # https://pagure.io/fedora-infrastructure/issue/5150
        # sops:
        #    - add the sop url here.
          description: >
            RTFM!  Everything you could ever want to know.
            Probably the best place to find documentation about Fedora,
            including the changes between releases (and a big kudos to
            the translation teams to keep this resource up to date in
            the different languages!)
  - name: QA
    data:
    description: >
      Tools for testers -- the people who tell us its broken so we can
      fix it.
    children:
      - name: Problem Tracker
        data:
          url: https://retrace.fedoraproject.org
          package_url: https://retrace.fedoraproject.org/faf/reports/?component_names={package}
          source_url: https://github.com/abrt/retrace-server/
          bugs_url: https://github.com/abrt/retrace-server/issues
          docs_url: https://abrt.readthedocs.org/en/latest/howitworks.html#faf
        # TODO - write SOPs for this
        # https://pagure.io/fedora-infrastructure/issue/5151
        # sops:
        #    - url goes here
        #    - and another one goes here
          description: >
            The Problem Tracker is a platform for collecting and
            analyzing package crashes reported via ABRT (Automatic Bug
            Reporting Tool). It makes it easy to see what problems
            users are hitting the most, and allows you to filter them
            by Fedora release, associate, or component.
      - name: Blocker Bugs
        data:
          url: https://qa.fedoraproject.org/blockerbugs
          source_url: https://pagure.io/fedora-qa/blockerbugs
          bugs_url: https://pagure.io/fedora-qa/blockerbugs
          docs_url: https://tflink.fedorapeople.org/blockerbugs/docs/
          sops:
            - https://infrastructure.fedoraproject.org/infra/docs/blockerbugs.rst
          status_mappings: [blockerbugs]
          description: >
            The Fedora Blocker Bug Tracker tracks release blocking bugs
            and related updates in Fedora releases currently under
            development.
      - name: Bugzilla
        data:
          icon: bugzilla.png
          url: https://bugzilla.redhat.com
          package_url: >
            https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Fedora&product=Fedora%20EPEL&query_format=advanced&component={package}
          description: >
            The Fedora Community makes use of a bugzilla instance
            run by Red Hat.  Notice something wrong with a Fedora
            package?  You can file an official bug here.
      - name: Review Status
        data:
          url: https://fedoraproject.org/PackageReviewStatus/
          package_url: >
            https://bugzilla.redhat.com/buglist.cgi?component=Package%20Review&query_format=advanced&short_desc_type=allwordssubstr&short_desc={package}
        # TODO - write the SOP for this
        # https://pagure.io/fedora-infrastructure/issue/5152
        # sops:
        #    - url goes here
          description: >
            These pages contain periodically generated reports with
            information on the current state of all Fedora package review
            tickets -- a super useful window on bugzilla.
      - name: Kerneltest
        data:
          icon: tux.png
          url: https://apps.fedoraproject.org/kerneltest
          source_url: https://github.com/jmflinuxtx/kerneltest-harness
          bugs_url: https://github.com/jmflinuxtx/kerneltest-harness/issues
          docs_url: https://fedoraproject.org/wiki/KernelTestingInitiative
          sops:
            - https://infrastructure.fedoraproject.org/infra/docs/kerneltest-harness.rst
          description: >
            As part of the kernel
            testing initiative we provide a webapp where users and
            automated systems can upload test results.  If you have
            access to hardware where we could catch tricky driver
            issues, your assistance here would be much appreciated.
      - name: Koschei
        data:
          icon: koschei.png
          url: https://koschei.fedoraproject.org/
          user_url: https://koschei.fedoraproject.org/user/{user}
          package_url: https://koschei.fedoraproject.org/package/{package}
          source_url: https://github.com/fedora-infra/koschei
          bugs_url: https://github.com/fedora-infra/koschei/issues
          docs_url: https://fedoraproject.org/wiki/Koschei
          sops: [https://infrastructure.fedoraproject.org/infra/docs/koschei.rst]
          status_mappings: [koschei]
          description: >
            Koschei is a continuous integration system for RPM packages. It
            tracks dependency changes done in Koji repositories and rebuilds
            packages whose dependencies change. It can help packagers to
            detect failures early and provide relevant information to narrow
            down the cause.
  - name: Coordination
    data:
    description: >
      Tools for people -- so we can talk to each other and share content
      and ideas.
    children:
      - name: Asknot
        data:
          url: https://whatcanidoforfedora.org
          source_url: https://github.com/fedora-infra/asknot-ng
          bugs_url: https://github.com/fedora-infra/asknot-ng/issues
          docs_url: https://github.com/fedora-infra/asknot-ng/blob/develop/README.md
        # TODO - write SOP for asknot-ng
        # https://pagure.io/fedora-infrastructure/issue/5154
        # sops:
        #    - url goes here
          status_mappings: []
          description: >
            Ask not what Fedora can do for you, but what you can do for
            Fedora?  This site is a starting place for brand new
            contributors to help them figure out where they can
            hop on board!
      - name: Elections
        data:
          url: https://elections.fedoraproject.org/
          source_url: https://github.com/fedora-infra/elections
          bugs_url: https://github.com/fedora-infra/elections/issues
          docs_url: https://github.com/fedora-infra/elections/blob/develop/README.md
          sops: [https://infrastructure.fedoraproject.org/infra/docs/voting.rst]
          status_mappings: [elections]
          description: >
            As a member of the community, you can now vote for the
            different steering committees and for this you will use the
            Election application.  Voting is a right and a duty as a member
            of the community; it is one of the things you can do to
            influence the development of Fedora.
      - name: The Mailing lists
        data:
          icon: hyperkitty.png
          url: https://lists.fedoraproject.org
          source_url: https://gitlab.com/mailman/hyperkitty
          bugs_url: https://gitlab.com/mailman/hyperkitty/issues
          docs_url: https://hyperkitty.readthedocs.org/en/latest/
          sops: [https://infrastructure.fedoraproject.org/infra/docs/mailman.rst]
          status_mappings: [mailinglists]
          description: >
            Mailing lists are used for communication within the community.
            There are lists for generic topics and lists more dedicated
            to a specific topic, there is for sure one for you.
      - name: FedoCal
        data:
          icon: fedocal.png
          url: https://calendar.fedoraproject.org/
          source_url: https://github.com/fedora-infra/fedocal
          bugs_url: https://github.com/fedora-infra/fedocal/issues
          docs_url: https://fedocal.readthedocs.org/en/latest/
          sops: [https://infrastructure.fedoraproject.org/infra/docs/fedocal.rst]
          status_mappings: [fedocal]
          description: >
            The Fedora Calendar (or fedocal), you might
            have already guessed, is a public calendar service.  You can
            create your own calendar, or subscribe to others.  Want to
            be kept abrest of releases, freezes, and events?  This is
            the tool for you.
      - name: Meetbot
        data:
          icon: meetbot.png
          url: https://meetbot.fedoraproject.org
          source_url: https://github.com/fedora-infra/mote
          bugs_url: https://github.com/fedora-infra/mote/issues
          docs_url: https://github.com/fedora-infra/mote/blob/master/README.md
          sops:
            - https://infrastructure.fedoraproject.org/infra/docs/mote.rst
            - https://infrastructure.fedoraproject.org/infra/docs/zodbot.rst
          status_mappings: [zodbot]
          description: >
            Fedora Infrastructure runs a friendly IRC bot that you may
            know named zodbot.
            Among its many and varied functions is logging IRC meetings,
            the archives of which you can find here.
  - name: Packaging
    data:
    description: >
      Tools for packagers -- where the pieces of the distribution get
      built.
    children:
      - name: Packages
        data:
          url: https://packages.fedoraproject.org/
          package_url: https://apps.fedoraproject.org/packages/{package}
          source_url: https://pagure.io/fedora-packages-static
          bugs_url: https://pagure.io/fedora-packages-static/issues
          docs_url: http://threebean.org/blog/history-of-fedora-packages/
          sops:
            - https://infrastructure.fedoraproject.org/infra/docs/fedorapackages.rst
          status_mappings: [packages]
          description: >
            A meta-app over the other packaging apps; the best place to
            find out what is in the Fedora repositories.  Which
            packages are present in which version, who is maintaining
            them, what patches have been applied, what bugs have been
            reported against them. All these kind of questions can be
            answered here.
            It is sometimes called "Fedora Community v2" after the old
            Fedora Community
            site.
      - name: COPR
        data:
          icon: copr.png
          url: https://copr.fedoraproject.org
          user_url: https://copr.fedoraproject.org/coprs/{user}/
          source_url: https://github.com/fedora-copr/copr
          bugs_url: >
            https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&classification=Community&list_id=4767864&product=Copr&query_format=advanced
          docs_url: https://copr-backend.readthedocs.org/
        # Also:
        # - https://copr-keygen.readthedocs.org/
        # - https://copr-rest-api.readthedocs.org/
          sops: [https://infrastructure.fedoraproject.org/infra/docs/copr.rst]
          status_mappings: [copr]
          description: >
            Copr is an easy-to-use automatic build system providing a
            package repository as its output.  You can make your **own** repositories!
      - name: Koji
        data:
          icon: koji.png
          url: https://koji.fedoraproject.org/koji
          package_url: >
            https://koji.fedoraproject.org/koji/search?match=glob&type=package&terms={package}
          user_url: https://koji.fedoraproject.org/koji/userinfo?userID={user}
          source_url: https://pagure.io/koji
          bugs_url: https://pagure.io/koji/issues
          docs_url: https://koji.build/
          sops:
            - https://infrastructure.fedoraproject.org/infra/docs/koji.rst
            - https://infrastructure.fedoraproject.org/infra/docs/koji-builder-setup.rst
          status_mappings: [koji]
          description: >
            Koji is the software that builds RPM packages for the
            Fedora project.  It uses Mock to create chroot
            environments to perform builds that are both safe and
            trusted.
      - name: Bodhi
        data:
          icon: bodhi.png
          url: https://admin.fedoraproject.org/updates
          package_url: https://admin.fedoraproject.org/updates/{package}
          user_url: https://admin.fedoraproject.org/updates/user/{user}
          source_url: https://github.com/fedora-infra/bodhi
          bugs_url: https://github.com/fedora-infra/bodhi/issues
          docs_url: https://bodhi.fedoraproject.org/docs
          sops: [https://infrastructure.fedoraproject.org/infra/docs/bodhi.rst]
          status_mappings: [bodhi]
          description: >
            The tool you will use to push your packages to the Fedora
            repositories as an update, first an update to be tested
            (repository: updates-testing) then a stable update
            (repository: updates).  Behold -- the Magic
            Cabbage.
      - name: Package Sources
        data:
          icon: package-sources.png
          url: https://src.fedoraproject.org/
          package_url: https://src.fedoraproject.org/rpms/{package}
          source_url: https://pagure.io/pagure
          bugs_url: https://pagure.io/pagure/issues
          docs_url: https://pagure.io/docs/pagure/
          status_mappings: [pkgs]
          description: >
            Ever wonder exactly what is in the new release
            of a Fedora package?  This is where the change histories
            of all the packages in Fedora for every release of
            Fedora (and EPEL) are kept.. forever!  A gold mine.
      - name: Mdapi
        data:
          url: https://apps.fedoraproject.org/mdapi
          description: >
            mdapi is a small API exposing the metadata contained in
            different RPM repositories.
  - name: Upstream
    data:
    description: >
      Tools for upstream
      developers -- because we love you.
    children:
      - name: Release Monitoring
        data:
          url: https://release-monitoring.org
          package_url: https://release-monitoring.org/projects/search/?pattern={package}
          source_url: https://github.com/fedora-infra/anitya
          bugs_url: https://github.com/fedora-infra/anitya/issues
          docs_url: https://fedoraproject.org/wiki/Upstream_release_monitoring
        # TODO - write sops for anitya and the-new-hotness
        # https://pagure.io/fedora-infrastructure/issue/5157
        # sops:
        #    - https://infrastructure.fedoraproject.org/infra/docs/anitya.rst
        #    - https://infrastructure.fedoraproject.org/infra/docs/hotness.rst
          description: >
            Code named anitya, this
            project is slated to replace the
            old wiki page for Upstream Release Monitoring.  It will
            track upstream tarball locations and publish notifications to
            the fedmsg bus when new ones are found.  Other daemons will
            then be responsible for filing bugs, attempting to
            automatically build packages, perform some preliminary QA
            checks, etc..
      - name: Webhook to Fedora Messaging
        data:
          url: https://webhook.fedoraproject.org/
          source_url: https://github.com/fedora-infra/webhook-to-fedora-messaging
          bugs_url: https://github.com/fedora-infra/webhook-to-fedora-messaging/issues
          docs_url: >
            https://github.com/fedora-infra/webhook-to-fedora-messaging/
          sops:
            - https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/webhook2fedmsg/
          description: >
            Webhook to Fedora Messaging is a web service that bridges upstream
            activity into the Fedora Infrastructure message bus. Visit the self-service
            dashboard to add your application.
      - name: Pagure
        data:
          icon: pagure.png
          url: https://pagure.io/
          status_mappings: [pagure]
          description: >
            Pagure is a git-centered forge, python based using pygit2.
            With pagure you can host your project with its documentation,
            let your users report issues or request enhancements using
            the ticketing system and build your community of contributors
            by allowing them to fork your projects and contribute to it
            via the now-popular pull-request mechanism.
  - name: Infrastructure
    data:
    description: >
      Tools for sysadmins -- the people who run the servers that run
      Fedora (and otherwise).
    children:
      - name: GeoIP
        data:
          url: https://geoip.fedoraproject.org
          source_url: https://github.com/fedora-infra/geoip-city-wsgi
          bugs_url: https://github.com/fedora-infra/geoip-city-wsgi/issues
          docs_url: https://github.com/fedora-infra/geoip-city-wsgi/blob/master/geoip-city.wsgi
        # TODO - write a sop for this thing
        # https://pagure.io/fedora-infrastructure/issue/5159
        # sops:
        #    - https://infrastructure.fedoraproject.org/infra/docs/geoip.rst
          description: >
            A simple web service running geoip-city-wsgi
            that will return geoip information to you.
      - name: Easyfix
        data:
          url: https://fedoraproject.org/easyfix
          source_url: https://github.com/fedora-infra/fedora-gather-easyfix
          bugs_url: https://github.com/fedora-infra/fedora-gather-easyfix/issues
          docs_url: https://github.com/fedora-infra/fedora-gather-easyfix/blob/master/README
          sops:
            - https://infrastructure.fedoraproject.org/infra/docs/gather-easyfix.rst
          description: >
            A list of easy-to-fix problems for the different projects in
            Fedora.  Interested in getting into helping out with sysadmin
            work or web application development?  This should be useful
            to you.
      - name: DataGrepper
        data:
          icon: fedmsg.png
          url: https://apps.fedoraproject.org/datagrepper
          package_url: https://apps.fedoraproject.org/datagrepper/raw?package={package}
          user_url: https://apps.fedoraproject.org/datagrepper/raw?user={user}
          source_url: https://github.com/fedora-infra/datagrepper
          bugs_url: https://github.com/fedora-infra/datagrepper/issues
          docs_url: https://github.com/fedora-infra/datagrepper/blob/develop/README.rst
          sops: [https://infrastructure.fedoraproject.org/infra/docs/datanommer.rst]
          status_mappings: [fedmsg]
          description: >
            DataGrepper is an HTTP API for querying the datanommer
            database.  You can use it to dig into the history of the
            fedmsg message bus.  You
            can grab events by username, by package, by message
            source, by topic... you name it.
      - name: Status
        data:
          icon: status-good.png
          url: http://www.fedorastatus.org
          source_url: https://github.com/fedora-infra/statusfpo/
          bugs_url: https://github.com/fedora-infra/statusfpo/issues
          docs_url: https://github.com/fedora-infra/statusfpo/README
          sops:
            - https://infrastructure.fedoraproject.org/infra/docs/status-fedora.rst
          description: >
            Sometimes the Fedora Infrastructure team messes up (or
            lightning strikes our datacenter(s)).  Sorry about that.
            You can use this website to check the status.  Is it
            "down for everyone, or just me?"
Notice the favicon in your browser tab. It changes based on the status, so if you keep this open you can check back to it at a glance. - name: MirrorManager data: icon: downloads.png url: https://mirrors.fedoraproject.org source_url: https://github.com/fedora-infra/mirrormanager2 bugs_url: https://github.com/fedora-infra/mirrormanager2/issues docs_url: https://mirrormanager.readthedocs.org/en/latest/ sops: - https://infrastructure.fedoraproject.org/infra/docs/mirrormanager.rst - https://infrastructure.fedoraproject.org/infra/docs/mastermirror.rst - https://infrastructure.fedoraproject.org/infra/docs/mirrorhiding.rst - https://infrastructure.fedoraproject.org/infra/docs/mirrormanager-S3-EC2-netblocks.rst status_mappings: [mirrormanager, mirrorlist] description: > Fedora is distributed to millions of systems globally. This would not be possible without the donations of time, disk space, and bandwidth by hundreds of volunteer system administrators and their companies or institutions. Your fast download experience is made possible by these donations. The list on the MirrorManager site is dynamically generated every hour, listing only up-to-date mirrors. - name: Nagios data: icon: nagios-logo.png url: https://admin.fedoraproject.org/nagios source_url: https://github.com/NagiosEnterprises/nagioscore bugs_url: https://pagure.io/fedora-infrastructure/issues docs_url: https://www.nagios.org/documentation/ sops: [https://infrastructure.fedoraproject.org/infra/docs/nagios.rst] description: > "Is telia down?" The answer can most definitively be found here (and in detail). The Fedora Infrastructure team uses Nagios to monitor the servers that serve Fedora. Accessing most details requires membership in the sysadmin group. - name: Collectd data: icon: collectd.png url: https://admin.fedoraproject.org/collectd/ source_url: https://github.com/collectd/collectd bugs_url: https://github.com/collectd/collectd/issues docs_url: https://collectd.org/documentation.shtml sops: [https://infrastructure.fedoraproject.org/infra/docs/collectd.rst] description: > Tracks and displays statistics on the Fedora Infrastructure machines over time. Useful for debugging ineffeciencies and problems. - name: HAProxy data: url: https://admin.fedoraproject.org/haproxy/proxy1 source_url: https://git.haproxy.org/ bugs_url: https://www.haproxy.org/knownbugs-1.3.html docs_url: https://www.haproxy.org/#docs sops: [https://infrastructure.fedoraproject.org/infra/docs/haproxy.rst] description: > Shows the health of our proxies. How many bytes? Concurrent sessions? Health checks? - name: In Development data: description: > These are the apps that we're working on, but that aren't quite ready for prime-time yet. Try and use them, and report bugs when they're broken -- it's a big help!. Check back here from time to time, as this section will change. children: - name: Ipsilon data: url: https://pagure.io/ipsilon description: >- Ipsilon is our central authentication agent that is used to authenticate users agains FAS. It is seperate from FAS. The only service that is not using this currently is the wiki. It is a web service that is presented via httpd and is load balanced by our standard haproxy setup.