From: Dilger, Andreas <andreas.dilger@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] lustre design docs
Date: Fri, 12 Jun 2015 21:49:04 +0000 [thread overview]
Message-ID: <D1A0AFE3.F7223%andreas.dilger@intel.com> (raw)
In-Reply-To: <9EE73FB1-18B8-4ADC-86BE-1C059358F798@cray.com>
On 2015/06/12, 3:04 PM, "Justin Miller" <jmiller@cray.com> wrote:
>I think a central document repository is a good idea, and would be a
>valuable asset. The plan you outline to collect the documents and
>metadata first and then convert the most useful documents to a
>maintainable format makes a lot of sense. In addition to the benefits you
>identify, it may also allow for the collection of some interesting
>metrics.
>
>I?d be happy to help with this project.
>
>- Justin Miller
>
>
>On 5/20/15, 1:06 PM, "lustre-devel on behalf of Vitaly Fertman"
><lustre-devel-bounces@lists.lustre.org on behalf of
>vitaly.fertman at seagate.com> wrote:
>
>>Hi All,
>>
>>there was an idea to publish existing design docs on opensfs wiki.
>>is centralised design repository interesting at all?
>>
>>currently the existing designs are not in the wiki format, mostly pdf,
>>so this is
>>not an ideal doc repository we want to have: not changeable, not
>>maintainable,
>>could be outdated, etc, but could be published very quickly.
>>
>>however, this is not the final step but just a beginning. at the same
>>time, we may get
>>some benefits immediately:
>>- all the docs are gathered in one centralised place, faster doc search;
>>- the fully documented product (although maybe not very up-to-date
>>initially) ?
>>attractive for many readers, especially newbies;
>>- a quick jump to unknown code having a design, faster than reading the
>>source code;
>>
>>after that, having these docs already published, next steps could be:
>>- docs to be split on those which are to be maintained and left
>>untouched;
>>- a procedure of converting to be maintained docs to wiki format could
>>be organised;
>>- a procedure of updating converted docs to be organised;
>>etc.
>>
>>would be valuable? thoughts?
>>
>>?
>>Vitaly?
>>_______________________________________________
>>lustre-devel mailing list
>>lustre-devel at lists.lustre.org
>>http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>_______________________________________________
>lustre-devel mailing list
>lustre-devel at lists.lustre.org
>http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>
Cheers, Andreas
--
Andreas Dilger
Lustre Software Architect
Intel High Performance Data Division
next prev parent reply other threads:[~2015-06-12 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 18:06 [lustre-devel] lustre design docs Vitaly Fertman
2015-05-26 15:08 ` Mohr
2015-06-12 21:04 ` Justin Miller
2015-06-12 21:49 ` Dilger, Andreas [this message]
2015-06-12 21:53 ` Dilger, Andreas
2015-06-12 22:49 ` John Suykerbuyk
2015-06-12 23:33 ` [lustre-devel] KVM Quick Start Guide Christopher J. Morrone
2015-06-12 23:35 ` Christopher J. Morrone
2015-06-19 16:19 ` John Suykerbuyk
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=D1A0AFE3.F7223%andreas.dilger@intel.com \
--to=andreas.dilger@intel.com \
--cc=lustre-devel@lists.lustre.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.