Alpha Announcement
by Eric Christensen
I need a volunteer (or two) to write up the Alpha Announcement and
have it done by Friday. Any takers?
--Eric
14 years, 8 months
Back to work with revised to-dos
by satya komaragiri
Hello,
I apologise for the inactivity for the past few days. I am now in Pune
and finished the initial procedures for joining RH. I can work
regularly from now. I will start off with the revised to-dos starting
from getting beacon in fedora. I just had a discussion with Nandeep
about making having beacon in fedora priority #1. He agreed too in his
mail of which I am pasting a snippet here (with his permission) to
give you an idea of what will be up on his agenda.
So far the idea is to have me concentrate on getting beacon integrated
with FAS, Zikula etc. while he works on core beacon improvements and
adds more features to make it really usable.
"So after lots of people jumping in and out of this project and
lukewarm response, I think the best way to roll this out is as a
standalone product firmly deployed somewhere. For a proper end user
product which users can employ to their benefits we need a cloud
set-up pretty much like what Google Docs has to offer. For this I can
think of the following core features that are absolutely essential for
a release (these are technical mostly):
1. Copy paste handling to prevent crappy HTML generation.
2. Revision history and being able to revert back to other revisions
3. Undo redo stack
4. Be able to add media like pictures.
5. File browser for documents
6. Directly related to above point: an account system like Google Docs
so per user cloud can exist. (For your Fedora system as mentioned, it
can be FAS)
7. Be able to download the file in various formats (publican, you
already have some work done on it).
Now we have to decide how much of this to implement within your GSoC
period or whatever it is that your revised schedule allows."
The last line also made me wonder if my deliverables for GSoC have
changed. It would be very convenient for me to know what is my to-do
from GSoC perspective. I am not limiting this project till SoC and
will make sure I work on it till it is in production use but knowing
what is expected for SoC can help me order the tasks accordingly.
Regards,
Satya
14 years, 8 months
Re: Adding pages on Transifex
by Dimitris Glezos
On Sat, Aug 8, 2009 at 3:14 PM, daniel
cabrera<h.daniel.cabrera(a)gmail.com> wrote:
> Hi,
>
> We were thinking at the Spanish team, if there's a possibility to add a
> couple of web pages to translate in Transifex. There's a kind of
> 'idiomatic gap' between the home pages of each language and, for
> instance, any any guide that the docs team has released.
>
> E.g. if a Dutch user wants to go from here [1] to here [2], he or she
> must first pass through these three pages: [3], [4], and [5], which are
> available only in English.
>
> [1] http://fedoraproject.org/nl/
> [2]
> http://docs.fedoraproject.org/installation-quick-start-guide/f11/nl-NL/ht...
> [3] http://docs.fedoraproject.org/
> [4] http://docs.fedoraproject.org/installation-quick-start-guide/
> [5] http://docs.fedoraproject.org/installation-quick-start-guide/f11/
>
> The idea is to make the navigation process be consistent, in any
> language. I know there must be a user incredibly lazy, or not being
> able to read a word in English to abandon the process before reaching
> the guide. Not sure about the second type, but in fact I know a
> couple of the first one.
This is a good point.
I'm CCing the Docs project, since this is purely something the folks
there can fix.
What we need is clear links to the localized documents. Here are two
alternatives:
1. On the Get Help page, we list all the documents that the user
might need. The listing is i18n-ized, so local groups can override the
English defaults.
2. We localize http://docs.fpo/ too. The link on the left menu of the
main site is localized, so a team which has docs.fpo localized will
link to the localized version.
-d
--
Dimitris Glezos
Transifex: The Multilingual Publishing Revolution
http://www.transifex.net/ -- http://www.indifex.com/
14 years, 8 months
CC license logos/buttons
by Richard Fontana
With the licensing switch from OPL to CC-BY-SA, there is some interest
in using Creative Commons' logos and CC-BY-SA license button image
thingies in generated Fedora documentation and the Fedora wiki. This is
raising some questions about whether we can actually package the
logo/button thingies in Publican and whether indeed such content can be
used on Fedora websites.
Based on discussions I have had with Spot, the default terms of use for
such content[1] clash with Fedora legal policy concerning freely
redistributable content. Moreover, based on preliminary communication
with lawyers for Creative Commons I believe we do not have permission
to package these logo/button thingies in Publican, regardless of Fedora
legal policy.
We are planning on exploring with Creative Commons' lawyers the
possibility of getting sufficient additional permission to address some
of these impediments, but for the time being we should assume that the
CC logo/button thingies can't be used by Fedora.
- RF
[1]See http://creativecommons.org/policies
--
Richard E. Fontana
Red Hat, Inc.
14 years, 8 months
Re: L10N Priority on Guides
by Ruediger Landmann
On 08/07/2009 10:09 PM, Eric Christensen wrote:
> On Thu, 2009-08-06 at 23:43 -0300, Domingo Becker wrote:
>
>> 1. Readme Burning ISOs.
>> 2. Readme Live Image.
>>
>>
> The first two in your list are going away.
>
So will these not be published on docs.fedoraproject.org any more?
I know that these won't be part of the Release Notes package any more,
but wouldn't it be easier to maintain translations in XML/Transifex
rather than just on the wiki?
Cheers
Ruediger
14 years, 8 months
Packages loaded into Fedora by default
by Eric Christensen
How do we ask for certain document guides to be loaded into the system
by default and do we have any guides that need to be in the default
install?
--Eric
14 years, 8 months
L10N Priority on Guides
by Eric Christensen
I've added a column to the Guide Table[1] that shows the priority that
we give to translations. This was a request from L10N so they would
know what guides to work on when manpower was limited. Here's my
recommendation:
1 Release Notes
2 Installation Guide
3 Installation Quick Start Guide
4 user Guide
???
Comments?
[1] https://fedoraproject.org/wiki/Docs_Project_guides_table
--Eric
14 years, 8 months
