All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	xen-api@lists.xen.org,
	"xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	xen-arm@lists.xen.org
Cc: "lars.kurth@xen.org" <lars.kurth@xen.org>, wei.liu2@citrix.com
Subject: Xen Document Day: Feb 25th, 2013 on IRC freenode #xendocs
Date: Mon, 18 Feb 2013 15:14:13 +0000	[thread overview]
Message-ID: <1361200453.3825.19.camel__16631.606539204$1361200853$gmane$org@zion.uk.xensource.com> (raw)

Hi everybody

A quick reminder that the next Xen Document Day is happening next Monday
(Feb 25). More info on document days at

http://wiki.xen.org/wiki/Xen_Document_Days

Hope to see you on IRC! Feel free to add stuff to the TODO
list(http://wiki.xen.org/wiki/Xen_Document_Days/TODO) or put your name
besides an item if you intend to work on it.


Best Regards
Wei.


********************* 
* Xen Document Days * 
********************* 

We have another Xen document day come up next Monday. 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). 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!

                 reply	other threads:[~2013-02-18 15:14 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='1361200453.3825.19.camel__16631.606539204$1361200853$gmane$org@zion.uk.xensource.com' \
    --to=wei.liu2@citrix.com \
    --cc=lars.kurth@xen.org \
    --cc=xen-api@lists.xen.org \
    --cc=xen-arm@lists.xen.org \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.