On Sun, 24 May 2020 at 01:00, Sam Ruby <ru...@intertwingly.net> wrote: > > On Sat, May 23, 2020 at 6:01 PM Craig Russell <apache....@gmail.com> wrote: > > > > The CoI policy adopted in March: > > > > Article VI - Annual Statements > > > > Each director, principal officer and member of a committee with > > governing board delegated powers shall annually sign a statement > > which > > affirms such person: > > > > a. Has received a copy of the conflicts of interest policy, > > > > b. Has read and understands the policy, > > > > c. Has agreed to comply with the policy, and > > > > d. Understands the ASF is charitable and in order to maintain its > > federal tax exemption it must engage primarily in activities which > > accomplish one or more of its tax-exempt purposes. > > > > For purposes of this article, a Project Management Committee (PMC) > > having only the normal powers of a PMC is not a committee with > > governing > > board delegated powers. > > > > I'd like to build on the whimsy/committer page to record the annual CoI > > affirmation. > > > > After the annual member meeting, secretary creates a file called > > foundation/officers/coi-required.yaml that resolves to a list of availids > > that are required to complete the CoI affirmation. > > > > When a member visits https://whimsy.apache.org/roster/committer/_self_ the > > tool looks in coi-required.yaml and if the availid is listed there, looks > > in foundation/officers/coi-2020/ for availid.txt. If it is not there, a red > > button outlined in green is clickable. When this is clicked, a modal dialog > > comes up that displays the CoI affirmation from > > foundation/officers/coi-affirmation.txt and two buttons: (confirm) and > > (cancel). When confirm is clicked, a file called <availid>.txt is > > constructed from cgi-affirmation.txt, replacing > > "Name: _______________" with "Name: _Craig Russell_" and > > "id: __________________" with "id: __clr_____________" and > > "Date: _________________" with "Date: _2020-06-10 14:20:48 PDT___" > > > > This file is then committed into the foundation/coi-2020/ directory. > > > > Some yet-to-be-decided tool iterates the contents of cgi-required.yaml and > > verifies that there is a corresponding file in coi-2020 for each entry. > > > > In each board meeting, the secretary includes a section > > <private> > > The following directors/officers have not yet completed the CoI affirmation > > for 2020: > > clr, rubys, boards > > </private> > > > > The file coi-affirmation.txt is a somewhat modified text representation of > > the board resolution with an affirmation and space at the bottom for name, > > id, and date. > > > > WDYT? > > Something to explore as an alternative. Much of what you describe > could be implemented by a separate tool as a CGI. There are > advantages and disadvantages to both approaches, ultimately it is up > to the person doing the coding. > > An example of a CGI that lets you fill out a form that is committed to SVN: > > https://github.com/apache/whimsy/blob/master/www/members/proxy.cgi > > An example of a CGI that updates a YAML file: > > https://github.com/apache/whimsy/blob/master/www/members/inactive.cgi > > In general, a separate CGI is easier to get up and running quickly.
It's likely easier to test. > Adding it to the roster tool provides for the possibility of increased > integration. One can always link to the CGI from the roster tool. > > Craig L Russell > > c...@apache.org > > - Sam Ruby
