[jira] [Commented] (WHIMSY-417) Board Agenda commit gives Argument Error

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865768#comment-17865768
 ] 

Sebb commented on WHIMSY-417:
-

I found a few more places where the match only expected a single digit.

Ideally all the matching should be centralised (or at least the REs), but not 
sure it's worth the effort.

> Board Agenda commit gives Argument Error
> 
>
> Key: WHIMSY-417
> URL: https://issues.apache.org/jira/browse/WHIMSY-417
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: Shane Curcuru
>Priority: Major
>
> * Open /board/agenda
>  * Preapprove some reports
>  * Click on navbar red box with number of cached changes
>  * Click Commit
> *Bug:* Dialog from whimsy.apache.org with error:
> Exception
> #
> Happens with a fresh browser.  Mac/Firefox.
> 
>   *  
> {panel}
> {panel}
>  
>  {panel}
> {panel}
> {panel}
> {panel}
> |||
> |transcript|[ "$ svn checkout --non-interactive --depth empty -- 
> https://svn.apache.org/repos/private/foundation/board 
> /tmp/d20240713-3214727-1lhcgf8", " U /tmp/d20240713-3214727-1lhcgf8", 
> "Checked out revision 117940.", "", "$ svn update --non-interactive -- 
> /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt", "Updating 
> '/tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt':", "A 
> /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt", "Updated to 
> revision 117940." ]|
> |0|"$ svn checkout --non-interactive --depth empty -- 
> https://svn.apache.org/repos/private/foundation/board 
> /tmp/d20240713-3214727-1lhcgf8"|
> |1|" U /tmp/d20240713-3214727-1lhcgf8"|
> |2|"Checked out revision 117940."|
> |3|""|
> |4|"$ svn update --non-interactive -- 
> /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt"|
> |5|"Updating '/tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt':"|
> |6|"A /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt"|
> |7|"Updated to revision 117940."|
> |exception|"# 2..3)>"|
> |backtrace|[ 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:169:in 
> `initialize'", 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:169:in `new'", 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:169:in `block 
> in _evaluate'", "/x1/srv/whimsy/www/board/agenda/models/agenda.rb:173:in 
> `block in update'", "/x1/srv/whimsy/www/board/agenda/models/agenda.rb:155:in 
> `open'", "/x1/srv/whimsy/www/board/agenda/models/agenda.rb:155:in `update'", 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:18:in 
> `_evaluate'", "/x1/srv/whimsy/www/board/agenda/routes.rb:359:in `block in 
> '", "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:225:in `call'", 
> "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:202:in `call'", … ]|
> {panel}
> {panel}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Secretary workbench is failing for me

[sebb]

See WHIMSY-417

On Sun, 14 Jul 2024 at 02:47, Craig Russell  wrote:
>
> This happens on both Safari and Chrome. I've never seen it before.
>
> > On Jul 13, 2024, at 17:35, Craig Russell  wrote:
> >
> > I have seven report approvals and when I try to commit:
> >
> > Exception
> > #
> >
> > This happens every time...
> >
> > Craig
> >
> > Craig L Russell
> > c...@apache.org
> >
>
> Craig L Russell
> c...@apache.org
>

[jira] [Commented] (WHIMSY-417) Board Agenda commit gives Argument Error

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865764#comment-17865764
 ] 

Sebb commented on WHIMSY-417:
-

Suddenly realised: there is an extra attachment this month, which means there 
are now two digits in the second number. The matching did not allow for this, 
now hopefully fixed.

Please try again.

> Board Agenda commit gives Argument Error
> 
>
> Key: WHIMSY-417
> URL: https://issues.apache.org/jira/browse/WHIMSY-417
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: Shane Curcuru
>Priority: Major
>
> * Open /board/agenda
>  * Preapprove some reports
>  * Click on navbar red box with number of cached changes
>  * Click Commit
> *Bug:* Dialog from whimsy.apache.org with error:
> Exception
> #
> Happens with a fresh browser.  Mac/Firefox.
> 
>   *  
> {panel}
> {panel}
>  
>  {panel}
> {panel}
> {panel}
> {panel}
> |||
> |transcript|[ "$ svn checkout --non-interactive --depth empty -- 
> https://svn.apache.org/repos/private/foundation/board 
> /tmp/d20240713-3214727-1lhcgf8", " U /tmp/d20240713-3214727-1lhcgf8", 
> "Checked out revision 117940.", "", "$ svn update --non-interactive -- 
> /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt", "Updating 
> '/tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt':", "A 
> /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt", "Updated to 
> revision 117940." ]|
> |0|"$ svn checkout --non-interactive --depth empty -- 
> https://svn.apache.org/repos/private/foundation/board 
> /tmp/d20240713-3214727-1lhcgf8"|
> |1|" U /tmp/d20240713-3214727-1lhcgf8"|
> |2|"Checked out revision 117940."|
> |3|""|
> |4|"$ svn update --non-interactive -- 
> /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt"|
> |5|"Updating '/tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt':"|
> |6|"A /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt"|
> |7|"Updated to revision 117940."|
> |exception|"# 2..3)>"|
> |backtrace|[ 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:169:in 
> `initialize'", 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:169:in `new'", 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:169:in `block 
> in _evaluate'", "/x1/srv/whimsy/www/board/agenda/models/agenda.rb:173:in 
> `block in update'", "/x1/srv/whimsy/www/board/agenda/models/agenda.rb:155:in 
> `open'", "/x1/srv/whimsy/www/board/agenda/models/agenda.rb:155:in `update'", 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:18:in 
> `_evaluate'", "/x1/srv/whimsy/www/board/agenda/routes.rb:359:in `block in 
> '", "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:225:in `call'", 
> "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:202:in `call'", … ]|
> {panel}
> {panel}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-417) Board Agenda commit gives Argument Error

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865757#comment-17865757
 ] 

Sebb commented on WHIMSY-417:
-

Thanks for the detailed report.

The first line of the backtrace shows that the app failed here:

