1 I'd strongly recommend this modification to ikiwiki. Any particular limitations that anyone can think of?
3 I might even have a try at this patch, though I'd have to hack the user preferences page to include author name...
5 As to the question of whether the committer was the 'script' or the wiki editor... I'm not sure. Marking it as the script somehow (`ikiwiki-cgi <ikiwiki@sitename>`)? seems to make sense and would make it easier to manage.
9 I've been thinking a bit about the GIT attribution in ikiwiki...
11 If no email set, I think "$USERNAME" is reasonable... no point in the
13 >> **adjustement wrt comments**: leave the '<>' in due to requirements in git
15 If no username set... then something like '@[IPADDR]' makes sense...
16 (not in email brackets).
18 In the case of OpenID login.. I think that's a special case... I don't
19 think attempting to munge something meaningful out of the OpenID makes
20 sense... but I think some massaging might need to be done.
22 Ex: I've noticed in the current mode where logging in w/
23 harningt.eharning.us/ shows up in the logs w/o HTTP and if I login w/
24 http://harningt.eharning.us/ is shows up w/ the http... causing some
25 inconsistency. I think it oughtta make sure that it has the properly
26 discovered, canonicalized form (ex: if there's a redirect to another
27 site (harningt.eharning.us -> www.eharning.us) then technically the
28 target site is the 'real' openid (at least according to how most OpenID
33 For OpenID edits, I think there should be a way to tell it what
34 username to show in the preferences dialog (so you can have a 'normal'
35 $USER <$EMAIL> setup.) This could by default be filled in w/ sreg
36 nickname value (as well as email for that matter)...
38 To convey the openid used to make the edit, I think it would be
39 important that some sort of footer line along the lines of the
40 Signed-off: $USER <$EMAIL> conventions I've seen.
42 Perhaps an OpenID: $OPENID_URL would make sense. This could help w/
43 making sure that no one irrefutably spoofs a post by someone (since w/
44 the setup where email and effective username are configurable, there's
45 no determination of uniqueness)
46 >> **adj re git req**: "$OPENID_URL <>"
50 [[madduck]]: git requires `Name <Email@address>` format, as far as I know.
54 > joey@kodama:~/tmp/foo/bar>git commit --author "foo"
55 > fatal: malformed --author parameter
57 > It seems to be happy with anything of the form "foo <foo>" -- doesn't seem to
58 > do any kind of strict checking. Even "http://joey.kitenet.net <>" will be
59 > accepted. --[[Joey]]