#1636 centralizing default index.html (from httpd/nginx/etc)
Closed 7 years ago Opened 7 years ago by jcpunk.

= phenomenon =
With Apache and NGINX they ship a default "you've got a working webserver" welcome page. It features the Fedora branding(1), but is something that the package owners end up maintaining. Artwork may not change in concert with Fedora's artwork or branding guidelines.

This probably appears in other packages that ship a default "welcome to Fedora" screen as well.

= reason =
Most of the Fedora artwork and branding has been centralized into various packages owned by the Branding & Design teams(2).

This team helps keep the branding in sync with the current style guidelines.

= recommendation =
A place to keep Fedora Approved "welcome" pages - possibly curated by the Branding & Design teams. It could be an extra file in fedora-release or a separate rpm. In either case the packages could depend on the relevant source for the welcome page.

This has the added benefit of reducing the number of items listed at (1).

(1) and is noted on https://fedoraproject.org/wiki/Marketing/Branding

(2) fedora-logos, fedora-icon-theme, etc


As long as we do not revert to the "stock" working webserver pages, this makes sense. I do not miss the emails to legal@ complaining that we've "hacked" their website.

Tom, could you provide a little more detail there? What was the situation and how can we avoid it?

The pages as provided by upstream were worded in a way that non-technical people did not understand, all they knew was that their website which worked yesterday had reverted to that, and would pick Fedora out of it, and email everyone they could find related to Fedora complaining that we had hacked their website.

I reworked them to include clearer language that explained who Fedora was and that we had no access to their website (legitimate or otherwise).

Downstream distro, not Fedora, but a classic example of this problem: http://www.theregister.co.uk/2006/03/24/tuttle_centos/

Is the situation has been already resolved or anything to discuss here?

I do not believe this is resolved. The initial question is still pending: is centralizing the default welcome page something to be pursued?

I think this is a great idea. Wouldn't it make sense to move some or all of the items listed at https://fedoraproject.org/wiki/Marketing/Branding to subpackages of fedora-release or fedora-logos package?

Personally, I'd largely support rathann's proposal, but I'm not a fesco member.

Do we need to add the "meeting" tag to this issue, so that it makes it to the FESCo meeting agenda?

Do we need to add the "meeting" tag to this issue, so that it makes it to the FESCo meeting agenda?

Sounds good to me, but I'm not a fesco member.

I'm still not sure if there's a specific proposal that we'll be voting on in today's meeting (which I will miss, unfortunately). That being said, I'm in agreement with the basic sentiment of centralizing the page. Consider me a +1 if this comes up for vote today.

  * ACTION: Rathann to shepherd this effort  (sgallagh, 17:43:50)

Sounded like there wasn't anything further for fesco to do here.

Please re-open and add meeting tag if thats not the case.

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

7 years ago

Rathann was going to shepherd this, but I've not seen any changes in fedora-release or fedora-logos to address.

In lieu of this (or until it's implemented), are there any guidelines that webservers should follow for their individual welcome pages?

This is marked as Fixed, but I'm unable to find any information on the proposed fix. Is there a link I can review?

Metadata Update from @jcpunk:
- Issue close_status updated to: None (was: Fixed)

5 years ago

Metadata Update from @sgallagh:
- Assignee reset
- Issue tagged with: meeting

5 years ago

Login to comment on this ticket.

Metadata