Guide/notes/document sponsorship
by David Nalley
During the Docs meeting tonight the issue of moving all documents
under a single fas group to grant access came up.
jjmcd brought up several issues - and I think they are worth
considering. More importantly he brought up a potential solution, that
I also think is worth considering. I'd encourage you to read through
the log if you weren't there.
Specifically as downsides to the proposal he enumerated the following:
* there is currently a progression from member -> committer ->
publisher - which we'd largely lose.
* currently new members tend to be 'frightened' by getting their first
document commit access, and giving it all in one fell swoop might
discourage contributors. (a new contributor echoed that he would feel
this way)
We discussed at length and said that the problems we were trying to solve were:
* Remove barriers to participation, particularly the 'need to find a
sponsor for $group during a hackfest' or to help someone get started
fresh.
* Make it easier for existing contributors to switch to a different
document/guide in the event there is some need or push such as the
recent work on the User Guide that laubersm led.
So jjmcd wisely noted that spreading sponsor powers around would solve
most of these problems. Heretofore, most of us have collected
memberships and sponsorship as needed. I'd like to propose at a
minimum (note that this isn't intended to be a rule or policy) that if
you own a document (release notes, a guide,
$other_repo_controlled_document) that you become a sponsor for all of
our documents. Additionally, someone who is comfortable with our
environment, and the processes should also get sponsor rights to all
of our documents to solve the above two problems.
One of the interesting things is that no one seemed concern about
granting access to people. We want to be pretty liberal with that.
So, I am bringing this to the list in hopes of generating more
discussion, and see if we want to do that moving forward.
Thoughts, comments, flames??
David Nalley
13 years, 11 months
Re: Upcoming Schedule Tasks
by Noriko Mizumoto
Hi Docs team,
I have a question on the trans-task schedule.
John Poelstra さんは書きました:
> Start End Name
> Tue 11-May Tue 18-May Translate GA Announcement
Due to recent slip, this task to be also slipped to Start 18-May End
24-May, no?
This is new task added in F13 schedule (if my memory serves correct). We
have not received any file so far, what file format will be for
translation?
noriko
> Fri 14-May Mon 24-May Translate rel-notes nightly POT builds
> Tue 18-May Tue 18-May Translation Deadline: GA Announcement
> Mon 24-May Mon 24-May Translation Deadline: 0-Day (PO Files complete)
> Tue 25-May Tue 25-May Final (GA) Release
> --
> trans mailing list
> trans(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/trans
13 years, 11 months
Musicians' User Guide Summer Coding Proposal.
by Christopher Antila
Hello:
I have now found a mentor from the Docs SIG (thank you to Rudi Landmann
for volunteering!) Another mentor from a music community would be
appreciated, but isn't necessary - it's probably easy enough to pick up
technical help with software along the way.
The last remaining obstacle in the application process is the proposal
page itself. As I am not an expert in either applying for jobs or
writing project proposals, I would appreciate any advice that can be
given. I've attempted to follow the requirements and recommendations of
the proposal page as closely as possible (see the model, URL below).
I understand that this is a rather lengthy document (and time is
probably short, with the upcoming release). If you could spare the time
to read even one section or a few paragraphs, and even if the resulting
comment is "looks good," I would appreciate that kind of feedback, too!
Likewise, no criticism is too harsh. In fact, "you sound full of
yourself" is probably very helpful.
Model Proposal Page:
https://fedoraproject.org/wiki/Summer_Coding_2010_proposal_-_Name_of_prop...
My Proposal Page:
https://fedoraproject.org/wiki/Summer_Coding_2010_proposal_-_Fedora_Music...
Thank you in advance for any advice. I look forward to working with the
community this summer.
Christopher Antila.
13 years, 11 months
Upcoming Schedule Tasks
by John Poelstra
Start End Name
Fri 14-May Mon 24-May 0-Day rel-notes update docs.fp.org
Fri 14-May Mon 24-May 0-Day rel-notes build updated rpm
Fri 14-May Mon 24-May 0-Day rel-notes generate POT
Tue 18-May Tue 18-May Fedora 13 Final Go/No-Go Meeting (20:00 EST)
Mon 24-May Mon 24-May Add translated zero-day updates to docs.fp.org
Tue 25-May Tue 25-May Final (GA) Release
13 years, 11 months
Publican 1.6.3 -- Important
by Ruediger Landmann
Hi all --
Just a note that Publican 1.6.3 will be in the repos shortly. This is a
major bugfix release with fixes for around 20 issues including quite a
few that specifically impact localization:
580360 - Publican does not allow programlisting/screen in entry
581397 - Updating zero-length PO files causes Publican to create
corrupted PO files
581773 - a manual page reference should not break a paragraph for
translations / PO files
582255 - <indexterm> is not translatable when outside of <para>
582649 - Some translated strings are not used, problem with non-breaking
space?
582680 - <indexterm> should be standalone in a translation
583224 - <keyword> should be translatable
The net effect of these fixes is that Publican now presents some strings
to translators that it did not present before (such as <keyword>,
<indexterm>, and the contents of <screen> and <programlisting>), and
divides some strings in PO files differently from how it did before (for
example, not breaking English strings into three separate strings around
<refentrytitle>). These changes should make life easier for translators
in future, and allow them to produce more complete translations.
As we approach the final push towards Fedora 13, it's really important
that Docs team members keep the POT (and therefore PO) files stable for
translators -- we don't want to shift the goalposts.
Therefore, do NOT use Publican 1.6.3 to refresh POT files for documents
already in translation. If you do so, it is very likely that you will
break existing translations.
If you do need to update or change POT files for an existing document
(which at this stage should require permission from the Localization
Team anyway) make sure that you use Publican 1.6.2.
However, if you need to generate or refresh PO files for some reason
(for example, to add a new language for a document), it's fine to use
1.6.3: the changes in Publican only affect XML-to-POT, not POT-to-PO.
Cheers
Rudi
13 years, 11 months
Summer Coding Project: Still Seeking Mentor
by Christopher Antila
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello:
Last week, I sent an introductory message, about the Fedora Summer
Coding project that I'm proposing. The proposal is almost finished (see
it online at
https://fedoraproject.org/wiki/Summer_Coding_2010_proposal_-_Fedora_Music...),
but some serious work remains.
The most important part still remaining is that I need a mentor! I
would really like to have somebody from Fedora and Planet CCRMA, because
of the opportunities it would allow. This co-mentoring possibility has
been approved in principal by the Fedora Summer Coding SIG, and they
also recommend it for this particular proposal.
The responsibilities for a mentor from the Docs SIG would probably be
like these:
- -assist in following established Docs practices
- -assist in possible conversion to DocBook XML and Publican
- -assist in getting volunteers to test efficacy of produced documentation
- -help with integration into the Docs community
I can't say for sure, but this is my best guess. You can contact the
Fedora Summer Coding people for more information, or see the wiki page,
available at
https://fedoraproject.org/wiki/Summer_Coding_2010#You_are_a_mentor
Thank you for considering my proposal. Any comments that you may have
are welcome!
Christopher Antila.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJL7bQOAAoJEInCktGVqZ8VN+MIAIXZebXgRbxexeHCpg/e9PLr
OcTyRYVa9M0VArEkNeqxNq7/UFS2C63581D2AYBdXtQVwxF6LmuH9u+NIAjnhXKt
DzgCXJ8tI5EnM8PxY7QQ/n/wArxsJ0SJH3qVfjE2P8X3LiTc9fOTGsLLmpDgCcrv
HCrwoh4S9ZnNNqAiV376hkoE0ofBzDco7enIzjPGaRvznOXKRob7VjUghjGIjR7P
UVdIu93OMi1YavOy7xYe3FyytG75Uq1OpRPkdlFebKwRlFJEtUBs+TqdzzVjbu2q
Bf6r4cituwKWCTMUviBLDOjTcc2Y8upPcrkF5oS26MQAxuZL+v2KemIMKRk2kqo=
=aIBO
-----END PGP SIGNATURE-----
13 years, 11 months
[Bug 590873] New: Following instructions to build a custom kernel doesn't work
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: Following instructions to build a custom kernel doesn't work
https://bugzilla.redhat.com/show_bug.cgi?id=590873
Summary: Following instructions to build a custom kernel
doesn't work
Product: Fedora Documentation
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: docs-requests
AssignedTo: eric(a)christensenplace.us
ReportedBy: sarcastic.mannequin(a)gmail.com
QAContact: fedora-docs-list(a)redhat.com
CC: stickster(a)gmail.com, kwade(a)redhat.com
Classification: Fedora
Instructions at http://fedoraproject.org/wiki/Building_a_custom_kernel for
building custom kernel do not work.
I'm trying to build a custom kernel for Fedora 10.
How reproducible:
Steps to Reproduce:
1. Follow the instructions as given at
http://fedoraproject.org/wiki/Building_a_custom_kernel. Copy new Kconfig(s) and
copy some source files into the ~/rpmbuild/BUILD/kernel-2.6.$ver.new directory.
Some source files are new and some are copied over existing source files.
2. Follow more instructions as given
3. Try to generate patch and perform "make menuconfig"
Actual results:
Patches are generated incorrectly and new options in new Kconfig files don't
show in the kernel configuration menus.
Expected results:
Following the instructions as given should work.
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
13 years, 11 months
Internet service disruption
by Ian MacGregor
Hi all,
Just a note to let everyone know that my internet service has been
temporarily disrupted and I'm now having to use my cell phone to
communicate. Thank goodness for cell phones, eh? Too bad I can't install git
and publican in it, though.
I'll continue working on a few things and learning more during this outage
but my replies to lists may be a bit behind.
Regards,
Ian MacGregor
http://fedoraproject.org/wiki/User:Ardchoille42
13 years, 11 months
