mattdm reported a new issue against the project: `fedora-websites` that you are following:
``
Putting this here in one ticket for reference:
* Fedora Workstation as normal
* Fedora Server: same, but will *also* include Fedora Cloud (but not Atomic/CoreOS)
* Fedora Atomic: no longer an edition. As I understand it, current version will be supported a little longer yet but we don't want to encourage new installs
* Fedora CoreOS: not _quite_ ready to be an edition, but we want to launch as an edition shortly after. (June?)
* Fedora IoT: also not quite ready to be an edition. Will be at https://iot.fedoraproject.org/. Also plan to launch as an edition in around June.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/946
catanzaro reported a new issue against the project: `fedora-websites` that you are following:
``
https://alt.fedoraproject.org/alt/ looks bad except at large window sizes. Here's a screenshot at 1169x1019 with the rendering of the download list clearly broken:
<!!image>
Here it is again a little bit wider, at 1291x1019. Now it looks OK:
<!!image>
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1023
bcotton reported a new issue against the project: `fedora-websites` that you are following:
``
Opened by @ankursinha as fedora-web/websites#71:
Hello,
The Comp-Neuro lab was accepted as a change for F32. We need to set up a page for it on labs.fp.o. How would we go about this please?
Cheers!
cc the neuro-sig @major @bt0dotninja @alciregi @mhough @zbyszek @sagitter @gicmo @blackfile @dan1mal @lbazan @sagitter @victortyau @sergiopr @terezahl @tanvi @sergiopr
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1010
adamwill reported a new issue against the project: `fedora-websites` that you are following:
``
Fedora 30 Final RC2 (RC-1.2) was the compose we signed off as the final release. Unfortunately, this compose was missing several images that failed due to download blips in the compose process. These include:
x86_64 Design Suite live
x86_64 Python Classroom live
x86_64 LXDE live
armhfp MATE image
armhfp LXqt image
and a few other less important ones. We have a plan to - as we have done a few times before - take nightly builds from composes after the Final packages are pushed stable (so the contents should be identical to the RC) and ship them alongside the RC contents in an 'unofficial' directory, and would like to ensure these images are linked from the download site.
This ticket is kinda intended to track this whole process, so tagging the relevant releng folks: @kevin @mohanboddu
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/951
jibecfed reported a new issue against the project: `fedora-websites` that you are following:
``
hello,
could we imaging changing the whole organization of fedora websites in Pagure?
Moving/renaming project is possible: https://pagure.io/fedora-infrastructure/issue/8237
My suggestion:
move "fedora-websites" as "fedora-web/websites-genshi"
move "fedora-docs/websites" as "fedora-web/docs"
rename "fedora-web/websites" as "fedora-web/getfedora.org-flask"
create "fedora-web/tickets"
move issues from "fedora-web/websites-genshi" and "fedora-web/getfedora.org-flask" as "fedora-web/tickets"
rename the "fedora-web" group as "fedora-websites"
at the end, we'll have:
fedora-websites/websites-genshi
fedora-websites/getfedora.org-flask
fedora-websites/docs
fedora-websites/tickets
I personally would find it easier to understand
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1018
Hello,
Can somebody from web team take a look at this.
Just to clarify, we don't need a web page, we just want to use a
fedoraproject.org URL as namespace name and make sure everybody is OK
with it.
Thank you
On 2/27/20 3:59 PM, Tom Callaway wrote:
> I would say if the web team is fine with it, that's all the approval
> you need.
>
> Tom
>
> On Thu, Feb 27, 2020, 8:37 AM Zdenek Veleba <zveleba(a)redhat.com
> <mailto:zveleba@redhat.com>> wrote:
>
> Hello,
>
> My team would like to open-source our testing tool for Anaconda.
> Currently it’s using our custom XML namespace with Red Hat URI. We
> think it would be best to change it to fedoraproject.org
> <http://fedoraproject.org>. Is there some kind of process for
> reserving/registering it for our tool? Or are we free coming up
> with some URI like:
> "http://fedoraproject.org/anaconda-testing/tool-name/recipe"
> <http://fedoraproject.org/anaconda-testing/tool-name/recipe> and
> using that as our namespace?
>
> Thank you.
>
> --
>
> Zdenek Veleba
>
> Quality Engineer
>
> Red Hat <https://www.redhat.com>
>
> Location: RH - Brno - TPB-C - 1C373
>
> <https://red.ht/sig>
>
> _______________________________________________
> legal mailing list -- legal(a)lists.fedoraproject.org
> <mailto:legal@lists.fedoraproject.org>
> To unsubscribe send an email to
> legal-leave(a)lists.fedoraproject.org
> <mailto:legal-leave@lists.fedoraproject.org>
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org
>
--
Zdenek Veleba
Quality Engineer
Red Hat <https://www.redhat.com>
Location: RH - Brno - TPB-C - 1C373
<https://red.ht/sig>
(Posting to many mailing lists for visibility. I apologize if you see
this more times than you'd like.)
You may have already seen my Community Blog post[1] about changing the
Release Readiness meeting process. The meeting has questionable value
in the current state, so I want to make it more useful. We'll do this
by having teams self-report readiness issues on a dedicated wiki
page[2] beginning now. This gives the community time to chip in and
help with areas that need help without waiting until days before the
release.
I invite teams to identify a representative to keep the wiki page up
to date. Update it as your status changes and I'll post help requests
in my weekly CommBlog posts[3] and the FPgM office hours[4] IRC
meeting. The Release Readiness meeting will be shortened to one hour
and will review open concerns instead of polling for teams that may or
may not be there. We will use the logistics mailing list[5] to discuss
issues and make announcements, so I encourage representatives to join
this list.
[1] https://communityblog.fedoraproject.org/fedora-program-update-2020-08/
[2] https://fedoraproject.org/wiki/Release_Readiness
[3] https://communityblog.fedoraproject.org/category/program-management/
[4] https://apps.fedoraproject.org/calendar/council/#m9570
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
bcotton reported a new issue against the project: `fedora-websites` that you are following:
``
As reported by @riecatnor:
1. Should be "Bronze", not "Silver" sponsor
2. Resize the logo to be the same height as other sponsors
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1020