User:Laubersm

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(adding links)
(Self Introduction - a.k.a "How I got here": update)
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
I am just getting started with [http://fedoraproject.org/wiki/DocsProject Fedora Docs].
+
<!-- Use code like this to put your hackergotchi or whatnot on the right side of the page. -->
 +
<!-- Upload the file and edit the code below to match. -->
 +
<!-- [[Image:|right]] -->
  
=Current Projects=
+
<!-- [[Image:userpicexample.png|thumbnail|right|frame|'''Don't forget to replace your_name.png with actual file name when uploading. Then edit this page and put the uploaded file name in place of <nowiki>Image:username.png</nowiki>.''']] -->
As I get started and learn the tools, I hope to help document the [http://fedoraproject.org/wiki/DocsProject/WorkFlow processes/workflow] so it is easier for other people to also [http://fedoraproject.org/wiki/DocsProject/Join get started].
+
  
Over the holiday and through the [https://fedoraproject.org/wiki/Docs_Project_Holiday_Virtual_Hackfest hackfest] and [http://fedoraproject.org/wiki/FUDCon/FUDConF11 FUDcon], I will add tips and reminders here.
+
== Contact ==
 +
[[Image:Hackergotchi-Laubersm.png|right]]
 +
* '''Email''': laubersm AT fedoraproject dOt org
 +
* '''IRC''': laubersm on [http://freenode.net freenode] (mostly in #fedora-docs but also others)
 +
* '''Fedora Account System''': Laubersm
 +
* '''GPG key''':
 +
<pre>
 +
pub  1024D/BFA10974 2005-12-13
 +
      Key fingerprint = 15AC F794 A3D9 64D1 D9CE  4C26 EFC3 11C2 BFA1 0974
 +
uid                  Susan Lauber <sml@laubersolutions.com>
 +
uid                  Lauber System Solutions, Inc. <lauber@ties.org>
 +
uid                  Susan Lauber <susan@ties.org>
 +
uid                  Susan Lauber <laubersm@gmail.com>
 +
uid                  Susan Lauber (Fedora Project) <laubersm@fedoraproject.org>
 +
sub  2048g/6425FFD3 2005-12-13
 +
</pre>
  
===communication===
+
==Current Projects==
*a FAS account [https://admin.fedoraproject.org/accounts/user/new create an account]
+
*mailing lists - [https://listman.redhat.com/mailman/listinfo/fedora-docs-list fedora-docs-list] and [https://admin.fedoraproject.org/mailman/listinfo/fedora-wiki fedora-wiki-list]
+
*ssh keys, gpg keys
+
*irc (client and nickname)- [https://fedoraproject.org/wiki/Communicate/IRCHowTo Fedora IRCHowTO]
+
*weekly irc meeting [https://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Meetings agenda]
+
*[https://fedoraproject.org/wiki/Communicate/GobbyHowTo gobby] collaboration tool
+
  
===guides===
+
I am a general contributor to the [[DocsProject | Docs Project]] which includes wiki gardening and assisting with the various guides such as the Users Guide and the Installation Guide which are updated each release. I would like to do more with the security related guides.
*style guide
+
*naming guide
+
*[https://fedoraproject.org/wiki/Wiki_gardening wiki gardening]
+
===packages/technologies===
+
*[http://git.or.cz/ git] an open source version control system in the category of distributed source code management tools
+
**[http://git.fedoraproject.org/git/ Fedora's git projects]
+
**[http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html gittuorial(7)]
+
**[[Git talk for and by dummies at FUDCon F11]] presenter notes
+
**[[User:laubersm/Git talk at FUDCon F11]] my notes from git talk fudcon11
+
**[[Git Talk FUDCon10]] a page from [[:Category:Pages that need love]]
+
 
+
  
*[https://fedorahosted.org/publican/ Publican] and the Fedora branding: <pre>su -c "yum install publican publican-fedora"</pre>
+
I am a member of the [[Ambassadors]] group. When I looked at the list of Ambassadors, I was surprised at how few are from North Carolina.  I also found that I could answer yes to all three of the questions raised on the [[Ambassadors/Join | join]] page and that as an Linux instructor in my $dayjob I already do many of the other tasks listed under how to be an active ambassador.
**[http://jfearn.fedorapeople.org/Publican/index.html User's Guide]
+
**[http://iquaid.org/2008/03/30/reviewing-toolchains-publican-and-cvsdocs/ Some reasons why (iquaid.org)]
+
 
+
  
*[http://www.docbook.org/ DocBook]
+
I am still interested in assisting the [[Infrastructure]] team and am on several of the mailing lists from when I joined several years ago.  It is an excellent way to watch a large project make use of cutting edge technology and if I could just dedicate some more time to it, I could learn so much about products I am aware of, interested in, but have not had a chance to really implement.
**[[DocsProject/DocBook]] has notes and more links for how we use DocBook.
+
**[[DocBook BarCamp session FUDConF11]] - my notes (thankfully cleanup by someone) plus the presentation slides
+
 
+
  
*[http://www.w3schools.com/xml/default.asp XML]
+
==Past Projects==
 
+
*soon: [[CMS solution for Fedora Project websites]]
+
  
=FUDCON=
+
As I was getting started, I took notes in hopes of helping the [[DocsProject/WorkFlow]] so it is easier for other people to also [[Join]]. Over the 2008 Christmas holiday and through the [[Docs Project Holiday Virtual Hackfest]] and [http://fedoraproject.org/wiki/FUDCon/FUDConF11 FUDcon], I added tips and reminders.  These are now located at
==links==
+
* [[User:Laubersm/Getting started with the docs project notes]]
*[[Docs_Project_tasks_during_FUDConF11]]
+
* [[User:Laubersm/Notes and links from FUDCON F11]]
*[[:User:Ianweller/FUDConF11_State_of_the_Wiki_presentation]]
+
*[[Your_Docs_Project_BarCamp_session_FUDConF11]]
+
  
*See writeup of BarCamp sessions - some by presenters, some by attendees: [[:Category:FUDConF11_BarCamp_sessions]]
+
<!--
 +
wiki pages that I would like to seen created, expanded, or generally cleaned up but haven't gotten to yet
 +
* Managing documentation guides with git (cloning, git vs ssh, global config, local config, branches, add, commit, push, diff, revert)
 +
* Category:Wiki Mainatainers with some of Ian's templates, how to patrol, tips for the cleanup process, using Special pages, etc.
 +
* Release Notes process - including [[Docs decisions for F12]]
 +
-->
  
*see a list of existing categories: [[:Special:Categories]] and special pages: [[:Special:SpecialPages]]
+
I have "herded cats" for updates to the User Guide and was the lead for that document for a couple of releases.
  
*In the end we want only a handful of top level categories: [[:Special:UncategorizedCategories]]
+
When I had more time to dedicate to the wiki each week, I was the Docs Project contact person for the Packaging Guide and related documentation.  Tasks were listed in [[Docs_tasks_for_Packaging_Guide_and_related_materials]].  The first step was wiki cleanup.  Then looking into using the CMS for better workflow and access control with the actual Packaging Guide documentation. As the testing of the CMS started, I also applied to the [[Infrastructure]] team.  Toshio was nice enough to ask and to sponsor me so that I can at least be involved in the testing of the CMS.  I am interested in being on the team but concerned that I do not have the time to contribute as much as is necessary.  Time will tell (pun intended).
  
* wikibot - is available (pywikibot) move pages, rename pages, remove double redirects, [[Wikibot_page_restructuring]]
+
==Self Introduction - a.k.a "How I got here"==
 
+
* wikipedia style manual for more organization tips
+
 
+
==QandA==
+
*Question: why cms instead of wiki?
+
** really it is not instead of - it is in addition to...
+
** wiki - quick collaboration, easily updated, frequently changing, end-users
+
** cms - more static content that must be in xml (docs) and transated and more restricted content like packaging and legal and logos. and lifecycle tracking - to end of life version specific content.
+
 
+
==wiki Pagenaming/style tip==
+
*page can only be in one namespace but can have multi categories.
+
*level1 headers are deprecated and bad bad bad - (page name can have spaces so name your page the level1 headers)
+
*first thing should not be section header so you get an intro para THEN the table of contents in intro mention that title (in bold). From mediawiki style guide.
+
*put category at the bottom of page
+
*can we find pages with a l1 header - and rename page using l1 header and remove l1 header
+
*look at [[https://fedoraproject.org/wiki/Category:Fonts fonts]] as how category page can have it's own content. uses templates to then list all pages within that category.
+
 
+
==Docbook presentation notes==
+
Note: This is just what is new to me and I have used docbook before so ...
+
so it is not all notes from the talk . See above for link to docbook documentation.
+
 
+
*do not forget the declaration for xml DOCTYPE docbook.dtd at the beginning.
+
** it may be used by tools (validators) or created by tools (Publican)
+
** it is used for validation
+
** we are using V4.4
+
** cut and paste - but note book vs article
+
 
+
*first element must match declaration (book vs article)
+
 
+
*Xincludes
+
** helps with repurposing content
+
** ie each chapter is in its own file. then the book/article just includes with appropriate chapters.
+
** can include any type - chapter, para, ...
+
 
+
*ENTITY
+
** define the entity  !ENTITY DISTRO "The Susan spin of Fedora"
+
*** inline or through a reference to a separate file (.ent file)
+
** publican will auto include (and use fedora-branding for this and more)
+
** use as &DISTRO; in content
+
 
+
*tools tools (for any xml not just docbook)
+
** xmlint - does it follow the dtd
+
** xsltproc - transforms to other types like pdf or html
+
** xmltidy
+
 
+
*toolchains
+
** lots of older one and custom one.
+
** Fedora now including and using Publican
+
 
+
* file.xml -> xsltproc -> file.fo -> fop -> file.pdf
+
** xsltproc read in style sheet
+
** fo is about layout
+
 
+
*publican
+
** can create template
+
<pre>create_book --brand=fedora --type=article --name=article2 </pre>
+
 
+
==git for dummies by dummies==
+
 
+
<pre> yum install git-all</pre>
+
 
+
<code>git-config</code> program is deprecated
+
 
+
<pre>git config --global user.name 'Susan Lauber'</pre>
+
 
+
*writes out to .gitconfig
+
*I missed Paul's list of other global settings as a minimum
+
 
+
Get a copy of a repo
+
*make a directory for your copy then clone the repo
+
<pre>git clone ssh://git.fedorahosts.org/git/docs/install-guide</pre>
+
 
+
*uses the .git subdir to hold objects, logs, info, branches, refs, and more
+
* .git/hooks include scripts
+
* .git/branches are low overhead, easy, very useful
+
* .git/HEAD points to tip of history
+
 
+
..missing stuff.. while checking gpg fingerprints...
+
 
+
useful git commands:
+
*status
+
*diff  and diff --cached  (from the "mob teaches Paul" series)
+
*add
+
*commit and commit -a
+
 
+
during commit edit msg
+
* first line,keep it short (summery and email subject)
+
* skip a line then type a longer log (details and email body)
+
 
+
git commit is just committing to local repo
+
git push actually pushes up
+
 
+
<code>git-format-patch</code>  to generate a patch file
+
 
+
reverting: <code>git reset</code>
+
 
+
more recommended documentation: [[http://book.git-scm.com/ Git Community Book]]
+
 
+
=Self Introduction=
+
 
Greetings,
 
Greetings,
  
I have been meaning to get more involved with fedoraproject for a while and I have been lurking here on the docs list for a few weeks now. I was struggling a little to figure out how this project worked but then I rescued about 50 messages from my spam folder and it is now starting to make more sense :)
+
I had been meaning to get more involved with fedoraproject for a while before I finally made the commitment. For all that I use and recommend opensource, this is the first project I actually joined (better late then never I guess).
  
I have been a contract instructor for Red Hat since 2000 and involved in network operating system support and training since 1992 (and *nix user even longer). I have contributed to Red Hat course materials including general bug reports, testing updated labs, helping to update the online training from RHEL3 to RHEL4, and providing content for the first release of Red Hat Academy materials.  
+
I am interested in all things related to learning and teaching - documentation, planning, consulting, corporate training, university settings, and youngsters too.
  
The Red Hat Academy project involved working with DocBook.
+
I have been a contract instructor for Red Hat since 2000 and involved in network operating system support and training since 1992 (and *nix user even longer). I have contributed to Red Hat course materials including general bug reports, testing updated labs, contributing to online course content and videos, updating existing courses, and providing content for the first release and later updates of Red Hat Academy materials (with docbook). I also teach courses related to other Linux distributions and general computing security topics.  In addition to teaching formal classes, I also do some consulting and really enjoy the short assignments that are often mostly an informal skill transfer.
I have taught and used cvs, seen subversion, and am sure I can figure out git relatively quickly.
+
I am not as versed in wiki and irc etiquette and usage but I have been poking around and reading some of the intro and FAQ docs and of course I have had plenty of experience with mailing lists and AIM.
+
  
And for all that I use and recommend opensource, this is the first project I have actually joined (better late then never I guess).
+
I started with the docs project because it seemed that I had most of the skills needed, felt confident that I could quickly pick up the remaining skills, and it seemed to be the most flexible on time commitments.  I had taught and used cvs and seen subversion so I quickly figuring out the basics of using git. I was new to wiki syntax and irc etiquette but I after poking around and reading some of the intro and FAQ docs I quickly felt comfortable with those tools as well.  
  
I am interested in all things related to learning and teaching - documentation, corporate training, university settings, and youngsters too.
+
I am interested in learning new software through the infrastructure team and expanding my rpm packaging skills.
 
+
I am also lurking on the OLPC list and as a longer term goal, I would like to learn more about packaging.
+
  
 
-Susan
 
-Susan
 
<pre>
 
pub  1024D/BFA10974 2005-12-13
 
      Key fingerprint = 15AC F794 A3D9 64D1 D9CE  4C26 EFC3 11C2 BFA1 0974
 
uid                  Lauber System Solutions, Inc. <lauber@ties.org>
 
uid                  Susan Lauber <susan@ties.org>
 
uid                  Susan Lauber <laubersm@gmail.com>
 
uid                  Susan Lauber <sml@laubersolutions.com>
 
sub  2048g/6425FFD3 2005-12-13
 
</pre>
 
  
 
--  
 
--  
Susan Lauber, (RHCX, RHCA, RHCSS)<br>
+
Susan Lauber, (RHCX, RHCSS, RHCA, RHCVA, CISSP)<br>
 
Lauber System Solutions, Inc. <br>
 
Lauber System Solutions, Inc. <br>
 
http://www.laubersolutions.com <br>
 
http://www.laubersolutions.com <br>
 
gpg: 15AC F794 A3D9 64D1 D9CE  4C26 EFC3 11C2 BFA1 0974
 
gpg: 15AC F794 A3D9 64D1 D9CE  4C26 EFC3 11C2 BFA1 0974
 +
 +
My [https://www.redhat.com/archives/fedora-docs-list/2008-November/msg00000.html self introduction] to the docs project list.
 +
My [https://www.redhat.com/archives/fedora-devel-list/2009-January/msg01545.html introduction] to the packaging and devel lists concerning wiki cleanup.
 +
 +
 +
 +
[[Category:Ambassadors from the USA]]

Revision as of 13:31, 5 October 2012


Contents

Contact

Hackergotchi-Laubersm.png
  • Email: laubersm AT fedoraproject dOt org
  • IRC: laubersm on freenode (mostly in #fedora-docs but also others)
  • Fedora Account System: Laubersm
  • GPG key:
pub   1024D/BFA10974 2005-12-13
      Key fingerprint = 15AC F794 A3D9 64D1 D9CE  4C26 EFC3 11C2 BFA1 0974
uid                  Susan Lauber <sml@laubersolutions.com>
uid                  Lauber System Solutions, Inc. <lauber@ties.org>
uid                  Susan Lauber <susan@ties.org>
uid                  Susan Lauber <laubersm@gmail.com>
uid                  Susan Lauber (Fedora Project) <laubersm@fedoraproject.org>
sub   2048g/6425FFD3 2005-12-13

Current Projects

I am a general contributor to the Docs Project which includes wiki gardening and assisting with the various guides such as the Users Guide and the Installation Guide which are updated each release. I would like to do more with the security related guides.

I am a member of the Ambassadors group. When I looked at the list of Ambassadors, I was surprised at how few are from North Carolina. I also found that I could answer yes to all three of the questions raised on the join page and that as an Linux instructor in my $dayjob I already do many of the other tasks listed under how to be an active ambassador.

I am still interested in assisting the Infrastructure team and am on several of the mailing lists from when I joined several years ago. It is an excellent way to watch a large project make use of cutting edge technology and if I could just dedicate some more time to it, I could learn so much about products I am aware of, interested in, but have not had a chance to really implement.

Past Projects

As I was getting started, I took notes in hopes of helping the DocsProject/WorkFlow so it is easier for other people to also Join. Over the 2008 Christmas holiday and through the Docs Project Holiday Virtual Hackfest and FUDcon, I added tips and reminders. These are now located at


I have "herded cats" for updates to the User Guide and was the lead for that document for a couple of releases.

When I had more time to dedicate to the wiki each week, I was the Docs Project contact person for the Packaging Guide and related documentation. Tasks were listed in Docs_tasks_for_Packaging_Guide_and_related_materials. The first step was wiki cleanup. Then looking into using the CMS for better workflow and access control with the actual Packaging Guide documentation. As the testing of the CMS started, I also applied to the Infrastructure team. Toshio was nice enough to ask and to sponsor me so that I can at least be involved in the testing of the CMS. I am interested in being on the team but concerned that I do not have the time to contribute as much as is necessary. Time will tell (pun intended).

Self Introduction - a.k.a "How I got here"

Greetings,

I had been meaning to get more involved with fedoraproject for a while before I finally made the commitment. For all that I use and recommend opensource, this is the first project I actually joined (better late then never I guess).

I am interested in all things related to learning and teaching - documentation, planning, consulting, corporate training, university settings, and youngsters too.

I have been a contract instructor for Red Hat since 2000 and involved in network operating system support and training since 1992 (and *nix user even longer). I have contributed to Red Hat course materials including general bug reports, testing updated labs, contributing to online course content and videos, updating existing courses, and providing content for the first release and later updates of Red Hat Academy materials (with docbook). I also teach courses related to other Linux distributions and general computing security topics. In addition to teaching formal classes, I also do some consulting and really enjoy the short assignments that are often mostly an informal skill transfer.

I started with the docs project because it seemed that I had most of the skills needed, felt confident that I could quickly pick up the remaining skills, and it seemed to be the most flexible on time commitments. I had taught and used cvs and seen subversion so I quickly figuring out the basics of using git. I was new to wiki syntax and irc etiquette but I after poking around and reading some of the intro and FAQ docs I quickly felt comfortable with those tools as well.

I am interested in learning new software through the infrastructure team and expanding my rpm packaging skills.

-Susan

-- Susan Lauber, (RHCX, RHCSS, RHCA, RHCVA, CISSP)
Lauber System Solutions, Inc.
http://www.laubersolutions.com
gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974

My self introduction to the docs project list. My introduction to the packaging and devel lists concerning wiki cleanup.