Update website
by wolfzert .
Hello People,
Please provide an update of the website: http://fedoraproject.org/es/
because is still refering to Fedora 20 in the download section and
announcing the new 21th version, thanks in advanced for your help.
Best Regards, wolfzert.
9 years, 4 months
[fedora-websites] #248: New Fedora.next website
by fedora-badges
#248: New Fedora.next website
----------------------+-------------------------
Reporter: shaiton | Owner: webmaster
Type: defect | Status: new
Priority: blocker | Milestone: Fedora 21
Component: General | Keywords: fedora.next
Blocked By: | Blocking:
----------------------+-------------------------
The Project is moving to Fedora.next. The websites have to follow!
== Web tasks
* delete spins.fpo
* delete /using and /features
* delete /get-fedora-all
* edit get-fedora to feature the 3 products. As simple/smart as possible
(few text, short description, a link to DL and more descriptions
(fpo/<product>)
* keep 960gs or move to bootstrap? (bootstrap is less customizable)
== Infra tasks
* create {desktop, worstation, cloud}.fpo (redirect to fpo/<product>)
* redirect spins.fpo to desktop.fpo?
discussion is going on on the mailing list
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/248>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 4 months
[fedora-websites] #284: Fedora 21 website: TODOs
by fedora-badges
#284: Fedora 21 website: TODOs
----------------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: critical | Milestone: Fedora 21
Component: General | Keywords:
Blocked By: 248, 282, 283 | Blocking:
----------------------------+-----------------------
We have already some tickets for F21 (adding them as Blocker), but there
are many things we need to do before release date. This ticket is intended
as a TODO list to not forget anything before we build getfedora.org in
production. Please add anything to the list I might forget:
* Check all pages for missing I18n (also modals and other templates)
* clean up our app.css file of unused classes and add browser prefixes
* Pages need to be optimized for mobile, they are not really responsive
ATM
* Pulling po files works now for stg only. For production delete /var/lib
/transifex-client/.tx/config on bapp and execute (if needed)
syncTranslations.sh
* We need to add redirects in redirects.conf on puppet for
-- fedoraproject.org/verify [[br]]
-- fedoraproject.org/keys [[br]]
-- fedoraproject.org/get-fedora* [[br]]
* In our external release counter we have a link to the F21 release
banner, which won't work. Maybe we should redirect that too.
* add 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
* add AMI IDs, our script is ready for Atomic and Base IDs (contact
oddshocks)
* decide where to put Workstation and Minimal ARM images
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/284>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 4 months
Broken link for FC21 KDE spin
by Beeson, Ayden
Hey guys,
Sorry I'm not a member on this list so you may already know, apologies if that is the case.
The FC21 KDE spin download link (the download now at the top) is linking to the FC20 torrent.
The two below specific 32bit and 64bit links are both fine.
You can find it here:
https://spins.fedoraproject.org/kde/#downloads
I hope this is the right place to raise it....
Thanks,
Ayden Beeson B.InfoTech, CCNA
Technology Officer (Networks)
Division Of Information Technology
Charles Sturt University
P.O. Box 789
Albury NSW 2640
Ph :02 60519788
Fax:02 60519919
abeeson(a)csu.edu.au<mailto:abeeson@csu.edu.au>
www.csu.edu.au<http://www.csu.edu.au/>
[cid:csu-logo3a9e.bmp]<http://www.csu.edu.au/>
| ALBURY-WODONGA | BATHURST | CANBERRA | DUBBO | GOULBURN | MELBOURNE | ONTARIO | ORANGE | PORT MACQUARIE | SYDNEY | WAGGA WAGGA |
________________________________
LEGAL NOTICE
This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University (CSU) does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with CSU may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at CSU. The views expressed in this email are not necessarily those of CSU.
Charles Sturt University in Australia<http://www.csu.edu.au> The Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83 878 708 551; CRICOS Provider Number: 00005F (National)). TEQSA Provider Number: PV12018
Charles Sturt University in Ontario<http://www.charlessturt.ca/> 860 Harrington Court, Burlington Ontario Canada L7N 3N4 Registration: www.peqab.ca<http://www.peqab.ca>
[cid:anniversay797d.bmp]
Consider the environment before printing this email.
9 years, 4 months
fedup instructions on fedoraproject.org are incorrect
by Luke Hutchison
Hi,
The Network install instructions at
https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_Fed...
are incorrect -- "server" is not the correct fedup instruction in the
second step (I don't know what the correct fedup command is though):
Using a network source is the easiest method of upgrading and will pull in
updates while upgrading - eliminating the potential issue if your current
system has a newer kernel version than the Fedora release to which you are
upgrading.
1. Start the upgrade prep by executing following commands
- sudo yum update fedup fedora-release
- server
1. Once the preparations have completed, check the /var/log/fedup.log
file if any errors show up in the output from fedup
Also, the numbering restarts: "1." is shown twice. (Same for point 5 of
"Executing the upgrade".)
9 years, 4 months