[jira] [Updated] (WHIMSY-414) Roll call tool to simplify PMC roll calls
[ https://issues.apache.org/jira/browse/WHIMSY-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig L Russell updated WHIMSY-414: --- Description: During review of project board reports, directors encounter projects that seem to be in decline. In order to determine whether the PMC is healthy enough for proper oversight, the board requests a roll call and assigns an action item to a director. To start the roll call, a director goes to the Whimsy roster page for the PMC, and clicks "send roll call". Director writes out an explanation of any specific board concerns, which is then sent out along with a boilerplate explanation of the roll call process, along with a "reply by this date to roll call here" link. PMC members click the link (which auth's them), fill out short form, and click submit. The board really needs to know the "how engaged are you" detail, and we could also have an extra comments field where PMC members might add extra data. Every submission results in a commit (by Whimsy) into a private repository (visible to Members and Officers) as well as an email to board@ and private@. The repository should be easy to search by name by logged-in users, e.g. [https://svn.apache.org/repos/private/pmc//|https://svn.apache.org/repos/private/pmc/]roll-call/2024-04-01/.json. The above directory will be created at the time the roll call request is being executed. The private/pmc// directory might need to be created by Whimsy if no roll call or other reason has been seen for this PMC. PMC members should be allowed to save their responses in a specific roll call request directory PMC members should be allowed to review/read responses from their peers in any of their svn project roll call directories Members and Officers should be allowed to review/read responses from any of the repositories Other access should be disallowed It's easy to track responses by Apache ID, and by date of response, as well as have a simple read-only dashboard showing the outcome of each roll call, assuming the right privileges. PMC members could also see each others' responses in email. Working example (you will be auth'd by your Apache ID): [https://whimsy.apache.org/officers/surveys?survey=test-rollcall.json] In this POC, commits go to foundation/officers/surveys. was: During review of project board reports, directors encounter projects that seem to be in decline. In order to determine whether the PMC is healthy enough for proper oversight, the board requests a roll call and assigns an action item to a director. To start the roll call, a director goes to the Whimsy roster page for the PMC, and clicks "send roll call". Director writes out an explanation of any specific board concerns, which is then sent out along with a boilerplate explanation of the roll call process, along with a "reply by this date to roll call here" link. PMC members click the link (which auth's them), fill out short form, and click submit. The board really needs to know the "how engaged are you" detail, and we could also have an extra comments field where PMC members might add extra data. Every submission results in a commit (by Whimsy) into a private repository (visible to Members and Officers) as well as an email to board@ and private@. The repository should be easy to search by name by logged-in users, e.g. [https://svn.apache.org/repos/private/pmc//|https://svn.apache.org/repos/private/pmc/]roll-call/2024-04-01/.json. PMC members should be allowed to save their responses in a specific roll call request directory PMC members should be allowed to review/read responses from their peers in any of their svn project roll call directories Members and Officers should be allowed to review/read responses from any of the repositories Other access should be disallowed It's easy to track responses by Apache ID, and by date of response, as well as have a simple read-only dashboard showing the outcome of each roll call, assuming the right privileges. PMC members could also see each others' responses in email. Working example (you will be auth'd by your Apache ID): [https://whimsy.apache.org/officers/surveys?survey=test-rollcall.json] In this POC, commits go to foundation/officers/surveys. > Roll call tool to simplify PMC roll calls > - > > Key: WHIMSY-414 > URL: https://issues.apache.org/jira/browse/WHIMSY-414 > Project: Whimsy > Issue Type: New Feature > Components: Roster >Reporter: Craig L Russell >Priority: Major > > During review of project board reports, directors encounter projects that > seem to be in decline. In order to determine whether the PMC is healthy > enough for proper oversight, the board requests a roll call and assigns an > action item to a director. > To start the roll call, a
[jira] [Commented] (WHIMSY-414) Roll call tool to simplify PMC roll calls
[ https://issues.apache.org/jira/browse/WHIMSY-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839427#comment-17839427 ] Sebb commented on WHIMSY-414: - Note: not all PMCs currently have private /pmc/ entries, but it does not take long to set them up. AFAICT the directory can be created by any ASF member. The permission database (pit-authorization-template) would need an Infra OK. > Roll call tool to simplify PMC roll calls > - > > Key: WHIMSY-414 > URL: https://issues.apache.org/jira/browse/WHIMSY-414 > Project: Whimsy > Issue Type: New Feature > Components: Roster >Reporter: Craig L Russell >Priority: Major > > During review of project board reports, directors encounter projects that > seem to be in decline. In order to determine whether the PMC is healthy > enough for proper oversight, the board requests a roll call and assigns an > action item to a director. > To start the roll call, a director goes to the Whimsy roster page for the > PMC, and clicks "send roll call". Director writes out an explanation of any > specific board concerns, which is then sent out along with a boilerplate > explanation of the roll call process, along with a "reply by this date to > roll call here" link. > PMC members click the link (which auth's them), fill out short form, and > click submit. The board really needs to know the "how engaged are you" > detail, and we could also have an extra comments field where PMC members > might add extra data. > Every submission results in a commit (by Whimsy) into a private repository > (visible to Members and Officers) as well as an email to board@ and > private@. The repository should be easy to search by name by > logged-in users, e.g. > [https://svn.apache.org/repos/private/pmc//|https://svn.apache.org/repos/private/pmc/]roll-call/2024-04-01/.json. > > > PMC members should be allowed to save their responses in a specific roll call > request directory > PMC members should be allowed to review/read responses from their peers in > any of their svn project roll call directories > Members and Officers should be allowed to review/read responses from any of > the repositories > Other access should be disallowed > It's easy to track responses by Apache ID, and by date of response, as well > as have a simple read-only dashboard showing the outcome of each roll call, > assuming the right privileges. > PMC members could also see each others' responses in email. > Working example (you will be auth'd by your Apache ID): > [https://whimsy.apache.org/officers/surveys?survey=test-rollcall.json] > In this POC, commits go to foundation/officers/surveys. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (WHIMSY-414) Roll call tool to simplify PMC roll calls
[ https://issues.apache.org/jira/browse/WHIMSY-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig L Russell updated WHIMSY-414: --- Description: During review of project board reports, directors encounter projects that seem to be in decline. In order to determine whether the PMC is healthy enough for proper oversight, the board requests a roll call and assigns an action item to a director. To start the roll call, a director goes to the Whimsy roster page for the PMC, and clicks "send roll call". Director writes out an explanation of any specific board concerns, which is then sent out along with a boilerplate explanation of the roll call process, along with a "reply by this date to roll call here" link. PMC members click the link (which auth's them), fill out short form, and click submit. The board really needs to know the "how engaged are you" detail, and we could also have an extra comments field where PMC members might add extra data. Every submission results in a commit (by Whimsy) into a private repository (visible to Members and Officers) as well as an email to board@ and private@. The repository should be easy to search by name by logged-in users, e.g. [https://svn.apache.org/repos/private/pmc//|https://svn.apache.org/repos/private/pmc/]roll-call/2024-04-01/.json. PMC members should be allowed to save their responses in a specific roll call request directory PMC members should be allowed to review/read responses from their peers in any of their svn project roll call directories Members and Officers should be allowed to review/read responses from any of the repositories Other access should be disallowed It's easy to track responses by Apache ID, and by date of response, as well as have a simple read-only dashboard showing the outcome of each roll call, assuming the right privileges. PMC members could also see each others' responses in email. Working example (you will be auth'd by your Apache ID): [https://whimsy.apache.org/officers/surveys?survey=test-rollcall.json] In this POC, commits go to foundation/officers/surveys. was: During review of project board reports, directors encounter projects that seem to be in decline. In order to determine whether the PMC is healthy enough for proper oversight, the board requests a roll call and assigns an action item to a director. To start the roll call, a director goes to the Whimsy roster page for the PMC, and clicks "send roll call". Director writes out an explanation of any specific board concerns, which is then sent out along with a boilerplate explanation of the roll call process, along with a "reply by this date to roll call here" link. PMC members click the link (which auth's them), fill out short form, and click submit. The board really needs to know the "how engaged are you" detail, and we could also have an extra comments field where PMC members might add extra data. Every submission results in a commit (by Whimsy) into a private repository (visible to Members and Officers) as well as an email to board@ and private@. The repository should be easy to search by name, e.g. foundation/officers/roll-calls//roll-call-2024-04-01/.json. PMC members should be allowed to save their responses in a specific roll call request directory PMC members should be allowed to review/read responses from their peers in any of their svn project roll call directories Members and Officers should be allowed to review/read responses from any of the repositories Other access should be disallowed It's easy to track responses by Apache ID, and by date of response, as well as have a simple read-only dashboard showing the outcome of each roll call, assuming the right privileges. PMC members could also see each others responses in email. Working example (you will be auth'd by your Apache ID): [https://whimsy.apache.org/officers/surveys?survey=test-rollcall.json] In this POC, commits go to foundation/officers/surveys. > Roll call tool to simplify PMC roll calls > - > > Key: WHIMSY-414 > URL: https://issues.apache.org/jira/browse/WHIMSY-414 > Project: Whimsy > Issue Type: New Feature > Components: Roster >Reporter: Craig L Russell >Priority: Major > > During review of project board reports, directors encounter projects that > seem to be in decline. In order to determine whether the PMC is healthy > enough for proper oversight, the board requests a roll call and assigns an > action item to a director. > To start the roll call, a director goes to the Whimsy roster page for the > PMC, and clicks "send roll call". Director writes out an explanation of any > specific board concerns, which is then sent out along with a boilerplate > explanation of the roll call process, along with a "reply by this date to > roll call
Re: [I] Problems running setupmymac --docker [whimsy]
sebbASF commented on issue #225: URL: https://github.com/apache/whimsy/issues/225#issuecomment-2068204564 I've not tried using setupmymac with Docker; I just followed the "Installation instructions" in Docker.md -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Problems running setupmymac --docker [whimsy]
chrisdutz opened a new issue, #225: URL: https://github.com/apache/whimsy/issues/225 So when running setupmymac for docker, this also seems to fail: ``` Traceback (most recent call last): 2: from /usr/bin/bundle2.7:23:in `' 1: from /usr/lib/ruby/2.7.0/rubygems.rb:294:in `activate_bin_path' /usr/lib/ruby/2.7.0/rubygems.rb:275:in `find_spec_for_exe': Could not find 'bundler' (1.17.2) required by your /srv/whimsy/tools/Gemfile.lock. (Gem::GemNotFoundException) To update to the latest version installed on your system, run `bundle update --bundler`. To install the missing version, run `gem install bundler:1.17.2` rake aborted! system!() failed! /srv/whimsy/rakefile:14:in `system!' /srv/whimsy/rakefile:96:in `block (3 levels) in ' /srv/whimsy/rakefile:84:in `chdir' /srv/whimsy/rakefile:84:in `block (2 levels) in ' /srv/whimsy/rakefile:83:in `each' /srv/whimsy/rakefile:83:in `block in ' /var/lib/gems/2.7.0/gems/rake-13.2.1/exe/rake:27:in `' Tasks: TOP => update (See full trace by running task with --trace) rake aborted! Command failed with status (1): [docker compose run --entrypoint 'bash -c "rake update"' web] /private/var/whimsy/whimsy/Rakefile:464:in `block (2 levels) in ' /Library/Ruby/Gems/2.6.0/gems/rake-13.2.1/exe/rake:27:in `' Tasks: TOP => docker:update (See full trace by running task with --trace) ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix/fix setupmymac [whimsy]
sebbASF commented on PR #224: URL: https://github.com/apache/whimsy/pull/224#issuecomment-2068014885 -1 Not necessary. Note that 'or' is low priority, and evaluation stops if the first clause is true, so the second clause will only be actioned if the file exists. Try it and see locally -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix/fix setupmymac [whimsy]
sebbASF closed pull request #224: Fix/fix setupmymac URL: https://github.com/apache/whimsy/pull/224 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Fix/fix setupmymac [whimsy]
chrisdutz opened a new pull request, #224: URL: https://github.com/apache/whimsy/pull/224 The If condition still would have caused an error if the file did not exist. fixes: #223 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Problems running setupmymac on my mac [whimsy]
chrisdutz commented on issue #223: URL: https://github.com/apache/whimsy/issues/223#issuecomment-2068009586 digging a bit deeper it seems to be related to my M2 mac ... from what I see it tries to instal the x86 version of nokogiri, but my system is: ``` cdutz@MacBook-Pro-von-Christofer config % bundle platform Your platform is: universal.arm64e-darwin23 Your app has gems that work on these platforms: * ruby Your Gemfile does not specify a Ruby version requirement. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Problems running setupmymac on my mac [whimsy]
sebbASF commented on issue #223: URL: https://github.com/apache/whimsy/issues/223#issuecomment-2068009577 Oops, you're correct; setupmymac now fixed. Note that you may find it easier to use Docker for testing, though if you have an Apple CPU (M1 etc) puppeteer does not work. Otherwise I find it works well, and anyway puppeteer is only needed for website checks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Problems running setupmymac on my mac [whimsy]
chrisdutz commented on issue #223: URL: https://github.com/apache/whimsy/issues/223#issuecomment-2068008486 This makes it possible to continue for quite a while, till the build then fails with: ``` $ rake git:pull mkdir -p /srv/git /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:130:in `require': cannot load such file -- nokogiri/nokogiri (LoadError) from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:130:in `rescue in require' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:34:in `require' from /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/extension.rb:30:in `rescue in ' from /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/extension.rb:4:in `' from /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri.rb:10:in `require_relative' from /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri.rb:10:in `' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:130:in `require' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:130:in `rescue in require' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:34:in `require' from /private/var/whimsy/whimsy/lib/whimsy/asf/podling.rb:1:in `' from /private/var/whimsy/whimsy/lib/whimsy/asf.rb:14:in `require_relative' from /private/var/whimsy/whimsy/lib/whimsy/asf.rb:14:in `' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /Users/cdutz/Projects/Apache/Whimsy/whimsy/config/setupmymac:434:in `' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- nokogiri/nokogiri (LoadError) from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/extension.rb:30:in `rescue in ' from /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/extension.rb:4:in `' from /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri.rb:10:in `require_relative' from /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri.rb:10:in `' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:130:in `require' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:130:in `rescue in require' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:34:in `require' from /private/var/whimsy/whimsy/lib/whimsy/asf/podling.rb:1:in `' from /private/var/whimsy/whimsy/lib/whimsy/asf.rb:14:in `require_relative' from /private/var/whimsy/whimsy/lib/whimsy/asf.rb:14:in `' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require' from /Users/cdutz/Projects/Apache/Whimsy/whimsy/config/setupmymac:434:in `' /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/extension.rb:7:in `require_relative': dlopen(/Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/2.6/nokogiri.bundle, 0x0009): tried: '/Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/2.6/nokogiri.bundle' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/2.6/nokogiri.bundle' (no such file), '/Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/2.6/nokogiri.bundle' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')) - /Library/Ruby/Gems/2.6.0/gems/nokogiri-1.13.10-x86_64-darwin/lib/nokogiri/2.6/nokogiri.bundle (LoadError) from
Re: [I] Problems running setupmymac on my mac [whimsy]
chrisdutz commented on issue #223: URL: https://github.com/apache/whimsy/issues/223#issuecomment-2068007056 I'll submit a pr and also I manaually needed to run: `brew install libyaml` Or I'd get the following error when installing psych. https://stackoverflow.com/questions/74715148/error-error-installing-psych-error-failed-to-build-gem-native-extension -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Problems running setupmymac on my mac [whimsy]
chrisdutz opened a new issue, #223: URL: https://github.com/apache/whimsy/issues/223 So I just ran setupmymac on my mac and I got errors. ``` $ sudo ln -s /var/log/apache2 /srv/whimsy/www/members/log /Users/cdutz/Projects/Apache/Whimsy/whimsy/config/setupmymac:374:in `read': No such file or directory @ rb_sysopen - /etc/apache2/other/passenger.conf (Errno::ENOENT) from /Users/cdutz/Projects/Apache/Whimsy/whimsy/config/setupmymac:374:in `' ``` When debugging the script it seems that in my case `passenger_conf` doesn't exist at `/etc/apache2/other/passenger.conf` and therefore the script goes into the second part of the expression in: `unless File.exist?(passenger_conf) or File.read(passenger_conf) != snippet` Which then fails ... could it be that this should be an `and` instead of an `or`? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (WHIMSY-414) Roll call tool to simplify PMC roll calls
[ https://issues.apache.org/jira/browse/WHIMSY-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839364#comment-17839364 ] Sebb commented on WHIMSY-414: - The private PMC directory entries at https://svn.apache.org/repos/private/pmc/ have suitable authentication requirements: RW for PMC members and ASF members, no access otherwise. These would be suitable for the survey response data and questionnaires. > Roll call tool to simplify PMC roll calls > - > > Key: WHIMSY-414 > URL: https://issues.apache.org/jira/browse/WHIMSY-414 > Project: Whimsy > Issue Type: New Feature > Components: Roster >Reporter: Craig L Russell >Priority: Major > > During review of project board reports, directors encounter projects that > seem to be in decline. In order to determine whether the PMC is healthy > enough for proper oversight, the board requests a roll call and assigns an > action item to a director. > To start the roll call, a director goes to the Whimsy roster page for the > PMC, and clicks "send roll call". Director writes out an explanation of any > specific board concerns, which is then sent out along with a boilerplate > explanation of the roll call process, along with a "reply by this date to > roll call here" link. > PMC members click the link (which auth's them), fill out short form, and > click submit. The board really needs to know the "how engaged are you" > detail, and we could also have an extra comments field where PMC members > might add extra data. > Every submission results in a commit (by Whimsy) into a private repository > (visible to Members and Officers) as well as an email to board@ and > private@. The repository should be easy to search by name, e.g. > foundation/officers/roll-calls//roll-call-2024-04-01/.json. > > > PMC members should be allowed to save their responses in a specific roll call > request directory > PMC members should be allowed to review/read responses from their peers in > any of their svn project roll call directories > Members and Officers should be allowed to review/read responses from any of > the repositories > Other access should be disallowed > It's easy to track responses by Apache ID, and by date of response, as well > as have a simple read-only dashboard showing the outcome of each roll call, > assuming the right privileges. > PMC members could also see each others responses in email. > Working example (you will be auth'd by your Apache ID): > [https://whimsy.apache.org/officers/surveys?survey=test-rollcall.json] > In this POC, commits go to foundation/officers/surveys. -- This message was sent by Atlassian Jira (v8.20.10#820010)