[https://github.com/apache/whimsy/blob/5cc4a796b94a916998d07c4bf1c8a0f57b027c34/www/board/agenda/views/actions/commit.json.rb#L169]

The code seems to be failing to match the expected text, however the agenda 
does appear to contain the text. Not sure yet what is happening.

> Board Agenda commit gives Argument Error
> 
>
> Key: WHIMSY-417
> URL: https://issues.apache.org/jira/browse/WHIMSY-417
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: Shane Curcuru
>Priority: Major
>
> * Open /board/agenda
>  * Preapprove some reports
>  * Click on navbar red box with number of cached changes
>  * Click Commit
> *Bug:* Dialog from whimsy.apache.org with error:
> Exception
> #
> Happens with a fresh browser.  Mac/Firefox.
> 
>   *  
> {panel}
> {panel}
>  
>  {panel}
> {panel}
> {panel}
> {panel}
> |||
> |transcript|[ "$ svn checkout --non-interactive --depth empty -- 
> https://svn.apache.org/repos/private/foundation/board 
> /tmp/d20240713-3214727-1lhcgf8", " U /tmp/d20240713-3214727-1lhcgf8", 
> "Checked out revision 117940.", "", "$ svn update --non-interactive -- 
> /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt", "Updating 
> '/tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt':", "A 
> /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt", "Updated to 
> revision 117940." ]|
> |0|"$ svn checkout --non-interactive --depth empty -- 
> https://svn.apache.org/repos/private/foundation/board 
> /tmp/d20240713-3214727-1lhcgf8"|
> |1|" U /tmp/d20240713-3214727-1lhcgf8"|
> |2|"Checked out revision 117940."|
> |3|""|
> |4|"$ svn update --non-interactive -- 
> /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt"|
> |5|"Updating '/tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt':"|
> |6|"A /tmp/d20240713-3214727-1lhcgf8/board_agenda_2024_07_17.txt"|
> |7|"Updated to revision 117940."|
> |exception|"# 2..3)>"|
> |backtrace|[ 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:169:in 
> `initialize'", 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:169:in `new'", 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:169:in `block 
> in _evaluate'", "/x1/srv/whimsy/www/board/agenda/models/agenda.rb:173:in 
> `block in update'", "/x1/srv/whimsy/www/board/agenda/models/agenda.rb:155:in 
> `open'", "/x1/srv/whimsy/www/board/agenda/models/agenda.rb:155:in `update'", 
> "/x1/srv/whimsy/www/board/agenda/views/actions/commit.json.rb:18:in 
> `_evaluate'", "/x1/srv/whimsy/www/board/agenda/routes.rb:359:in `block in 
> '", "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:225:in `call'", 
> "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:202:in `call'", … ]|
> {panel}
> {panel}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: whimsy roster is not working

[sebb]

Should now be working again.

It looks like the latest version of one of the Ruby plugins (the ffi
Gem) is no longer compatible with the rest of the system, and that
caused other updates to fail.
I have temporarily pinned ffi to a previous compatible version.

Sebb

On Fri, 5 Jul 2024 at 06:03, Benchao Li  wrote:
>
> When I opened this url[1], the issue happened.
>
> [1] https://whimsy.apache.org/roster/committee/calcite
>
> Craig Russell  于2024年7月5日周五 12:03写道：
> >
> > Where were you in the process when this occurred? There was an issue 
> > earlier that was resolved in a different part of the tool...
> >
> > Craig
> >
> >
> > Begin forwarded message:
> >
> > From: Benchao Li 
> > Subject: whimsy roster is not working
> > Date: July 4, 2024 at 20:12:09 PDT
> > To: d...@community.apache.org
> > Reply-To: d...@community.apache.org
> >
> > Hi,
> >
> > When I was trying to use the whimsy tool to add new PMC members, it
> > seems not working. Can someone help on this?
> >
> > There are some error messages on the page:
> >
> > You have already activated stringio 3.1.1, but your Gemfile requires
> > stringio 3.1.0. Prepending `bundle exec` to your command may solve
> > this. (Gem::LoadError)
> >  /usr/lib/ruby/2.7.0/bundler/runtime.rb:312:in `check_for_activated_spec!'
> >  /usr/lib/ruby/2.7.0/bundler/runtime.rb:31:in `block in setup'
> >  /usr/lib/ruby/2.7.0/bundler/spec_set.rb:147:in `each'
> >  /usr/lib/ruby/2.7.0/bundler/spec_set.rb:147:in `each'
> >  /usr/lib/ruby/2.7.0/bundler/runtime.rb:26:in `map'
> >  /usr/lib/ruby/2.7.0/bundler/runtime.rb:26:in `setup'
> >  /usr/lib/ruby/2.7.0/bundler.rb:149:in `setup'
> >  /usr/lib/ruby/2.7.0/bundler/setup.rb:20:in `block in '
> >  /usr/lib/ruby/2.7.0/bundler/ui/shell.rb:136:in `with_level'
> >  /usr/lib/ruby/2.7.0/bundler/ui/shell.rb:88:in `silence'
> >  /usr/lib/ruby/2.7.0/bundler/setup.rb:20:in `'
> >  /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
> >  /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/ruby_supportlib/phusion_passenger/loader_shared_helpers.rb:380:in
> > `activate_gem'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/ruby_supportlib/phusion_passenger/loader_shared_helpers.rb:221:in
> > `block in run_load_path_setup_code'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/ruby_supportlib/phusion_passenger/loader_shared_helpers.rb:544:in
> > `running_bundler'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/ruby_supportlib/phusion_passenger/loader_shared_helpers.rb:220:in
> > `run_load_path_setup_code'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/helper-scripts/rack-preloader.rb:91:in
> > `preload_app'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/helper-scripts/rack-preloader.rb:189:in
> > `block in '
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/ruby_supportlib/phusion_passenger/loader_shared_helpers.rb:397:in
> > `run_block_and_record_step_progress'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/helper-scripts/rack-preloader.rb:188:in
> > `'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/helper-scripts/rack-preloader.rb:30:in
> > `'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.19/src/helper-scripts/rack-preloader.rb:29:in
> > `'
> >
> >
> >
> >
> > --
> >
> > Best,
> > Benchao Li
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
> > Craig L Russell
> > c...@apache.org
> >
>
>
> --
>
> Best,
> Benchao Li

Re: Secretary workbench is down

[sebb]

I think I have fixed the issue temporarily by uninstalling stringio 3.1.1.
However I suspect the problem will recur.

On Thu, 4 Jul 2024 at 19:35, Craig Russell  wrote:
>
> Every time...
>
> You have already activated stringio 3.1.1, but your Gemfile requires stringio 
> 3.1.0. Prepending `bundle exec` to your command may solve this. 
> (Gem::LoadError)
>
> Craig L Russell
> c...@apache.org
>

Re: Whimsy roster listing of Attic entities?

[sebb]

On Sun, 16 Jun 2024 at 01:47, sebbaz(Test)  wrote:
>
> On Sat, 15 Jun 2024 at 16:28, Shane Curcuru  wrote:
> >
> > In reviewing the June agenda, there are several projects listed as
> > reporting that don't need to report, due to WHIMSY-415 somehow.

I don't think that is the cause.

> > This includes Submarine, which was resolutioned to the Attic in May as
> > Special Order 7A.

Submarine was removed from committee-info.txt AFTER the agenda was created.

>> So researching which project reports we don't
> > actually need now in June led me to cross-check what the Roster tool
> > says about various projects - and I realized: there's no
> > whimsy.a.o/roster/attic/ listing!
> >
> > - Why doesn't public/committee-retired.json include URLs?  It would be
> > super-useful to have a link to the existing homepage there.
>
> Raise an JIRA request.
>
> > - Does anyone have any tips/energy to make a super-simple roster/attic
> > service, so this is easy for humans to discover when looking at our
> > rosters?  I'd definitely call this roster/attic, to explicitly list
> > things that the Attic thinks they own, rather than just "retired" which
> > might be thought of including other retired things (like failed podlings
> > or petri groups somehow).
>
> What are the qualifications for a project to appear in this listing?
>
> > - Why does roster/other still list Flume and Submarine?
>
> As the page header says, this is because the LDAP project groups still exist.
>
> > Is there a bug
> > or cleanup needed in Whimsy here, or is something in Attic-land not
> > properly marked as done/finalized/whatever?
> >
> > --
> > - Shane
> >Member
> >The Apache Software Foundation

[jira] [Commented] (WHIMSY-416) Removal of self from mailing list failures

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853298#comment-17853298
 ] 

Sebb commented on WHIMSY-416:
-

No idea how that can happen, unless you are using a browser extension that 
affects the behaviour.

For example, LastPass has been known to affect id.apache.org.

Which browser are you using, and does it have any plugins?

Can you try with a different browser?

> Removal of self from mailing list failures
> --
>
> Key: WHIMSY-416
> URL: https://issues.apache.org/jira/browse/WHIMSY-416
> Project: Whimsy
>  Issue Type: Bug
>  Components: Mail
>Reporter: Claude Warren
>Priority: Major
>
> I tried to remove myself (cla...@apache.org) from members-announce (and 
> several others, but that is the one I remember) and received an error message 
> that said:
> {noformat}
> Invalid Input
> Both email and list to subscribe to are required!
> {noformat}
> The error occurred within the last 5 minutes or so and multiple times.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-416) Removal of self from mailing list failures

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853069#comment-17853069
 ] 

Sebb commented on WHIMSY-416:
-

Exactly what input did you provide?

> Removal of self from mailing list failures
> --
>
> Key: WHIMSY-416
> URL: https://issues.apache.org/jira/browse/WHIMSY-416
> Project: Whimsy
>  Issue Type: Bug
>  Components: Mail
>Reporter: Claude Warren
>Priority: Major
>
> I tried to remove myself (cla...@apache.org) from members-announce (and 
> several others, but that is the one I remember) and received an error message 
> that said:
> {noformat}
> Invalid Input
> Both email and list to subscribe to are required!
> {noformat}
> The error occurred within the last 5 minutes or so and multiple times.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-415) /agenda/new fails to mark some reports due when calendar outdated

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850208#comment-17850208
 ] 

Sebb commented on WHIMSY-415:
-

I updated committee-info.yml in r117402 (the YAML file records retirements etc)

> /agenda/new fails to mark some reports due when calendar outdated
> -
>
> Key: WHIMSY-415
> URL: https://issues.apache.org/jira/browse/WHIMSY-415
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: Shane Curcuru
>Priority: Minor
>
> On Wednesday 22 May I hit whimsy.a.o/board/agenda/new to create a new agenda, 
> but got several errors on the original screen, since the 
> committers/board/calendar.txt file didn't have any further dates ready.  
> Whimsy did guess at the correct third wednesday of the month, but I didn't 
> check the rest of the details.
> I closed the whimsy window without pushing Post.  Then I updated calendar.txt 
> and waited a day.
> Coming back Thursday to /board/agenda/new, I pressed Post, and it sent out 
> the normal reminders (and sent me a report).
> *BUG*
> Reminders went out to Aries and Struts, even though they had submitted 
> reports in May.  Struts in particular had missed April, so the PMC chair was 
> really confused when they thought we hadn't accepted the May report (which we 
> did).
> Not sure if this is reproduceable, may have been due to calendar.txt not 
> having future dates, or may be because I used /agenda/new, but didn't Post, 
> then came back later and did it all over again.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Bug in secretary workbench

[sebb]

OK, so it looks like Whimsy is behaving OK; the problem is with the browser(s).

On Tue, 28 May 2024 at 12:20, Craig Russell  wrote:
>
> I should have mentioned that I deleted the blank form in workbench.
>
> On Tue, May 28, 2024, 12:07 sebb  wrote:
>
> > On Tue, 28 May 2024 at 06:54, Craig Russell  wrote:
> > >
> > > The ICLA to be filed from London seems to display the first page of the
> > pdf but then scrolling, the entire page hangs. In order to continue, the
> > page needs to be force reloaded.
> > >
> > > The ICLA opens just fine in Preview pdf viewer.
> > >
> > > Can someone open the ICLA in the workbench and see if you can scroll
> > past the first page?
> >
> > Work OK for me on macOS using Chrome. Can also read both pages using
> > Safari, but the text is all fuzzy - looks like it has been added with
> > a printing stamp, twice, slightly out of registration.
> >
> > However on iPad I could not see the second page in any of the browsers I
> > tried.
> >
> > The original email has two copies of the attachment, one of which has
> > not been filled in.
> > However Whimsy only shows one.
> >
> > I just downloaded the original PDFs from the direct email I received,
> > and the signed version displays fine in macOS Preview, but when I use
> > Safari to open the file, it shows the same fuzzy text.
> >
> > So the display problem does not appear to be anything to do with
> > Whimsy, but it's odd that only one of the PDFs is shown by Whimsy.
> > I'll look into that.
> >
> > Sebb
> > > Craig L Russell
> > > c...@apache.org
> > >
> >

Re: Bug in secretary workbench

[sebb]

On Tue, 28 May 2024 at 06:54, Craig Russell  wrote:
>
> The ICLA to be filed from London seems to display the first page of the pdf 
> but then scrolling, the entire page hangs. In order to continue, the page 
> needs to be force reloaded.
>
> The ICLA opens just fine in Preview pdf viewer.
>
> Can someone open the ICLA in the workbench and see if you can scroll past the 
> first page?

Work OK for me on macOS using Chrome. Can also read both pages using
Safari, but the text is all fuzzy - looks like it has been added with
a printing stamp, twice, slightly out of registration.

However on iPad I could not see the second page in any of the browsers I tried.

The original email has two copies of the attachment, one of which has
not been filled in.
However Whimsy only shows one.

I just downloaded the original PDFs from the direct email I received,
and the signed version displays fine in macOS Preview, but when I use
Safari to open the file, it shows the same fuzzy text.

So the display problem does not appear to be anything to do with
Whimsy, but it's odd that only one of the PDFs is shown by Whimsy.
I'll look into that.

Sebb
> Craig L Russell
> c...@apache.org
>

[jira] [Commented] (WHIMSY-415) /agenda/new fails to mark some reports due when calendar outdated

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849362#comment-17849362
 ] 

Sebb commented on WHIMSY-415:
-

Is there any point working on this since the agenda functionality is due to be 
taken over by Infra?

Seems like it could be a lot of work for something that seems unlikely to recur.

> /agenda/new fails to mark some reports due when calendar outdated
> -
>
> Key: WHIMSY-415
> URL: https://issues.apache.org/jira/browse/WHIMSY-415
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: Shane Curcuru
>Priority: Minor
>
> On Wednesday 22 May I hit whimsy.a.o/board/agenda/new to create a new agenda, 
> but got several errors on the original screen, since the 
> committers/board/calendar.txt file didn't have any further dates ready.  
> Whimsy did guess at the correct third wednesday of the month, but I didn't 
> check the rest of the details.
> I closed the whimsy window without pushing Post.  Then I updated calendar.txt 
> and waited a day.
> Coming back Thursday to /board/agenda/new, I pressed Post, and it sent out 
> the normal reminders (and sent me a report).
> *BUG*
> Reminders went out to Aries and Struts, even though they had submitted 
> reports in May.  Struts in particular had missed April, so the PMC chair was 
> really confused when they thought we hadn't accepted the May report (which we 
> did).
> Not sure if this is reproduceable, may have been due to calendar.txt not 
> having future dates, or may be because I used /agenda/new, but didn't Post, 
> then came back later and did it all over again.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-414) Roll call tool to simplify PMC roll calls

[Sebb (Jira)]

[ 
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] [Commented] (WHIMSY-414) Roll call tool to simplify PMC roll calls

[Sebb (Jira)]

[ 
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)

[jira] [Commented] (WHIMSY-414) Roll call tool to simplify PMC roll calls

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839228#comment-17839228
 ] 

Sebb commented on WHIMSY-414:
-

Some thought needs to be given to the karma required to read and write the 
survey data.

For a PMC roll call, it is obviously vital that all current PMC members can 
provide responses to their own surveys, but what access should PMC members have 
to surveys for other PMCs (if they are not an ASF member)? One solution to this 
might be to store the survey data under the relevant SVN /private/pmc/ 
directory tree.

Should non-ASF members be able to see the survey questions for PMCs other than 
their own?

> 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.
>   
> 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)

Re: Github account not shown in ASF account profile

[sebb]

I already answered this question on the private users@infra list: Whimsy
only shows what the LDAP record contains.

Whimsy is not involved in account authentication.

Please ask on your project list first.
There must be others who have performed the same steps.


On Tue, 2 Apr 2024 at 17:14, Mirko Kämpf  wrote:

> Hello dear Whimsy team,
>
> we have observed an anomaly in my ASF account (user: kamir)
> which should be linked to the Github account kamir.
> [image: image.png]
> I can see in boxer, that I am listed for repositories
> from Apache Training and Apache Wayang, but inside the project's pages
> my Github username is invisible.
>
> *Why do I ask?*
> My goal is to work on the release 1.0 of Apache Wayang and also on a
> "tool-subproject release" in Apache Training. In both cases I get this
> error during the release process:
>
> *Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy
> (default-deploy) on project wayang: ArtifactDeployerException: Failed to
> deploy artifacts: Could not transfer artifact
> org.apache.wayang:wayang:pom:0.7.1 from/to apache.releases.https 
> (**https://repository.apache.org/service/local/staging/deploy/maven2
> **):
> status code: 401, reason phrase: Unauthorized (401) -> [Help 1]*
>
> Committing to Github seems to work well, but the deploy step fails.
>
> Best wishes,
> Mirko
>
> --
>
> Dr. rer. nat. Mirko Kämpf
> Müchelner Str. 23
> 06259 Frankleben
>
>

Re: Assistance with surveys write error

[sebb]

On Sat, 23 Mar 2024 at 11:43, Shane Curcuru  wrote:
>
> If anyone can spot my error when submitting to officers/surveys, I'd
> love help understanding how this is not working, even though the form
> submission code seems to be exactly the same structure as coi and
> mentor-update are (which work).
>
> Checkout works fine, but I can't write to the file:
>
> # /srv/svn/officers_surveys/boardf2f2024-data.json>
>/x1/srv/whimsy/www/officers/surveys.cgi:129:in `write'
> ...

In order to update files in SVN, you need to update the copy in the
temporary checkout and commit it.
pubsub will then update the checkout.

Looks like filename does not point to the temporary checkout.

> Separately, someday I'll get help to figure out why using GitHub desktop
> to submit PRs and merge them often litters the commit stream with an
> extra "Merge branch 'apache:master' into master" commit (with nothing in
> it).

If only.

> Thanks!
>
> --
> - Shane
>Member
>The Apache Software Foundation

Re: Delivery Status Notification (Failure) for private@legal

[sebb]

Try again

On Mon, 18 Mar 2024 at 22:53, sebbaz(Test)  wrote:

> I would have thought the legal-private@ list would be more in line with
> how PMCs are handled.
>
> I'll see if I can fix that.
>
> On Mon, 18 Mar 2024 at 17:40, Craig Russell  wrote:
>
>> This email was generated by clicking on the Legal Affairs agenda. Maybe
>> legal-discuss is a better email to use for this purpose?
>>
>> Craig
>>
>> Begin forwarded message:
>>
>> *From: *Mail Delivery Subsystem 
>> *Subject: **Delivery Status Notification (Failure)*
>> *Date: *March 18, 2024 at 10:21:20 PDT
>> *To: *apache@gmail.com
>>
>> [image: Error Icon]
>> Address not found
>> Your message wasn't delivered to *priv...@legal.apache.org
>> *because the domain legal.apache.org couldn't
>> be found. Check for typos or unnecessary spaces and try again.
>> LEARN MORE 
>> The response was:
>>
>> DNS Error: DNS type 'mx' lookup of legal.apache.org responded with code
>> NXDOMAIN Domain name not found: legal.apache.org For more information,
>> go to https://support.google.com/mail/?p=BadRcptDomain
>> Reporting-MTA: dns; googlemail.com
>> Received-From-MTA: dns; apache@gmail.com
>> Arrival-Date: Mon, 18 Mar 2024 10:21:19 -0700 (PDT)
>> X-Original-Message-ID: <630821ed-93d3-415e-afc8-28794e678...@gmail.com>
>>
>> Final-Recipient: rfc822; priv...@legal.apache.org
>> Action: failed
>> Status: 5.1.2
>> Diagnostic-Code: smtp; DNS Error: DNS type 'mx' lookup of
>> legal.apache.org responded with code NXDOMAIN
>> Domain name not found: legal.apache.org For more information, go to
>> https://support.google.com/mail/?p=BadRcptDomain
>> Last-Attempt-Date: Mon, 18 Mar 2024 10:21:20 -0700 (PDT)
>>
>> *From: *Craig Russell 
>> *Subject: **Missing Legal Affairs Board Report*
>> *Date: *March 18, 2024 at 10:21:17 PDT
>> *To: *Roman Shaposhnik 
>> *Cc: *priv...@legal.apache.org, Apache Board 
>>
>>
>> Dear Roman Shaposhnik,
>>
>> The board report for Legal Affairs has not yet been submitted for this
>> month's board meeting.  Please try to submit these reports by the Friday
>> before the meeting.
>>
>> Thanks,
>>
>> Craig L Russell
>>
>>
>> Craig L Russell
>> c...@apache.org
>>
>>
>> Craig L Russell
>> c...@apache.org
>>
>>

Re: Who/how set up memapp-received.txt?

[sebb]

Which I have just done.
I think the runbook probably needs some work...

On Fri, 8 Mar 2024 at 15:34, sebb  wrote:
>
> Looks like someone is supposed to populate it using
>
> https://svn.apache.org/repos/private/foundation/Meetings/candidates.rb
>
> According to runbook.txt it is the job of the Secretary to do this.
>
> On Fri, 8 Mar 2024 at 14:54, Craig Russell  wrote:
> >
> > The foundation/Meetings/20240307/memapp-received.txt needs to be set up. I 
> > do not see instructions how to set  it up.
> >
> > "Surely" it does not need to be manually edited?
> >
> > Craig L Russell
> > c...@apache.org
> >

Re: Who/how set up memapp-received.txt?

[sebb]

Looks like someone is supposed to populate it using

https://svn.apache.org/repos/private/foundation/Meetings/candidates.rb

According to runbook.txt it is the job of the Secretary to do this.

On Fri, 8 Mar 2024 at 14:54, Craig Russell  wrote:
>
> The foundation/Meetings/20240307/memapp-received.txt needs to be set up. I do 
> not see instructions how to set  it up.
>
> "Surely" it does not need to be manually edited?
>
> Craig L Russell
> c...@apache.org
>

Re: Has memapp-received.txt been set up yet?

[sebb]

Does it appear in the meeting directory?
https://svn.apache.org/repos/private/foundation/Meetings/20240307/

On Fri, 8 Mar 2024 at 00:32, Craig Russell  wrote:
>
> Whimsy secretary workbench wants to know...
>
> Craig L Russell
> c...@apache.org
>

[jira] [Resolved] (WHIMSY-413) Download checker does not recognize sub-projects

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-413.
-
Resolution: Not A Bug

Please see my reply on the dev@mailing list

> Download checker does not recognize sub-projects
> 
>
> Key: WHIMSY-413
> URL: https://issues.apache.org/jira/browse/WHIMSY-413
> Project: Whimsy
>  Issue Type: Bug
>  Components: General
>Reporter: Craig L Russell
>Priority: Minor
>
> https://whimsy.apache.org/members/download_check.cgi
>  
> fails page db.apache.org/jdo/download.html because it doesn't recognize db as 
> an umbrella project that currently has two sub-projects: jdo and derby, which 
> have their respective web sites and download pages.
>  
> https://db.apache.org/derby/
> https://db.apache.org/jdo/
>  
> and their download pages
>  
> https://db.apache.org/derby/derby_downloads.html
> https://db.apache.org/jdo/downloads.html
>  
> This is a special case



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Bug in download checker

[sebb]

On Thu, 7 Mar 2024 at 00:35, Craig Russell  wrote:
>
>
> https://whimsy.apache.org/members/download_check.cgi
>
> fails page db.apache.org/jdo/download.html because it doesn't recognize db as 
> an umbrella project that currently has two sub-projects: jdo and derby, which 
> have their respective web sites and download pages.

That page does not exist.

> https://db.apache.org/derby/
> https://db.apache.org/jdo/
>
> and their download pages
>
> https://db.apache.org/derby/derby_downloads.html
> https://db.apache.org/jdo/downloads.html

Those pages exist, but they are not download pages.

Try one of the linked version pages.

> This is a special case.

I see no evidence for that.

> Craig L Russell
> c...@apache.org
>

[jira] [Resolved] (WHIMSY-412) Proxy volunteers are not all selectable in the proxy designation form

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-412.
-
Resolution: Information Provided

Greg has assigned a proxy for himself; as such, he cannot be a proxy.

> Proxy volunteers are not all selectable in the proxy designation form
> -
>
> Key: WHIMSY-412
> URL: https://issues.apache.org/jira/browse/WHIMSY-412
> Project: Whimsy
>  Issue Type: Bug
>Reporter: C. Michael Pilato
>Priority: Major
> Attachments: Screenshot from 2024-02-29 15-38-45.png, Screenshot from 
> 2024-02-29 15-39-42.png
>
>
> At the time of writing, there are three members listed as having volunteered 
> as proxies at [https://whimsy.apache.org/members/proxy]. Unfortunately, one 
> of those ({{{}Greg Stein (gstein){}}}) is not presented in the drop-down 
> selector as a viable option.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (WHIMSY-411) False negatives for sponsors

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-411.
-
Resolution: Invalid

https://www.apache.org/foundation/marks/pmcs#navigation

says

"Sponsors", "Thanks" or "Thanks to our Sponsors" should link to: 
www.apache.org/foundation/thanks.html

> False negatives for sponsors 
> -
>
> Key: WHIMSY-411
> URL: https://issues.apache.org/jira/browse/WHIMSY-411
> Project: Whimsy
>  Issue Type: Bug
>  Components: Website
>Reporter: Craig L Russell
>Priority: Minor
>
> The website checker fails pages that do not link to the thanks page.
> However, links to the sponsors page should also be passed. For example, 
> [https://pekko.apache.org|https://pekko.apache.org/] fails the check but has 
> "Thanks" text that links to [https://www.apache.org/foundation/sponsors] 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Signing key repository

[sebb]

On Sun, 18 Feb 2024 at 23:46, sebbaz(Test)  wrote:
>
> On Sun, 18 Feb 2024 at 17:14, Craig Russell  wrote:
> >
> > As you might have notices, we received an SGA signed with a GPG key. Whimsy 
> > verified the key but as far as I can see, the filing process did not store 
> > the key in the repository.
>
> Note that all the sig checks are done in the same routine, which saves
> the key if it was successfully imported.
>
> It tried to save the SGA key, but failed; there was a problem with the
> credentials (which I will try to fix).
>
> Was no error reported?
>
> > Perhaps we should change the name of the key repository to reflect that any 
> > of several documents might be signed, and change the code to store the key 
> > if it is used to sign any of the documents.
> >
>
> The __keys__ directory is currently under iclas; perhaps it should be
> moved to the same level as the iclas, cclas and grants.

Upon further checking, this would entail setting up a new entry SVN
auth entry with the appropriate permissions; not sure it's worth it.

> > WDYT?
> >
> > Craig L Russell
> > c...@apache.org
> >

Re: Web site checks feature request

[sebb]

On Sun, 18 Feb 2024 at 19:12, Craig Russell  wrote:
>
> I was just looking at the web site check tool and I've added a board 
> discussion about the hundreds of failures.

OK, but out of scope for Whimsy.

> I also clicked on one link
> https://whimsy.apache.org/site/project/aries
> and followed it to
> https://aries.apache.org/documentation/index.html
> and then to
> https://github.com/apache/aries-antora-site/edit/master/modules/ROOT/pages/index.adoc
>
> This repository must be forked in order to propose changes.

AFAICT that is normal. Only project committers can create branches in
ASF git repos, and PRs need branches.

> Here's what I think needs to be done:
> check for a link to the source code to the web site repository; if not, 
> yellow flag

Whimsy only checks the index page, which would imply that all websites
would need to link to the website repo (which might also be in SVN)
from the main index page.
It would be useful if every page had an Edit button, but that may not
be easy to do, depending on the website repo and build process.
I think it would be a mistake to make that mandatory.

> check that the repository is at least readable for the public

That is potentially possible to check, though I think it is unnecessary.
AFAICT Infra does not use any authn to fetch the websites for display,
so problems will be immediately apparent.

> and read/write for committers of that project; if not, yellow flag

I think that is out of scope for Whimsy.
In any case, if project committers cannot update the website I'm sure
they will complain.

> I also think that policy should mandate a link to the repository and 
> read/write access by project committers.

That is outside the scope of the Whimsy project.

> Craig L Russell
> c...@apache.org
>

[jira] [Commented] (WHIMSY-408) Update meetings.cgi to derive meeting dates automatically

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818112#comment-17818112
 ] 

Sebb commented on WHIMSY-408:
-

Well spotted, and thanks for the patch.

Note that it was reversed, but as it is quite a simple change I did it manually.


> Update meetings.cgi to derive meeting dates automatically
> -
>
> Key: WHIMSY-408
> URL: https://issues.apache.org/jira/browse/WHIMSY-408
> Project: Whimsy
>  Issue Type: Task
>    Reporter: Sebb
>Priority: Major
> Attachments: weekday.patch
>
>
> The meeting.cgi file currently needs to be manually updated each year, see 
> the code near 
> https://github.com/apache/whimsy/blob/master/www/members/meeting.cgi#L157
> It might perhaps make sense to automate this by reading from
> https://svn.apache.org/repos/private/foundation/Meetings/MMDD/README.txt
> or the script that generates it
> https://svn.apache.org/repos/private/foundation/Meetings/create-meeting.rb
> Better yet might be for create-meeting.rb to generate a data file in a fixed 
> location that can be used by other scripts.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (WHIMSY-409) members/proxy.cgi allows for submission of non-selected proxy

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-409.
-
Resolution: Fixed

Updated code to reject invalid/missing proxy entries

> members/proxy.cgi allows for submission of non-selected proxy
> -
>
> Key: WHIMSY-409
> URL: https://issues.apache.org/jira/browse/WHIMSY-409
> Project: Whimsy
>  Issue Type: Bug
>Reporter: Sander Striker
>Priority: Major
>
> The proxy.cgi script allows for submission of an empty proxy.  This results 
> in the tool no longer working as the proxies file becomes invalid when parsed.
> Potential workaround is to preselect the secretary as the default: 
> https://github.com/apache/whimsy/pull/197



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (WHIMSY-410) members/inactive.cgi does not show the 2023 meeting

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-410.
-
Resolution: Information Provided

> members/inactive.cgi does not show the 2023 meeting
> ---
>
> Key: WHIMSY-410
> URL: https://issues.apache.org/jira/browse/WHIMSY-410
> Project: Whimsy
>  Issue Type: Bug
>Reporter: Sander Striker
>Priority: Major
>
> Visiting [https://whimsy.apache.org/members/inactive] I don't see 2023 in the 
> list.  The text on the page suggest we are missed a step in updating our 
> attendance records after the 2023 meeting?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-410) members/inactive.cgi does not show the 2023 meeting

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815664#comment-17815664
 ] 

Sebb commented on WHIMSY-410:
-

There is no attend file under Meetings/20230309; possibly other files are 
missing.
Fixing this is out of scope for Whimsy

> members/inactive.cgi does not show the 2023 meeting
> ---
>
> Key: WHIMSY-410
> URL: https://issues.apache.org/jira/browse/WHIMSY-410
> Project: Whimsy
>  Issue Type: Bug
>Reporter: Sander Striker
>Priority: Major
>
> Visiting [https://whimsy.apache.org/members/inactive] I don't see 2023 in the 
> list.  The text on the page suggest we are missed a step in updating our 
> attendance records after the 2023 meeting?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (WHIMSY-408) Update meetings.cgi to derive meeting dates automatically

[Sebb (Jira)]

Sebb created WHIMSY-408:
---

 Summary: Update meetings.cgi to derive meeting dates automatically
 Key: WHIMSY-408
 URL: https://issues.apache.org/jira/browse/WHIMSY-408
 Project: Whimsy
  Issue Type: Task
Reporter: Sebb


The meeting.cgi file currently needs to be manually updated each year, see the 
code near 
https://github.com/apache/whimsy/blob/master/www/members/meeting.cgi#L157

It might perhaps make sense to automate this by reading from
https://svn.apache.org/repos/private/foundation/Meetings/MMDD/README.txt
or the script that generates it
https://svn.apache.org/repos/private/foundation/Meetings/create-meeting.rb

Better yet might be for create-meeting.rb to generate a data file in a fixed 
location that can be used by other scripts.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-407) SVN authentication prevents mailinglist subscription

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813359#comment-17813359
 ] 

Sebb commented on WHIMSY-407:
-

Please try again; there was a config error which has hopefully been corrected.

> SVN authentication prevents mailinglist subscription
> 
>
> Key: WHIMSY-407
> URL: https://issues.apache.org/jira/browse/WHIMSY-407
> Project: Whimsy
>  Issue Type: Bug
>  Components: Mail
>Reporter: Arnout Engelen
>Priority: Major
>
> When I tried to subscribe myself (address 
> [enge...@apache.org|mailto:enge...@apache.org]) to the mailinglist 
> priv...@pekko.apache.org, I got:
>  
> Submitting subscribe request: \{ "version": 3, "availid": "engelen", "addr": 
> "enge...@apache.org", "listkey": "priv...@pekko.apache.org", "member_p": 
> false, "chair_p": false }
> svn checkout --non-interactive -- 
> https://svn.apache.org/repos/infra/infrastructure/trunk/subreq/ 
> /tmp/d20240201-1070894-1xv3tbb
> svn: E170013: Unable to connect to a repository at URL 
> 'https://svn.apache.org/repos/infra/infrastructure/trunk/subreq'
> svn: E215004: No more credentials or we tried too many times.
> Authentication failed
> svn commit --non-interactive --message priv...@pekko.apache.org\ +\=\ engelen 
> -- engelen-pekko-private.json
> svn: E155007: '/tmp/d20240201-1070894-1xv3tbb/engelen-pekko-private.json' is 
> not a working copy
>  
> Trying again did not appear to help.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (WHIMSY-386) public_ldap_committees is redundant

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-386.
-
Resolution: Fixed

Gone, not sure when...

> public_ldap_committees is redundant
> ---
>
> Key: WHIMSY-386
> URL: https://issues.apache.org/jira/browse/WHIMSY-386
> Project: Whimsy
>  Issue Type: Task
>    Reporter: Sebb
>Priority: Major
>
> The public_ldap_committees.json file has long been deprecated, and AFAICT it 
> is not being used. It should be dropped.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (WHIMSY-406) Roster modify may fail to list selected committer(s)

[Sebb (Jira)]

Sebb created WHIMSY-406:
---

 Summary: Roster modify may fail to list selected committer(s)
 Key: WHIMSY-406
 URL: https://issues.apache.org/jira/browse/WHIMSY-406
 Project: Whimsy
  Issue Type: Bug
Reporter: Sebb


See https://lists.apache.org/thread/w27gsgddjx7ob1nhw3cqqzcw9hq981c3



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (WHIMSY-401) Board agenda tool comments

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-401.
-
Resolution: Information Provided

> Board agenda tool comments
> --
>
> Key: WHIMSY-401
> URL: https://issues.apache.org/jira/browse/WHIMSY-401
> Project: Whimsy
>  Issue Type: Task
>  Components: BoardAgenda
>Reporter: Craig L Russell
>Priority: Major
>
> The agenda tool allows users to add comments to the agenda which are saved in 
> the agenda and are subsequently sent to the project PMC private list. The 
> comments are durable in the agenda and can be viewed in subsequent agendas.
> The agenda tool should allow comments to be divided into multiple categories, 
> depending on the intended audience:
> feedback: congratulations, nice report, healthy community
> discussion: notes for other Directors about the project that might lead to 
> future action
> request: information is needed from the project, possibly to clarify an item 
> in the report
> action: the project is requested to perform some corrective action
> Additionally, a Director might want to flag the report for the upcoming board 
> meeting
> Proposal:
> 1. Update the comment pop-up dialog to add a drop-down called *Category* to 
> select one of four categories:
> [ ] feedback
> [X] discuss is default
> [ ] request
> [ ] action
> Text entered as "feedback" will be sent unmodified to the PMC private list. 
> It will be stored in the agenda unmodified.
> Text entered as "discuss" will not be sent to the PMC private list. It will 
> be stored in the agenda with a prefix of [discuss]
> Text entered as "request" will be sent to the PMC with a prefix "Please reply 
> to this request" and will be stored in the agenda with a prefix of [request]
> Text entered as "action" will be sent to the PMC with a prefix "Please take 
> the requested action" and will be stored in the agenda with a prefix of 
> [action] 
> 2. The field "Initials" will be changed to "From"
> 3. Directors will be able to edit current comments by clicking on the author 
> of a current comment, regardless of the author. This will bring up a comment 
> pop-up allowing editing of any of the fields, e.g. to change the "From" from 
> "clr" to "board"; or to change the Category; or to update the text of the 
> comment.
> The action boxes at the bottom of the pop-up will additionally allow [Delete 
> Comment] as an option (in addition to [Cancel] and [Save])



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: not able to add a PMC member

[sebb]

On Thu, 23 Nov 2023 at 09:39, Daan  wrote:
>
>
>
> On 2023/11/23 09:32:53 sebb wrote:
> > There is a question with a check-box which needs to be answered.
> >
>
> I know and did click, acknowledging the board notice was sent.
>  The list is not getting populated with the id to modify and the button does 
> not get enabled.

That was not clear from your original description.
It looks like the code sometimes fails to pick up the selected entry.
Try revisiting the page or using a different browser.

> > On Thu, 23 Nov 2023 at 08:53, Daan Hoogland  wrote:
> > >
> > > Hey, devs,
> > >
> > > I have not done this before so am assuming I am at fault here, but
> > >
> > > I try to add an exsisting committer to the roster of PMC members on
> > > https://whimsy.apache.org/roster/committee/cloudstack
> > > - I select the committer (shwstppr in this case, but I tried several 
> > > others)
> > > - I click "Modify" on the top of the page
> > > - in the dialog the "Add PMC" button is inactive and no edit field is
> > > available that might enable it.
> > >
> > > I am a member so I think I should be able to. Any help appreciated.
> > >
> > > kind regards,
> > > Daan (cloudstack pmc)
> >

Re: not able to add a PMC member

[sebb]

There is a question with a check-box which needs to be answered.

On Thu, 23 Nov 2023 at 08:53, Daan Hoogland  wrote:
>
> Hey, devs,
>
> I have not done this before so am assuming I am at fault here, but
>
> I try to add an exsisting committer to the roster of PMC members on
> https://whimsy.apache.org/roster/committee/cloudstack
> - I select the committer (shwstppr in this case, but I tried several others)
> - I click "Modify" on the top of the page
> - in the dialog the "Add PMC" button is inactive and no edit field is
> available that might enable it.
>
> I am a member so I think I should be able to. Any help appreciated.
>
> kind regards,
> Daan (cloudstack pmc)

Re: Board agenda oopsie

[sebb]

What happens if you change it back again?

On Mon, 13 Nov 2023 at 22:30, Craig Russell  wrote:
>
> I made a comment on a project report, and since we have discussed having 
> directors' real names in emails sent to projects after meetings, I changed my 
> asf id in the comment.
>
> But apparently that action changed the id in all of the approvals as well.
>
> If this is expected behavior, I certainly did not expect it.
>
> I know that there may be little enthusiasm for making any changes at this 
> time, but we perhaps could discuss it.
>
> Craig L Russell
> c...@apache.org
>

Re: Bug in secretary workbench

[sebb]

It is the browser that displays the PDF, so there's not a lot that the
Whimsy code can do.

Works fine for me in Opera, Firefox, Chrome.
Only hangs in Safari.

Sebb

On Sun, 5 Nov 2023 at 01:46, Craig Russell  wrote:
>
> The ICLA submitted today from J.S. fails. When viewing the pdf, scrolling 
> stops in the middle of the document and the page hangs. The only thing that 
> it will do is reload the page and then try again.
>
> Seems that scrolling the pdf causes a failure.
>
> Craig L Russell
> c...@apache.org
>

Re: [whimsy] branch master updated: Add pen name option to rejection template

[sebb]

On Tue, 10 Oct 2023 at 21:56, Matt Sicker  wrote:
>
> Well, I wouldn’t say we disallow them entirely. The problem is that 99% of 
> the time, people put their userid in the public name field without intending 
> that to be their public name. If someone’s pen name is their userid, that’s 
> fine, but we want them to verify that in such a case. Perhaps we should 
> include a note in that description about it?

That would help, but rather than rejecting the application, we should
ask if they intended to use their id as the public id.
Or just allow it, and fix the name later.

> The general idea here is that we want people to use some sort of public name 
> intentionally and non-maliciously (i.e., no impersonations).

Using their user id as their public name is definitely not malicious
or an impersonation.
It may not be ideal, but it can always be changed later if they did
not intend it.

> We want to allow people to safely contribute to projects here without having 
> to expose their legal name or any of the complications that can involve when 
> it differs from their name they normally go by (e.g., I go by “Matt” instead 
> of “Matthew”, and some systems break if I use the short name; other people 
> have entirely different first or last names from what their current “legal” 
> name might be, or they use their middle name, or they just wish to remain 
> mostly anonymous).

That is not relevant to the issue of rejecting ICLAs.

> > On Sep 26, 2023, at 5:02 PM, sebb  wrote:
> >
> > On Tue, 26 Sept 2023 at 21:59,  wrote:
> >>
> >> This is an automated email from the ASF dual-hosted git repository.
> >>
> >> mattsicker pushed a commit to branch master
> >> in repository https://gitbox.apache.org/repos/asf/whimsy.git
> >>
> >>
> >> The following commit(s) were added to refs/heads/master by this push:
> >> new 5e47f5a9 Add pen name option to rejection template
> >> 5e47f5a9 is described below
> >>
> >> commit 5e47f5a97fe987dc542737f795263472092c7a82
> >> Author: Matt Sicker 
> >> AuthorDate: Tue Sep 26 15:58:19 2023 -0500
> >>
> >>Add pen name option to rejection template
> >>
> >>Since we've clarified that pen names are allowed for public names, this 
> >> updates the template used for rejecting invalid use of public names to 
> >> indicate that.
> >> ---
> >> www/secretary/workbench/views/actions/incomplete.json.rb | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/www/secretary/workbench/views/actions/incomplete.json.rb 
> >> b/www/secretary/workbench/views/actions/incomplete.json.rb
> >> index 61f33611..ee4252e3 100644
> >> --- a/www/secretary/workbench/views/actions/incomplete.json.rb
> >> +++ b/www/secretary/workbench/views/actions/incomplete.json.rb
> >> @@ -16,7 +16,7 @@ REASONS = {
> >>   '@missing_address' => 'missing or incomplete postal address',
> >>   '@missing_email' => 'missing email address',
> >>   '@corporate_postal' => 'the postal address does not appear to be a 
> >> personal postal address',
> >> -  '@invalid_public' => 'the public name should be a real name and not a 
> >> user id',
> >> +  '@invalid_public' => 'the public name should be a real name or pen name 
> >> and not a user id',
> >
> > Is there a reason why we disallow user ids for public names?
> >
> > It does not make sense to me to discriminate on that basis.
> >
> >
> >>   '@separate_signature' => 'the document and signature must be sent 
> >> attached to the same email',
> >>   '@unauthorized_signature' => 'the signature must be from an authorized 
> >> person, usually a company executive',
> >>   '@empty_form' => 'the form appears to be completely empty',
> >>
>

Re: [whimsy] branch master updated: Add pen name option to rejection template

[sebb]

On Tue, 26 Sept 2023 at 21:59,  wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> mattsicker pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/whimsy.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
>  new 5e47f5a9 Add pen name option to rejection template
> 5e47f5a9 is described below
>
> commit 5e47f5a97fe987dc542737f795263472092c7a82
> Author: Matt Sicker 
> AuthorDate: Tue Sep 26 15:58:19 2023 -0500
>
> Add pen name option to rejection template
>
> Since we've clarified that pen names are allowed for public names, this 
> updates the template used for rejecting invalid use of public names to 
> indicate that.
> ---
>  www/secretary/workbench/views/actions/incomplete.json.rb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/www/secretary/workbench/views/actions/incomplete.json.rb 
> b/www/secretary/workbench/views/actions/incomplete.json.rb
> index 61f33611..ee4252e3 100644
> --- a/www/secretary/workbench/views/actions/incomplete.json.rb
> +++ b/www/secretary/workbench/views/actions/incomplete.json.rb
> @@ -16,7 +16,7 @@ REASONS = {
>'@missing_address' => 'missing or incomplete postal address',
>'@missing_email' => 'missing email address',
>'@corporate_postal' => 'the postal address does not appear to be a 
> personal postal address',
> -  '@invalid_public' => 'the public name should be a real name and not a user 
> id',
> +  '@invalid_public' => 'the public name should be a real name or pen name 
> and not a user id',

Is there a reason why we disallow user ids for public names?

It does not make sense to me to discriminate on that basis.


>'@separate_signature' => 'the document and signature must be sent attached 
> to the same email',
>'@unauthorized_signature' => 'the signature must be from an authorized 
> person, usually a company executive',
>'@empty_form' => 'the form appears to be completely empty',
>

Re: Please remove the GitHub ID field from the whimsy roster

[sebb]

Try the following:
https://whimsy.apache.org/roster/committer/__self__

Text can be adjusted if necessary

On Tue, 19 Sept 2023 at 15:42, sebb  wrote:
>
> On Tue, 19 Sept 2023 at 13:11, Shane Curcuru  wrote:
> >
> > sebb wrote on 9/18/23 6:17 PM:
> > > On Mon, 18 Sept 2023 at 20:18, Daniel Gruno  wrote:
> > >>
> > >> Hi, whimsy folks,
> > >> Could you please remove the GitHub ID field from the whimsy roster 
> > >> service?
> > >> The field is not canonical/authoritative, and mostly just serves to 
> > >> confuse new committers these days. The only authoritative place for 
> > >> GitHub IDs is through https://gitbox.apache.org/boxer/
> >
> > If this is causing problems for Infra, we absolutely need to at least
> > clearly annotate the field, and provide a link to gitbox, to ensure
> > users don't keep asking questions in the wrong place.
>
> I would be interested to know how many of the Ids in Whimsy differ
> from the ones tied to ASF accounts?
>
> > > The GitHub ids in Whimsy are provided by their owners, so can be
> > > considered authoritative, even if they might not be the ones that are
> > > linked to ASF accounts.
> > > I am told that people find them useful.
> > >
> > > Maybe a solution would be to add a note that the id might not be the
> > > one that is linked to the ASF id.
> > > Even better would be if the boxer system could validate which GH Id is
> > > being used for linking?
> >
> > Having GitHub ID in whimsy is useful, because many committers know it as
> > a place to find information about accounts.  However, we should
> > deprecate/document any fields that have specific ties to other systems,
> > especially which ones are authoritative either for viewing or writing.
> >
> > Proposal: Leave a "user supplied githubid" field here, with a clear note
> > about how it gets populated.  Some new committers may not have tied them
> > together yet, and will be curious.
> >
> > Also have a "GitBox Registered GH ID" field or the like, which is
> > read-only and just pulls whatever gitbox tells us, and if you click on
> > it, takes you to the gitbox login or register screen.
> >
> > If we just delete it completely from whimsy, some committers will wonder
> > where it went.
>
> Indeed, and that may result in more confusion and complaints than is
> currently seen by Infra.
>
> > Does that make sense?
>
> OK by me.
>
> >
> > --
> > - Shane
> >Whimsy PMC
> >The Apache Software Foundation
> >

Re: Please remove the GitHub ID field from the whimsy roster

[sebb]

On Tue, 19 Sept 2023 at 13:11, Shane Curcuru  wrote:
>
> sebb wrote on 9/18/23 6:17 PM:
> > On Mon, 18 Sept 2023 at 20:18, Daniel Gruno  wrote:
> >>
> >> Hi, whimsy folks,
> >> Could you please remove the GitHub ID field from the whimsy roster service?
> >> The field is not canonical/authoritative, and mostly just serves to 
> >> confuse new committers these days. The only authoritative place for GitHub 
> >> IDs is through https://gitbox.apache.org/boxer/
>
> If this is causing problems for Infra, we absolutely need to at least
> clearly annotate the field, and provide a link to gitbox, to ensure
> users don't keep asking questions in the wrong place.

I would be interested to know how many of the Ids in Whimsy differ
from the ones tied to ASF accounts?

> > The GitHub ids in Whimsy are provided by their owners, so can be
> > considered authoritative, even if they might not be the ones that are
> > linked to ASF accounts.
> > I am told that people find them useful.
> >
> > Maybe a solution would be to add a note that the id might not be the
> > one that is linked to the ASF id.
> > Even better would be if the boxer system could validate which GH Id is
> > being used for linking?
>
> Having GitHub ID in whimsy is useful, because many committers know it as
> a place to find information about accounts.  However, we should
> deprecate/document any fields that have specific ties to other systems,
> especially which ones are authoritative either for viewing or writing.
>
> Proposal: Leave a "user supplied githubid" field here, with a clear note
> about how it gets populated.  Some new committers may not have tied them
> together yet, and will be curious.
>
> Also have a "GitBox Registered GH ID" field or the like, which is
> read-only and just pulls whatever gitbox tells us, and if you click on
> it, takes you to the gitbox login or register screen.
>
> If we just delete it completely from whimsy, some committers will wonder
> where it went.

Indeed, and that may result in more confusion and complaints than is
currently seen by Infra.

> Does that make sense?

OK by me.

>
> --
> - Shane
>Whimsy PMC
>The Apache Software Foundation
>

Re: Please remove the GitHub ID field from the whimsy roster

[sebb]

On Mon, 18 Sept 2023 at 20:18, Daniel Gruno  wrote:
>
> Hi, whimsy folks,
> Could you please remove the GitHub ID field from the whimsy roster service?
> The field is not canonical/authoritative, and mostly just serves to confuse 
> new committers these days. The only authoritative place for GitHub IDs is 
> through https://gitbox.apache.org/boxer/

The GitHub ids in Whimsy are provided by their owners, so can be
considered authoritative, even if they might not be the ones that are
linked to ASF accounts.
I am told that people find them useful.

Maybe a solution would be to add a note that the id might not be the
one that is linked to the ASF id.
Even better would be if the boxer system could validate which GH Id is
being used for linking?

> With regards,
> Daniel.

[jira] [Commented] (WHIMSY-404) Can't post project report.

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753937#comment-17753937
 ] 

Sebb commented on WHIMSY-404:
-

It only exists as a command-line tool at present; it cannot be plugged into 
Whimsy without further work.

The manual process is:
- checkout the relevant agenda
- run the tool (requires Ruby)
- check the changes
- replace the agenda with the fixed version
- commit the changes

> Can't post project report.
> --
>
> Key: WHIMSY-404
> URL: https://issues.apache.org/jira/browse/WHIMSY-404
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: James Bognar
>Priority: Major
>
> Trying to save project report gives this error message:
> Exception
> #
> Here's the report we're trying to submit.
> https://whimsy.apache.org/board/agenda/2023-08-16/Juneau



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (WHIMSY-405) Probably user error, not bug, but I'm not certain...

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-405.
-
Resolution: Fixed

> Probably user error, not bug, but I'm not certain...
> 
>
> Key: WHIMSY-405
> URL: https://issues.apache.org/jira/browse/WHIMSY-405
> Project: Whimsy
>  Issue Type: Wish
>  Components: Website
> Environment: Trying from Windows 10 64-bit, using Firefox 116.0.2 
> (32-bit)
>Reporter: Joseph Kessselman
>Priority: Trivial
>
> I've just been re-added to the Xalan PMC, as jkess...@apache.org.
> I've been trying to access Whimsy to determine what my current permissions 
> are and to confirm that I do appear on that PMC list. Which a PMC member 
> should be able to do, right?
> But my id.apache credentials don't seem to be sufficient to log into Whimsy.
> If someone could check that I *should* have access, and figure out why I 
> don't, that would be greatly appreciated. Or tell me what bit of stupidity 
> I'm probably committing; I won't be at all surprised if the problem is one 
> loose nut behind the keyboard.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-405) Probably user error, not bug, but I'm not certain...

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753475#comment-17753475
 ] 

Sebb commented on WHIMSY-405:
-

https://issues.apache.org/jira/browse/INFRA-24887

> Probably user error, not bug, but I'm not certain...
> 
>
> Key: WHIMSY-405
> URL: https://issues.apache.org/jira/browse/WHIMSY-405
> Project: Whimsy
>  Issue Type: Wish
>  Components: Website
> Environment: Trying from Windows 10 64-bit, using Firefox 116.0.2 
> (32-bit)
>Reporter: Joseph Kessselman
>Priority: Trivial
>
> I've just been re-added to the Xalan PMC, as jkess...@apache.org.
> I've been trying to access Whimsy to determine what my current permissions 
> are and to confirm that I do appear on that PMC list. Which a PMC member 
> should be able to do, right?
> But my id.apache credentials don't seem to be sufficient to log into Whimsy.
> If someone could check that I *should* have access, and figure out why I 
> don't, that would be greatly appreciated. Or tell me what bit of stupidity 
> I'm probably committing; I won't be at all surprised if the problem is one 
> loose nut behind the keyboard.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-405) Probably user error, not bug, but I'm not certain...

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753474#comment-17753474
 ] 

