From: zren <zren@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2-tools.git is moving, ocfs2 web site plans
Date: Mon, 09 Feb 2015 11:39:32 +0800 [thread overview]
Message-ID: <54D82BF4.5040408@suse.com> (raw)
In-Reply-To: <20150206210203.GI21790@wotan.suse.de>
Hi Mark and all,
I am wondering whether this plan will also cover ocfs2-test project.
I noticed that ocfs2-test on oss.oracle.com has not any update since
2012-03-15.
However,there are two branches on github I found which have some
updates. They are:
1. pibroch/ocfs2-test: https://github.com/pibroch/ocfs2-test and
2. goldwynr/ocfs2-test: https://github.com/goldwynr/ocfs2-test/tree/suse.
Any information about this issue is appreciated.
Thanks,
-- zhen
On 2015?02?07? 05:02, Mark Fasheh wrote:
> Hi all,
>
> I used to have commit access to ocfs2-tools.git but legitimate
> security concerns at Oracle have no longer made that possible. Moving
> forward, I will host the official ocfs2-tools.git in my github:
>
> https://github.com/markfasheh/ocfs2-tools
>
> I started with a mirror of what's on oss.oracle.com. Both Srini and Goldwyn
> have commit access to the repo. The way we commit should not change -
> patches need to have at least one reviewed-by (as well as a sign-off). If
> anyone feels strongly that they should also have commit access, let me know.
>
> I will send a patch to update our kernel documentation regarding the
> location of ocfs2-tools.git shortly.
>
> 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.
>
> Thanks,
> --Mark
>
> --
> Mark Fasheh
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>
--
Regards,
Zhen, Ren
HA team, SUSE
next prev parent reply other threads:[~2015-02-09 3:39 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 [this message]
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
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=54D82BF4.5040408@suse.com \
--to=zren@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox