Self introduction: Kirsti van Wessel
by Kirsti van Wessel
My name is Kirsti van Wessel and I am currently a Support Relationship Manager with Red Hat
My background in writing comes from my early career in IT, when I developed training material for an outsourcing company.
In every job after I liked to keep my work documented, so that others can take over when I am gone.
For software vendors to be considered good and dependable, documentation is an essential.
In my previous jobs I have been specializing heavily in the desktop, hardware as well as everything that runs on it.
So imaging and rolling out desktops up to Windows 7, Ms Office expert (technical and functional), packaging of software, print server management, SharePoint Server 2007, Exchange up to 2003, housstyle (branding) programming (VBA).
I have been running Ubuntu desktop at home for about 7 years, getting a knowledge base slightly over beginner. I am in any case not new to the command prompt, and am not afraid to use it.
I have a basic knowledge of HTML, and can read CSS and VB scripts.
Before moving to the UK to work for Red Hat I have been a project/program manager, and in later years IT advisor for the City of Rotterdam.
In these roles I have improved my social skills, and have followed extensive soft skill training, including coaching.
Working in the Open Source industry now, I would like to contribute. Being a native Dutch speaker, I have looked at the Dutch translations on the Fedora site, and they could do with some tuning up, language wise.
Having graduated with a BA in English I realise I would like to have a look at the grammar and consistency in English manuals as well.
Before I start writing I think it would be a good experience to edit existing material. Partly to get to know the community, and to get used to the tools (Git would be entirely new for me for example).
I am a fairly fast learner, and am keen to pick up on anything that comes my way.
---------------------------------------------------------------------------------------------------
pub 2048R/5F5439AE 2015-03-17
Key fingerprint = A49C 242F 4200 71F3 9600 610D F36B E8CB 5F54 39AE
uid Kirsti van Wessel (kvanwess) <kvanwess(a)redhat.com>
sub 2048R/219D089E 2015-03-17
---------------------------------------------------------------------------------------------------
9 years
I missed yet another meeting, sigh
by kendell clark
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
hi all
My name is kendell clark, and I just switched over to fedora a couple
of weeks ago. I keep meaning to show up at the documentation meetings
but I keep sleeping through them. I've been working on the abandoned
accessibility guide, and I've basically completed it. The problem is,
I've only modified the plain text version, not the docbook xml markup.
I'll attach it so that others can look at it. Would anyone here be
willing to help convert that into the docbook that the fedora
documentation expects? I'm trying to learn the language so I can
eventually do this myself but I'm not there yet.
Thanks for reading
Kendell clark
Sent from Fedora GNU/Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJVFHCQAAoJEGYgJ5/kqBTdMR0QAJ7U+MlwOQZTuzmd9tt+yeZL
PNL6S7x3S7KMGWh1//MTSfHF/5rAutlPjVqAVVjVxFJXRJMm41wXbkrtjYTqsC7G
ew0k8wKULqRu8bboWMXoyhjRItG2oNTX6fEBQUa1bcWNO6I41RJXL93+UozCXOM7
i8lswgbh3AllmT67hSvMmtuDO+GNHT7cnXnRH+AzrBHc+5cKbcLKEb92DQL23lNo
SzAX3sRsT987ii8PHY/Chif5GILYMui19PRjNTsxlcO+tRB4R6iCFGdv5IwqoLvu
a/YrZIPOFKt/0pBEqH9DF0Nn2RML8smMj8XlHwtZrFw7V5YYq4twFI8Wa47Gnljy
rbuwqMsS31tcGmk7M1+c5ikeNbHsu/65osshGTSBeflSGq6RhIzYueoA/rgEr9jP
UC5H09EWJzsSIzafTlG0xqQhajjyU7/boBmijOSHSS+hc7flTLN1QXk0NIROwqwx
HzVweUKTyoR09b7ZuHBk0x+e2xa+nnFhBkUU1HayTC/zqxsiMTVoXtkPLgJ+kc0v
tfxgIQNt/uOXCv/1O5oMurqnbYVkNMrMwuAdpgtlny6jCmaworob84CwqhuvVp7B
elsQDizVCfZ4xGAU7lXFUdzySwU9/Fr5tBzTwgFWzBYT4rF67xdyEv8iTw5fdHoj
BfwiQDlfl0guIx37df5N
=kUdk
-----END PGP SIGNATURE-----
9 years
Need some remedial git help
by Sandra McCann
Hi folks -
I’m trying to follow these direction
<http://fedoraproject.org/wiki/Infrastructure/fedorapeople.org#Pushing_to_...>s
so that I have a personal branch to work on the virt getting started guide,
that is backed up to fedorapeople. Somehow I’m failing but I don’t know
where.
This is what I tried :
1.
git clone --bare
https://git.fedorahosted.org/cgit/docs/virtualization-getting-started-gui...
virtualization-getting-started-guide.git
2.
cd virtualization-getting-started-guide.git
3.
git branch smccann_virtmanager
4.
git checkout smccann_virtmanager
This gives me the following error: fatal: this operation must be run in a
work tree.
Looking that up, it seems I shouldn’t have cloned as --bare.
So I try again….w/o the bare…
1.
git clone
https://git.fedorahosted.org/cgit/docs/virtualization-getting-started-gui...
virtualization-getting-started-guide.git
2.
cd virtualization-getting-started-guide.git
3.
git branch smccann_virtmanager
4.
git checkout smccann_virtmanager
this looks better…
1.
touch git-daemon-export-ok (so it’s visible on cgit)
scp it up to fedorapeople:
1.
scp -r virtualization-getting-started-guide.git/
mccann2(a)fedorapeople.org:
public_git/virtualization-getting-started-guide.git
So far so good. Let’s make a minor edit, add and commit…
1.
(edit Book_Info.xml and build to ensure it works)
2.
git add en-US/Book_Info.xml
3.
git commit -m ‘first commit. Fix Book_Info.xml so it will build’
Now try to push that to fedorapeople:
1.
git remote add fedorapeople mccann2(a)fedorapeople.org
:public_git/virtualization-getting-started-guide.git
2.
git push --mirror fedorapeople
This gets me the following batch of errors:
git push --mirror fedorapeople
Counting objects: 4, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 394 bytes | 0 bytes/s, done.
Total 4 (delta 3), reused 0 (delta 0)
remote: error: refusing to update checked out branch:
refs/heads/smccann_virtmanager
remote: error: By default, updating the current branch in a non-bare
repository
remote: error: is denied, because it will make the index and work tree
inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to
match
remote: error: the work tree to HEAD.
remote: error:
remote: error: You can set 'receive.denyCurrentBranch' configuration
variable t
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing
int
remote: error: its current branch; however, this is not recommended unless
you
remote: error: arranged to update its work tree to match what you pushed in
som
remote: error: other way.
remote: error:
remote: error: To squelch this message and still keep the default
behaviour, se
remote: error: 'receive.denyCurrentBranch' configuration variable to
'refuse'.
To mccann2(a)fedorapeople.org:
public_git/virtualization-getting-started-guide.git
! [remote rejected] smccann_virtmanager -> smccann_virtmanager (branch is
currently checked out)
error: failed to push some refs to 'mccann2(a)fedorapeople.org:
public_git/virtualization-getting-started-guide.git'
So now I’m lost in some weird catch-22 where --bare is needed for one set
of commands, but won’t work for the other. I’m guessing I’m missing
something obvious here… Any clues what that is?
Thanks,
Sandra
9 years
Help write the Fedora 22 Release Notes!
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
The Fedora 22 release preparations are in full swing. Between the Alpha
and Beta release, community members following F22 developments
collaborate on what will become the Release Notes.
This can be a great opportunity to make a contribution that doesn't
require a big time investment or background in documentation. Simply
choose a feature or piece of software that you love, read about the F22
version of that software, and write down what you learn.
A few tools will help. If you're using F22, you can get info about the
package, like the upstream developer's website, like this:
rpm -qi inkscape
And a package changelog like this:
rpm -q --changelog pidgin
Packaged documentation, which will often include a detailed CHANGELOG or
NEWS file, can be listed with:
rpm -qd cairo
If you aren't quite ready to make the jump to F22, don't worry, you can
still get the info. The `rpm` commands above work with `repoquery` too, ie:
repoquery -q --changelog gimp --releasever 22
The Fedora Packages app, https://apps.fedoraproject.org/packages/ , is
also a great way to get a picture of the package without installing it.
While the commands above will help get you on the right path, the best
information will usually come from the software's developers directly.
Big projects like XFCE or LibreOffice will have detailed release notes
of their own we can learn from, and even small projects will provide a
release announcement.
An item in the Release Notes should cover a few basic points:
1. What is this thing? What does it do?
2. How do I use it?
3. What's different about the new version in F22?
4. Where do I learn more?
Don't worry about making the writing perfect, we're still in the
information gathering stage. Pick an item, choose a section from
https://fedoraproject.org/wiki/Category:Documentation_beats , and leave
your note there. If you have questions, you can ask me or anyone in
#fedora-docs on freenode, or the docs list, or reply to this message on
the join list.
Around the beta release (that's in just a few weeks!) the content on the
wiki will converted to docbook and moved into a git repo. I'm looking
forward to reading what you write, thanks for helping show all the great
things Fedora has to offer.
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVDxCZAAoJEL1wZM0+jj2ZOTMH/1xOAqozjJbQnT1C0SvxBBn6
H323MrOdhpW24tFopduuzTYQGRYAIKk5LfYOzxcDuZ893sQLpf/bbCzWOJZwJJfP
kwdt40cF7bFp9U1iQMeBrQe5kp7RS8Uj+LaTHFXKc0HPBS3IYTag6vHz4kz5dorJ
6qw6f+qquroU48jl4MzKVO6zVhd2tLW6ifTDeyaEod8xehxlbslfztZHH13jRCHj
QlKUx59sWjCzBZ0rZaTYPixmq/C5tvScnwivUNAYHr+ToGIWhUPBQi2q/CE6e4RX
wobvs82uJD8YqjmTZjZLlNwtuhmZ4y2oheX1PFwEioGgklHPaWY4aDYPLLSkoZU=
=1NXr
-----END PGP SIGNATURE-----
9 years
Proposed plan for the Virtualization Getting Started Guide
by Sandra McCann
Hi folks -
We’ve been batting around ideas for the virtualization guides for a bit now
in irc, but I’d like to get some more feedback on the approach we can take.
Seems there are two personas involved. Using our draft personas
<https://fedoraproject.org/wiki/Docs_Project_Focus#Personas> we have :
-
Technical Tony - experienced IT person virtualizing on servers etc,
knows his stuff and is spinning up VMs like they’re candy.
-
Novice Ned (or Novice Nancy in my case :-) - Fairly new to
virtualization, and looking to spin up a VM or two for her own work.
Given these two personas, I’d like to suggest that the Virtualization
Getting Started guide be targeted to Novice Nancy. To do this we would:
-
Add an installing virtualization tools chapter - simple effort to
install the virtualization group package and bring up virt-manager.
(smccann)
-
Add an ‘Creating Guests with Virt-Manager chapter - copying from here
<http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/V...>.
(smccann)
-
Adding a ‘Creating Guests with Boxes chapter (grundblom)
-
Make minor edits as needed to remove Fedora 19 references and any
references (if present) to a larger set of virtualization guides that may
not be available as F21 guides yet.
I also had one question -
-
not sure what to do about the list of emulated devices - is it accurate?
http://docs.fedoraproject.org/en-US/Fedora/19/html/Virtualization_Getting...
Anyway, I’d like to get the getting started done and committed before
considering the Admin and Deploy guide (because..ahem.. I AM Novice Nancy
here and it will take longer for me to parse that guide).
Thoughts?
Sandra
9 years