urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update

master
Joey Hess 2010-03-13 19:40:20 -05:00
parent 8f4f81cdfd
commit 702c097ac2
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/todo/Separate_OpenIDs_and_usernames.mdwn
View File

@ -18,15 +18,25 @@ A slightly more complex next step would be to request sreg from the provider and
> page).
>
> I am considering displaying the userid or fullname, if available,
> instead of the munged openid url in recentchanges. It would be nice
> for those nasty [[google_openids|forum/google_openid_broken?]]. But,
> I first have to find a way to encode the name in the VCS commit log,
> instead of the munged openid url in recentchanges and comments.
> It would be nice for those nasty [[google_openids|forum/google_openid_broken?]].
> But, I first have to find a way to encode the name in the VCS commit log,
> while still keeping the openid of the committer in there too.
> Perhaps something like this (for git): --[[Joey]]
>
> Author: Joey Hess <http://joey.kitenet.net/@web>
>
> So, what needs to be done:
>
> * Change `rcs_commit` and `rcs_commit_staged` to take a session object,
> instead of just a userid. (For back-compat, if the parameter is
> not an object, it's a userid.) Bump ikiwiki plugin interface version.
> * Modify all RCS plugins to include the session username somewhere
> in the commit, and parse it back out in `rcs_recentchanges`.
> * Modify recentchanges plugin to display the username instead of the
> `openiduser`.
> * Modify comment plugin to put the session username in the comment
> template instead of the `openiduser`.
Unfortunately I don't speak Perl, so hopefully someone thinks these suggestions are good enough to code up. I've hacked on openid code in Ruby before, so hopefully these changes aren't all that difficult to implement. Even if you don't get any data via sreg, you're no worse off than where you are now, so I don't think there'd need to be much in the way of error/sanity-checking of returned data. If it's null or not available then no big deal, typing in a username is no sweat.