[Fedora Infrastructure] #5184: update icons for admon/warning and
admon/important on wiki
by fedora-badges
#5184: update icons for admon/warning and admon/important on wiki
--------------------------+-----------------------------
Reporter: duffy | Owner: webmaster
Type: task | Status: new
Priority: minor | Milestone: HANDWAVY-FUTURE
Component: Web Content | Version:
Severity: Normal | Keywords: wiki
Blocked By: | Blocking:
Sensitive: 0 |
--------------------------+-----------------------------
the icons for admon/warning and admon/important are the same, and commops
requested we use different icons. i've attached two Tango (public domain
license) icons to use - can these be set up to replace the existing ones?
This requires wiki admin privs.
--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/5184>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to our source code.
8 years, 1 month
[Fedora Infrastructure] #5140: Wiki editing via API failing when
captcha has to be solved
by fedora-badges
#5140: Wiki editing via API failing when captcha has to be solved
--------------------------+-----------------------
Reporter: adamwill | Owner: webmaster
Type: bug | Status: new
Priority: major | Milestone: asap
Component: Web Content | Version:
Severity: High | Keywords:
Blocked By: | Blocking:
Sensitive: 0 |
--------------------------+-----------------------
Well this is odd. My 'wikitcms' project has a bit of code for handling the
captcha system we have on the wiki. It's been working fine for years.
Suddenly, it seems like it's not working any more. When I try and make an
edit that requires a captcha solve with wikitcms, it fails.
I have verified six ways from Sunday that wikitcms is parsing the question
correctly, producing the correct answer, and sending the correct params
back to mwclient - 'captchaid' and 'captchaword'. I have even stuck a
couple of log lines in mwclient to check that 'captchaid' and
'captchaword' are in the params it sends along to the mw API, and they
are.
I have tried with old versions of both wikitcms and mwclient - old
versions I know were working, because we got validation events for the
last couple of months - and no dice. So *something* must have changed
outside of wikitcms and mwclient, and I wanna say it's on the server end,
but I don't see any huge changes in
https://fedoraproject.org/wiki/Special:Version , and I get the same errors
from both stg and prod wiki.
So...what the hell gives?!
This is a major issue because relval can't create release validation pages
ATM.
--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/5140>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to our source code.
8 years, 1 month
[Fedora Infrastructure] #5171: wiki will not let 'coconut' log in
by fedora-badges
#5171: wiki will not let 'coconut' log in
--------------------------+-----------------------
Reporter: adamwill | Owner: webmaster
Type: bug | Status: new
Priority: critical | Milestone: asap
Component: Web Content | Version:
Severity: High | Keywords:
Blocked By: | Blocking:
Sensitive: 0 |
--------------------------+-----------------------
'coconut' is the account we use for reporting openQA results to the wiki.
However, the wiki seems to refuse to allow coconut to log in at present.
Contact me via IRC or email for the account password. I can log into FAS
just fine using the same password; logging into the wiki shows the error
"You have entered an invalid username and password. If you are certain
that your username and password are correct, confirm that you can log in
to the Fedora Account System (https://admin.fedoraproject.org/accounts/)
and that you have signed the CLA.". coconut has signed the CLA.
this is a major problem because it prevents automatic openQA result
transfer to the wiki pages; I have to hack things up manually to report
the results with my account but have them show up with 'coconut' as the
user.
--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/5171>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to our source code.
8 years, 1 month
Fedora 24 Alpha Release Readiness Meeting, Thursday, March 17 @ 19:00 UTC
by Jan Kurik
Join us on irc.freenode.net in #fedora-meeting for the Fedora 24 Alpha
Release Readiness Meeting meeting.
The meeting is going to be held on Thursday, March 17, 2016 19:00 UTC.
Please check the [FedoCal] link for your time zone.
We will meet to make sure we are coordinated and ready for the Alpha
release of Fedora 24 on Tuesday, March 22nd, 2016. Please note that
this meeting is going to be held even if the release is delayed at the
Go/No-Go meeting on the same day two hours earlier.
You may received this message several times, but I was asked to open
this meeting to the teams and I'll 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.
[FedoCal] https://apps.fedoraproject.org/calendar/meeting/3336/
Thank you for your support and Regards, Jan
More information available at:
https://fedoraproject.org/wiki/Release_Readiness_Meetings
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
8 years, 1 month
Re: Guidelines and objectives about Fedora tools and translation
by Robert Mayr
2016-03-06 18:06 GMT+01:00 Jean-Baptiste <jean-baptiste(a)holcroft.fr>:
> Hi there,
>
> [snip]
>
> As a new contributor, I was a bit confused about the many websites and
> tools of Fedora, because some are homemade others where use as SaaS
> solutions and didn't really know how to navigate from one to another, nor
> understood if translation was missing because the software didn't support
> it or because of the lack contributors.
>
> I made a list of every websites I found :
> https://fedoraproject.org/wiki/G11N/List_of_Fedora_sites
Some of these websites are outdated, others are missing in your list.
Others are not maintained by the websites team, but generally speaking when
it comes to I18n we should clearly split apps and websites, as these are
different groups and workflows.
> The status is not very good :
> * some websites are not translated (ex : developer.fedora)
>
developer.fp.o is kind of "hosted" by the websites team, and we had some
discussions in the past with its maintainers if we want to include I18n or
not. It is still a very new project, and we agreed to not do any
translation for now as soon as we don't know how much this webapp is used
by developers. Probably we can add translation markups later, but it is not
a priority in this specifical moment.
Another website we do not translate is fudcon.fp.o, which is rather old and
we will probably drop/rewrite/update it soon, also with I18n. All the other
websites *are* set up for I18n, also our latest ones, which are:
* flocktofedora.org
* budget.fedoraprojedct.org
You will find the sources on zanata, but they are still closed, because we
don't have final strings for these websites. I will open them soon and send
out an update to the trans ML.
> * many sites don't have the Fedmenu button to help navigation
>
I don't understand what you mean here, navigation is easy using the footer,
within websites. We don't link to apps, this is not a function we need on
the websites. If you like to have links to all our apps, you can go to
apps.fedoraproject.org.
> * most of tools are not translated
>
This is an Infra topic, but let me throw in another question: are we able
to translate the changing contents of all our apps?
>
> It was pretty much expected, but now, how do we fix this ?
>
My answer actually is: by translating what we have :)
Just an example: our main website (getfedora.org) is 100% translated by
only 6 local teams! Only 14 local teams reached more than 80%.
Spins.fp.o is even worse, only 3 teams reached 100% and only 7 teams have
translated more than 80%, only 8 teams more than 70%.
Personally I think we should first concentrate the activity towards the
strings we have, and they are on the main websites. Otherwise we would add
more and more strings, but if translation teams already have difficulties
with the actual websites, it would become worse. Unfortunately L10n teams
have so much to translate (docs, software, web, apps...) we probably need
more hands to get the work done.
>
> The work is huge, so we need to make a little bit of planning.
> What are the guidlines we would like to have for websites and tools ?
>
Here I can give just a personal opinion. I would make a list of the main
websites and put them on a TODO list for every new release cycle; that
means other stuff would get a lower priority. Some teams already do that
internally, but it's a good practice if you would say: first of all let's
get getfedora.org, spins.fp.o, labs.fp.o and arm.fp.o translated, even
start.fp.o as the default website for Firefox and Chromium is important
IMHO.
This kind of setting priorities to all L10n members could help to go into
the right direction.
>
> We also have to agree between trans/infra/website teams and be realistic :
> none of our groups can handle and objective like 100% of websites and tools
> have to be internationalized and translated.
>
True.
>
> Anyone would like to help us writing and then discussing this between
> #trans, #infra and #websites ?
>
> Subjects are :
> * global guidelines
> * short term objectives (2016)
> * mid-term objectives (2017)
>
>
Hopefully we have someone from the websites team who can help you here, I
have too many things on my plate actually.
> Sincerely,
> --
> Jean-Baptiste Holcroft
>
Thanks for taking care of this.
Best.
--
Robert Mayr
(robyduck)
8 years, 1 month
New websites repository created on pagure: RECLONE PLEASE!
by Robert Mayr
Hi,
after some tests and discussions about the best way of creating our new
websites repository on pagure, I've just created a new project:
https://pagure.io/fedora-websites
The repository went down from uncompressed 890MB to 180MB as desired and
cloning it should be pretty fast now;
IMPORTANT: ALL GITFEDORA-WEB MEMBERS NEED TO RECLONE THE REPO!!!
git clone ssh://git@pagure.io/fedora-websites.git
If you never logged in to pagure, please do so and let me know, in order to
add you to the group with commit access to the repository. Actually we have
two branches, master and f24-alpha.
In the next days I'll add the source files of the documentation I wrote so
far, so anyone can also contribute there.
The workflow for the next weeks is a bit awful, but it will not last too
much. Websites are still build from the fedora-web repository on
fedorahosted, but we will test the build from pagure with the staging
websites, as soon as we have something new in that branch.
For any changes on the master branch we need to sync them out manually, so
please push to fedora-web, but do your fixes also in fedora-websites on
pagure (I have choosen a different name because it's better to not mix the
two repos up, they are very different actually).
To avoid this double coding we should try to not push anything to
production right now, unless it is "very" important. If we can wait with
the changes until F24 Alpha, let's do so.
Please ping me or drop me a message if you have any doubts or questions, I
will try to update this post anytime something is changing in our workflow.
We will also need to update the wiki...
Thanks.
Kind regards.
--
Robert Mayr
(robyduck)
8 years, 1 month
Guidelines and objectives about Fedora tools and translation
by Jean-Baptiste
Hi there,
I'm working in translation team, and did a job about the current status
of translation of our tools and publication sites.
As a new contributor, I was a bit confused about the many websites and
tools of Fedora, because some are homemade others where use as SaaS
solutions and didn't really know how to navigate from one to another,
nor understood if translation was missing because the software didn't
support it or because of the lack contributors.
I made a list of every websites I found :
https://fedoraproject.org/wiki/G11N/List_of_Fedora_sites
The status is not very good :
* some websites are not translated (ex : developer.fedora)
* many sites don't have the Fedmenu button to help navigation
* most of tools are not translated
It was pretty much expected, but now, how do we fix this ?
The work is huge, so we need to make a little bit of planning.
What are the guidlines we would like to have for websites and tools ?
We also have to agree between trans/infra/website teams and be realistic
: none of our groups can handle and objective like 100% of websites and
tools have to be internationalized and translated.
Anyone would like to help us writing and then discussing this between
#trans, #infra and #websites ?
Subjects are :
* global guidelines
* short term objectives (2016)
* mid-term objectives (2017)
Same message in trans@ :
https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.o...
Sincerely,
--
Jean-Baptiste Holcroft
8 years, 1 month
