Introducing myself
by martin scun
Hi! My name is Martin Scuncia. I'm from Argentina. I'm 20 years old. I'm an
engineering student. I had the experience of using several linux distros,
like ubuntu, debian, openSUSE. But I'm a fedora fan! Now I'm using Fedora
13 (yes, an old version, hahaha), but soon I will download the Fedora 18.
I never have worked in a linux project.
As an user of several different linux distribution, I was bothered by
various bugs. Those bugs allowed me to learn a lot of things, specially
solving hardware configuration problems, and working with a lot of
important packages. I'm a great fan of the terminal. In some task, like
installing software and packages, and working with configuration modules,
is a really fast tool; faster than using the gnome. By the way, I prefer a
gnome desktop instead of KDE.
I have some skills in networks configuration and administration. I know a
little python.
As an aerospacial engineering student, I have abilities on confectioning
technical documentation. My useful social skill for the Docs Project is
solidarity. I am always willing to help someone. I wouldn't have learn
anything about linux, if someone on the web had not share his knowledge. I
want to do the same, working for the documantation project.
This is my CPG keyid:
[root@mshome ~]# gpg --fingerprint 495F2720
pub 2048R/495F2720 2013-05-10 [caduca: 2014-02-04]
Huella de clave = B3ED 1D6C 7700 A068 1186 0CEF 258B 6624 495F 2720
uid Martin Scuncia (nanofan) <msscuncia(a)gmail.com>
sub 2048R/3E8219BA 2013-05-10 [caduca: 2014-02-04]
10 years, 11 months
Hello / Bonjour from Montreal
by Leslie S Satenstein
Hi docs group
* Name (Mr) Leslie Satenstein
* GMt-5, Canada (Montréal Québec)
* Basic skills and experiences. 50 years in IT, many many years of technical writing for operations, support and users. As well, a Fedora user since Core (2005)
* Why you're joining I noted that some of the English documentation was written with slang, which made it difficult to translate to French or Spanish. I am fluent in French, write/read/speak, edit.
* What you're looking to do (be specific) Initially, I saw that the websites were only partially translated to French, and this needs to be completed. The second reason, the English to French translations were literal (using software translation), and this results in the wrong words being presented.
* How much time you can contribute (usually hours per week). Between 4 to 8 hours per week.
* I can work on English documentation and translation of same or other to French.
Regards
Leslie
Mr. Leslie Satenstein
An experienced Information Technology specialist.
Yesterday was a good day, today is a better day,
and tomorrow will be even better.lsatenstein(a)yahoo.com
alternative: leslie.satenstein(a)gmail.com
SENT FROM MY OPEN SOURCE LINUX SYSTEM.
10 years, 11 months
A reminder to writers
by John J. McDonough
Within our documentation, we do not like to over use the word "see" as
this can be an uncomfortable reminder to visually impaired readers. It
is especially challenging in the Release Notes as almost every other
paragraph tends to refer the reader to an external link. The result is
paragraph after paragraph of "for details see ..." or "for more
information see ...".
Instead of "see", it is preferable to use terms like "refer to", "may be
found at" or other terms that do not imply a particular way of reading.
When referencing some user-visible change, exchange terms like "users
will see improved performance" for phrases like "users will notice
improved performance".
Simply being alert to this also helps make the prose a little less
repetitive.
Thanks
--McD
10 years, 11 months
Maintainer input on release notes
by John J. McDonough
We had a short discussion of this at this morning's meeting but felt a
broader discussion here was warranted.
When preparing the Release Notes, we often ask the developers for wiki
input, and generally come up dry. More recently, we look though the
repos for changes, but the upstream release notes are often very poor or
nonexistent. Every release includes literally thousands of changed
packages, and while we strive to document "significant" changes, these
poor upstream release notes leave us little clue as to what constitutes
"significant". Certainly the feature pages get us started, but they
only capture a tiny fraction of what changes in a release.
But if we think about the maintainers, chances are they begin working on
the next thing just as soon as the compose closes for the previous
release, if not sooner. Very likely they have an interest in the
packages they are maintaining, and it would not be surprising if they
viewed some features to be important.
But by the time we ask for input, odds are they have moved on and most
of the updated packages in the new release are ancient history.
However, if we were to open the beats as soon as possible, certainly
when the compose closes or even as soon as we have converted the beats
to XML, then the developers could make a note in the wiki about what is
significant, right at the time they are working on it and interested in
it.
Of course we would still need to remind the maintainers that we want
their input, and especially that it doesn't need to be beautiful prose -
all we really need is a clue as to what is important. But I think if we
can capture the input early, we have better odds of getting more
complete release notes.
Is this something we should do? Is there something different we should
be doing?
--McD
10 years, 11 months
Fedora Docs Meeting 1400UTC 13 May 2013
by Pete Travis
It's meeting time again - in the usual place, #fedora-meeting on freenode.
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
10 years, 11 months
(no subject)
by martin scun
Hi! My name is Martin Scuncia. I'm from Argentina. I'm 20 years old. I'm an
engineering student. I had the experience of using several linux distros,
like ubuntu, debian, openSUSE. But I'm a fedora fan! Now I'm using Fedora
13 (yes, an old version, hahaha), but soon I will download the Fedora 18.
I never have worked in a linux project.
As an user of several different linux distribution, I was bothered by
various bugs. Those bugs allowed me to learn a lot of things, specially
solving hardware configuration problems, and working with a lot of
important packages. I'm a great fan of the terminal. In some task, like
installing software and packages, and working with configuration modules,
is a really fast tool; faster than using the gnome. By the way, I prefer a
gnome desktop instead of KDE.
I have some skills in networks configuration and administration. I know a
little python.
As an aerospacial engineering student, I have abilities on confectioning
technical documentation. My useful social skill for the Docs Project is
solidarity. I am always willing to help someone. I wouldn't have learn
anything about linux, if someone on the web had not share his knowledge. I
want to do the same, working for the documantation project.
This is my CPG keyid:
[root@mshome ~]# gpg --fingerprint 495F2720
pub 2048R/495F2720 2013-05-10 [caduca: 2014-02-04]
Huella de clave = B3ED 1D6C 7700 A068 1186 0CEF 258B 6624 495F 2720
uid Martin Scuncia (nanofan) <msscuncia(a)gmail.com>
sub 2048R/3E8219BA 2013-05-10 [caduca: 2014-02-04]
10 years, 11 months
Fedora Docs Meeting - 6 May 2012 1400UTC
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
GDTY, Docs writers!
We're having a meeting soon, at 1400UTC in #fedora-meeting on freenode. Hope
you can make it!
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRh0y+AAoJEL1wZM0+jj2Z45gH+gLjlB4AAq+WopA7jAef+4Qf
drr8Ov3ZBnkc+P/6EnqK11X3FycHGJlkfSMtLHNY7Oj8ziZFPuJlR3rmBQR/XjOJ
9Exn6G+9ujIlXqki6i/U2CSAyJZNGIIhFKfSrMtL4oVpl5+xr5aog2M6yeUyhXz8
REClT1zuqWU6IW5HquuHUFvm3DkRww+a4BvD1/OLjx7+GS+jk02fPcIxwUZyctNt
FtB0XrLOEqavh84QzkOqGKnvuqDHN8Cfn8X5LhH765sfxecGMTRwmjvJGDNPYYyD
xziseQ3TxwXkwp04qlWSuM6DdcV04cJX6dCQZyIegBLf2+/fR5b1BjcBv3WXETs=
=Y7rH
-----END PGP SIGNATURE-----
10 years, 11 months
