#351: Prepare websites for F23 Beta release
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: critical | Milestone:
Component: General | Keywords:
Blocked By: | Blocking:
Fedora 23 beta branch has been created (f23-beta) and is ready for working
All these 4 websites already have a prerelease page (or pages), but we
need to update them for the Beta release.
* update globalvar state and ID
* add beta banner for every website
* add CHECKSUMS and delete Alpha checksums
* check ALL links (DL, DOCS, footer)
* add image sizes for getfedora.org and spins.fp.o to our globalvar.py
* verify if all spins are build for GOLD RC, actually we have only 3 Alpha
spins in labs.fp.o
* add AMI IDs, our script is ready for Atomic and Base IDs - use the get-
ami.py tool for that, all IDs now are in the globalvar file
* build all websites in staging
* update/verify the news banner is pointing correctly to the Beta
Check all prerelease informations are displayed correctly for Beta
prerelease. We use a lot of variables there now, but we wrote the code
only for Alpha, so checking if it changes the state as expected is
necessary. Also, have a ''special'' look at cloud editions, paths and
images might change again.
Finally, we don't need to freeze translations for beta, but we should try
to get in contact with L10n teams because the percentage of translated
strings is very low :(
Beta release is scheduled for september 22th, pages should be ready at
least by thursday 17th.
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/351>
Fedora Website Team's Trac instance
Hello there, I just joined the team not long time ago and am a green newbie
in all such things. So I am looking for a mentor who could introduce and
teach me how a team works. Currently I do front end, so I wish I could find
a person who could train me with that as well.
Hello, my name is Malin, I'm a 1st year bachelor's student in Computer
Science currently studying at Kyiv Polytechnic Institute. I am a beginner
in web-development with a little experience in HTML/CSS, did over 20 PSD
templates using a bit jQuery. In the last life I was a member of tiny
web-projects, but had to stop that activity due to my entrance University
I want to join fedora project to get more experience and to have an
opportunity to take part in creating things which I really like (I am
talking about Fedora).
Now I am good only in HTML/CSS, but I am sure, that it is temporally. :)
#352: Minor update to the Fedora cloud text on getfedora.org
Reporter: ankursinha | Owner: webmaster
Type: task | Status: new
Priority: trivial | Milestone: Fedora 23
Component: getfedora | Keywords:
Blocked By: | Blocking:
The cloud SIG has made a minor change to the text on getfedora.org. As per
this ticket (https://fedorahosted.org/cloud/ticket/108#comment:10), they'd
like this to be the text:
"Fedora Cloud provides a minimal image of Fedora for use in public and
private cloud environments. It includes just the bare essentials making it
very light on resources, but you get enough to run your cloud
At the moment, it is:
"Fedora Cloud provides a minimal image of Fedora for use in public and
private cloud environments. It includes just the bare essentials, so you
get enough to run your cloud application -- and nothing more."
It's a very minor change :)
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/352>
Fedora Website Team's Trac instance
I have recently started using Fedora and am really excited to contribute to
something i love most.
I have worked on consolidating different webpages and also built some right
from the scratch
I have attached my Resumé.
I would really be glad to be on the Fedora Websites Team.
*Department of Mathematics*
So this idea came up in the netinstall download info thread ,
although I have been thinking offhand for a while it might be a good
idea for other reasons (eg enabling testers to find the test images more
easily - every time I need to find a test image I can never find it. :) )
I'd like to mock something up so we can visualize what this would look
like and if it would work, but I'm not 100% sure all of the
downloadtypes we'd want on there. I think the primary things listed on
the site should be those that are not featured on the main websites -
they are not editions, spins, or labs (although we can link out to those
To be able to mock this up though, I need to figure out what downloads
should be featured on the site, and we should probably talk about their
relative merits / use cases. Here is a (perhaps not exhaustive) list of
things we could list on this page:
- Netinstall ISOs (so these are built for specific editions, but this is
the one exception to featuring things not normally featured I think
would be a good idea)
- the minimal fedora image (it doesn't seem to have a home now?)
- docker containers
- Bittorrent torrent files (could just be a link to refer to torrent.fpo)
- Alternative architecture downloads
- Digging out dl.fpo / download.fpo / alt.fpo I found x86, aarch64,
ppc64, ppc64le, s390x, and s390 images.
- boot.fpo images
- testing images
- alpha / beta / tc / rc images
- archival images (could just point to archive.fpo)
- the everything DVD that lets you choose a desktop in syslinux that we
hand out at conferences (does this still exist?)
Am I forgetting anything?
Matthew Miller pointed me at this bug:
The OP had to drop back to a netinstall when he had a bad experience
with the KDE spin. If there are some problems with a spin, certainly
the responsible SIG can work on solving that. But in thinking about
the reporter's comments about finding netinstall: perhaps it would
make sense for the spin site to include an unobtrusive pointer to
Workstation or Server netinstall ISO. This might be analogous to the
Other Downloads section found on the Server and Workstation download
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
you did a great work, I really appreciate your help. I'm sure the design
implementation is completed, so we can work on the dynamic stuff you've
pointed out - like blog posts and search box.
To implement the header on the page.html template, we might need to write a
simple decorator to get the description. As you said, it doesn't make sense
to copy any texts all over.
I like the idea of DevAssistant banner as a rotation. We're thinking about
adding Vagrant and Docker.
Thanks a lot!
On Wed, Sep 9, 2015 at 9:56 PM, Máirín Duffy <duffy(a)redhat.com> wrote:
> On 07/29/2015 03:27 AM, Petr Hracek wrote:
>> sorry for bother you with this item but I would like to ask
>> you If you can thing about how Fedora Developer Portal could look like.
> I've worked the past couple of weeks or so on implementing the mockups 
> in html/css , and I think I'm at a point where it would be reasonable to
> turn it back over to you guys? What do you think?
> There are a few issues that I'm not sure of the best way to address -
> namely for the page.html layout, I'd like the title header to have the name
> of the top level section + the top level section's description + the icon
> that goes to the top level section. It seems wrong to copy/paste this
> information to the front matter of each of the subpages, but I'm not sure
> if there's some other data structure or way of accessing that data
> available to grab this info?
> The mockup I'm trying to make those pages look like is here:
> Other things that need doing:
> - All of the blog highlights / blog content on the front page is
> copy/pasta'ed from the RH developer website. It needs to be hooked up
> properly to an actual blog.
> - The Dev Assistant banner on the front page could be placed on other
> pages, and could be done as a rotation if you had other things you wanted
> to highlight.
> - The search box is fake too; I think it's not hooked up.
> Let me know what you think.
>  https://github.com/developer-portal/mockups
>  https://github.com/developer-portal/website
> env-and-stacks mailing list
Associate Software Engineer
This Thursday, we will meet on irc.freenode.net in #fedora-meeting-2
to make sure we are coordinated and ready for the Beta release of
Fedora 23 on Tuesday, September 22, 2015.
Please note that this meeting will occur even if the release is
delayed at the Go/No-Go meeting on the same day two hours earlier.
Please follow the [FedoCal] link to find the time of the meeting in
You may received this message several times as this meeting is opened
to all teams. I also hope this will raise awareness and more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
Thanks for attending,
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
I've tried fedora a few times over the years. I recently met Remy
(fedora community lead) at oscon and he convinced me to give it
another try and give some feedback. This is meant to be constructive,
just my impression, I could be missing things.
I google "fedora firewall", because I'd like to learn generally about
it, how to do a few common things like opening a port, or forwarding
something. I see links to official fedora docs. So I think, yes, lets
2.8.2. Basic Firewall Configuration - Fedora Documentation
(click link, it's fedora 11 doc)
3.8.13. Configuring the Firewall - Fedora Documentation
(click link, it's fedora 19 doc)
3.8.9. Disabling firewalld - Fedora Documentation
(click link, it's fedora 20 doc)
16.7. Firewall Configuration - Fedora Documentation
(click link, its fedora 20 doc)
So... now I really want to know if fedora 22 doc has a section on
I see the url's all look like this:
so I try changing the 19 to 22, but it takes me to
So then I look for a search feature. I don't see one. So then I expand
the fedora 22 drop down, and I see 7 high level categories with no
obvious right place, so now I'm fairly confused as to how to find
So I search firewall on google
site:https://docs.fedoraproject.org/en-US/Fedora/22. And the closest
thing I see is the #1 link, 14.15. Configure the Firewall to Allow
Incoming NTP Packets. But I'm wondering if there is a general section
like link 2 or link 3 from the original google search, so I click around
some more, I figure there are 4 of the 7 sections in the sidebar which
could cover firewall: installation guide, networking guide, selinux
users and administrators guide, and system administrators guide. So I
click on administrators guide, (and I'm slightly surprised to find a
comprehensive table of contents, as the ui design of left menu sort of
implied that it was THE table of contents, not that there was more
useful list of sections within. Why couldn't I see those things in the
expandable menu?). I do a word search, find the ntp related link I saw
before, repeat for the other 3 sections, find one in the installation
section which looks generic, only learn that installation has a limited
set of firewall configuration options and this is not what I'm looking
for. So I'm deciding there is no general firewall documentation for 22.
So now I look back at the best link I originally found,
and I think, yes, I'm confirming my original impression that this is
really the kind of documentation I was looking for, but I'm really
confused and frustrated: does any of this still apply? did they abandon
firewall-config? What's the story?
I've had this same experience several times with fedora, and at this
point I've mostly given up frustrated and annoyed.
Once, when I was feeling a bit more ambitious, I thought. Hmm, maybe I
can help out on docs, cuz I have noticed the new links like "click to
contribute to fedora!" So click through, quickly get to this page:
Well, after 15 minutes of reading lots of stuff I'm not interested in, I
can't find the source code to the fedora 22 official docs, or anything
about how to improve them, and I think, I'd have gotten way more done
by just going to the arch wiki firewall page, and I could have just hit
edit and improved the thing.
Suggestions: make previous fedora version documentation link to the
relevant current documentation because google links to old docs are the
reality for most fedora searches, or if there is no newer, say that, and
say whether this is still relevant to newer distros. And port
documentation forward, it seems there is lots of good documentation
sections which only exist for older fedora versions. Make contributing
to the official docs possible in some short amount of time. Make a
search feature (this is 2015), even if it's just to some 3rd party
search engine (google site search gave me good results).
Oh, and how about filing a bug? First google link: "How to file a bug
report - FedoraProject"
https://fedoraproject.org/wiki/How_to_file_a_bug_report It's like a
horribly bad novel when I wanted a tldr for any reader who's filed bugs
before for free software projects and wants to file one for fedora:
Up top, "Documentation Summary:", doesn't try whatsoever to summarize
"how to file a bug report", but just talks about meta things about the
document, complete waste of my time.
1st section after the fake summary: "How to File a Bug Report", first
sentence: "This page describes a procedure for reporting software bugs
to Fedora developers." Well, I'm not a fedora developer, so this isn't
for me? Well, I don't see any other way to file a bug sooo, does fedora
accept bug reports from it's users? And it's redundant, making it just
bad quality writing, leaving a bad impression, and making me think no
one actually reads or improves this page. Significant chunk of new users
are giving up at this
Ok, this is a wiki, so let's try and edit this page. Click log in, which
leads to this page this page:
which is a novel length page which as far as I can see does not actually
lead to getting a wiki account! No wonder no one edited the page,
creating a wiki account if a total nightmare! Suggestion: fix that.
Ok, flash back to the filing a bug wiki page. Next sentence: 'A bug is
defined as "an error, flaw"'..., am I doing a homework assigment? This
document is called "how to file a bug report", not spend an hour reading
wikipedia. Ok, next sentence says this is about
https://bugzilla.redhat.com/, let's skip to the chase and try using
that, because the rest of this document looks pretty useless.
Go there, and see from the 1st sentence.: "Thank you for visiting Red
Hat Bugzilla. Red Hat Bugzilla is the Red Hat bug-tracking system and is
used to submit and review defects that have been found in Red Hat
distributions." Ok, so am I at the wrong place? This is confusing. Is
fedora a "a red hat distribution"? I skim
a bit more... "If you are a Fedora Project user and require assistance,
please consider using one of the mailing lists we host for the Fedora
Project. " Well, I'm filing a bug to get "assistance" in it being fixed,
so it seems I should post it on the mailing list instead?
So, wondering if fedora is a red hat distribution, I remember that there
is a link on the main fedora page "Learn more about the relationship
between Red Hat and Fedora »." So I go there. It's not very helpful, its
not well written to stand on it's own. The first section goes like this
"jill makes pizza for anyone. John makes pizza for big companies. People
go to jill in order to collaborate with john. Businesses love john's
pizza. The end. (notice a gaping hole? Why would someone go to john in
order to collaborate with jill? And tt's pretty relevant title of the
page.). Anyways, this one is a minor gripe compared to the rest, but my
suggestion is to replace it with a higher quality fedora domain page,
which includes a link to the red hat page.