<br><br><div class="gmail_quote">On Sun, May 4, 2008 at 9:36 AM, Guido van Rossum <<a href="mailto:guido@python.org">guido@python.org</a>> 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 class="Ih2E3d">On Sun, May 4, 2008 at 2:58 AM, Stefan Behnel <<a href="mailto:stefan_ml@behnel.de">stefan_ml@behnel.de</a>> wrote:<br>
> Personally, I would consider the following sufficient:<br>
><br>
> 1) people who have authenticated themselves against the underlying VCS (i.e.<br>
> project members) may post public comments and comment on other comments<br>
<br>
</div>Tell me how to authenticate against a SVN project using HTTP only.<br>
<div class="Ih2E3d"><br>
> 2) anonymous users can post comments that won't become publicly visible until<br>
> an authenticated user acknowledges them or comments on them.<br>
<br>
</div>Can you work out this design more? I don't understand how an<br>
authenticated user can acknowledge an anonymous comment if it isn't<br>
publicly visible. Also, AFAIK our bug tracker doesn't support<br>
anonymous comments either, so I don't think this is an important use<br>
case.<br>
<div class="Ih2E3d"></div></blockquote><div><br>Rather than svn authentication i suggest just piggybacking on top of the bug trackers authentication. that is an integration i think we should aim for anyways and it should keep the no-google-account fear mongers happy. code comments (as bug comments are today) should not require svn commit access.<br>
<br></div>anyways, i expect someone else may implement that once the code is out there.<br><br></div>-gps<br><br>