#9882 [Pagure] [database] Change group name/ID from "WebDev SIG" to "Websites & Apps"
Closed: Insufficient data 3 years ago by kevin. Opened 3 years ago by jflory7.

Describe what you would like us to do:


The Fedora WebDev SIG is now the Fedora Websites & Apps Team. This is the evolution of the Fedora Websites team. We need to change our Pagure namespace from sig-webdev to websites-apps. The group membership and repository access remains the same.

https://pagure.io/group/sig-webdev

When do you need this to be done by? (YYYY/MM/DD)


2021-04-23.

Our team meets weekly and we need to standardize the URLs we share since we agreed to work from Pagure. We meet weekly on Fridays, so before our next weekly meeting would be helpful.


Note that if this is done, it will break every link and git clone that are out
there.

It will need to be done in the DB itself as well as have the repository moved at
the filesystem level.

I acknowledge the broken HTTP URL and that local git remotes will need to be updated. We are OK with it breaking, since we have not fully established our work yet (finalizing our name enables us to move forward with using Pagure).

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

3 years ago

Why not create a new group and migrate repositories? At leas for a while it wouldn't break anything.

Metadata Update from @asaleh:
- Issue untagged with: low-trouble, medium-gain, ops
- Issue priority set to: Needs Review (was: Waiting on Assignee)

3 years ago

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

3 years ago

The old namespace should no longer exist. The name was a source of confusion and it is easier to not have it as leftover "community cruft."

@jflory7 I'm not sure I understand your last comment, is there anything you'd like us to do?

@pingou wrote…
@jflory7 I'm not sure I understand your last comment, is there anything you'd like us to do?

Now I am confused. :sweat_smile: Are you asking me if there is more I would like done than what was described earlier in the ticket?

@pingou wrote…
It will need to be done in the DB itself as well as have the repository moved at the filesystem level.

A good first step for @jflory7 here, might be to do the following (@pingou please advise if this is a bad idea :) )

  1. Create a new Group / Namespace "websites-apps" ("Websites & Apps"), which will create the websites-apps namespace
  2. Add the new websites-apps group as a member to all the repos you want in the websites-apps namespace, there are a few around, in the fedora-web group in the sig-webdev.

once this is done, we can go though that list, and decide what to change the namespaces and or the reponames to, and make a plan for the pagure admins to change them.

I assume the following repos are on the list to add to a namespace and or renamespace / rename:

  • fedora-docs/websites
  • UNNAMESPACED/fedora-websites
  • UNNAMESPACED/ui-patterns
  • fedora-web/translations
  • fedora-web/websites

after all this, the fedora-web and sig-webdev groups are removed, leaving only just websites-apps group with something like the following namespaced repos in the group:

  • websites-apps/docs (renamed repo from fedora-docs/websites)
  • websites-apps/fedora-websites
  • websites-apps/ui-patterns
  • websites-apps/translations
  • websites-apps/websites

Hey, thanks for being patient. The instructions above make sense. I will work on completing this by this coming Monday (28 June).

@ryanlerch wrote…
Create a new Group / Namespace "websites-apps" ("Websites & Apps"), which will create the websites-apps namespace

This is done: https://pagure.io/group/websites-apps

@ryanlerch wrote…
Add the new websites-apps group as a member to all the repos you want in the websites-apps namespace, there are a few around, in the fedora-web group in the sig-webdev.

I added the repositories I have access to, which are two:

  • fedora-docs/websites
  • sig-webdev/home

@ryanlerch wrote…
once this is done, we can go though that list, and decide what to change the namespaces and or the reponames to, and make a plan for the pagure admins to change them.

Let me know if any more work is needed on my side. I appreciate the time for handling this request!

@ryanlerch wrote…
after all this, the fedora-web and sig-webdev groups are removed, leaving only just websites-apps group with something like the following namespaced repos in the group:

This looks correct to me.


FYI: @riecatnor @ramyaparimi @t0xic0der

@ryanlerch I got info from @pingou on how to move projects in the db.

Lets touch base soon on this and see if we can get it done?

sorry @kevin @jflory7 missed these updates somehow.

lets see if we can get this sorted :)

okay, added all of these to the websites-apps group other than:

https://pagure.io/fedora-websites

didnt have access to be able to add it -- you are admin on there now @jflory7

i ahve been giving the group the commit priv

okay, added all of these to the websites-apps group other than:

https://pagure.io/fedora-websites

didnt have access to be able to add it -- you are admin on there now @jflory7

i ahve been giving the group the commit priv

I have added that one with commit priv

@jflory -- the first one we probably want to get the namespace changed for is

https://pagure.io/sig-webdev/home

right?

one thing i wanted to check on that is are those docs that are in the home repo automatically published on docs.fp.o? if so we will probably have to change whatever that points to

@jflory7 -- just wondering what we want to do with this one since gitlab is now a thing -- keep working on trying to fix all these projects/namespaces?

or work on migrating the repos to gitlab?>

It's been 3 months here, so we are going to go ahead and close this.

However, if you still need/want this, please reopen or file a new ticket and we will be happy to move it forward.

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

3 years ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog