I have created wiki page for reference and add this in 'Task' page as
This should be updated asap basis, however decent review -> modification
-> proofreading are needed before final. Any particular date/event that
can be a target as appropriate due date? Any one who can involve any
stage of this update? Anything have I missed out?
The "About this Computer" item was added to the System menu in Rawhide
on March 8. It's provided by about-this-desktop.desktop, in the
gnome-system-monitor package. As it wasn't added in any of the PO files
and it needs to be localized, developer of this package has provided a
facility to translate this message into the local language directly on
the web page.
Screenshot of the untranslated message taken from Punjabi desktop:
*Here is the URL where you can put your translations*:
- When you visit this URL, you can find it already translated into some
languages. If you find it's not translated into your language, you can
add your translation.
- We need to translate two things, Name and Comment both.
- Make sure you put your translations in "Name[de]=Über diesen Computer"
and "Comment[de]=Erhalten Sie Basis-Informationen über dieses System"
format, where you have to replace the language code [de] with your
Reference bug: https://bugzilla.redhat.com/show_bug.cgi?id=437997
Last date for finishing this task is 22nd of April.
Let me know if you have any queries!
I've noticed that the comps pot file has been updated at least a couple of
times after both the string and the translation freezes. I know comps is a
bit different from a lot of the other packages that we translate, but if
breaking the freezes is absolutely necessary, at least a mail about the
changes should be sent to this list. That way the translators would know to
update their po files.
Here are the two wiki pages explaining L10n freezes:
Apologies for the delay!
The Fedora Documentation Project is pleased to deliver the POT file
for the Fedora 9 GA release notes. These release notes are going to
be delivered with the Fedora 9 GA Release.
Translations are due at 2359 UTC on 2008-04-15.
Access via Transifex:
Access via CVS:
If you want a complete documentation build environment for the release notes:
cvs co release-notes-devel
If you need just the directory with XML and /po directory:
cvs co release-notes-dir
Definitely let us know if we are missing any of the steps in making
the files available for translators. We'll fix it right away! Stop
by #fedora-docs on irc.freenode.net or send an email back to this
- Fedora release notes team
As I may not make a clear statement before regarding TQSG but assumed
that we all understand same level. So here is what is happening just in
case for whom not aware of.
Thanks to many of you who have filed bugs, since new FAS2 introduced, we
have identified that the above chapter contains old information which
are no longer relevant (e.g. submitting SSH key & GPG key ID, creating
new Fedora account, signing CLA, joining cvsl10n group etc.). Currently
the guide is under reviewing and soon it will be updated (looking at
same timing of FC9 final).
For existing translators, only you have to do is to change your password
as you have automatically been transfered, AFAIK.
Any question, feel free to drop by #fedora-l10n channel.
* glezos has changed the topic to: Fedora Localization Group meeting
-- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- Init
* MrTom (n=mrtom@fedora/MrTom) has joined #fedora-meeting
glezos right on, who is around?
petreu PeterReuschlein (de)
* wolfy (n=lonewolf@fedora/wolfy) has left #fedora-meeting ("I'm
willing to make the mistakes if someone else is willing to learn from
glezos Dimitris Glezos (el)
vpv Ville-Pekka Vainio (fi)
glezos marek, are you around?
glezos Okey, let's get started, and others might join in
glezos We haven't prepared an agenda for this meeting
glezos Here's an action list from the previous one:
marek MrTom: yes
glezos I'm a bit confused whether they were done.
marek glezos: yes
* marek Marek Mahut (sk)
glezos At least the first 3 were done, if I understand them correctly.
glezos runa isn't around for the 4th.
glezos The major topic is FLSCo elections I guess.
MrTom ping Bousk1
* AndreasR has quit ("Ex-Chat")
glezos Nomination period is still on, and we've got 10 canditates,
which is a very good number for 7 slots.
glezos I'm *extremely* glad that most of the active people in FLP have
MrTom a French will *normaly* join them
glezos MrTom: awesome.
glezos This is probably a good moment to remind something we probably
already know, that while an FLSCo is important for a variety of
reasons (mainly democracy, a good decision-making process, and a
stronger FLP presence)...
glezos the people who won't make it in FLSCo should definitely
continue being active and keep doing what they're already doing great.
MrTom don't worry for this :)
glezos MrTom: I'd just like to make that crystal clear. Being a member
of FLSCo means you have the community's stamp of approval, but not
being one does not mean the opposite.
glezos Just to clear out any doubts or misunderstandings, all
discussions will still go on in public, and a different mailing list
will not be made.
* viking-ice has quit (Read error: 110 (Connection timed out))
glezos So, we had some problems with the voting system, so Infra has
asked some more days to set it up
glezos If nothing goes wrong, elections start 22/4.
glezos and that's all I have to say about that. :)
glezos comments, etc/
glezos okey. A quick reminder that today is the deadline for F9
glezos An update that a hungarian team is being created.
glezos .bug 440372
buggbot Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=440372
low, low, ---, Dimitris Glezos, CLOSED NEXTRELEASE, hu translations
zodbot glezos: Bug 440372: hu translations coordinator setup -
* glezos has changed the topic to: Fedora Localization Group meeting
-- Agenda: http://fedoraproject.org/wiki/L10N/Meetings#agenda -- Open
glezos So, these are the topics that came to my head.
vpv do you know anything about the status of the GSoC applications for
glezos vpv: yes.
glezos We've had 7 applications for Transifex and L10n in general
* abadger1999 has quit ("Leaving.")
glezos 5 of them made it to the top 20 (out of ~70)
glezos and so far 4 of those are in the number of estimated slots to
be given to Fedora
glezos oops, that's 3.
glezos This might change, but it seems that the 2 of those will most
likely be accepted.
glezos I hope the third one will also make it, because it'll have
immediate use in FLP.
vpv That sounds good, considering there are a lot of other
sub-projects in Fedora as well
* glezos hints that one of those 3 is a guy of our own. :-)
* kital (n=Joerg_Si@fedora/kital) has joined #fedora-meeting
glezos okey, anything else?
glezos any action items we should write down for next 2 weeks?
glezos I'll make sure the voting system is up in time and tested.
vpv should the FLSCo elections be over in two weeks?
glezos vpv: yeah, election period is now 22-29
marek glezos: is it one vote per person (to one person)?
glezos marek: 7 votes, one per person.
* linuxlala (n=linuxlal(a)184.108.40.206) has joined #fedora-meeting
* linuxlala has quit (Read error: 104 (Connection reset by peer))
marek glezos: ok
marek we should also think for some marketing for voting
glezos well, this is something we could change of course..
marek (announces etc...)
glezos The current voting system gives each voter as many votes as
there are open seats. They may vote for each candidate only one time,
and can use as many or few of their votes as they wish.
glezos (quoting http://fedoraproject.org/wiki/L10N/SteeringCommittee/Elections)
glezos marek: right, let's raise some noise on Tuesday.
glezos Anything else before closing..
* aggelidis (n=transife(a)220.127.116.11) has joined #fedora-meeting
marek nothing for me
glezos Closing in 30.
glezos thanks folks.
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
Hi! My name is Vasilis Kalintiris and I live in Greece. I'd like to
contribute to the Fedora Project not only by translating
PO-files from English to Greek, but also by developing an
authentication/permission layer for Transifex.
This is a project mentioned as an idea for the Transifex Project in the
Summer of Code (SoC) 2008. In this e-mail I include the
abstract from my SoC application. It's a little bit general so if you
want more information or if you have any question please let
me know. Also, if you have ideas or proposals for the project don't
hesitate to contact me 8-) !
Most open source softwares (OOSs) are developed in a public,
collaborative manner. In order to make this collaboration
both creative and applicable to the needs of the OOS, Revision Control
Systems (RCSs) are employed. Concurrent Version Systems (CVSs)
and Subversion (svn) are examples of tools that help centrally manage
the source code files and the changes to those files for a software project.
In real life, there's the need to categorize the users or the
groups that have access to project's resources. In Fedora Project for
example there are
many developers, administrators, languages leaders, translators,
anonymous users and so on. These people or teams contribute to the
of the project and need access to specific resources. Each user or team
is given specific privileges usually based on the status of the project
and the role that they have.
A new project named Transifex has been developed in the previous
summer during the Google Summer of Code program. It's a very promising
that provides the user a Web UI with which he can access a software's
project resources without caring about the underlying implementation of
project's RCS and it's interface. This way the user has to learn only
the Transifex and not the specific RCS that the project uses and can involve
in many different projects as long as they use Transifex.
My goal is to contribute to the Transifex project by adding a
permission and authorization layer.
This enhancement will solve all these problems that I explained
before. The development of a software project will be secure, stable and
all productivity will be maximized. Maintainers won't care about users'
or teams' mistakes like overwriting files that aren't responsible for.
Moreover, transition to different phases of software project
development will be easier and seamless.
Extra features like OpenID support and Vertimus interoperateability
(that's a long word!!!) are furthermore goals of the project.
PS: For more information about Transifex and ideas for the SoC 2008,
visit the following sites: Transifex
<https://hosted.fedoraproject.org/transifex/>, Transifex - Project Ideas