[fedora-websites] #210: Should we re-organize download pages?
by fedora-badges
#210: Should we re-organize download pages?
--------------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: enhancement | Status: new
Priority: major | Milestone:
Component: get.fp.o | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
Our actual download pages are still remanends from older methods of
shipping Fedora. We had 6 or 7 CDs, spins and some netinstall CDs, but now
the arches and formats are much more and we are creating confusion. This
leads to misunderstandings and we are also not able to promote all the
arches the right way.
Actually we have 4 download pages on fp.o:
* get-fedora
* get-fedora-options
* get-fedora-all
* get-prerelease
and we have also http://spins.fedoraproject.org
My thought would be to:
* Drop the get-fedora-all page completely
* Avoid any kind of duplicates, i.e. some spins (the major ones) are
available on 2 or 3 pages. All spins should reside on spins.fp.o!
* Use the get-fedora page to promote all the shipping methods
The clearest method to do so IMHO would be to drop also the right random
banners we have on the sidebar (Desktop, 2nd-arches, Cloud, Spins) and to
put them into the get-fedora page.\\
They should link to the tabs in get-fedora-options or to our spins page
and give users a clear idea of what is available.\\
Same for get-pre-release: it would be easy to promote on the get-fedora
page, and we could also advertise it better on our main page.
If I can find some time after F19 GA I could give it a try, but if you
have concerns or ideas please let me know and comment.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/210>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
10 years, 4 months
[Fedora Infrastructure] #3796: remove _csrf_token from display URLs
by fedora-badges
#3796: remove _csrf_token from display URLs
--------------------------+-----------------------------
Reporter: till | Owner: webmaster
Type: enhancement | Status: new
Priority: major | Milestone: HANDWAVY-FUTURE
Component: Web Content | Version:
Severity: Normal | Keywords:
Blocked By: | Blocking:
Sensitive: 0 |
--------------------------+-----------------------------
= problem =
Several web-apps use a URL paramenter called _csrf_token to prevent CSRF
attacks. This token is shown in the URL location bar in browsers and makes
URLs ugly and might lead to people exposing their CSRF token in e-mails.
= analysis =
HTML5 allows to manipulate the contents of the URL location bar.
= enhancement recommendation =
Deploy JavaScript like
{{{
new_url = window.location.href.replace(/_csrf_token=[0-9a-f]{40}/,
"").replace(/(\?|&)$/, "");
history.replaceState({}, document.title, new_url);
}}}
to remove the CSRF token from URLs shown in Browsers.
This code might be adjusted to work in all browsers, but it works at least
in Firefox. Maybe a JavaScript expert can take a look. The only
disadvantage of this method is that going back in the history will reload
a page that requires to reload re-verify. But this might be solved by
storing the CSRF token in the history state. Also it does not seem to
cause really trouble.
--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/3796>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to our source code.
10 years, 4 months
[fedora-websites] #197: Should we create a schedule static page
by fedora-badges
#197: Should we create a schedule static page
--------------------------+-----------------------
Reporter: shaiton | Owner: webmaster
Type: enhancement | Status: new
Priority: major | Milestone:
Component: General | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
There is no easy way to know when our next Fedora will be released.
People should look for the right wiki page, and there could be frequent
updates.
I propose to design a simple page containing the main schedules (Alpha,
Beta and GA releases).
The data would be taken from the online official schedule (parsing as XML
I think). This would be shared by ou main fpo websites (for the countdown
banner..)
The content would be in fpo/get-prerelease and on a secondary page like
schedule.fpo? or just fpo/schedule?
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/197>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
10 years, 6 months
[fedora-websites] #167: spins: we need to update the screenshots, and make it nicer
by fedora-badges
#167: spins: we need to update the screenshots, and make it nicer
-------------------------+------------------------
Reporter: shaiton | Owner: webmaster
Type: defect | Status: new
Priority: critical | Milestone:
Component: General | Version:
Keywords: srceenshots | Blocked By:
Blocking: |
-------------------------+------------------------
we need to update many screenshots on the spins website.
Also, we need to make it easily maintainable, they should all be on a
specific folder, using the same overview/code (like kde Vs Xfce page). On
big pic and the other one smaller.
It could be great to reuse the on on the get-fedora-options fpo page.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/167>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
10 years, 9 months
Hello,
by Hicham Mallah
Hello,
I am Hicham Mallah, been using Fedora for 2 years now, I used Linux
(Ubuntu) long time ago for a long time, then I left it since Unity. I love
Fedora, and I hope I can help in some way. I am a web developer with 6
years of experience, my experience is more in PHP but I know Python and
hope will be learning more while helping. I am currently the CTO of
domainagents.com. I really hope I can find the time and way I can help out
an open source project that I love.
- - - - - - - - - -
Sincerely:
Hicham Mallah
Software Developer
mallah.hicham(a)gmail.com
00961 700 49 600
10 years, 9 months
[fedora-websites] #174: New website required for the Fedora Jam audio spin.
by fedora-badges
#174: New website required for the Fedora Jam audio spin.
------------------------+-------------------------
Reporter: bsjones | Owner: webmaster
Type: task | Status: new
Priority: major | Milestone: Fedora 18
Component: spins.fp.o | Version: Production
Keywords: | Blocked By:
Blocking: |
------------------------+-------------------------
This has been approved by the Spins team and the board for Fedora 18, but
has missed the deadline for release engineering to be included as part of
the official release media.
However, everything else is in place. Link to the nightly build rather
than the official spin ISO.
Content is laid out as per requirements here:
https://fedoraproject.org/wiki/Fedora_jam
(Included Packages section can be ommitted or left as a link addendum)
Thanks!
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/174>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
10 years, 9 months
Have Chat support on the fedora website.
by Sherry Jindal
Hey Folks,
Though fedora has IRC channels, but given the changing usage pattern, it
would be much useful to users if there was an on-website-IRC kind of
support, were users can discuss among themselves and get doubts resolved,
all from the website.
I am co-founder at Confaber (http://confaber.com), we provide exactly that
kind of service, it just needs two lines of HTML to be embedded on the
website. The service is completely free of cost.
We would request you to try out our service on the fedora website. We would
be happy to provide all kinds of support.
We are sure that this will be very beneficial to fedora users and
developers alike.
Do let me know if you need any other info.Hope to hear from you soon.
Sherry Jindal,
Co-founder and VP Marketing,
Confaber Inc
(http://confaber.com)
10 years, 9 months
