Hi all!
I would like to install The Fedora Ring Tone on my phone. :)
I think, there is no such tone, but this may be a good idea and I would
like to file a bug for this. :)
Which project against I can file a bug?
Best regards!
Valentin Laskov
Hi all,
In f.p.o website, by default for downloading will be Fedora 17 64-bit
version. I think that this must be mentioned in the Release notes.
Best regards!
Valentin Laskov
Please visit
https://admin.fedoraproject.org/updates/fedora-release-notes-17.0.0-1.fc17
Check out the RPM and the translations and give karma. This corrects
all the outstanding bugs.
There are a few new untranslated strings.
- I added a revision history entry for 17.0 but Publican seems to
think this is already translated.
- I added the Bulgarian and Ukranian translators names to the
contributors - these shouldn't need to be translated.
I will continue to build new RPMs as new translations become available.
--McD
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2012-05-07/fedora_docs.2012…
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2012-05-07/fedora_docs.2012…
Log:
http://meetbot.fedoraproject.org/fedora-meeting/2012-05-07/fedora_docs.2012…
===================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
http://fedoraproject.org/wiki/Docs_Project_meetings
===================================================================================================
Meeting started by bcotton at 14:01:40 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2012-05-07/fedora_docs.2012…
.
Meeting summary
---------------
* Roll Call (bcotton, 14:01:54)
* Release Notes (bcotton, 14:06:11)
* LINK: https://fedoraproject.org/wiki/Release_Notes_schedule
(bcotton, 14:06:17)
* karma early and karma often (bcotton, 14:09:04)
* thanks to bug providers (jjmcd, 14:09:37)
* Guide Status (bcotton, 14:11:33)
* LINK:
http://rbergero.fedorapeople.org/schedules/f-17/f-17-docs-tree-tasks.html
(bcotton, 14:11:39)
* String Freeze today (bcotton, 14:11:46)
* LINK:
http://fedoraproject.org/wiki/FAQ#How_do_I_configure_network_connections.3F…
(claneys, 14:24:54)
* ACTION: Capesteve to investigate incorporating Admin Guide changes
into Wireless Guide (jjmcd, 14:27:47)
* ACTION: jjmcd to check with nb on moving WG into git from SVN
(jjmcd, 14:33:01)
* ACTION: Sparks to open question on list of merging SSH guide into
another (jjmcd, 14:38:26)
* ACTION: randomuser to investigate issue with branching tech notes
(jjmcd, 14:44:08)
* ACTION: pkovar to warn L10n of guides ready for translation (jjmcd,
14:49:17)
* Open Help Conference (jjmcd, 14:52:09)
* Outstanding BZ Tickets (jjmcd, 14:56:02)
* LINK: http://tinyurl.com/lbrq84 (jjmcd, 14:56:10)
* Open floor discussion (jjmcd, 14:58:59)
Meeting ended at 15:03:06 UTC.
Action Items
------------
* Capesteve to investigate incorporating Admin Guide changes into
Wireless Guide
* jjmcd to check with nb on moving WG into git from SVN
* Sparks to open question on list of merging SSH guide into another
* randomuser to investigate issue with branching tech notes
* pkovar to warn L10n of guides ready for translation
Action Items, by person
-----------------------
* Capesteve
* Capesteve to investigate incorporating Admin Guide changes into
Wireless Guide
* jjmcd
* jjmcd to check with nb on moving WG into git from SVN
* nb
* jjmcd to check with nb on moving WG into git from SVN
* pkovar
* pkovar to warn L10n of guides ready for translation
* randomuser
* randomuser to investigate issue with branching tech notes
* Sparks
* Sparks to open question on list of merging SSH guide into another
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jjmcd (76)
* pkovar (20)
* Capesteve (17)
* Sparks (15)
* bcotton (15)
* randomuser (11)
* sgordon (11)
* claneys (9)
* zodbot (6)
* adamw (3)
* nb (3)
* jhradilek (3)
This is an automated message to remind you that we will be meeting at 1400 UTC in #fedora-meeting. Unless we've previously agreed that we will not be meeting today.
Hi
docs.fedoraproject.org is not accessible if the browser's accepting
language is set to 'Chinese (Taiwan)' (zh_TW). And the translations
done at https://fedora.transifex.net/ do not appear there.
Regards,
Walter Cheuk
Hey,
can we please add a sentence to the Fedora 17 Release Notes about the
new out-of-the-box multi-seat setup?
It's the first time for Linux to be able to support something like
that properly in the Base OS, or without complex manual configuration,
or without adding additional software. It's a useful feature for
schools and other setups where several people want or need to share a
single computer.
We like to get the word out and have Fedora taking the credit for
being the first distro, and also for letting us do all that in the
distro.
Details and background is here:
http://0pointer.de/blog/projects/multi-seat.htmlhttp://www.phoronix.com/scan.php?page=article&item=plugable_multiseat_kick
Thanks,
Kay
So I thought of one more big F17 change that should go in the release
notes and/or install guide, when it comes to installation.
There are a few use cases for doing a 'direct boot' of the Fedora
installer: that is, you don't actually boot from any release medium, but
you boot the installer kernel/initrd directly, manually. The most
obvious case is a PXE install.
In F16, you really _only_ needed to specify the kernel and initrd
location, and the install would work - kernel/initrd got you stage1, and
stage1 got you stage2. With noloader, this is no longer the case: when
you're doing a direct kernel boot, you need to tell it where to find
'stage2'. In other words: you have to pass repo= or stage2= (or
inst.repo= or inst.stage2=, as it's now preferred), pointing to a
repository. If you want to get just the stage2 image from one server but
then the installation packages from some other server, you have to use
stage2= : repo= should only be used if the server you're pointing to
contains everything needed for the install (both the stage2 image _and_
all the packages you want to install). Note that stage2= still expects
to see a 'repository' tree, you can't just pass the path direct to a
squashfs.img file (which is how stage2= worked when it previously
existed in F15 and earlier).
label linux
kernel vmlinuz
append initrd=initrd.img
(or something like that), you need:
label linux
kernel vmlinuz
append initrd=initrd.img repo=http://dl.fedoraproject.org/pub/fedora/linux/development/17/x86_64/os/
or:
label linux
kernel vmlinuz
append initrd=initrd.img stage2=http://my.internal.server/17/x86_64/os/
(or any other valid mirror).
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
Hi translators,
We have updated the Fedora 17 Release Notes POT in transifex.net,
please, start translating them:
https://fedora.transifex.net/projects/p/fedora-release-notes/
You'll notice that few files (Accounts, Entertainment, Boot,
Dedication, Networking, Web_Servers) are not accepting translations,
that's because we don't have those sections in the current RN. We will
clean that later.
You should be able to proofread online at
http://fedorapeople.org/groups/docs/release-notes/
Please come back to the docs team if translations are not updated, I
haven't checked if they are currently rebuilt daily (they should).
Be aware that we could update the some bit of the Release Notes if
feel the need to.
I could already told you that Security.po will be lighter as the
firewalld will probably be dropped (feature moved to F18). <= jjmcd,
please?
Sincere apologies for being this late to provides POTs, we still are
setting the right process and writing some scripts…
And the maitainers thought that we already had them on transifex.
Best Regards,
--
Kévin Raymond
(shaiton)
GPG-Key: A5BCB3A2
Technical Notes is now 100% translated into Chinese (Taiwan) (zh_TW).
Should I ask for it be published as described in [1] or it will got
published automatically? And how can I test it and can it be modified
after published?
Regards,
Walter Cheuk
[1]: https://fedoraproject.org/wiki/L10N/Guide#Publishing_Docs