REQUEST: specific narrow focus list for my participation
by George (Skip) VerDuin
Greetings,
It is my expectation that your interests and mine are best served by my
participation in some area that is a fairly narrow focus - networking.
I could use your guidance.
I am actively developing a documentation wiki for application software
in ham radio digital communication topic area. It fits on my own FC
platform and as such I expect to provide links to specific FC Docs
project pages. That is the easy part which does not need help from
yourselves. I have come upon a feature in FC-6 that does not function,
has little written about it, but probably does not constitute a bug. It
is here that I see I might fit.
Specific to this subject, using the "ifconfig" statement to establish an
alias IP address does produce what seems to be a valid definition, but
when a packet is built it contains an incorrect source IP address. This
is true on FC-6 up-to-date within weeks, but not true on ubuntu platform
operated by an associate of mine. Until FC documentation contains the
passage to describe the "should be" definition (that I can not locate
and believe may not exist) I can not consider this situation to be a
software bug.
IF I am correct in my assertion, I am willing to draft a topic specific
FC-docs text as well as the alert text to my software users regarding FC
and an appropriate workaround. If I am not correct, perhaps I have
wasted your time...
So, I ask your direction into the group of developers for this subject
area to explore the options at hand?
Warmest regards from here,
George
17 years
hardware solutions and other one-off
by Karsten Wade
Below is an example of a request that we haven't been able to fill, to
support a community-based set of content about hardware compatibility
and solutions. I think a knowledgebase solution (kbase) is the best way
to tackle this, and it has been discussed here before. We can get this
specified, planned, and put into a queue for deployment by Fedora
Infrastructure.
Anyone interested in moving ahead on this? A post Fedora 7 project, to
be sure. Sam Folk-Williams, iirc, was interested ... who else?
Any other ideas for supporting this kind of thing in a non-crazy way?
< whojarr> is there a documentation project for hardware specific
setups?
< whojarr> want to put my laptop specific issues and resolution
somewhere.
< vpv> maybe the fedoramobile site would be the right place?
< jmbuser> whojarr: I get results from www.linux-on-laptops.com
< jmbuser> whojarr: It points to other sites, though
< jmbuser> whojarr: Assuming it's a laptop you're talking about
< whojarr> yeah. cheers.. my solutions are all specific to ferdora. will
see what fits best.
< quaid> I think a kbase is probably the best technical and
collaborative solution to "community hardware compatibility and
solutions"
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
17 years
Alexander Bub. SelfIntroduction
by apocalypse-now
Alexander Bub
My name's Alexander Bub. I am from
Rubtsovsk, Altai region, Russian Federation. I work as the teacher of computer subjects at Rubtsovsk technical school for machinebuilding ( databases, operating systems, administration of local networks) and system integrator ( linux & windows heterogenious networks interoperability).
The goal of my participation in the project is to help people in my country interested in Fedora OS to get the latest and the most actual information on Fedora linux achievements and the deployment of Fedora OS as the main OS on boxes in my technical school and other institutions country-wide. (Fedora OS is the only worthy alternative I see at my place opposing to the proprietary and pricey Windows XP)
I have graduated from one of our local universities and majored in English language. I am a qualified technical writer, thus, I think my skills and experience can help a lot in achievement of my goals.
I am an experienced linux user and system administrator.
Working at tech school gives me a good opportunity to test
Fedora OSes at my computer labs and get my students' opinions on problems we sometimes face when using this operating system.
I think my own Fedora experience and interest to this OS would be of certain help to the Fedora community in my country.
17 years
Pushing content from SMG
by Jonathan Roberts
Hi all,
What do people think of moving some of the content from the software
management guide to the DUG and the AG.
i.e. Updating and installing software with pirut/pup in the DUG
Adding repos in the AG
Whatever the split, I think the idea is to move the simple content
aimed at end users to someone less scary than all the command line yum
stuff...
Jon
17 years
Bye bye inconsistencies
by Bart Couvreur
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
Some old habits should change. We're going to update all the /en/ to
/en_US/ on our http://docs.fedoraproject.org site.
This will allow us to use a consistent language code throughout the
whole toolchain and will allow en_UK / en_AU versions of our docs to
coexist with the current en_US versions.
Any objections, possible complications by doing this change?
Bart
- --
Bart <couf(a)fedoraproject.org> <couf(a)skynet.be>
key fingerprint: 6AAB 544D 3432 D013 776D 3602 ADB6 6B2A D93F 0F93
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGUIOIrbZrKtk/D5MRAut+AJ4jetXKmXHiaL9tl8rH/j5d1b+7OgCfQlgX
jMv3lbVvPoWJpItqtCy35xQ=
=a7JI
-----END PGP SIGNATURE-----
17 years
content developer, writer, oh my!
by Karsten Wade
On this page:
http://fedoraproject.org/wiki/Join
It previously said "Content Developer" for this link:
http://fedoraproject.org/wiki/Join#ContentDeveloper
Where it says, "Description of this role: Communicate through words."
So why don't we say "Technical Writer"? Well, I did update the role
today to say "Content Developer (Writer)" instead, so at least it's not
deceiving.
One reason is to maintain the developer/contributor paradigm -- everyone
is a developer.
Another is to align with new industry standards.
Yet, I have personally had problems with this label, so I am mixed about
the usage. The main reason is that most job roles look for "technical
writing" skills, which are specific to technical roles/needs. A
"content developer" could be developing content about toothpaste and cat
food; there is nothing in the title that specifies that it is focused on
the technical aspects.
Your thoughts? Do you care?
- Karsten
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
17 years
Self Introduction: Frank
by Francis Earl
My real name is Francis Earl, for obvious reason however, I prefer
Frank. I currently reside in Phoenix, Arizona. (PST)
I'm currently not working, however I am 3 classes from an AAS in Network
Technology.
My primary purpose for joining the arts team is to hopefully make entry
easier for people interested in Fedora. I wish to do this by providing
information on fedoraproject.org that will hopefully assist them in
getting started. I believe that other projects are so popular because
the requirements for entry are lower, and hopefully I'll help ensure
Fedora starts down a similar path.
I was an early contributor to Ubuntu documentation, and have made
contributions to
many OpenSUSE wiki pages. These are mostly related to what normal users
will want to do when they get started, very basic things explained
because I was sick of answering them in the IRC channels, and also to
remind me of the process :)
I don't think anything really makes me an excellent match for the
project. I think I simply have the time to write the pages many would
find tedious, things directed at new users. Everyone was one once
though, and I don't know about you, but it was very confusing for me.
There are no User Manuals for Fedora users, I believe the wiki should
become exactly that. A User Manual for Users by Users, and I don't think
such things can be written by anyone but the users :)
I feel like I just went through an interview process, is that really the
feel people want for contribution to the project?
-------------------------------------------------
[fearl@thabox ~]$ gpg --fingerprint 7BDB4407
pub 1024D/7BDB4407 2007-04-29
Key fingerprint = 7125 6099 AAEF C64F 3F3E DC5F 9172 8F72 7BDB
4407
uid Frank Earl (Trey) <lunitik(a)gmail.com>
sub 2048g/590237A4 2007-04-29
17 years
FDSCo Meeting 2007-05-20 Summary
by Karsten Wade
Attendees:
-----------
= FDSCo Folken =
Bart Couvreur (couf)
John Babich (jmbuser)
Karsten Wade (quaid)
[[Note]] No quorum of FDSCo were present
= Ye Olde Peanut Gallery =
Jonathan Roberts (jonrob)
Summary:
---------
* Release notes are building from CVS HEAD, ready for F7
* Top writing and editing need this week is the Installation Guide; help
if you can:
export CVSROOT=:pserver:anonymous@cvs.fedora.redhat.com:/cvs/docs
cvs -z3 login
cvs -z3 co install-guide-devel
cd install-guide-devel/install-guide
make xml-validate ## this step generates needed XML files
yelp en_US/install-guide.xml &
* Post-edit, Installation Guide on-target for POT drop for translation
* All other guides are not essential for F7 release; they will complete
ASAP, then be made available for translation on a rolling basis
* Bulk of writing for other guides (User, Administration) to be done
between releases, then updated as needed just prior to the next release
* Proposing that the Software Management Guide content be divided into
the User and Administration Guides:
"updating your software -> DUG, adding repo's -> AG"
* We need to make sure that our published documents on docs.fp.o are
using the ab_XY (language_COUNTRYCODE) designation, e.g. en_US, pt_BR.
* docs.fp.o could happily take on the new CSS look/feel being rolled out
for F7
17 years
FDSCo Meeting 2007-05-15 Summary
by Karsten Wade
Attendees:
-----------
= FDSCo =
Bart Couvreur (couf)
Paul W. Frields (stickster)
Karsten Wade (quaid)
Bob Jensen (EvilBob)
John Babich (jmbuser)
= Peanut Gallery =
Guillermo Gomez (gomix)
Summary:
---------
* Translation of release notes and related files that comprise the
fedora-release-notes package are essentially complete:
http://fedoraproject.org/wiki/DocsProject/Translation/Statistics
* No additional items were added to the release notes, we'll be relying
upon the Web-only version
* Each XML page of the release notes is going to have a copy of the
admonition to refer to the Web-based notes for the latest information.
Annoying, but with deep-linking and such, it makes sure people know
about those Web-only notes. This will be on substantive pages, not e.g.
Colophon.xml
* PackageChanges content is going to be on the Wiki only, so is removed
from the packaged notes
* Installation Guide (IG) on schedule for translation drop and release:
http://fedoraproject.org/wiki/DocsProject/Schedule#Guides
* Translations of the guides are released on a rolling basis -- when
done, they are published. This is different from e.g. the release
notes, which need to ship with the ISO. When a translation is
completed, the translator posts a note on the publish page:
http://fedoraproject.org/wiki/DocsProject/PublishQueue
* Target content for F7 release is: release notes (and related bits)
and the Installation Guide. We are pushing to release the English
version of the guides
* The PublishQueue needs to make it into the Translation Quick Start
Guide:
http://bugzilla.redhat.com/bugzilla/198848
... at least until we have a new method in the middle of this summer :)
17 years
