I request to create fedimg.fedoraproject.org. Right now the docs are hosted on http://fedimg.readthedocs.io/en/latest/ but we don't have access to build the latest docs there anyore. So, I request to create fedimg.fedoraproject.org where we can host the new docs and there would be no issues regarding maintaining ACLs
When do you need this? (YYYY/MM/DD) The quicker the better
When is this no longer needed or useful? (YYYY/MM/DD) As long as fedimg lives
If we cannot complete your request, what is the impact? We cannot host the latest docs for fedimg.
but we don't have access to build the latest docs there anyore.
Can't we fix this instead?
We tried, but had no luck.
I don't know that I would look for docs at fedimg.fedoraproject.org. I would expect the application to be there and have something like status or a dashboard or something.
Also, we aren't really setup to build and publish docs like that. We do have the websites, but it would need to be added to them and is not likely the way they are set up now.
We could try and use docs.fedoraproject.org/fedimg or something using the docs building stuff.
Or perhaps we could make a fedimg2 project in readthedocs?
Metadata Update from @kevin: - Issue priority set to: Next Meeting (was: Needs Review)
Out of curiosity, what's the blocker?
That's an idea, I guess hosting them on docs.pagure.io may also be valid.
We tried, but had no luck. Out of curiosity, what's the blocker?
No luck contacting the owner there or getting it reassigned. ;(
We could try and use docs.fedoraproject.org/fedimg or something using the docs building stuff. That's an idea, I guess hosting them on docs.pagure.io may also be valid.
Yeah, true. Our still is kind of all over the place. Might be nice to pick at least a primary and secondary, but I guess thats beyond the scope of this ticket. ;)
https://readthedocs.org/projects/fedimg/ now lists @sayanchowdhury as admin, so I assume this can be closed?
Metadata Update from @puiterwijk: - Issue priority set to: Waiting on Reporter (was: Next Meeting)
This got fixed upstream. ;)
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)