On 2020/06/27 23:52:20, Craig Russell <apache....@gmail.com> wrote: > > On Jun 27, 2020, at 3:11 PM, Greg Stein <gst...@apache.org> wrote: > > > > On 2020/06/27 00:15:39, Craig Russell <apache....@gmail.com> wrote: >... > >> ... > >> The term "annually" can be read in a few ways, which can be reflected in different wordings on the web > > > > Just read "current year" and "prior year", and weave them together. > > Nope. In June 2021 after we have a new team in place, currentyearprioryear would show everyone has signed. Not good enough.
Hmm? In June 2021, you'd see that John Doe hasn't signed in, in the past 12 months. By "weave", I meant a hash/dict of name->date. You'd know that John Doe signed in January 2020, so he'd need to sign again on-or-about January 2021. And when you go look at June 2021, and find "jdoe->jan2020", you'd find he was 5 months out of compliance. > But assuming that we make a trivial change to the tool to iterate the years directories, we can have the sidebar give quick access to all COI documents ever signed, or just the last three or whatever we like. Later. Sure! > > You'll be able to synthesize "annual" in any fashion you like. Whether that is calendar, Board election cycle, or fiscal year. "svn info" gives you the last modification date, which is presumably the signing date. > > I still prefer to keep it simple. Organize all documents signed in a calendar year in a directory named after that calendar year. Everything else, including the following, is icing. I'm suggesting: keep your current organization. It works totally fine. The *tool* weaves current+prior together for its processing and display. >... > > Note that comparing the file means stripping the metadata from the end. I would suggest to make the file the policy-at-time, and use svn properties for the metadata (that is why they are there). >... > Let's get past this year's exercise and wait until something more complicated becomes necessary and agreed. Mixing metadata into your primary content may make things harder down the line. But, meh. It's data processing. I will echo sebb's discussion point about 2020/template.txt. What if it gets changed in October 2020, for some reason? If the answer is "well, we can see that in the svn revision log". And if *that* is the answer, then move it outside the per-year directory and use a single revision log for understanding which COI policy was extent on $date. Cheers, -g
