could we imaging changing the whole organization of fedora websites in Pagure?

It's worth talking about.

move "fedora-websites" as "fedora-web/websites-genshi"

I'm not necessarily opposed to this, but I'd rather just get the content migrated to the new framework and then retire this repo. We're working to find people who can do that.

move "fedora-docs/websites" as "fedora-web/docs"

Seems reasonable, if the docs team is okay with it.

rename "fedora-web/websites" as "fedora-web/getfedora.org-flask"

I don't like this suggestion. We can do one of two things: we can either put other sites in that repo as they move to Flask (in which case the rename is obviously wrong) or we can have a repo per-site, in which case I'd suggest naming it by the domain, and not the technology.

create "fedora-web/tickets"
move issues from "fedora-web/websites-genshi" and "fedora-web/getfedora.org-flask" as "fedora-web/tickets"

I'm strongly opposed to this. Having the issues and the code in the same repo is easier to work with.

rename the "fedora-web" group as "fedora-websites"

I'm not opposed to this, but I don't understand what the benefit is.

Thanks for your answers=2E

I'll only response about the ticket repository=2E

I assume the team work and on boarding is easier if issues are all in one =
place=2E
You only have to follow one project instead of many=2E
And whatever the request, you know where to ask/where to search=2E
And ticket triage/gardening sounds easier to me=2E

As an example, I opened two tickets related to Weblate migration and I am =
still confused about where to comment and why=2E My whole work is on the hi=
storic tracker and conversation started on the new tracker=2E

Hi, I am an Outreachy applicant and i wish to contribute to Fedora Project Websites. I therefore need some guidance as to which issue can I take up as my first issue.
I would like to like to look into this issue if not taken up and ready to be worked upon.

Hi, @specs all Outreachy interns for the March 2020 round have been asked to work on one task. Check out this resource http://bit.ly/2Qe4zHT for more details on the task and how to get started.

A lot of the organization of the sites will be easier once the subdomain sites are removed and replaced by getfedora.org pages. This is something we are working toward and after that this repository will be deprecated as @bcotton said. So I'm going to close this to bump it out of the queue. The confusing organization is something we're aware of and actively working to improve.