fedora-infrastructure

#12900 [Forgejo] New Organization and Teams Request: Mobility
Closed: Fixed by ryanlerch. Opened by samcday.

Closed: Fixed
Reopen Issue

Hi infra team,

We’d like to request a new organization and team on https://forge.fedoraproject.org for the Fedora Mobility SIG.

New Organization Details:

  • Desired Organization Name (Short Name): mobility
  • Full Name of Organization: Fedora Mobility SIG
  • Fedora Accounts Group for Organization Owners: mobility-sig
  • Website URL: https://fedoraproject.org/wiki/Mobility
  • We do not have our own logo at this time.

Description

The Fedora Mobility SIG is working on better support for mobile devices (smartphones & tablets) in Fedora.

We're focusing on a small number of devices (PinePhones and a handful of Snapdragon-based) for now. We're making and contributing packaging, kernel enablement and image generation changes necessary for official Fedora releases to (eventually! hopefully!) be usable on these devices.

New Team Details (within 'mobility' organization):

Fedora Remix Mobility

  • Target Organization Name: mobility
  • Team Name: remix-mobility
  • Desired Permission Level in Forgejo: Write
  • Fedora Accounts Group to Map to Team: mobility-sig
  • Include all repositories?: No. Some repos that end up under the mobility org will not be relevant to the Remix effort. We'll manage the team ACLs on our repos manually.

(Yes, I'm aware that the same FAS group is being used to own the whole org, and for the Remix team. We don't currently have clear distinctions between the two initiatives. If/when necessary I'll sort out a separate FAS group. For now I think, and hope, it's okay to overlap them like this)

Description

This team is working on building and distributing a Fedora Remix that can (live) boot on SDM845/SDM670 devices. The changes we make in this "as-close-to-upstream-as-possible" downstream will be proposed upstream once stabilized and validated.

Thanks in advance!
– Sam (on behalf of Fedora Mobility SIG)

Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

Hi, thanks for filing your request!

Just one quick note -- we are typically trying to keep the group names we use for forge teams to a specific naming scheme: (see https://docs.fedoraproject.org/en-US/forge-documentation/fas_group_naming_standards/)

can i suggest this structure:

  • forge-mobility-ownersFAS Group -> Owners team on Forge. -- admin access all repos
  • forge-mobility-membersFAS Group -> Members team on Forge -- write access all repos
  • forge-mobility-remix FAS Group -> Remix team on forge -- write access to select repos

I can make these FAS groups for you too -- all i need for those are the list of sponors for the fac group, you can add the members.

Sounds good to me @ryanlerch

Let's start with these sponsors for the groups:

  • forge-mobility-owners: @kevin
  • forge-mobility-members: @samcday + @lihis + @alho + marcin
  • forge-mobility-remix: @samcday + marcin

... Since you're already looking at this I won't edit the original request, but could I please sneak in an addendum here:

New Team Details (within 'mobility' organization):

Pocketblue

Target Organization Name: mobility
Team Name: pocketblue
Desired Permission Level in Forgejo: Write
Fedora Accounts Group to Map to Team: `forge-mobility-pocketblue`
Include all repositories?: No

Description

This team is working on building and distributing a Fedora Remix to bring Atomic Desktop support to mobile devices.

The initial sponsors for this forge-mobility-pocketblue group should be: onesaladleaf + gmanka

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: forgejo_migration, medium-gain, medium-trouble

Metadata Update from @zlopez:
- Issue untagged with: medium-gain, medium-trouble
- Issue tagged with: low-gain, low-trouble

Thanks for using Fedora Forge!

I have:

  1. Created the forge-mobility-owners Fedora Accounts group with the following:
    • Fedora Accounts Sponsors: @kevin
    • Fedora Accounts Members: @kevin @samcday
  2. Created the forge-mobility-members group with the following:
    • Fedora Accounts Sponsors: @samcday + @lihis + @alho + marcin
    • Fedora Accounts Members: @samcday + @lihis + @alho + marcin
  3. Created the forge-mobility-remix group with the following:
    • Fedora Accounts Sponsors: @samcday + @marcin
    • Fedora Accounts Members: @samcday + @marcin
  4. Created the forge-mobility-pocketblue group with the following:
    • Fedora Accounts Sponsors: @onesaladleaf + @gmanka
    • Fedora Accounts Members: @onesaladleaf + @gmanka
  5. Created the new mobility organization on Fedora Forge -- https://forge.fedoraproject.org/mobility/
  6. Added 4 teams to the new mobility org:
    • Owners -- https://forge.fedoraproject.org/org/mobility/teams/owners
    • Members -- https://forge.fedoraproject.org/org/mobility/teams/members
    • Remix -- https://forge.fedoraproject.org/org/mobility/teams/remix
    • Pocketblue -- https://forge.fedoraproject.org/org/mobility/teams/pocketblue
  7. Updated the teams mapping so the Fedora Accounts teams map, and on next login any users in the Fedora Accounts groups will be granted access to the mapped teams in Fedora Forge.
  8. Changed the avatar to the fedora logo.

Next Steps
1. Update the settings for your org, including the details like description etc -- https://forge.fedoraproject.org/org/cloud/settings
2. Review the permissions for each team, and add the repos to that team.
2. File a request for an icon with the design team to use as your avatar here on forge: https://gitlab.com/fedora/design/team/requests/-/issues
3. Add a profile page for your organization: https://docs.fedoraproject.org/en-US/forge-documentation/create_org_profile_page/
4. Migrate from Pagure: https://docs.fedoraproject.org/en-US/forge-documentation/migration/pagure_repository/

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

Thanks @ryanlerch :tada:

This is closed already but the issues from https://pagure.io/fedora-mobility/issues were not migrated? Were they intentionally left behind? Ping @ryanlerch and @samcday

This is closed already but the issues from https://pagure.io/fedora-mobility/issues were not migrated? Were they intentionally left behind? Ping @ryanlerch and @samcday

My understanding is that we can migrate whatever we please now using Forgejo's migration tools. Fedora Forge has first class support for migrating from Pagure, I assume issues will be included: https://docs.fedoraproject.org/en-US/forge-documentation/migration/pagure/

Thanks! Migrated https://pagure.io/fedora-mobility to https://forge.fedoraproject.org/mobility/issues
Metadata

forgejo_migration low-gain low-trouble

None
None
Normal
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.