Guide Translations Published on Monday
by Eric Christensen
In our last Docs meeting we discussed the final schedule for releasing
all guides. To account for unexpected problems I'd like to start
publishing all languages >=90% to docs.fp.o starting 00:01 UTC on 01
November (Monday).
If you need more time to get your translations in before the release
please send a message to the Docs list (docs(a)lists.fedoraproject.org).
Everything should be posted by 00:01 UTC on 02 November (Tuesday) so
the servers will be ready to go for release time.
If your language isn't at 100% and you would like for us to not post
the partially translated guide please let the Docs list know that.
The same goes for guides that haven't met the 90% mark and your group
would like for it to be published.
Thanks for all your hard work!
--Eric
13 years, 5 months
Tasks in BZ
by Eric Christensen
As an easier way to differentiate between customer reported bugs and
tasks that we put in BZ for tracking purpose please use "Task" in the
keyword field so we can keep the two types of tickets separate. I've
already marked some tickets as tasks. If, however, I marked them
incorrectly please remove the keyword. Likewise, if I missed
something please add "Task" to the keyword of that ticket.
I'll be updating links on the Docs Project wiki page so we can easily
find these tickets and I'll also broadcast the RSS feeds that are
associated with these so everyone can keep track of these tickets.
--Eric
13 years, 5 months
[Bug 504063] New: Toolchain next steps
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Toolchain next steps
https://bugzilla.redhat.com/show_bug.cgi?id=504063
Summary: Toolchain next steps
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: project-tracking
AssignedTo: kwade(a)redhat.com
ReportedBy: mel(a)redhat.com
QAContact: kwade(a)redhat.com
CC: fedora-docs-list(a)redhat.com
Classification: Fedora
Sorting out what fedora-doc-utils does, where to use Publican, etc. --
Principals to discuss status, progress, direction on IRC.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
13 years, 5 months
Docs Project meeting summary for 27 October 2010
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2010-10-27/fedora_docs.20...
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2010-10-27/fedora_docs.20...
Log:
http://meetbot.fedoraproject.org/fedora-meeting/2010-10-27/fedora_docs.20...
===================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
http://fedoraproject.org/wiki/Docs_Project_meetings
===================================================================================================
Meeting started by Sparks at 23:00:07 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2010-10-27/fedora_docs.20...
.
Meeting summary
- ---------------
* Roll Call (Sparks, 23:00:07)
* Follow up on last week's action items (Sparks, 23:04:27)
* ACTION: GadgetWisdomGuru to assist rbergeron with the Release
Announcement (Sparks, 23:04:55)
* ACTION: GadgetWisdomGuru to send a message to the Docs list
regarding the "Fedora Library" and fixing FBReader (Sparks,
23:05:08)
* LINK:
https://fedoraproject.org/wiki/Docs_Project_workflow_-_translations
(Sparks, 23:05:26)
* ACTION: rbergeron to work with GadgetWisdomGuru on the Release
Announcement (Sparks, 23:06:22)
* LINK: https://fedoraproject.org/wiki/Fedora_14_announcement
(Sparks, 23:08:48)
* Doc's announcement (Sparks, 23:09:38)
* LINK:
https://fedoraproject.org/wiki/Docs_Project_14_Release_Announcement
(Sparks, 23:09:47)
* Will be posted to the Docs Project blog and will go public at
10:00AM on 02 November (Sparks, 23:09:56)
* Release Notes (Sparks, 23:13:22)
* LINK: https://fedoraproject.org/wiki/Release_Notes_schedule
(Sparks, 23:13:27)
* Guide Status (Sparks, 23:18:30)
* All Docs should be published no later than Monday at 23:59 UTC.
(Sparks, 23:21:54)
* update to Publican 2.3 and Publican-Fedora 2.0 before publishing
(rudi_, 23:22:11)
* ACTION: Sparks to broadcast that All Docs should be published no
later than Monday at 23:59 UTC via email (Sparks, 23:22:39)
* ACTION: nb to get the Bugzilla owners.list sync script fixed to use
git. (Sparks, 23:25:34)
* ACTION: rudi to add "get a bugzilla component" to the "Creating a
new Guide" page http://fedoraproject.org/wiki/Creating_a_new_guide
(rudi_, 23:26:14)
* ACTION: rudi to add "get a bugzilla component" to the "Creating a
new Guide" page http://fedoraproject.org/wiki/Creating_a_new_guide
(jjmcd, 23:26:47)
* nb does not know much about meetbot and who can do what :) (nb,
23:29:18)
* Outstanding BZ Tickets (Sparks, 23:34:04)
* LINK: http://tinyurl.com/lbrq84 (Sparks, 23:34:11)
* 96 Open Bugs (Sparks, 23:34:32)
* 40 New Bugs (Sparks, 23:35:07)
* Open floor discussion (Sparks, 23:42:58)
* LINK: https://fedoraproject.org/wiki/Automating_publishing (rudi_,
23:44:59)
* LINK: https://fedoraproject.org/wiki/Automating_publishing
(Sparks, 23:45:25)
* LINK:
http://fedoraproject.org/wiki/Publishing_a_document_with_Publican
(rudi_, 23:54:27)
* LINK: http://fedoraproject.org/wiki/Branching_a_document_in_git
(rudi_, 23:54:44)
* ACTION: Sparks to add creating and publishing links to the Docs wiki
page (Sparks, 23:58:14)
Meeting ended at 00:00:31 UTC.
Action Items
- ------------
* GadgetWisdomGuru to assist rbergeron with the Release Announcement
* GadgetWisdomGuru to send a message to the Docs list regarding the
"Fedora Library" and fixing FBReader
* rbergeron to work with GadgetWisdomGuru on the Release Announcement
* Sparks to broadcast that All Docs should be published no later than
Monday at 23:59 UTC via email
* nb to get the Bugzilla owners.list sync script fixed to use git.
* rudi to add "get a bugzilla component" to the "Creating a new Guide"
page http://fedoraproject.org/wiki/Creating_a_new_guide
* rudi to add "get a bugzilla component" to the "Creating a new Guide"
page http://fedoraproject.org/wiki/Creating_a_new_guide
* Sparks to add creating and publishing links to the Docs wiki page
Action Items, by person
- -----------------------
* nb
* nb to get the Bugzilla owners.list sync script fixed to use git.
* Sparks
* Sparks to broadcast that All Docs should be published no later than
Monday at 23:59 UTC via email
* Sparks to add creating and publishing links to the Docs wiki page
* **UNASSIGNED**
* GadgetWisdomGuru to assist rbergeron with the Release Announcement
* GadgetWisdomGuru to send a message to the Docs list regarding the
"Fedora Library" and fixing FBReader
* rbergeron to work with GadgetWisdomGuru on the Release Announcement
* rudi to add "get a bugzilla component" to the "Creating a new Guide"
page http://fedoraproject.org/wiki/Creating_a_new_guide
People Present (lines said)
- ---------------------------
* Sparks (122)
* rudi_ (40)
* jjmcd (35)
* nb (27)
* tezcatl (19)
* laubersm (11)
* zodbot (8)
* kecalli (5)
* jhradilek (4)
* bcotton (2)
* sgordon (1)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMyL5TAAoJEDbiLlqcYamxcNIP/2jCdiKSWq1tIGJGqZmdV0ma
KkZCrUFsWbmjyL23PuBZE4B40jence1kj/nw6blB6dq+TCMVun6e3+P1owry6Bsq
Cby87SlSU5P6x7fYj2AQdtZJGrLrTfm/3G9qlbdhqF//EBI/6m54ACBxalgqSZl3
li2wNF2K6kseuH8bqE4UQMDqkze9j8/W3DqxhagNS0d8Oudkjab1Gib3L7R6RIJ9
h6IvozYrQ1jrr1+k5uRKdfKnU9YonPgk19TFe7tciwsMREWYNdtHskhJ8M9b1f/s
0i1PqIfA5X+O8dxSo1UQRLDyL+BWeoTZC/A53fWVBkqVNLer4Ml3cAvBvzuIvgCj
3DJ5xI2tH5/Bc+5At1p+WNuIj5OF7TMrB1vLfDxSeySY88QLYvJmc+bL5cluK+ei
UUFhWEiwVy245ZBPi3Uf2fBE1KWpjqj0LAbBiKM3EfjpfMTf+4biTFkNp0TBinFa
ngHhI7Tnp/UQ6hVH1OWHTPcF0m4GhHSwWd/xyWaqh76btTaDuETsXC6ZAmuF3SuM
aNc0FBzLii6u71MVyCUyxfg5W1JTMucVENuouPHs/vuzffFqYNQGmlUKLrGhFuaX
uy5MNgdRnUVdpW9UVashSxYGSKml7duA62tgxvx2nmf4kz741/90xvT3zhf8zzXh
WuALCZx8BbzR2ZOmQ9AA
=oDaR
-----END PGP SIGNATURE-----
13 years, 5 months
Re: docs Digest, Vol 80, Issue 26
by Christopher Antila
Hi:
Welcome to the Docs Project! I'm also a new contributor, and I think
that I can provide some useful feedback to help with your idea to
document the "mentoring process." Through June, July, and August, I
took part in the Fedora Summer Coding effort (now called "Fedora
Students Contributing"), and wrote the Musicians' Guide (that should be
published soon).
So, I will be watching this list, but please feel free to ask me to help
out where appropriate.
Christopher.
On 10/27/2010 06:10 AM, docs-request(a)lists.fedoraproject.org wrote:
> ...
> Date: Tue, 26 Oct 2010 20:31:21 -0500
> From: Jes?s Franco <tezcatl(a)fedoraproject.org>
> Subject: Re: Membership requests to Docs FAS Group
> To: For participants of the Documentation Project
> <docs(a)lists.fedoraproject.org>
> Cc: quaid(a)fedoraproject.org
> Message-ID: <20101027013120.GC2677(a)opuntia.gateway.2wire.net>
> Content-Type: text/plain; charset=iso-8859-1
>
> On Wed, Oct 20, 2010 at 10:22:06AM -0400, Eric "Sparks" Christensen wrote:
>> > I just sent a message to six people that requested membership in the
>> > Docs project (via the FAS group) but did not complete the other
>> > requirements, namely the introduction on the list. These requests are
>> > from between 14 September and 15 October. I'll revisit the queue next
>> > week to determine whether or not these people have met the membership
>> > requirements[1] or not. If not I will remove them from the queue.
>> >
>> > [1] https://fedoraproject.org/wiki/Join_the_Docs_Project#Yes
>> >
>> > --Eric
> I wonder if we could think about some "Bounty tasks" to become
> contributors at Documentation Project. Something like mizmo wonderfull
> idea to engage more active contributors. Around concrete and
> not-so-scary design tasks: Docs tasks at this group, of course. Maybe
> a specific Beat, or pages marked as "need love" (again, not so
> scary). And guiding them through the process of making a successfull
> contribution, getting more confident contributors to commit later
> bigger tasks.
>
> As "eating my own dogfood", i want to ask someone interested in
> mentoring "me" (remember, i'm kinda sort of first test pilot on this
> idea). I'm actually an active translator on the wiki and at a few
> guides. But i'd like:
>
> 1: to help at Docs project to reorganize the pages under its scope
> * Maybe marking at first place as "Old-for archive" really not very
> useful at this very moment. I talked a few weeks ago with jjmcd
> about jumping on this train, but i think i need a most slow
> approach, and maybe there is not much time until after release
> party.
>
> 2: Starting *some* guides for digital literacy.
>
> * I talked with Rudi about an idea we are talking on Fedora LATAM:
> Escuela Fedora. As #fedora-classroom it's an idea for teaching new
> skills to contributors, but there is a real need for more outreach
> as M?ir?n show us with her projects this year teaching Inkscape and
> GIMP. A guatemalan Ambassador: Edna Rheinier, and Damaris Trujillo,
> have teached too high school girls, on Inkscape and Gimp and gived
> talks about women in free software and Fedora Project, of course.
>
> * We have too, some wonderful ideas on TOSS (on collaboration on
> real world in free software projects) by K. Wade and Greg
> DeKoenigsberg, P2PU ("peer to peer university") and
> CollabOERation. It's hard to outline a full book, but i think
> i'll be ready at this weekend to show a first draft of chapters
> and the first chapter.
>
> Said this, i'd like to document the mentoring process if someone wants
> to help, from having the initial idea, upto getting an usable book,
> ready for translation. This would make too "raw data" for a first
> course about "Fedora writer first steps" as we are talinkg too at
> Fedora LATAM. And a potential first course on future Escuela Fedora
> project.
>
> I think will i need to apply to docs-writer group in FAS, and
> docs-publishers when i've accomplished the first version, right?
>
> ----
> In summary,
>
> i think a Documentation Challenge could be a good compromise between
> having a docs group "invite only" (having sponsored the in by his/her
> mentor at real), and being open and getting best documented our
> processes.
>
> Let me know what do you think, if you'd like to be "my" mentor (you
> know, documenting publicly the whole process), just drop me a dent
> @tzk on identi.ca if you have a little bit of time.
>
> Thanks in advance, and peace for all.
>
> Jes?s Franco
> Translator and Ambassador
> http://fedoraproject.org/wiki/User:Tezcatl
>
> P.S. I cc'ed this message to Karsten Wade with my apologies for not
> getting in touch for edusol summit. A quick look at my wiki page could
> tell you why that project failed since they don't wanna anything to do
> at this moment, with OpenSource projects, sadly.
>
>
> ------------------------------
13 years, 5 months
