From: Russ Pavlicek <russell.pavlicek@xenproject.org>
To: xen-devel@lists.xen.org
Subject: Xen Document Day is next TUESDAY 28 May
Date: Fri, 24 May 2013 09:44:24 -0400 [thread overview]
Message-ID: <CAHehzX2gAM-_AH6=vNt2aN_UEMi2_c6KF-rn1j3xgBe8WyA-Fw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1027 bytes --]
REMINDER: Xen Document Day is next TUESDAY due to holidays next Monday
in multiple countries.
*********************
* Xen Document Days *
*********************
We have another Xen document day come up next *TUESDAY*. Xen Document Days
are for people who care about Xen Documentation and want to improve it.
We introduced Documentation Days, because working on documentation in
parallel with like minded-people, is just more fun than working alone!
Everybody who can contribute is welcome to join!
For a list of items that need work, check out the community maintained
TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO
<http://wiki.xen.org/wiki/Xen_Document_Days/TODO>). Of course, you can
work on anything you like: the list just provides suggestions.
How do I participate?
=====================
- Join us on IRC: freenode channel #xendocs
- Tell people what you intend to work on (to avoid doing something somebody
else is already working on)
- Fix some documentation
- Help others
- And above all: have fun!
[-- Attachment #1.2: Type: text/html, Size: 1504 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
reply other threads:[~2013-05-24 13:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHehzX2gAM-_AH6=vNt2aN_UEMi2_c6KF-rn1j3xgBe8WyA-Fw@mail.gmail.com' \
--to=russell.pavlicek@xenproject.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).