Sam Ruby wrote on 6/12/17 9:24 PM: > On Mon, Jun 12, 2017 at 9:06 PM, Sam Ruby <ru...@intertwingly.net> wrote: ...snip... >> I learned all this the hard way on the original whimsy_vm where >> directories often got 'wedged' and needed manual intervention for >> cleanup. That's why I instituted a hard separation between what can >> be updated in each process. > > Adding to my answer: this decision (which can be changed if that what > we collectively want to do) was to prefer slightly stale data over > data that (at best) might occasionally stop updating, and (at worst) > can become corrupt. > > The /srv/svn files update every 10 minutes. For most purposes, that > is fast enough.
General comments: - This is a per-tool decision. - We need to ensure each tool has clear maintenance documentation, so fixing out of date or bogus data is easy. - We need to start thinking about how to consistently document these kinds of things to our users, since the userbase is increasing for many tools (and overall number of tools total!) -- Many tools are read-only visualizations of data. Useful information is: what does this data mean, how recently was it updated, and where specifically did it come from (see also test/dataflow.cgi) -- Read/Write tools should consider explaining how quickly changes take effect, as well as any auth questions: i.e. are there any tools that have separate auth from being able to load/see the tool vs. being able to change any editable data? -- Some tools should probably explicitly note in the About This Script that they are access-protected. This will help remind members to not share links for some of the member-private data pages, for example. It's not obvious in many cases to users which specific bits of data might be member-private vs. committer-private, I think. Any other "explain to the user what this page is" aspects to cover? > > Programs like the board agenda tool, the secretary mail tool, and now > the roster take great care to update svn in separate tmp directories. > > - Sam Ruby > -- - Shane https://www.apache.org/foundation/marks/resources
