I entered the issue: http://code.google.com/p/support/issues/detail?id=4303 You may want to star it.
Adding the page name to the default is easy. I'll just start that change right now. In terms of a way to force users to enter a better commit log message, that would need to be a per-project option for the project owner to turn on. I would make the effect of that option be: (1) always keep the commit log message text area expanded, and (2) make the commit log message be a required field that must be touched before the "Submit" button is enabled. The reason to not do a 2nd page is that it will cause "post-completion errors". http://www.system-concepts.com/articles/usability-articles/2007/post-completion-errors-and-how-to-avoid-them.html Thanks, jason! On Wed, Aug 11, 2010 at 7:28 AM, Nathan Ingersoll <[email protected]> wrote: > On Tue, Aug 10, 2010 at 1:36 PM, Darren Pearce-Lazard > <[email protected]> wrote: >>> > I will, in fact, say it: it is good practice to supply a meaningful log >>> > message even for the smallest of edits. >> >> I agree with this completely. However... >> >>> >>> Just do a search and see the number of commit messages that remain at >>> 'Editing wiki page thru web interface' and you will see the problem. >>> Its very unhelpul without going into the diff page to see what wiki >>> page was changed. The default message is a very poor choice and many >>> developers just wont change that message if the edit is minor. Human >>> nature. Give us better defaults. Or give us the code to change it to >>> a better default ;D >> >> ... I often find I miss editing the field and just click on 'save' (probably >> something to do with the fact that conceptually seeing the wiki as part of >> the VCS is still 'new' to me). I am always evangelising about providing good >> commit messages but editing them post hoc is a bit of a pain. >> So, how about when you click 'save', there is a *further* page which then >> prompts for the commit message? This would -- for me at least! -- make it a >> lot easier to remember to enter a sensible message. The second page could >> also show the diff so it could be summarised properly. > > We usually take efforts to minimize the number of steps necessary to > achieve a goal. This seems like a bit heavyweight to me. I am > personally leaning towards the more sane default of simply including > the wiki page name in the default message presented to the user. It at > least provides a better starting point when reviewing changes in the > version control system. > >> As jagernot says, users could specify their own default message. I was also >> wondering if there could be a length restriction that project owners could >> enforce, especially requiring a non-empty log message. >> What do you think, Nathan? Others? >> :Darren. > > This could be useful if we provide a template system for the messages. > It's quite likely that project owners may want to include the edited > wiki page name, project name, user name, or some other piece of > pertinent information. > > Thanks, > Nathan > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-code-hosting?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