Sebb commented on WHIMSY-405:
-

I've just checked, and access to much of Whimsy requires committer membership.

It looks like your id has not been set up. I will raise an INFRA issue.

> Probably user error, not bug, but I'm not certain...
> 
>
> Key: WHIMSY-405
> URL: https://issues.apache.org/jira/browse/WHIMSY-405
> Project: Whimsy
>  Issue Type: Wish
>  Components: Website
> Environment: Trying from Windows 10 64-bit, using Firefox 116.0.2 
> (32-bit)
>Reporter: Joseph Kessselman
>Priority: Trivial
>
> I've just been re-added to the Xalan PMC, as jkess...@apache.org.
> I've been trying to access Whimsy to determine what my current permissions 
> are and to confirm that I do appear on that PMC list. Which a PMC member 
> should be able to do, right?
> But my id.apache credentials don't seem to be sufficient to log into Whimsy.
> If someone could check that I *should* have access, and figure out why I 
> don't, that would be greatly appreciated. Or tell me what bit of stupidity 
> I'm probably committing; I won't be at all surprised if the problem is one 
> loose nut behind the keyboard.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-405) Probably user error, not bug, but I'm not certain...

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753473#comment-17753473
 ] 

Sebb commented on WHIMSY-405:
-

Can you login to lists.apache.org using the same credentials?

