A couple of thoughts occur to me. Most of the agenda actions have been perfectly fine until now.
Maybe it's possible to change the (edit report) function so the user can see a diff of the agenda prior to committing it and asking for the user to (commit) or (cancel). That change would solve two issues: Eliminate disasters like this one where the entire incubator report was duplicated Allow the user to verify that (reflow) actually worked (this is the most popular (edit report) function for me Pending this (or similar) change, I'd be happy disallowing editing the incubator report, since that is the report that has had (any) problems. Craig > On Jan 11, 2019, at 3:47 PM, sebb <[email protected]> wrote: > > On Fri, 11 Jan 2019 at 23:21, Craig Russell <[email protected]> wrote: >> >> I believe this mess was caused by Myrle editing the incubator report in >> whimsy. The intended change was: >> >> [X](weex) Willem Ning Jiang >> Comments: >> + [X](weex) Myrle Krantz >> >> - [ ](weex) Myrle Krantz >> Comments: >> >> >> Can someone please take a look? >> > > I know very little about that code and have not actually used the tool > to change a report. > I don't know if it's possible to test locally without committing. > > But I think we need to know what actions were taken apart from editing > the report. > E.g. was it reflowed? > > S. Craig L Russell Secretary, Apache Software Foundation [email protected] <mailto:[email protected]> http://db.apache.org/jdo <http://db.apache.org/jdo>
