Last release we had an idea that I'm proposing we try for Fedora 7. For reasons that should be obvious as you read, the Ambassadors seem to be a natural group to do this. Perhaps in coordination/collaboration with Fedora Translation/L10n contributors?
The basic idea is to distribute to countries/regions a list of "talking points". Talking points are specific items we want to see covered in any release announcement. Then each region/language can choose to i) form a small team, and ii) collaborate to write a truly localized release announcement.
http://fedoraproject.org/wiki/Docs/Drafts/ReleaseAnnouncements#Process
Background ----------
In the past, the announcement introduction has been written in English in a semi-humorous way. To understand it, you had to know specific cultural references. This made them fairly impossible to translate (or transliterate). Or even understand, period.
This new method would rely entirely upon the local groups to collaborate on an announcement, then distribute it within their region as a formal Fedora release announcement. One place to start is fedora-announce.
How many different language announcements can we get on fedora-announce for Fedora 7?
One concern that is that a release announcement is a very big chance to start misinformation about Fedora. For example, an announcement may be written in a language not read by most of the Fedora leadership, and the authors accidentally choose terms or phrasing that reflect negatively on Fedora. The quality of the writing or grammar also reflects on Fedora.
To lower this risk, it seems like a good idea to have the release announcement draft due for review by the final test (usually test3, occasionally test4). Every draft announcement then needs an independent review by a reader of that language.
I'm sure that this has been done informally in various countries. This idea is to formalize the process, recognize the people involved with the honor of speaking LOUDLY for Fedora, and make an ever bigger impact with this next release.
- Karsten
+1 to Karsten's idea.
The key: getting the talking points right. Karsten, will you be leading us in this effort? :)
--g
On Wed, 28 Feb 2007, Karsten Wade wrote:
Last release we had an idea that I'm proposing we try for Fedora 7. For reasons that should be obvious as you read, the Ambassadors seem to be a natural group to do this. Perhaps in coordination/collaboration with Fedora Translation/L10n contributors?
The basic idea is to distribute to countries/regions a list of "talking points". Talking points are specific items we want to see covered in any release announcement. Then each region/language can choose to i) form a small team, and ii) collaborate to write a truly localized release announcement.
http://fedoraproject.org/wiki/Docs/Drafts/ReleaseAnnouncements#Process
Background
In the past, the announcement introduction has been written in English in a semi-humorous way. To understand it, you had to know specific cultural references. This made them fairly impossible to translate (or transliterate). Or even understand, period.
This new method would rely entirely upon the local groups to collaborate on an announcement, then distribute it within their region as a formal Fedora release announcement. One place to start is fedora-announce.
How many different language announcements can we get on fedora-announce for Fedora 7?
One concern that is that a release announcement is a very big chance to start misinformation about Fedora. For example, an announcement may be written in a language not read by most of the Fedora leadership, and the authors accidentally choose terms or phrasing that reflect negatively on Fedora. The quality of the writing or grammar also reflects on Fedora.
To lower this risk, it seems like a good idea to have the release announcement draft due for review by the final test (usually test3, occasionally test4). Every draft announcement then needs an independent review by a reader of that language.
I'm sure that this has been done informally in various countries. This idea is to formalize the process, recognize the people involved with the honor of speaking LOUDLY for Fedora, and make an ever bigger impact with this next release.
- Karsten
Greg Dekoenigsberg ha scritto:
+1 to Karsten's idea.
The key: getting the talking points right. Karsten, will you be leading us in this effort? :)
--g
On Wed, 28 Feb 2007, Karsten Wade wrote:
Last release we had an idea that I'm proposing we try for Fedora 7. For reasons that should be obvious as you read, the Ambassadors seem to be a natural group to do this. Perhaps in coordination/collaboration with Fedora Translation/L10n contributors?
The basic idea is to distribute to countries/regions a list of "talking points". Talking points are specific items we want to see covered in any release announcement. Then each region/language can choose to i) form a small team, and ii) collaborate to write a truly localized release announcement.
http://fedoraproject.org/wiki/Docs/Drafts/ReleaseAnnouncements#Process
Background
In the past, the announcement introduction has been written in English in a semi-humorous way. To understand it, you had to know specific cultural references. This made them fairly impossible to translate (or transliterate). Or even understand, period.
This new method would rely entirely upon the local groups to collaborate on an announcement, then distribute it within their region as a formal Fedora release announcement. One place to start is fedora-announce.
How many different language announcements can we get on fedora-announce for Fedora 7?
One concern that is that a release announcement is a very big chance to start misinformation about Fedora. For example, an announcement may be written in a language not read by most of the Fedora leadership, and the authors accidentally choose terms or phrasing that reflect negatively on Fedora. The quality of the writing or grammar also reflects on Fedora.
To lower this risk, it seems like a good idea to have the release announcement draft due for review by the final test (usually test3, occasionally test4). Every draft announcement then needs an independent review by a reader of that language.
I'm sure that this has been done informally in various countries. This idea is to formalize the process, recognize the people involved with the honor of speaking LOUDLY for Fedora, and make an ever bigger impact with this next release.
- Karsten
+1 too
Francesco Ugolini
On Wed, 2007-02-28 at 09:54 -0500, Greg Dekoenigsberg wrote:
+1 to Karsten's idea.
The key: getting the talking points right. Karsten, will you be leading us in this effort? :)
Sure thing. How about we open the discussion on f-marketing-l, collaborate and identify some core folks to help with it, and convene IRC meetings as-needed?
/me drafts email to f-marketing-l
- Karsten
+1 very good idea - I can help with slovak and czech
/Marek Mahut
On Wed, Feb 28, 2007 at 04:20:18AM -0800, Karsten Wade wrote:
Last release we had an idea that I'm proposing we try for Fedora 7. For reasons that should be obvious as you read, the Ambassadors seem to be a natural group to do this. Perhaps in coordination/collaboration with Fedora Translation/L10n contributors?
The basic idea is to distribute to countries/regions a list of "talking points". Talking points are specific items we want to see covered in any release announcement. Then each region/language can choose to i) form a small team, and ii) collaborate to write a truly localized release announcement.
http://fedoraproject.org/wiki/Docs/Drafts/ReleaseAnnouncements#Process
Background
In the past, the announcement introduction has been written in English in a semi-humorous way. To understand it, you had to know specific cultural references. This made them fairly impossible to translate (or transliterate). Or even understand, period.
This new method would rely entirely upon the local groups to collaborate on an announcement, then distribute it within their region as a formal Fedora release announcement. One place to start is fedora-announce.
How many different language announcements can we get on fedora-announce for Fedora 7?
One concern that is that a release announcement is a very big chance to start misinformation about Fedora. For example, an announcement may be written in a language not read by most of the Fedora leadership, and the authors accidentally choose terms or phrasing that reflect negatively on Fedora. The quality of the writing or grammar also reflects on Fedora.
To lower this risk, it seems like a good idea to have the release announcement draft due for review by the final test (usually test3, occasionally test4). Every draft announcement then needs an independent review by a reader of that language.
I'm sure that this has been done informally in various countries. This idea is to formalize the process, recognize the people involved with the honor of speaking LOUDLY for Fedora, and make an ever bigger impact with this next release.
- Karsten
-- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\
Le mercredi 28 février 2007 à 04:20 -0800, Karsten Wade a écrit : [snip]
I'm sure that this has been done informally in various countries.
Yep, we [French Amb.] did it for FC6. Armel Kermorvant wrote the announcement and we discussed it on our French mailing list. Once we got it done, we sent it to every news websites (related to computer science of course) and to linux websites as well the day before FC6 was released.
Our announcements were well followed, some websites pasted and copied our mails in the columns. The even thanked "The French Ambassador Group". :) In this announcement, we clearly gave a link to the Fedora logo, to avoid websites to run to the first RedHat logo they could find on the web.
I think it is a good idea to formalise the process. It will give us the material to write a good release announcement.
Of course, I join the translation effort for the French team.
Thomas Canniot
+1 here..a very good idea..
+1 here..a very good idea..
-- ssh 0x86DD170A http://www.fedoraproject.org/wiki/SusmitShannigrahi
+1
last month celebrated the "International mother language day"
On 28/02/07, Karsten Wade kwade@redhat.com wrote:
Last release we had an idea that I'm proposing we try for Fedora 7. For reasons that should be obvious as you read, the Ambassadors seem to be a natural group to do this. Perhaps in coordination/collaboration with Fedora Translation/L10n contributors?
The basic idea is to distribute to countries/regions a list of "talking points". Talking points are specific items we want to see covered in any release announcement. Then each region/language can choose to i) form a small team, and ii) collaborate to write a truly localized release announcement.
http://fedoraproject.org/wiki/Docs/Drafts/ReleaseAnnouncements#Process
Background
In the past, the announcement introduction has been written in English in a semi-humorous way. To understand it, you had to know specific cultural references. This made them fairly impossible to translate (or transliterate). Or even understand, period.
This new method would rely entirely upon the local groups to collaborate on an announcement, then distribute it within their region as a formal Fedora release announcement. One place to start is fedora-announce.
How many different language announcements can we get on fedora-announce for Fedora 7?
One concern that is that a release announcement is a very big chance to start misinformation about Fedora. For example, an announcement may be written in a language not read by most of the Fedora leadership, and the authors accidentally choose terms or phrasing that reflect negatively on Fedora. The quality of the writing or grammar also reflects on Fedora.
To lower this risk, it seems like a good idea to have the release announcement draft due for review by the final test (usually test3, occasionally test4). Every draft announcement then needs an independent review by a reader of that language.
I'm sure that this has been done informally in various countries. This idea is to formalize the process, recognize the people involved with the honor of speaking LOUDLY for Fedora, and make an ever bigger impact with this next release.
- Karsten
-- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\
-- Fedora-ambassadors-list mailing list Fedora-ambassadors-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-ambassadors-list
ambassadors@lists.fedoraproject.org