What URL were you using to access Whimsy? Some parts require additional 
permissions.
But you should be able to login to

https://whimsy.apache.org/roster/committer/__self__

> Probably user error, not bug, but I'm not certain...
> 
>
> Key: WHIMSY-405
> URL: https://issues.apache.org/jira/browse/WHIMSY-405
> Project: Whimsy
>  Issue Type: Wish
>  Components: Website
> Environment: Trying from Windows 10 64-bit, using Firefox 116.0.2 
> (32-bit)
>Reporter: Joseph Kessselman
>Priority: Trivial
>
> I've just been re-added to the Xalan PMC, as jkess...@apache.org.
> I've been trying to access Whimsy to determine what my current permissions 
> are and to confirm that I do appear on that PMC list. Which a PMC member 
> should be able to do, right?
> But my id.apache credentials don't seem to be sufficient to log into Whimsy.
> If someone could check that I *should* have access, and figure out why I 
> don't, that would be greatly appreciated. Or tell me what bit of stupidity 
> I'm probably committing; I won't be at all surprised if the problem is one 
> loose nut behind the keyboard.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (WHIMSY-404) Can't post project report.

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-404.
-
Resolution: Implemented

> Can't post project report.
> --
>
> Key: WHIMSY-404
> URL: https://issues.apache.org/jira/browse/WHIMSY-404
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: James Bognar
>Priority: Major
>
> Trying to save project report gives this error message:
> Exception
> #
> Here's the report we're trying to submit.
> https://whimsy.apache.org/board/agenda/2023-08-16/Juneau



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-404) Can't post project report.

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753366#comment-17753366
 ] 

