All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Update: Re: ocfs2-tools.git is moving, ocfs2 web site plans
Date: Thu, 19 Feb 2015 07:16:28 -0600	[thread overview]
Message-ID: <54E5E22C.5020005@suse.de> (raw)
In-Reply-To: <20150213225659.GR21790@wotan.suse.de>

Hi Mark,

On 02/13/2015 04:56 PM, Mark Fasheh wrote:
> On Fri, Feb 06, 2015 at 01:02:03PM -0800, Mark Fasheh wrote:
>> The other issue I wanted to discuss was the 'official' ocfs2 web
>> page. By 'official', I mean the page we refer users to in our kernel
>> documentation. Right now it's http://oss.oracle.com/projects/ocfs2
>> which is somewhat Oracle specific, but more importantly has the same
>> restrictions as the git tree (I or other interested parties can no
>> longer edit it).
>>
>> I'm looking into securing ourselves a new 'official' page, which can give a
>> description of Ocfs2 and also link to any Oracle or SUSE pages, so their
>> users know where to go. Again I don't envision anything at SUSE or Oracle
>> has to change here, just that if someone opens up linux-2.6.git/fs/ocfs2.txt
>> it points them somewhere common to all Ocfs2 development (and we can branch
>> out from there). Also, in the future it would be nice if we put design docs
>> on an official site.
>>
>> Right now I'm hoping I can get ocfs2.wiki.kernel.org going, otherwise I
>> could always put it in another github project (or the ocfs2-tools project).
>> If anyone has suggestions, please let me know. Also if anyone could help
>> with any web/wiki for the project, also let me know. Both wiki.kernel.org
>> and github wikis allow multiple collaborators.
>
> The fine folks at kernel.org have given us a wiki:
>
> https://ocfs2.wiki.kernel.org/
>
> It is very bare right now, but I made sure to link to as much important
> information as possible (including the oss.oracle.com page). From what I
> understand, you should be able to edit it with your Linux Foundation ID. If
> you don't have one, it's very simple to create:
>
> https://identity.linuxfoundation.org/
>
> If anyone is willing to help with this, I would appreciate it, otherwise
> I'll fill things in at my own pace. In particular, I'd like to import our
> old design docs from:
>
> https://oss.oracle.com/osswiki/OCFS2.html
>
> In general, I feel these would also be good to have on the wiki:
>
> - some examples where Ocfs2 is used and why it's good there (web servers, virtual machines, databases)
>
> - more information on our feature set (in particular, reflink)
>
>
> I should be sending a patch to update our kernel docs with the new git /
> homepage links shortly.
>

Thanks a lot for doing this. Hopefully, now incorporating patches in the 
git would be faster and efficient.

In the meantime, I will work on improving the wiki pages.

Regards,

-- 
Goldwyn

  reply	other threads:[~2015-02-19 13:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 21:02 [Ocfs2-devel] ocfs2-tools.git is moving, ocfs2 web site plans Mark Fasheh
2015-02-09  3:39 ` zren
2015-02-12 23:26   ` Mark Fasheh
2015-02-13  2:13     ` Gang He
2015-02-13 22:46       ` Mark Fasheh
2015-02-13 22:56 ` [Ocfs2-devel] Update: " Mark Fasheh
2015-02-19 13:16   ` Goldwyn Rodrigues [this message]
2015-02-20 18:58     ` Mark Fasheh

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=54E5E22C.5020005@suse.de \
    --to=rgoldwyn@suse.de \
    --cc=ocfs2-devel@oss.oracle.com \
    /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.