<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi David, <br>
<br>
Hmmm. So, you mean, that at OIDF, the editors are fully delegated the
responsibility to maintain the IPR integrity unlike OASIS etc. ? Since
I was having OASIS as a model where TC admins (== OASIS staffs) and the
infrastructure controls the access, and these processes are documented
in the IPR process, I had an impression that that should be the way,
but if OIDF takes this "Editor Controlled" model, I am fine with it.
Perhaps <br>
<br>
4.13 Intellectual Property. The WG will at all times comply with the
IPR Policy.<br>
<br>
of the OpenID Process Document actually tacitly speaking of this
"Editor Control" Model? <br>
<br>
=nat<br>
<br>
(2009/12/28 15:43), David Recordon wrote:
<blockquote
cite="mid:fd6741650912272243x5aa00244q995d702446c561d3@mail.gmail.com"
type="cite">Hey Nat,
<div>The IPR process determines the process around contributions to a
working group's mailing list. It is up to the editor(s) to be
responsible in terms of requesting access to the specification's
repository. The Board should be overseeing that a good IPR policy is
in place and to provide infrastructure to working groups if it is
missing.</div>
<div><br>
</div>
<div>The Board should have less control over these sorts of minute
details, not more. There are far more important things for the Board
to spend time on compared to whether a given working group uses
Subversion, Git, or Mercurial. If a working group's editor(s) can't
make that decision then they shouldn't be editors. :)</div>
<div><br>
</div>
<div>--David<br>
<br>
<div class="gmail_quote">On Sun, Dec 27, 2009 at 10:40 PM, Nat
Sakimura <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">Well, the users are specs@
but the board has an oversight
responsibility to avoid IPR contamination. <br>
Thus, where the repositories are, and how they are managed are of
interest and responsibility of the board. <br>
<br>
As to the location of the WG repositories are concerned, if we are
allowed to use ones that the WG likes, we probably need to establish a
mechanism to <br>
<br>
1) Board approval on the location and the management method of the
repository. <br>
2) Advertise it to the internet (A link from WG main page should be
good enough.) <br>
<br>
It should not be complicated, but the mechanism should be well defined
and documented. <br>
<br>
=nat
<div>
<div class="h5"><br>
<br>
(2009/12/28 15:04), David Recordon wrote:
<blockquote type="cite">Agreed with Will. (And this is an issue
for specs@, not
board@.)
<div><br>
<div class="gmail_quote">On Sun, Dec 27, 2009 at 8:41 PM, Will
Norris <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:will@willnorris.com" target="_blank">will@willnorris.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'm
not
sure that it needs to be either/or. We have the 'openid' account
secured on github, bitbucket, and google code. Let individual working
groups use whichever version control system they are most comfortable
with. Of course the final deliverables that come out of any working
group should be in common location (such as <a moz-do-not-send="true"
href="http://openid.net/developers/specs/" target="_blank">http://openid.net/developers/specs/</a>),
but
that doesn't necessarily mean that they all need to use the same
technology to develop them.<br>
<br>
-will<br>
<div>
<div><br>
On Dec 26, 2009, at 6:57 PM, Nat Sakimura wrote:<br>
<br>
> David and Allen,<br>
><br>
> I suppose we should ask the wider community, so I am including
board@<br>
> in the distribution list.<br>
><br>
> For those of you who are new to this topic, we have been<br>
> "experimenting/trying a move to" github from svn. However, after<br>
> having used it for sometime, I have started to find some problems
with<br>
> github and it now looks to me that <a moz-do-not-send="true"
href="http://bitbucket.org" target="_blank">bitbucket.org</a> is a
better option<br>
> than github.<br>
><br>
> The reasons are:<br>
><br>
> 1. It uses OpenID for web interface login.<br>
> 2. It allows the use of https logins through proxies so it can be<br>
> accessed through corporate firewalls etc. as well. (It is extremely<br>
> difficult to do this for github -- it can be done, but it probably
is<br>
> beyond many people because you need to build a tunnel through the<br>
> proxy.)<br>
> 3. It allows CNAMEs when paid US$5 a month, so that it could be<br>
> accessed as <a moz-do-not-send="true" href="http://openid.net"
target="_blank">openid.net</a>., e.g., <a moz-do-not-send="true"
href="http://specs.openid.net/ax/" target="_blank">http://specs.openid.net/ax/</a>
-><br>
> <a moz-do-not-send="true" href="http://bitbucket.org/openid/ax/"
target="_blank">http://bitbucket.org/openid/ax/</a> This is kind of
vanity thing, but is<br>
> important to establish the "authenticity" of the repository to the<br>
> public.<br>
><br>
> For our use, I have secured account "openid" at bitbucket.<br>
><br>
> What would you think?<br>
><br>
> =nat<br>
><br>
> On Sat, Dec 26, 2009 at 5:56 PM, Nat <<a moz-do-not-send="true"
href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>>
wrote:<br>
>> One problem that I found about github is that it is very
difficult to<br>
>> configure it to work with corporate proxies. We started to use
github for<br>
>> translation project as well, but several members got stack
there. Do you<br>
>> know of a work around?<br>
>><br>
>> =nat@Tokyo via iPhone<br>
<br>
</div>
</div>
_______________________________________________<br>
board mailing list<br>
<a moz-do-not-send="true" href="mailto:board@lists.openid.net"
target="_blank">board@lists.openid.net</a><br>
<a moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-board"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
</blockquote>
</div>
<br>
</div>
<pre><fieldset></fieldset>
_______________________________________________
board mailing list
<a moz-do-not-send="true" href="mailto:board@lists.openid.net"
target="_blank">board@lists.openid.net</a>
<a moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-board"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a>
</pre>
</blockquote>
<br>
<br>
</div>
</div>
<font color="#888888">
<pre cols="72">--
Nat Sakimura (<a moz-do-not-send="true"
href="mailto:n-sakimura@nri.co.jp" target="_blank">n-sakimura@nri.co.jp</a>)
Nomura Research Institute, Ltd.
Tel:+81-3-6274-1412 Fax:+81-3-6274-1547</pre>
</font></div>
<br>
_______________________________________________<br>
board mailing list<br>
<a moz-do-not-send="true" href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
<a moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-board"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:board@lists.openid.net">board@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-board">http://lists.openid.net/mailman/listinfo/openid-board</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Nat Sakimura (<a class="moz-txt-link-abbreviated" href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>)
Nomura Research Institute, Ltd.
Tel:+81-3-6274-1412 Fax:+81-3-6274-1547</pre>
</body>
</html>