Sebb commented on WHIMSY-404:
-

I've created a library routine and CLI tool which is able to repair the broken 
agenda file from r113354.

This leaves the file in a state that can be modified and committed without an 
error.

However, it does not look to be at all easy to include it in the agenda 
work-flow.
For example, currently only individual report bodies can be edited, but the 
errors may occur in the headers.

Given that broken files are very rare, I don't propose to update the agenda 
tool.
The file repair code is in a separate library module, so can easily be invoked 
from the agenda if it is decided to integrate it into app at a later point.


> Can't post project report.
> --
>
> Key: WHIMSY-404
> URL: https://issues.apache.org/jira/browse/WHIMSY-404
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: James Bognar
>Priority: Major
>
> Trying to save project report gives this error message:
> Exception
> #
> Here's the report we're trying to submit.
> https://whimsy.apache.org/board/agenda/2023-08-16/Juneau



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-404) Can't post project report.

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752194#comment-17752194
 ] 

Sebb commented on WHIMSY-404:
-

The most recent case was caused by the use of characters encoded in a scheme 
other than UTF-8.
They were correct in their encoding, but not in UTF-8.

As such, the characters needed replacement not deletion.

Given that this hardly every occurs, I am not sure that it is worth the effort 
of doing anything other than replacing the bad characters with the relevant 
marker and flagging up that the agenda needs to be corrected at some point.
It is easy enough to search for this character in the source, and usually the 
correct replacement will be obvious (all of the recent issues were caused by 
accents in names, apart from one spurious symbol).

There is no way of knowing for sure what the original encoding of each 
character was, so in general it is not possible to automate replacement. Indeed 
if several edits are made outside Whimsy, multiple encodings may be involved. 
If this was a frequent occurrence it might be worth trying to develop some 
heuristics to automate the process, but I suspect that would be quite a lot of 
effort, and not guaranteed to work.

Also note that the Whimsy agenda app is slated to be retired at some point, so 
non-essential work on it is likely to be wasted effort.

I think the minimum that needs to be done is to replace invalid characters with 
the standard unknown character marker - � - so that edits no longer cause a 
crash.

It would be sensible to provide some sort of notification that this has been 
necessary so the necessary manual correction(s) can be made at some point.

> Can't post project report.
> --
>
> Key: WHIMSY-404
> URL: https://issues.apache.org/jira/browse/WHIMSY-404
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: James Bognar
>Priority: Major
>
> Trying to save project report gives this error message:
> Exception
> #
> Here's the report we're trying to submit.
> https://whimsy.apache.org/board/agenda/2023-08-16/Juneau



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-404) Can't post project report.

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751814#comment-17751814
 ] 

Sebb commented on WHIMSY-404:
-

Seems to me it would be better to replace any errant characters with the 
standard unknown character marker:
https://www.fileformat.info/info/unicode/char/fffd/index.htm

Also, it would be helpful to provide feedback that the file contains one or 
more such characters, so these can be found and fixed.

Note that the file may be updated outside Whimsy.

> Can't post project report.
> --
>
> Key: WHIMSY-404
> URL: https://issues.apache.org/jira/browse/WHIMSY-404
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: James Bognar
>Priority: Major
>
> Trying to save project report gives this error message:
> Exception
> #
> Here's the report we're trying to submit.
> https://whimsy.apache.org/board/agenda/2023-08-16/Juneau



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-404) Can't post project report.

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751342#comment-17751342
 ] 

Sebb commented on WHIMSY-404:
-

This was caused by a commit that added a character which was not in UTF-8.

The agenda has been adjusted to replace the invalid characters, and commits 
appear to be working again.

 

It's not clear if the erroneous commit was originated by Whimsy or externally, 
but ideally Whimsy should not fail if the problem recurs.

> Can't post project report.
> --
>
> Key: WHIMSY-404
> URL: https://issues.apache.org/jira/browse/WHIMSY-404
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: James Bognar
>Priority: Major
>
> Trying to save project report gives this error message:
> Exception
> #
> Here's the report we're trying to submit.
> https://whimsy.apache.org/board/agenda/2023-08-16/Juneau



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Unable to submit Libcloud August 2023 board report

[sebb]

On Thu, 3 Aug 2023 at 22:42, Craig Russell  wrote:
>
> I am also unable to file a board report. The error I get is
> Exception
> #
>
> Any ideas?

Looks like there are some characters in the file that are not valid UTF-8.

AFAICT the problem started with r113340, see:
https://lists.apache.org/thread/h6gc90tw2wqto0zp9vt69ft02g3y3g9r
Search for 7:59; the next character does not display correctly so is
probably the culprit.

There were other bad chars in later commits, which I think I have fixed.

