All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>
To: lars.kurth@xen.org,
	"xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>
Subject: Re: Xen Documentation Day: March 26th
Date: Mon, 26 Mar 2012 13:19:59 +0800	[thread overview]
Message-ID: <4F6FFC7F.2030305@gmail.com> (raw)
In-Reply-To: <4F6C86D3.1040908@xen.org>

Hi!

I have connected to #xendocday chatroom but there's nobody there at all 
except me!

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)
Singapore

On 23/03/2012 22:21, Lars Kurth wrote:
> Hi,
>
> everybody. A quick reminder that the next Xen Document Day is 
> happening next Monday. For more detail see 
> http://blog.xen.org/index.php/2012/03/22/xen-documentation-day-march-26th/ 
> or below ...
>
> 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
> Lars
>
> *************************************
> * Xen Documentation Day: March 26th *
> *************************************
>
> 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 #xendocday
> - 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!
>
> Interesting items on the TODO list
> ==================================
> I just went through our community maintained Docs Day TODO list and 
> thought I’d
> highlight some items:
> - A feature status document that shows which features work in which 
> Xen release!
> That would be something for our developers to create!
> - Admin docs covering topics such as “Setting boot order for domUs (PV 
> and HVM)”,
> “Chaining pypxeboot and pygrub”, etc. Any proficient Xen user can help 
> put these together!
> - Reviewing Wiki main page categories such as Beginners could really 
> benefit from
> YOUR input. It would help to see whether the documents in a category 
> are useful
> to YOU and which ones should be highlighted in a trail.
> - There is also some easy Wiki maintenance work that needs doing: some 
> of it is as
> easy as formatting. Anybody who knows could do this!
>
> Personally, I will be working on:
> - A new “Why Xen” and maybe “Which Xen” document, to help people 
> decide whether Xen is
> for them and what flavour of Xen is best
> - I will also be working on content for the new xen.org website
>
> I am looking forward to the day and hopefully documentation days will 
> become a regular Xen event. See you on IRC!
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

       reply	other threads:[~2012-03-26  5:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F6C86D3.1040908@xen.org>
2012-03-26  5:19 ` Teo En Ming (Zhang Enming) [this message]
     [not found]   ` <CAE2VTbObeoh=YQJTiiWnWJbbM_jpFdpnQ69KTBA5jX+2nb_mbw@mail.gmail.com>
2012-03-26  6:40     ` [Xen-users] Xen Documentation Day: March 26th Teo En Ming (Zhang Enming)
2012-03-23 14:21 Lars Kurth

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=4F6FFC7F.2030305@gmail.com \
    --to=singapore.mr.teo.en.ming@gmail.com \
    --cc=lars.kurth@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.