> > Begin forwarded message:
> >
> > From: Tomaz Muraus 
> > Subject: Re: Unable to submit Libcloud August 2023 board report
> > Date: August 3, 2023 at 14:21:25 PDT
> > To: bo...@apache.org
> > Cc: Tomaž Muraus 
> > Reply-To: bo...@apache.org
> >
> > I see the board agenda file is now present in the svn repo
> > (board_agenda_2023_08_16.txt), but I still receive the same error when
> > trying to submit the report using Reporter tool.
> >
> > I sent report via email to bo...@apache.org and I will also manually
> > add it to the agenda file in the svn repo.
> >
> > Regards,
> > Tomaz
> >
> > On Tue, Aug 1, 2023 at 12:01 PM Tomaz Muraus  wrote:
> >>
> >> Dear board,
> >>
> >> I missed Libcloud board report during the last 2 reporting cycles so I
> >> want to post August report a bit early in case there will be any
> >> comments, etc.
> >>
> >> I wanted to post it via board report tool
> >> (https://reporter.apache.org/wizard/?libcloud), but I received the
> >> following error:
> >>
> >>> Something went wrong, and we couldn't publish your report.
> >> Please check with the Whimsy tool to see if there is already a report 
> >> posted!
> >>
> >> I couldn't find existing report in the board agenda file. In fact, I
> >> couldn't find board agenda file for August 2023 at all.
> >>
> >> I imagine the issue is likely related to board agenda file for August
> >> 2023 not yet existing.
> >>
> >> How should I go about posting Apache Libcloud August 2023 report?
> >> Should I want until the board agenda file is created or should I email
> >> the report directly to board@ as soon as possible?
> >>
> >> Thanks,
> >> Tomaz
>
> Craig L Russell
> c...@apache.org
>

Re: CoI affirmations is missing VP, Public Affairs

[sebb]

I don't see the 'VP' bit, but I do see 'Public Affairs' in the listing.

Sebb

On Tue, 25 Jul 2023 at 04:22, Craig Russell  wrote:
>
> I don't know exactly how to fix this but it needs to be done.
>
> https://whimsy.apache.org/officers/coi.cgi
>
>
> Craig L Russell
> c...@apache.org
>

Re: problem with committer editor

[sebb]

Looks like the code does not like it when Avail ID is at the end of the entry.

Could you please try moving it nearer the top?

This will help with solving the issue.

Thanks.

Sebb

On Mon, 24 Jul 2023 at 12:57, Claude Warren  wrote:
>
> Greetings,
>
> I am attempting to edit the "members text" portion of my committer info [1]
> but am having no luck.
> If I double click on the "Members txt" line and then click on the "submit"
> button (no edits) I get the following error:
>
> {noformat}
>
> {
>   "exception": "#",
>   "backtrace": [
> "/x1/srv/whimsy/www/roster/views/actions/memtext.json.rb:5:in
> `_evaluate'",
> "/x1/srv/whimsy/www/roster/main.rb:260:in `block in '",
> "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:226:in `call'",
> "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:52:in `call'",
> "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:203:in `call'",
> "/x1/srv/whimsy/lib/whimsy/asf/rack.rb:257:in `call'",
>
> "/var/lib/gems/2.7.0/gems/passenger-6.0.17/src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:107:in
> `process_request'",
>
> "/var/lib/gems/2.7.0/gems/passenger-6.0.17/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:157:in
> `accept_and_process_next_request'",
>
> "/var/lib/gems/2.7.0/gems/passenger-6.0.17/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:110:in
> `main_loop'",
>
> "/var/lib/gems/2.7.0/gems/passenger-6.0.17/src/ruby_supportlib/phusion_passenger/request_handler.rb:419:in
> `block (3 levels) in start_threads'",
>
> "/var/lib/gems/2.7.0/gems/passenger-6.0.17/src/ruby_supportlib/phusion_passenger/utils.rb:113:in
> `block in create_thread_and_abort_on_exception'"
>   ]
> }
>
> {noformat}
>
> needless to say, this is the same error I get if I attempt to change the
> text.
>
> Any assistance would be appreciated,
> Claude
>
> [1] https://whimsy.apache.org/roster/committer/claude
>
> --
> LinkedIn: http://www.linkedin.com/in/claudewarren

[jira] [Resolved] (WHIMSY-399) Board agenda minutes should handle PMC name changes better

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-399.
-
Resolution: Fixed

Seems to have worked.

> Board agenda minutes should handle PMC name changes better
> --
>
> Key: WHIMSY-399
> URL: https://issues.apache.org/jira/browse/WHIMSY-399
> Project: Whimsy
>  Issue Type: Improvement
>  Components: Website
>Reporter: Shane Curcuru
>Priority: Minor
>
> Sometimes PMCs change their name.  The board/minutes feature should better 
> tie together past minutes for PMCs when names change.
> Example: Isis changed it's name to Causeway, but minutes are a little mixed 
> (if still findable):
> [https://whimsy.apache.org/board/minutes/Causeway.html]
> https://whimsy.apache.org/board/minutes/Isis.html



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (WHIMSY-399) Board agenda minutes should handle PMC name changes better

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743190#comment-17743190
 ] 

Sebb edited comment on WHIMSY-399 at 7/14/23 2:49 PM:
--

Should be fixed in the next run of the script - there was a typo in the rename 
section of the parser.


was (Author: s...@apache.org):
Should be fixed now - there was a typo in the rename section of the parser.

> Board agenda minutes should handle PMC name changes better
> --
>
> Key: WHIMSY-399
> URL: https://issues.apache.org/jira/browse/WHIMSY-399
> Project: Whimsy
>  Issue Type: Improvement
>  Components: Website
>Reporter: Shane Curcuru
>Priority: Minor
>
> Sometimes PMCs change their name.  The board/minutes feature should better 
> tie together past minutes for PMCs when names change.
> Example: Isis changed it's name to Causeway, but minutes are a little mixed 
> (if still findable):
> [https://whimsy.apache.org/board/minutes/Causeway.html]
> https://whimsy.apache.org/board/minutes/Isis.html



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-399) Board agenda minutes should handle PMC name changes better

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743190#comment-17743190
 ] 

Sebb commented on WHIMSY-399:
-

Should be fixed now - there was a typo in the rename section of the parser.

> Board agenda minutes should handle PMC name changes better
> --
>
> Key: WHIMSY-399
> URL: https://issues.apache.org/jira/browse/WHIMSY-399
> Project: Whimsy
>  Issue Type: Improvement
>  Components: Website
>Reporter: Shane Curcuru
>Priority: Minor
>
> Sometimes PMCs change their name.  The board/minutes feature should better 
> tie together past minutes for PMCs when names change.
> Example: Isis changed it's name to Causeway, but minutes are a little mixed 
> (if still findable):
> [https://whimsy.apache.org/board/minutes/Causeway.html]
> https://whimsy.apache.org/board/minutes/Isis.html



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-401) Board agenda tool comments

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736700#comment-17736700
 ] 

Sebb commented on WHIMSY-401:
-

Any decisions on additional agenda functionality also need to be forwarded to 
the Infra team working on the agenda replacement.

> Board agenda tool comments
> --
>
> Key: WHIMSY-401
> URL: https://issues.apache.org/jira/browse/WHIMSY-401
> Project: Whimsy
>  Issue Type: Task
>  Components: BoardAgenda
>Reporter: Craig L Russell
>Priority: Major
>
> The agenda tool allows users to add comments to the agenda which are saved in 
> the agenda and are subsequently sent to the project PMC private list. The 
> comments are durable in the agenda and can be viewed in subsequent agendas.
> The agenda tool should allow comments to be divided into multiple categories, 
> depending on the intended audience:
> feedback: congratulations, nice report, healthy community
> discussion: notes for other Directors about the project that might lead to 
> future action
> request: information is needed from the project, possibly to clarify an item 
> in the report
> action: the project is requested to perform some corrective action
> Additionally, a Director might want to flag the report for the upcoming board 
> meeting
> Proposal:
> 1. Update the comment pop-up dialog to add a drop-down called *Category* to 
> select one of four categories:
> [ ] feedback
> [X] discuss is default
> [ ] request
> [ ] action
> Text entered as "feedback" will be sent unmodified to the PMC private list. 
> It will be stored in the agenda unmodified.
> Text entered as "discuss" will not be sent to the PMC private list. It will 
> be stored in the agenda with a prefix of [discuss]
> Text entered as "request" will be sent to the PMC with a prefix "Please reply 
> to this request" and will be stored in the agenda with a prefix of [request]
> Text entered as "action" will be sent to the PMC with a prefix "Please take 
> the requested action" and will be stored in the agenda with a prefix of 
> [action] 
> 2. The field "Initials" will be changed to "From"
> 3. Directors will be able to edit current comments by clicking on the author 
> of a current comment, regardless of the author. This will bring up a comment 
> pop-up allowing editing of any of the fields, e.g. to change the "From" from 
> "clr" to "board"; or to change the Category; or to update the text of the 
> comment.
> The action boxes at the bottom of the pop-up will additionally allow [Delete 
> Comment] as an option (in addition to [Cancel] and [Save])



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-401) Board agenda tool comments

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736678#comment-17736678
 ] 

Sebb commented on WHIMSY-401:
-

Given that Infra are taking over the agenda tool, it seems pointless making any 
further changes to the soon to be obsolete Whimsy version.

> Board agenda tool comments
> --
>
> Key: WHIMSY-401
> URL: https://issues.apache.org/jira/browse/WHIMSY-401
> Project: Whimsy
>  Issue Type: Task
>  Components: BoardAgenda
>Reporter: Craig L Russell
>Priority: Major
>
> The agenda tool allows users to add comments to the agenda which are saved in 
> the agenda and are subsequently sent to the project PMC private list. The 
> comments are durable in the agenda and can be viewed in subsequent agendas.
> The agenda tool should allow comments to be divided into multiple categories, 
> depending on the intended audience:
> feedback: congratulations, nice report, healthy community
> discussion: notes for other Directors about the project that might lead to 
> future action
> request: information is needed from the project, possibly to clarify an item 
> in the report
> action: the project is requested to perform some corrective action
> Additionally, a Director might want to flag the report for the upcoming board 
> meeting
> Proposal:
> 1. Update the comment pop-up dialog to add a drop-down called *Category* to 
> select one of four categories:
> [ ] feedback
> [X] discuss is default
> [ ] request
> [ ] action
> Text entered as "feedback" will be sent unmodified to the PMC private list. 
> It will be stored in the agenda unmodified.
> Text entered as "discuss" will not be sent to the PMC private list. It will 
> be stored in the agenda with a prefix of [discuss]
> Text entered as "request" will be sent to the PMC with a prefix "Please reply 
> to this request" and will be stored in the agenda with a prefix of [request]
> Text entered as "action" will be sent to the PMC with a prefix "Please take 
> the requested action" and will be stored in the agenda with a prefix of 
> [action] 
> 2. The field "Initials" will be changed to "From"
> 3. Directors will be able to edit current comments by clicking on the author 
> of a current comment, regardless of the author. This will bring up a comment 
> pop-up allowing editing of any of the fields, e.g. to change the "From" from 
> "clr" to "board"; or to change the Category; or to update the text of the 
> comment.
> The action boxes at the bottom of the pop-up will additionally allow [Delete 
> Comment] as an option (in addition to [Cancel] and [Save])



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [401] Not Authorized - help with: Trying to access whimsy.apache.org/board/agenda/ but no luck. Any suggestions?

[sebb]

You can check your permissions here:

https://whimsy.apache.org/committers/testauth.cgi

What does this show?

I notice that your email address (as used in this post) is not listed
on your LDAP record.
If you visit https://whimsy.apache.org/roster/committer/__self__ it
can be added by double-clicking on the "Email addresses (alt)' field.

AFAIK this won't affect access to the Agenda, but it will allow you to
post to most ASF mailing lists without needing to subscribe or be
moderated.

Sebb

On Wed, 17 May 2023 at 22:55, Radcliffe, Mark
 wrote:
>
>
>
>
> The information contained in this email may be confidential and/or legally 
> privileged. It has been sent for the sole use of the intended recipient(s). 
> If the reader of this message is not an intended recipient, you are hereby 
> notified that any unauthorized review, use, disclosure, dissemination, 
> distribution, or copying of this communication, or any of its contents, is 
> strictly prohibited. If you have received this communication in error, please 
> reply to the sender and destroy all copies of the message. To contact us 
> directly, send to postmas...@dlapiper.com. Thank you.

Re: Promote committer to new PMC member

[sebb]

On Tue, 25 Apr 2023 at 12:24, Shane Curcuru  wrote:
>
> Craig Russell wrote on 4/24/23 8:08 PM:
> > I did a bad job at designing the update to the whimsy/roster tool to add 
> > new PMC member.
> >
> > When I got to actually looking at the User Interface, I was surprised to 
> > see that the process is not fit for purpose and would need to be redesigned.
> >
> > What I found was that the tool is organized to be able to process multiple 
> > committers at a time, or multiple PMC members at a time. Not only have I 
> > never seen multiple actions occur, but the pop-up doesn't allow for 
> > multiple links to VOTEs. So we need another pop-up with just one name on it.
>
> Instead of trying to shoehorn new change actions into the existing set
> of tables, why not make this action be explicit with a separate button
> or the like that then gives the user an edit/listbox to enter a single
> name for the newly proposed PMC member?
>
> Then the user can either select a name of an existing committer on that
> project from the list, or can type in a new availid of an existing
> committer (anywhere) to add them?
>
> If we think about UI design overall, having change actions - especially
> add/delete actions - be explicit buttons/separate links/whatever that
> are *not* just part of a giant list (with lots of data), that makes it
> much clearer to the user that they're modifying data, not just viewing.
>
> I've never quite liked the fact that we don't have a solid UI design
> pattern for whimsy tools, especially ones that modify data.
>
> Does that make sense?

I agree it might be simpler to have separate buttons to make changes.
However the existing GUI will have to be modified to drop the existing
PMC change functions (otherwise the new code can be bypassed).

And for consistency the GUIs that deal with podlings and non-PMCs etc
should also be changed.

That's a lot of work.
Maybe that should be considered for a separate enhancement.

> --
> - Shane
>Whimsy PMC
>The Apache Software Foundation
>

Re: Promote committer to new PMC member

[sebb]

On Tue, 25 Apr 2023 at 01:08, Craig Russell  wrote:
>
> I did a bad job at designing the update to the whimsy/roster tool to add new 
> PMC member.
>
> When I got to actually looking at the User Interface, I was surprised to see 
> that the process is not fit for purpose and would need to be redesigned.
>
> What I found was that the tool is organized to be able to process multiple 
> committers at a time, or multiple PMC members at a time. Not only have I 
> never seen multiple actions occur, but the pop-up doesn't allow for multiple 
> links to VOTEs. So we need another pop-up with just one name on it.
>
> And, it was pretty tough to figure out, just looking at the PMC list with all 
> the PMC members followed by all the committers, that the idea is to tick the 
> box next to the committer and go back to the top of the screen to (ADD) 
> (MODIFY).
>
> So my design decision is to add a box to the committer line which will bring 
> up the pop-up with the link to lists.apache.org and votelink.

Remember that people can be added to the PMC without being promoted
from committer.
e.g. the person is already a committer elsewhere, or the PMC treats
has committers === PMC.

It might be better to just disable PMC promotion if more than one
person is selected.

> I'll still need help with the details but I'm going to start over with the 
> implementation.
>
> Thanks,
> Craig
>
> Craig L Russell
> c...@apache.org
>

Re: I need some help with tooling

[sebb]

I suggest you create a branch for your changes so they can be tested separately.

On Sun, 23 Apr 2023 at 18:50, Craig Russell  wrote:
>
> I'm going to update the PMC policy page and would like to update the whimsy 
> tool at the same time.
>
> The current roster/pmc tool updates the committee-info.txt file via svn but 
> does not notify anyone except (indirectly via svn) listeners of 
> committers-cvs.
>
> Additionally, the tool will need to add a text field where the user can enter 
> the lists.apache.org permanent link to the [VOTE] or other discussion on the 
> private list where the PMC candidate was approved. There should also be a 
> link to lists.apache.org (private list last 6 months) so the user can choose 
> the correct link. When clicked, the link should open in a tab.
>
> Once the discussion link has been entered, the tool will perform the svn 
> update and the tool will send a [NOTICE] email to board with the new PMC 
> member information including the link to lists.apache.org.
>
> Once this is working I will update the policy.
>
> I'll take a look at the existing code and will probably need some help with 
> the changes.
>
> Thanks,
> Craig
>
> Craig L Russell
> c...@apache.org
>

Are the package.json files still needed?

[sebb]

They seem to be rather out of date if they are in use:

https://raw.githubusercontent.com/apache/whimsy/master/www/roster/package.json
links to non-existent whimsy repo in SVN

and

https://raw.githubusercontent.com/apache/whimsy/master/www/board/agenda/package.json
links to a non-existent Git repo

Sebb

[jira] [Resolved] (WHIMSY-400) Whimsy DOAP file has a parsing error

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-400.
-
Resolution: Fixed

Thanks, should be fixed now.

BTW, how was the issue noticed?

> Whimsy DOAP file has a parsing error
> 
>
> Key: WHIMSY-400
> URL: https://issues.apache.org/jira/browse/WHIMSY-400
> Project: Whimsy
>  Issue Type: Bug
>  Components: PublicData
>Reporter: Claude Warren
>Priority: Minor
>
> The DOAP file [1] as listed in [2] has the error:
>  [line: 43, col: 22] \{E201} Multiple children of property element
> [1] 
> https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob_plain;f=doap_Whimsy.rdf;hb=HEAD
> [2] 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Unable to remove one of Email addresses (other)

[sebb]

On Fri, 31 Mar 2023 at 12:42, Mikhail Khludnev  wrote:
>
> Thanks. It makes sense.
> Is it worth sending a new signed ICLA form scan?

What problem are you trying to solve?

The email address is not stored in LDAP, and is not generally visible.

> On Fri, Mar 31, 2023 at 10:50 AM sebb  wrote:
>
> > Whimsy 'other' email includes the email from the ICLA (and I think it
> > includes emails from members.txt for ASF members).
> >
> > The ICLA email cannot be changed except by providing another ICLA.
> > However, whether it should be shown is another matter.
> >
> > On Fri, 31 Mar 2023 at 08:25, Mikhail Khludnev  wrote:
> > >
> > > Hello Shane.
> > > Thanks for your answer.
> > > That's actually what I expected, but the crux is that whimsy displays
> > email
> > > absent in id.a.o.
> > > Here's how it looks like Obsolete email – Telegraph
> > > <https://telegra.ph/Obsolete-email-03-31> <-pics
> > >
> > > Regards.
> > >
> > >
> > > On Thu, Mar 30, 2023 at 11:41 PM Shane Curcuru 
> > wrote:
> > > >
> > > > Mikhail Khludnev wrote on 3/30/23 3:26 PM:
> > > > > Hello,
> > > > > I beg your pardon, if I ask in the wrong place.
> > > > > I noticed wrong oudated @.com email in Email addresses (other) at
> > > > > https://whimsy.apache.org/roster/committer/
> > > > > This field is not green - I can't edit it.
> > > > > My id.apache.org profile is editable and right - has no that email.
> > > > > How to remove outdated (other) email?
> > > >
> > > > When editing your Apache ID data fields, the best place to use is the
> > > > Infra team supported ID service here:
> > > >
> > > >https://id.apache.org/
> > > >
> > > > Whimsy merely displays the data stored in various other ASF systems in
> > a
> > > > convenient way, but changing email addresses or other items in your ID
> > > > is best done with the ID tool above.
> > > >
> > > > Let us know if that doesn't work!
> > > >
> > > > --
> > > > - Shane
> > > >Whimsy PMC
> > > >The Apache Software Foundation
> > > >
> > >
> > >
> > > --
> > > Sincerely yours
> > > Mikhail Khludnev
> > > https://t.me/MUST_SEARCH
> > > A caveat: Cyrillic!
> >
>
>
> --
> Sincerely yours
> Mikhail Khludnev
> https://t.me/MUST_SEARCH
> A caveat: Cyrillic!

Re: Unable to remove one of Email addresses (other)

[sebb]

Whimsy 'other' email includes the email from the ICLA (and I think it
includes emails from members.txt for ASF members).

The ICLA email cannot be changed except by providing another ICLA.
However, whether it should be shown is another matter.

On Fri, 31 Mar 2023 at 08:25, Mikhail Khludnev  wrote:
>
> Hello Shane.
> Thanks for your answer.
> That's actually what I expected, but the crux is that whimsy displays email
> absent in id.a.o.
> Here's how it looks like Obsolete email – Telegraph
>  <-pics
>
> Regards.
>
>
> On Thu, Mar 30, 2023 at 11:41 PM Shane Curcuru  wrote:
> >
> > Mikhail Khludnev wrote on 3/30/23 3:26 PM:
> > > Hello,
> > > I beg your pardon, if I ask in the wrong place.
> > > I noticed wrong oudated @.com email in Email addresses (other) at
> > > https://whimsy.apache.org/roster/committer/
> > > This field is not green - I can't edit it.
> > > My id.apache.org profile is editable and right - has no that email.
> > > How to remove outdated (other) email?
> >
> > When editing your Apache ID data fields, the best place to use is the
> > Infra team supported ID service here:
> >
> >https://id.apache.org/
> >
> > Whimsy merely displays the data stored in various other ASF systems in a
> > convenient way, but changing email addresses or other items in your ID
> > is best done with the ID tool above.
> >
> > Let us know if that doesn't work!
> >
> > --
> > - Shane
> >Whimsy PMC
> >The Apache Software Foundation
> >
>
>
> --
> Sincerely yours
> Mikhail Khludnev
> https://t.me/MUST_SEARCH
> A caveat: Cyrillic!

[jira] [Commented] (WHIMSY-398) Editing my Whimsy members.txt messed up my data

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703410#comment-17703410
 ] 

Sebb commented on WHIMSY-398:
-

As I wrote, Whimsy should probably check that the required elements are still 
present before updating the file.
AFAIK this is the first time this problem has occurred, and given that the file 
is in SVN, reverting is easy. So it's not a high priority.

Note that the fields are not generally stored in LDAP.
Obviously AvailId is stored in LDAP, but as it used as the key, it must appear 
in all instances of related data.

> Editing my Whimsy members.txt messed up my data
> ---
>
> Key: WHIMSY-398
> URL: https://issues.apache.org/jira/browse/WHIMSY-398
> Project: Whimsy
>  Issue Type: Bug
>  Components: Roster
> Environment: Firefox 107.0 on Fedora
>Reporter: Ken Coar
>Priority: Major
>
> I just used [https://whimsy.apache.org/roster/committer/coar] to edit my 
> '{{{}Members.txt{}}}' entry, and now it appears to be gone.  As does my 
> 'forms on file' and 'member status' fields, possibly among others.
> I _did_ remove some of the textual information that appeared to be duplicated 
> in the other fields on the page (like PMC membership,  '{{{}Avail ID{}}}', 
> {_}{_}), but AFAIK i didn't delete the entire {{Members.txt}} form field 
> *content* before clicking on submit.
> So, hopefully, there's a way to roll this back.  The 
> {{/committers/{_}user{_}}} form appears to be an update-in-place, so I can't 
> use my browser's Back button to move to a version prior to the edit.
> If some of the information that populates the other fields on the form has 
> its authoritative version in the {{members.txt}} entry, it came as a surprise 
> to me..!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-398) Editing my Whimsy members.txt messed up my data

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703405#comment-17703405
 ] 

Sebb commented on WHIMSY-398:
-

Avail ID is used as the key to your entry, so it's not surprising the entry 
disappeared.

Also Forms on File is maintained by the secretary, and should be left alone.

I have restored those fields, and your entry is now visible again.

Whimsy should probably check that the amended entry still has the required 
content.

> Editing my Whimsy members.txt messed up my data
> ---
>
> Key: WHIMSY-398
> URL: https://issues.apache.org/jira/browse/WHIMSY-398
> Project: Whimsy
>  Issue Type: Bug
>  Components: Roster
> Environment: Firefox 107.0 on Fedora
>Reporter: Ken Coar
>Priority: Major
>
> I just used [https://whimsy.apache.org/roster/committer/coar] to edit my 
> '{{{}Members.txt{}}}' entry, and now it appears to be gone.  As does my 
> 'forms on file' and 'member status' fields, possibly among others.
> I _did_ remove some of the textual information that appeared to be duplicated 
> in the other fields on the page (like PMC membership,  '{{{}Avail ID{}}}', 
> {_}{_}), but AFAIK i didn't delete the entire {{Members.txt}} form field 
> *content* before clicking on submit.
> So, hopefully, there's a way to roll this back.  The 
> {{/committers/{_}user{_}}} form appears to be an update-in-place, so I can't 
> use my browser's Back button to move to a version prior to the edit.
> If some of the information that populates the other fields on the form has 
> its authoritative version in the {{members.txt}} entry, it came as a surprise 
> to me..!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-397) ML Subscription Helper improvement

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703397#comment-17703397
 ] 

Sebb commented on WHIMSY-397:
-

The subscribe drop-down is not currently filtered to remove existing 
subscriptions; perhaps it should be.

Note also that subscriptions are not updated immediately; they are updated 
every few hours.

> ML Subscription Helper improvement
> --
>
> Key: WHIMSY-397
> URL: https://issues.apache.org/jira/browse/WHIMSY-397
> Project: Whimsy
>  Issue Type: Improvement
>  Components: Mail, Website
>Reporter: Ken Coar
>Priority: Trivial
>
> Currently the mailing list subscription helper at 
> [https://whimsy.apache.org/committers/subscribe.cgi] is a most excellent 
> tool.  I have a suggestion for possible improvement:
> Adjust the pulldown of lists to which one can subscribe to *omit* the ones to 
> which the given eddress is _already_ subscribed.
> It's possible this is already the case, and it looked otherwise because the 
> list-of-lists wasn't refreshed after subscription requests were submitted.
> Thanks!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Error in secretary workbench

[sebb]

Not a Whimsy bug.

The workbench get the list of potential members from the
memapp-received.txt file in the meetings directory.
Not sure who or what is suppose to pre-populate that, but at present
it is an empty template.

Sebb

On Fri, 10 Mar 2023 at 01:04, sebb  wrote:
>
> Just noticed that as well. Will try to look into it tomorrow if no-one
> else gets there first
>
> On Fri, 10 Mar 2023 at 00:52, Craig Russell  wrote:
> >
> > Membership application form is unusable. The field for Public Name cannot 
> > be filled and the form cannot be filed.
> >
> > Craig L Russell
> > c...@apache.org
> >

Re: Error in secretary workbench

[sebb]

Just noticed that as well. Will try to look into it tomorrow if no-one
else gets there first

On Fri, 10 Mar 2023 at 00:52, Craig Russell  wrote:
>
> Membership application form is unusable. The field for Public Name cannot be 
> filled and the form cannot be filed.
>
> Craig L Russell
> c...@apache.org
>

[jira] [Resolved] (WHIMSY-396) Shane Caraveo attendance status out of sync

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-396.
-
Resolution: Fixed

Fixed

> Shane Caraveo attendance status out of sync
> ---
>
> Key: WHIMSY-396
> URL: https://issues.apache.org/jira/browse/WHIMSY-396
> Project: Whimsy
>  Issue Type: Task
>  Components: Roster
>Reporter: Ken Coar
>Priority: Minor
> Attachments: 2023-03-04-members_attendance-xcheck.png
>
>
> As of date, the members/attendance-xcheck Web page shows an insynchronicity 
> for Shane Caraveo's attendance status. 
> !2023-03-04-members_attendance-xcheck.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-395) collated minutes specify incorrect VP

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694446#comment-17694446
 ] 

Sebb commented on WHIMSY-395:
-

Well spotted.

The report format has changed several times over the years, and information has 
moved around.
The current approach of using multiple searches means that changes are unlikely 
to be detected, and items are likely to be missed. Indeed that has happened 
with Jakarta EE [1] which is recently mostly reported as missing.

It would be safer to do an initial parse to split the report into individual 
sections and then classify them all. Unexpected sections could then be reported 
and investigated.

This may take a while.

[1] https://whimsy.apache.org/board/minutes/Jakarta_EE_Relations.html

> collated minutes specify incorrect VP
> -
>
> Key: WHIMSY-395
> URL: https://issues.apache.org/jira/browse/WHIMSY-395
> Project: Whimsy
>  Issue Type: Bug
>Reporter: Greg Stein
>Priority: Minor
>
> Take a look at: https://whimsy.apache.org/board/minutes/Infrastructure.html
> The VP has been David Nalley for many years. Yet I see Rob Tompkins, John 
> Kinsella, Chris Mattman ... etc.
> I do not see a cognizable pattern to suggest the root of the error. I have 
> not looked at other collated minutes to see if a similar problem exists.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Update email addresses in whimsy/committer

[sebb]

On Mon, 27 Feb 2023 at 21:30, Craig Russell  wrote:
>
> I see that I can add/update/delete email addresses using id.apache.org:
> Forwarding email address:

That's the LDAP 'mail' attribute.

> Alias addresses:

That's the LDAP 'asf-altEmail' attribute.

>
> In whimsy, there are three categories:
> Email forwarded to:

mail

> Email (alt):

asf-altEmail

> Email (other):

That's asf-committer-email plus the email address from the ICLA.

> It seems that whimsy allows updates to forwarded to and (alt) but not (other).
>
> So:
> What/why is there an (alt) address in whimsy?

I assume it's to allow people to associate other emails with their login.

> Why can whimsy not update email (other)

See above.

> What is (other) used for?

Not entirely sure.

> Thanks,
> Craig
>
> Craig L Russell
> c...@apache.org
>

Re: [Bug] Data Privacy and TAC mailing list names are not up to date

[sebb]

On Sun, 12 Feb 2023 at 11:06, Daniel Gruno  wrote:
>
> Hi folks,
> It appears that the mailing list targets in
> https://whimsy.apache.org/public/committee-info.json are out of date for
> Data Privacy and TAC, and I'm not sure where this gets defined.
>
> For data privacy, their mailing list domain is privacy.apache.org

AFAICT the privacy lists are still privacy*@apache.org

> for TAC, their domain is tac.apache.org
>

That does appear to have changed; will fix the override.

Re: Conversions of uncommon vowels are incorrect: ươễ

[sebb]

On Sat, 4 Feb 2023 at 18:37, Craig Russell  wrote:
>
> These vowels are incorrectly converted by workbench.
>
> These: ươễ should be converted to uoe.
>

There is a lot of workbench code.
Where is this behaviour evident?

Does it need fixing always, or just in some circumstances?
e.g. I would expect original vowels in names to be preserved for entry
in iclas.txt, and probably other places such as emails.

> Not a big priority but should be done at some point.

Needs more detail first.

> Craig
>
> Craig L Russell
> c...@apache.org
>

Re: Secretary workbench is down

[sebb]

Fixed

On Sat, 28 Jan 2023 at 18:32, Craig Russell  wrote:
>
> NameError at /secretary/workbench/
> undefined local variable or method `empty' for # @name="202301", @mbox=nil>
>
> Craig L Russell
> c...@apache.org
>

Re: Error in secretary workbench

[sebb]

Hopefully now fixed.

On Tue, 17 Jan 2023 at 22:27, Craig Russell  wrote:
>
> Seems to be related to sending email to submitter, although it is hard to 
> tell what failed. The icla was apparently correctly filed but no email was 
> sent.
>
> > On Jan 17, 2023, at 14:24, Craig Russell  wrote:
> >
> > Happens every time after successful filing of an ICLA...
> >
> > #
> >  /var/lib/gems/2.7.0/gems/net-smtp-0.3.3/lib/net/smtp.rb:1076:in 
> > `check_response'
> >  /var/lib/gems/2.7.0/gems/net-smtp-0.3.3/lib/net/smtp.rb:1044:in `getok'
> >  /var/lib/gems/2.7.0/gems/net-smtp-0.3.3/lib/net/smtp.rb:972:in `rcptto'
> >  /var/lib/gems/2.7.0/gems/net-smtp-0.3.3/lib/net/smtp.rb:954:in `block in 
> > rcptto_list'
> >  /var/lib/gems/2.7.0/gems/net-smtp-0.3.3/lib/net/smtp.rb:952:in `each'
> >  /var/lib/gems/2.7.0/gems/net-smtp-0.3.3/lib/net/smtp.rb:952:in 
> > `rcptto_list'
> >  /var/lib/gems/2.7.0/gems/net-smtp-0.3.3/lib/net/smtp.rb:768:in 
> > `send_message'
> >  
> > /var/lib/gems/2.7.0/gems/mail-2.8.0.1/lib/mail/network/delivery_methods/smtp_connection.rb:53:in
> >  `deliver!'
> >  
> > /var/lib/gems/2.7.0/gems/mail-2.8.0.1/lib/mail/network/delivery_methods/smtp.rb:101:in
> >  `block in deliver!'
> >  /var/lib/gems/2.7.0/gems/net-smtp-0.3.3/lib/net/smtp.rb:612:in `start'
> >  
> > /var/lib/gems/2.7.0/gems/mail-2.8.0.1/lib/mail/network/delivery_methods/smtp.rb:109:in
> >  `start_smtp_session'
> >  
> > /var/lib/gems/2.7.0/gems/mail-2.8.0.1/lib/mail/network/delivery_methods/smtp.rb:100:in
> >  `deliver!'
> >  /var/lib/gems/2.7.0/gems/mail-2.8.0.1/lib/mail/message.rb:269:in `deliver!'
> >  /x1/srv/whimsy/www/secretary/workbench/views/actions/icla.json.rb:175:in 
> > `block (2 levels) in _evaluate'
> >  /x1/srv/whimsy/www/secretary/workbench/tasks.rb:47:in `complete'
> >  /x1/srv/whimsy/www/secretary/workbench/views/actions/icla.json.rb:174:in 
> > `block in _evaluate'
> >  /x1/srv/whimsy/www/secretary/workbench/tasks.rb:12:in `task'
> >  /x1/srv/whimsy/www/secretary/workbench/views/actions/icla.json.rb:105:in 
> > `_evaluate'
> >  /x1/srv/whimsy/www/secretary/workbench/server.rb:129:in `block in  > (required)>'
> >  /x1/srv/whimsy/lib/whimsy/asf/rack.rb:227:in `call'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.16/src/ruby_supportlib/phusion_passenger/rack/out_of_band_gc.rb:48:in
> >  `call'
> >  /x1/srv/whimsy/lib/whimsy/asf/rack.rb:152:in `call'
> >  /x1/srv/whimsy/lib/whimsy/asf/rack.rb:83:in `call'
> >  /x1/srv/whimsy/lib/whimsy/asf/rack.rb:258:in `call'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.16/src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:107:in
> >  `process_request'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.16/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:157:in
> >  `accept_and_process_next_request'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.16/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:110:in
> >  `main_loop'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.16/src/ruby_supportlib/phusion_passenger/request_handler.rb:419:in
> >  `block (3 levels) in start_threads'
> >  
> > /var/lib/gems/2.7.0/gems/passenger-6.0.16/src/ruby_supportlib/phusion_passenger/utils.rb:113:in
> >  `block in create_thread_and_abort_on_exception'
> > Craig L Russell
> > c...@apache.org
> >
>
> Craig L Russell
> c...@apache.org
>

Re: Trouble with secretary workbench

[sebb]

On Wed, 11 Jan 2023 at 15:28, Craig Russell  wrote:
>
> Hi Sebb,
>
> The error that is now permanent (whimsy secretary workbench is unusable for 
> me) seems like a programming error.
> NoMethodError at /secretary/workbench/
> undefined method `cn' for #
> file: ldap.rb location: method_missing line: 880
>
> > Begin forwarded message:
> >
> > From: sebb 
> > Subject: Re: Trouble with secretary workbench
> > Date: January 11, 2023 at 03:47:41 PST
> > To: Chris Lambertus 
> > Cc: Craig Russell , Users 
> >
> > I've had a look.
> >
> > This is not related to the changes made recently to support LDAP
> > lockdown (nor document updates).
> >
> > Whimsy code relies on Emeritus requests being filed under the ASF id.
> > However someone filed an emeritus request with a non-conforming name.
> > If this is renamed, the workbench should start working again.
> > Renaming is necessary to allow further processing of the request.
>
> When I filed the Emeritus Request the field for file name was incorrect.

What was the name that was proposed?

> If there is supposed to be a specific format name here, then whimsy should 
> fill it and not allow it to be changed.

It does provide a name which is derived from the selected entry.

It may make sense to disallow changing the name.

> If you like I can file a JIRA for it.
>
> Craig
> >
> > On Wed, 11 Jan 2023 at 04:18, Chris Lambertus  wrote:
> >>
> >> Please contact the Whimsy project for issues regarding the service.
> >>
> >>
> >>> On Jan 10, 2023, at 5:18 PM, Craig Russell  wrote:
> >>>
> >>> I'm getting a permanent error at
> >>>
> >>> https://whimsy.apache.org/secretary/workbench/
> >>>
> >>> NoMethodError at /secretary/workbench/
> >>> undefined method `cn' for #
> >>>  • file: ldap.rb
> >>>
> >>>  • location: method_missing
> >>>  • line: 880
> >>>
> >>> Craig L Russell
> >>> c...@apache.org
> >>>
> >>
>
> Craig L Russell
> c...@apache.org
>

Re: whimsy.a.o seems to be broken

[sebb]

On Fri, 9 Dec 2022 at 16:01, Craig Russell  wrote:
>
> I'm still seeing this error on all of the roster pages:
> Error: The application encountered the following error: You have already 
> activated stringio 3.0.4, but your Gemfile requires stringio 3.0.3. 
> Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

I did say that the problem was only fixed 'for now' ...

I will try again.

> Regards,
> Craig
>
> > On Dec 9, 2022, at 07:24, sebb  wrote:
> >
> > Hopefully fixed -- for now.
> >
> > However all I did was update the Gemfile.lock files to point to 3.0.3
> > instead of 3.0.2, which is a bit of a hack.
> >
> > I'm not sure why the lock files got out of step.
> >
> > On Fri, 9 Dec 2022 at 14:56, Daniel Gruno  wrote:
> >>
> >> A bunch of pages (roster, agenda etc) seem to not be working right now, 
> >> with the error:
> >>
> >> Error: The application encountered the following error: You have already 
> >> activated stringio 3.0.3, but your Gemfile requires stringio 3.0.2. 
> >> Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
> >>
> >> Can this be looked at?
>
> Craig L Russell
> c...@apache.org
>

Re: whimsy.a.o seems to be broken

[sebb]

Hopefully fixed -- for now.

However all I did was update the Gemfile.lock files to point to 3.0.3
instead of 3.0.2, which is a bit of a hack.

I'm not sure why the lock files got out of step.

On Fri, 9 Dec 2022 at 14:56, Daniel Gruno  wrote:
>
> A bunch of pages (roster, agenda etc) seem to not be working right now, with 
> the error:
>
> Error: The application encountered the following error: You have already 
> activated stringio 3.0.3, but your Gemfile requires stringio 3.0.2. 
> Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
>
> Can this be looked at?

Re: [SITE] Website Checker Question

[sebb]

On Fri, 11 Nov 2022 at 13:30, Nathan Hartman  wrote:
>
> Hi all,
>
> https://whimsy.apache.org/site/project/subversion complains that we
> don't have the required link to apache.org/licenses, but the
> Subversion site does have the link. Any ideas why it complains?

As per the comment on the report, and the link:
https://www.apache.org/foundation/marks/pmcs#navigation

There should be a "License" navigation link which points to:
http[s]://www.apache.org/licenses[/]

That is not the case on that page.

> Thanks,
> Nathan Hartman

Re: Whitespace comparison too strict for certain resolution checks in agenda tool

[sebb]

Given that the agenda tool is due to be replaced, is it worth spending
any time on this?

It would be a good idea to check that the replacement tool can cope
better with wrapping of hyphenated words.

On Tue, 15 Nov 2022 at 09:04, sebb  wrote:
>
> Another solution would be to adjust word-wrapping so it treats hyphen
> as a normal letter.
>
> On Tue, 15 Nov 2022 at 01:52, Daniel Gruno  wrote:
> >
> > Hi folks,
> > I noticed that item 7B for November seems to fail the standard checks due 
> > to a whitespace irregularity that stems from word-wrapping in the 
> > resolution. A word with a dash in it (real-time) has been broken into two 
> > lines, which the agenda then reconstitutes as "real- time", thus failing 
> > the comparison. Not sure what the ideal fix is here, perhaps interpreting a 
> > newline as being able to be both a space and not a space at the same time?

[jira] [Resolved] (WHIMSY-394) Whimsy sends mailing list subscription confirmation notifications to the entire list

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-394.
-
Resolution: Information Provided

The messages to the list are not sent by Whimsy, but by the script which 
processes automatic (un)subscriptions (i.e. not using a human moderator).

That script is managed by Infrastructure.

As I understand it, confirmation messages are only sent for private lists, and 
are done to give human oversight. For further information, please contact Infra.

> Whimsy sends mailing list subscription confirmation notifications to the 
> entire list
> 
>
> Key: WHIMSY-394
> URL: https://issues.apache.org/jira/browse/WHIMSY-394
> Project: Whimsy
>  Issue Type: Bug
>Reporter: Mike Drob
>Priority: Critical
>
> I was switching which personal email address I use to subscribe to the 
> members@ list and this ended up sending a pair of messages to the entire 
> membership. This seems like it would be very noisy and also a little 
> unnecessary.
> [https://lists.apache.org/thread/kb5g8no90brh9d4tds9pv80hqvnzttl6]
> [https://lists.apache.org/thread/k0k7w7mno1mfqvlg3t4562smdkltg0f3]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Whitespace comparison too strict for certain resolution checks in agenda tool

[sebb]

Another solution would be to adjust word-wrapping so it treats hyphen
as a normal letter.

On Tue, 15 Nov 2022 at 01:52, Daniel Gruno  wrote:
>
> Hi folks,
> I noticed that item 7B for November seems to fail the standard checks due to 
> a whitespace irregularity that stems from word-wrapping in the resolution. A 
> word with a dash in it (real-time) has been broken into two lines, which the 
> agenda then reconstitutes as "real- time", thus failing the comparison. Not 
> sure what the ideal fix is here, perhaps interpreting a newline as being able 
> to be both a space and not a space at the same time?

[jira] [Comment Edited] (WHIMSY-393) Cannot login to create a form for new account request

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630387#comment-17630387
 ] 

Sebb edited comment on WHIMSY-393 at 11/8/22 2:51 PM:
--

Sorry, but only ASF members or PMC chairs can request new accounts


was (Author: s...@apache.org):
Sorry, but only ASF members can update the podling roster.

> Cannot login to create a form for new account request
> -
>
> Key: WHIMSY-393
> URL: https://issues.apache.org/jira/browse/WHIMSY-393
> Project: Whimsy
>  Issue Type: Wish
>Reporter: Wang, Gang
>Priority: Major
>
> Dear Whimsy,
> My ASF ID is "garyw", I'm IPMC and a mentor of Teaclave community.
> I can login the home page of whimsy(https://whimsy.apache.org/)  but I cannot 
> login to create a form for new account request 
> (https://whimsy.apache.org/officers/acreq).
> Please help grant permissions to me as I have 2 new committers waiting for 
> account creation, thanks.
> Best regards
> Gordon



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (WHIMSY-393) Cannot login to create a form for new account request

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-393.
-
Resolution: Fixed

Sorry, but only ASF members can update the podling roster.

> Cannot login to create a form for new account request
> -
>
> Key: WHIMSY-393
> URL: https://issues.apache.org/jira/browse/WHIMSY-393
> Project: Whimsy
>  Issue Type: Wish
>Reporter: Wang, Gang
>Priority: Major
>
> Dear Whimsy,
> My ASF ID is "garyw", I'm IPMC and a mentor of Teaclave community.
> I can login the home page of whimsy(https://whimsy.apache.org/)  but I cannot 
> login to create a form for new account request 
> (https://whimsy.apache.org/officers/acreq).
> Please help grant permissions to me as I have 2 new committers waiting for 
> account creation, thanks.
> Best regards
> Gordon



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-389) unsubscribe feature does not work for all registered emails

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628566#comment-17628566
 ] 

Sebb commented on WHIMSY-389:
-

I never said it was not a bug.

> unsubscribe feature does not work for all registered emails
> ---
>
> Key: WHIMSY-389
> URL: https://issues.apache.org/jira/browse/WHIMSY-389
> Project: Whimsy
>  Issue Type: Bug
>Reporter: Jim Jagielski
>Priority: Minor
> Attachments: Screen Shot 2022-08-08 at 7.39.04 AM.png
>
>
> When trying to unsubscribe from a list, either the email pulldown does not 
> allow selection of any addresses or else on those rare occasions when you can 
> select an address, it errors out with:
>  
> h2. Invalid Input
> Both email and list to subscribe to are required!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Closed] (WHIMSY-391) Provide Bugzilla Statistics

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb closed WHIMSY-391.
---

> Provide Bugzilla Statistics
> ---
>
> Key: WHIMSY-391
> URL: https://issues.apache.org/jira/browse/WHIMSY-391
> Project: Whimsy
>  Issue Type: New Feature
>Reporter: Jan Materne
>Priority: Minor
>
> https://reporter.apache.org/wizard/statistics should include Bugzilla stats 
> as it includes JIRA stats.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (WHIMSY-391) Provide Bugzilla Statistics

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-391.
-
Resolution: Invalid

Reporter is maintained by COMDEV; please raise the issue there

> Provide Bugzilla Statistics
> ---
>
> Key: WHIMSY-391
> URL: https://issues.apache.org/jira/browse/WHIMSY-391
> Project: Whimsy
>  Issue Type: New Feature
>Reporter: Jan Materne
>Priority: Minor
>
> https://reporter.apache.org/wizard/statistics should include Bugzilla stats 
> as it includes JIRA stats.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Feedback on moderation helper app

[sebb]

On Thu, 18 Aug 2022 at 17:31, Sidney Markowitz  wrote:
>
> The two links to "Guide for moderators" on the whimsy Mail List Moderation
> Helper page are out of date. They point to a page that says that info on 
> mailing
> list moderation has moved to
>   https://infra.apache.org/mailing-list-moderation.html

Not sure I follow.
Why do you consider that link to be out of date?

[jira] [Updated] (WHIMSY-389) unsubscribe feature does not work for all registered emails

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb updated WHIMSY-389:

Summary: unsubscribe feature does not work for all registered emails  (was: 
unsubscribe feature does not work)

> unsubscribe feature does not work for all registered emails
> ---
>
> Key: WHIMSY-389
> URL: https://issues.apache.org/jira/browse/WHIMSY-389
> Project: Whimsy
>  Issue Type: Bug
>Reporter: Jim Jagielski
>Priority: Minor
> Attachments: Screen Shot 2022-08-08 at 7.39.04 AM.png
>
>
> When trying to unsubscribe from a list, either the email pulldown does not 
> allow selection of any addresses or else on those rare occasions when you can 
> select an address, it errors out with:
>  
> h2. Invalid Input
> Both email and list to subscribe to are required!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (WHIMSY-389) unsubscribe feature does not work

[Sebb (Jira)]

 [ 
https://issues.apache.org/jira/browse/WHIMSY-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb updated WHIMSY-389:

Priority: Minor  (was: Major)

> unsubscribe feature does not work
> -
>
> Key: WHIMSY-389
> URL: https://issues.apache.org/jira/browse/WHIMSY-389
> Project: Whimsy
>  Issue Type: Bug
>Reporter: Jim Jagielski
>Priority: Minor
> Attachments: Screen Shot 2022-08-08 at 7.39.04 AM.png
>
>
> When trying to unsubscribe from a list, either the email pulldown does not 
> allow selection of any addresses or else on those rare occasions when you can 
> select an address, it errors out with:
>  
> h2. Invalid Input
> Both email and list to subscribe to are required!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (WHIMSY-389) unsubscribe feature does not work

[Sebb (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576893#comment-17576893
 ] 

Sebb commented on WHIMSY-389:
-

In theory only the host part is case-insensitive, though most providers don't 
distinguish the local part.
But matching must take that into account.

One might say that the use of capital letters in host names goes against 
expectation and usage.

Given that there is a work-round this is not an urgent issue.

> unsubscribe feature does not work
> -
>
> Key: WHIMSY-389
> URL: https://issues.apache.org/jira/browse/WHIMSY-389
> Project: Whimsy
>  Issue Type: Bug
>Reporter: Jim Jagielski
>Priority: Major
> Attachments: Screen Shot 2022-08-08 at 7.39.04 AM.png
>
>
> When trying to unsubscribe from a list, either the email pulldown does not 
> allow selection of any addresses or else on those rare occasions when you can 
> select an address, it errors out with:
>  
> h2. Invalid Input
> Both email and list to subscribe to are required!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)