Re: Bug in secretary workbench

[Craig Russell]

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

Bug in secretary workbench

[Craig Russell]

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?

Craig L Russell
c...@apache.org

Workbench: better processing of base64 encoded text

[Craig Russell]

Currently if secretary receives a message from a CCLA admin, instead of filing 
a new CCLA with new contributors, they will simply list the people in the email 
itself. This is fine as long as we establish the provenance of the email and 
save it in documents/cclas.

Workbench displays the processed email in the "text" view which might contain 
base64 encoded text. But since base64 is not human readable, the rawmessage.txt 
is not human readable either, so it cannot be usefully filed in documents/cclas.

Perhaps we can file the rawmessage.xxx in another format (instead of text/plain 
or text/plain;charset=UTF-8) so a browser could view it, decoding the base64.

WDYT?

Craig L Russell
c...@apache.org

ICLAs with no valid requested id should generate more explicit acknowledgment

[Craig Russell]

I'm thinking that we can make life easier for new committers if secretary can 
give more explicit instructions.

Instead of "if you have been invited as a committer..."

"It appears that you have been invited as a committer for . However, 
your ICLA does not have a valid requested id. Please choose an id... and 
forward this message (you can reply all) to the project, including your chosen 
id."

This message would be generated in response to receiving an ICLA where 
secretary finds an invitation (perhaps the sender forwarded the invitation 
email). Secretary would fill the project and vote fields and leave id field 
blank.

WDYT?

Craig L Russell
c...@apache.org

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

[Craig Russell]

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
> 
> 
> Address not found
> Your message wasn't delivered to  <>priv...@legal.apache.org 
> <mailto:priv...@legal.apache.org>because the domain legal.apache.org 
> <http://legal.apache.org/> couldn't be found. Check for typos or unnecessary 
> spaces and try again.
> LEARN MORE <https://support.google.com/mail/?p=BadRcptDomain>
> The response was:
> DNS Error: DNS type 'mx' lookup of legal.apache.org 
> <http://legal.apache.org/> responded with code NXDOMAIN Domain name not 
> found: legal.apache.org <http://legal.apache.org/> For more information, go 
> to https://support.google.com/mail/?p=BadRcptDomain 
> <https://support.google.com/mail/?p=BadRcptDomain>Reporting-MTA: dns; 
> googlemail.com <http://googlemail.com/>
> Received-From-MTA: dns; apache@gmail.com <mailto: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 
> <mailto:630821ed-93d3-415e-afc8-28794e678...@gmail.com>>
> 
> Final-Recipient: rfc822; priv...@legal.apache.org 
> <mailto:priv...@legal.apache.org>
> Action: failed
> Status: 5.1.2
> Diagnostic-Code: smtp; DNS Error: DNS type 'mx' lookup of legal.apache.org 
> <http://legal.apache.org/> responded with code NXDOMAIN
> Domain name not found: legal.apache.org <http://legal.apache.org/> For more 
> information, go to https://support.google.com/mail/?p=BadRcptDomain 
> <https://support.google.com/mail/?p=BadRcptDomain>
> Last-Attempt-Date: Mon, 18 Mar 2024 10:21:20 -0700 (PDT)
> 
> From: Craig Russell mailto:apache@gmail.com>>
> Subject: Missing Legal Affairs Board Report
> Date: March 18, 2024 at 10:21:17 PDT
> To: Roman Shaposhnik mailto:r...@apache.org>>
> Cc: priv...@legal.apache.org <mailto:priv...@legal.apache.org>, Apache Board 
> mailto:bo...@apache.org>>
> 
> 
> 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 <mailto:c...@apache.org>
Craig L Russell
c...@apache.org

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

[Craig Russell]

Like a charm, it works.

Thanks for that,
Craig

> On Mar 8, 2024, at 07:48, sebb  wrote:
> 
> 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
>>> 

Craig L Russell
c...@apache.org

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

[Craig Russell]

-rw-r--r--1 clr  staff 204 Feb 20 14:47 memapp-received.txt

But I think you know that...

> On Mar 8, 2024, at 00:36, sebb  wrote:
> 
> 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
>> 

Craig L Russell
c...@apache.org

Who/how set up memapp-received.txt?

[Craig Russell]

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

Has memapp-received.txt been set up yet?

[Craig Russell]

Whimsy secretary workbench wants to know...

Craig L Russell
c...@apache.org

Re: Bug in download checker

[Craig Russell]

Hi Sebb,

Thanks for taking a look. Once I put in the correct url and override it found 
problems that we will fix.

Regards,
Craig

> On Mar 7, 2024, at 00:49, sebb  wrote:
> 
> 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
>> 

Craig L Russell
c...@apache.org

Bug in download checker

[Craig Russell]

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.

Craig L Russell
c...@apache.org

Re: Please update the report reminders for Flume (was: Re: Flume Board Report due by Wed Mar 13th - Initial Reminder)

[Craig Russell]

Thinking out loud here.

If this ever happens again, where should we leave breadcrumbs in the 
documentation so we can avoid going through this? 

I seriously doubt that we would spend the time to update whimsy PMC tooling to 
make this easier. 

I don't see anywhere in the whimsy web site to put this information, which will 
require a combination of updates to the receiving PMC to include some of the 
retiring PMC members; an update to committer-info.txt; an update to 
committer-info.yaml; and... anything else?

Craig

> On Mar 1, 2024, at 09:22, sebb  wrote:
> 
> I've dropped Flume from CI.txt and updated CI.yaml.
> Hopefully that is sufficient.
> Probably at some stage the YAML tags need to be enhanced to better
> cater for merges.
> 
> Sebb
> 
> On Fri, 1 Mar 2024 at 15:43, Craig Russell  wrote:
>> 
>> Hi Ralph,
>> 
>>> On Feb 29, 2024, at 23:10, Ralph Goers  wrote:
>>> 
>>> The Flume PMC members WERE added to the Logging Services PMC. That was 
>>> reported in the board report at the time.
>> 
>> But the Flume PMC information is still in committee-info.txt so the tooling 
>> still thinks it exists...
>> 
>> Craig
>>> 
>>> Ralph
>>> 
>>>> On Feb 29, 2024, at 1:15 PM, Craig Russell  wrote:
>>>> 
>>>> The required action that I see (which was never done) is to remove Flume 
>>>> from committers/board/committee-info.txt and add the four Flume PMC 
>>>> members to the Logging project PMC.
>>>> 
>>>> Then run some scripts to broadcast the change to the rest of infra.
>>>> 
>>>> I'd expect either Secretary or any Logging PMC member with privileges 
>>>> would be the right person for the task.
>>>> 
>>>> Craig
>>>> 
>>>>> On Feb 29, 2024, at 11:20, Matt Sicker  wrote:
>>>>> 
>>>>> Flume wasn’t retired, though; it was merged with Logging Services. This 
>>>>> is the first time two PMCs went through M, so I’m not sure on the 
>>>>> specifics here.
>>>>> 
>>>>>> On Feb 29, 2024, at 03:44, sebb  wrote:
>>>>>> 
>>>>>> I'm not sure on this one.
>>>>>> 
>>>>>> Whimsy has a function to retire a PMC, but that may includes other
>>>>>> actions which are not appropriate here.
>>>>>> Merely removing the entry is insufficient, as that can lose some
>>>>>> important details. These are recorded in the sibling YAML file.
>>>>>> 
>>>>>> Will need to check further if anything else needs to be done for this 
>>>>>> case.
>>>>>> 
>>>>>> On Thu, 29 Feb 2024 at 07:10, Christian Grobmeier  
>>>>>> wrote:
>>>>>>> 
>>>>>>> Thanks, Sebb.
>>>>>>> Can I edit the file and remove all references to Flume directly?
>>>>>>> Or is there some other process to manipulate this file?
>>>>>>> 
>>>>>>> --
>>>>>>> The Apache Software Foundation
>>>>>>> V.P., Data Privacy
>>>>>>> 
>>>>>>> On Thu, Feb 29, 2024, at 00:01, sebb wrote:
>>>>>>>> It looks like Flume is still listed as a separate PMC in
>>>>>>>> committee-info.txt, which is presumably why the reminder was sent.
>>>>>>>> 
>>>>>>>> On Wed, 28 Feb 2024 at 20:53, Christian Grobmeier 
>>>>>>>>  wrote:
>>>>>>>>> 
>>>>>>>>> Hello Secretary,
>>>>>>>>> 
>>>>>>>>> The Apache flume project was merged into logging services. Please be 
>>>>>>>>> so kind and update the report reminders.
>>>>>>>>> 
>>>>>>>>> Thank you!
>>>>>>>>> Christian
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> The Apache Software Foundation
>>>>>>>>> V.P., Data Privacy
>>>>>>>>> 
>>>>>>>>> On Wed, Feb 28, 2024, at 21:19, Bessenyei Balázs Donát wrote:
>>>>>>>>> 
>>>>>>>>> I am still getting these emails, even though I believe I should not.
>>>>>>>>> Who do I reach out to about this?
>>>>>>>>> 
>>>>>&g

Re: Signing key repository

[Craig Russell]

Hi Sebb(TEST)

> On Feb 18, 2024, at 16:18, sebb  wrote:
> 
> On Sun, 18 Feb 2024 at 23:46, sebbaz(Test)  <mailto:sebbaz+t...@gmail.com>> 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).

I did notice that there was some permissions problem with the __keys__ 
directory but reloading the whimsy page seemed to fix it.
>> 
>> Was no error reported?

No error. It just seemed like the SGA code did not try to save the key. 
>> 
>>> 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.

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

Thanks for checking. If it's not too much work, moving the __keys__ directory a 
level above would make sense to me.

Thanks,
Craig
> 
>>> WDYT?
>>> 
>>> Craig L Russell
>>> c...@apache.org <mailto:c...@apache.org>
Craig L Russell
c...@apache.org

Board agenda bug

[Craig Russell]

If I change my name when adding a comment, my "approved by" name also changes.

The name on the comment should not change the "approved by" name.

WDYT?

Craig L Russell
c...@apache.org

Web site checks feature request

[Craig Russell]

I was just looking at the web site check tool and I've added a board discussion 
about the hundreds of failures.

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.

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
check that the repository is at least readable for the public and read/write 
for committers of that project; if not, yellow flag

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

Craig L Russell
c...@apache.org

Signing key repository

[Craig Russell]

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.

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.

WDYT?

Craig L Russell
c...@apache.org

Re: 2024 Conflict of Interest

[Craig Russell]

> On Jan 21, 2024, at 01:41, sebbaz(Test)  wrote:
> 
> I think anyone who can sign the COI can create the directory.

So if I do svn mkdir 
https://svn.apache.org/repos/private/documents/conflict-of-interest/2024
all of the defaults will be ok?

Craig
> On Sun, 21 Jan 2024 at 01:53, Craig Russell  wrote:
>> 
>> Hi,
>> 
>> Currently, https://whimsy.apache.org/officers/coi.cgi returns
>> Sorry, cannot access COI documents
>> 
>> I'm pretty sure that "someone" needs to create the 2024 directory. Any 
>> takers?
>> 
>> Thanks,
>> Craig
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Re: 2024 Conflict of Interest

[Craig Russell]

I was hoping that you could "just do it" now that we all know that it's broken 
and it would take me a while to figure out the svn command that had the proper 
url and permissions.

> On Jan 21, 2024, at 01:41, sebbaz(Test)  wrote:
> 
> I think anyone who can sign the COI can create the directory.
> 
> On Sun, 21 Jan 2024 at 01:53, Craig Russell  wrote:
>> 
>> Hi,
>> 
>> Currently, https://whimsy.apache.org/officers/coi.cgi returns
>> Sorry, cannot access COI documents
>> 
>> I'm pretty sure that "someone" needs to create the 2024 directory. Any 
>> takers?
>> 
>> Thanks,
>> Craig
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Re: 2024 Conflict of Interest

[Craig Russell]

Here's the code:

coi_url = ASF::SVN.svnurl('conflict-of-interest')
COI_CURRENT_TEMPLATE_URL = File.join(coi_url, 'template.txt')

YEAR = Time.now.strftime "%Y"
COI_CURRENT_URL = File.join(coi_url, YEAR)

Any ideas what COI_CURRENT_URL resolves to?

> On Jan 21, 2024, at 01:41, sebbaz(Test)  wrote:
> 
> I think anyone who can sign the COI can create the directory.
> 
> On Sun, 21 Jan 2024 at 01:53, Craig Russell  wrote:
>> 
>> Hi,
>> 
>> Currently, https://whimsy.apache.org/officers/coi.cgi returns
>> Sorry, cannot access COI documents
>> 
>> I'm pretty sure that "someone" needs to create the 2024 directory. Any 
>> takers?
>> 
>> Thanks,
>> Craig
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

2024 Conflict of Interest

[Craig Russell]

Hi,

Currently, https://whimsy.apache.org/officers/coi.cgi returns 
Sorry, cannot access COI documents

I'm pretty sure that "someone" needs to create the 2024 directory. Any takers?

Thanks,
Craig

Craig L Russell
c...@apache.org

Board agenda oopsie

[Craig Russell]

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

Markpub is not an option on whimsy subscribe request

[Craig Russell]

Markpub can be subscribed manually but doesn't appear to be an option on whimsy 
"subscribe to mail lists". Is this intentional or an oversight?

Craig L Russell
c...@apache.org

Bug in secretary workbench

[Craig Russell]

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: Board report due - anything to include?

[Craig Russell]

> On Sep 8, 2023, at 14:21, Shane Curcuru  wrote:
> 
> I'm definitely positively putting in the board report this month. Anyone have 
> items to add, besides the usual "we're here, and sebb is fixing various 
> useful things"?

Good to hear it. P.S. without Secretary Workbench you would have a very hard 
time finding volunteers to staff the Secretary position...
> 
> -- 
> - Shane
>  Whimsy VP
>  The Apache Software Foundation

Craig L Russell
c...@apache.org

Unable to parse PDF in secretary workbench

[Craig Russell]

Hi,

I'm processing the icla.pdf from Flash and when I press the Parse/use PDF data 
I get an error. [1]

I've left the document unprocessed so you can see the error directly. Please 
let me know if you can take a look at it.

Thanks,
Craig

[1] 


  
  JSON::GeneratorError at 
secretaryworkbenchactionsparse-icla

  
  //
  

Fwd: Unable to submit Libcloud August 2023 board report

[Craig Russell]

I am also unable to file a board report. The error I get is 
Exception
#

Any ideas?

> 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

Board agenda 2023-08-16

[Craig Russell]

The board agenda for August refers to the board minutes for May and June.

What I see in the agenda tool does not match what is in svn, specifically the 
private references in the May XMLGraphics report which is marked  in 
the agenda but appears in the public minutes.

Surprisingly, the changes made to the June agenda (marking the private section 
of the Data Privacy report) appear to be ok.

What am I doing wrong? I've refreshed the agenda a few times.

Craig L Russell
c...@apache.org

Re: CoI affirmations is missing VP, Public Affairs

[Craig Russell]

Thanks, missed it.

> On Jul 25, 2023, at 00:49, sebb  wrote:
> 
> 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
>> 

Craig L Russell
c...@apache.org

CoI affirmations is missing VP, Public Affairs

[Craig Russell]

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: Reverted change to members.txt as it broke Whimsy

[Craig Russell]

Hi Sebb,

What broke? How can I fix it?

Thanks,
Craig

> On Jul 12, 2023, at 16:44, sebb  wrote:
> 
> As the subject says.
> 
> Whimsy (and probably other tool) depend on format of members.txt.
> 
> Any changes need to be co-ordinated with updates the these tools.
> 
> Sebb

Craig L Russell
c...@apache.org

Re: [whimsy] branch master updated: Better URL for submitting docs

[Craig Russell]

Hi Sebb,

Much better.

Thanks for doing this,
Craig

> On Jul 8, 2023, at 08:51, s...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> sebb 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 574a430d Better URL for submitting docs
> 574a430d is described below
> 
> commit 574a430de638af1c2d09b4a211edced637a7daf1
> Author: Sebb 
> AuthorDate: Sat Jul 8 16:51:19 2023 +0100
> 
>Better URL for submitting docs
> ---
> www/secretary/icla-lint.cgi  | 2 +-
> www/secretary/workbench/templates/incomplete.erb | 2 +-
> www/secretary/workbench/templates/pubkey.erb | 2 +-
> www/secretary/workbench/templates/unsigned.erb   | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/www/secretary/icla-lint.cgi b/www/secretary/icla-lint.cgi
> index 080b83f8..45b8cc10 100755
> --- a/www/secretary/icla-lint.cgi
> +++ b/www/secretary/icla-lint.cgi
> @@ -385,7 +385,7 @@ _html do
> body = "Dear " + name + ",\n\n" +
> "We are reviewing our records to be sure that all submitted ICLAs 
> are on file.\n" +
> "Unfortunately, we are unable to locate the ICLA that you 
> submitted earlier.\n\n" +
> -"Can you please resubmit to secret...@apache.org? 
> http://apache.org/licenses/#submitting\n; +
> +"Can you please resubmit to secret...@apache.org? 
> https://apache.org/licenses/contributor-agreements.html#submitting\n; +
> "Please do *not* use an apache email as your E-Mail address.\n" +
> "You can send the original ICLA (if the email address is still 
> valid) or a new one.\n\n" +
> "Best regards,\n"
> diff --git a/www/secretary/workbench/templates/incomplete.erb 
> b/www/secretary/workbench/templates/incomplete.erb
> index 49e56497..e3455098 100644
> --- a/www/secretary/workbench/templates/incomplete.erb
> +++ b/www/secretary/workbench/templates/incomplete.erb
> @@ -4,7 +4,7 @@ We received this document but we cannot file it as is.
> <%= @missing_items %>
> Please fill all required fields and resubmit all pages
> to secret...@apache.org
> -https://www.apache.org/licenses/#submitting
> +https://apache.org/licenses/contributor-agreements.html#submitting
> 
> Warm Regards,
> 
> diff --git a/www/secretary/workbench/templates/pubkey.erb 
> b/www/secretary/workbench/templates/pubkey.erb
> index b27e53f9..24bd73e7 100644
> --- a/www/secretary/workbench/templates/pubkey.erb
> +++ b/www/secretary/workbench/templates/pubkey.erb
> @@ -6,7 +6,7 @@ your public key. Please upload your public key to 
> keyserver.ubuntu.com.
> If you have trouble uploading your key, you can print, sign, date,
> scan, and email the pdf to secret...@apache.org
> 
> -http://www.apache.org/licenses/#submitting
> +https://apache.org/licenses/contributor-agreements.html#submitting
> 
> Warm Regards,
> 
> diff --git a/www/secretary/workbench/templates/unsigned.erb 
> b/www/secretary/workbench/templates/unsigned.erb
> index d63f355d..81cd4226 100644
> --- a/www/secretary/workbench/templates/unsigned.erb
> +++ b/www/secretary/workbench/templates/unsigned.erb
> @@ -2,7 +2,7 @@ Dear <%= @email.display_names.join(', ') %>,
> 
> We received this document but it appears to be unsigned.
> Please sign and resubmit to secret...@apache.org
> -https://www.apache.org/licenses/#submitting
> +https://apache.org/licenses/contributor-agreements.html#submitting
> 
> Please note that your name typed in a script font
> does not constitute a signature.
> 

Craig L Russell
c...@apache.org

Re: Kaustubh Beedkar added to Wayang committers

[Craig Russell]

A little more background.

The ICLA was filed for new committer and wayang was the project. But the new 
account request created by whimsy was filed with incubator as the project. So 
the new committer had to be added to wayang manually instead of automatically.

So Greg and I are trying to figure out where the process went sideways. It 
looks like whimsy secretary workbench is the most likely culprit.

Craig


> On May 6, 2023, at 20:39, Craig Russell  wrote:
> 
> Hi,
> 
> Is secretary workbench broken?
> 
> The ICLA was filed and an account was requested. But instead of "wayang" 
> being in the new account request, it was incubator. Pasted here from the 
> commit to acreq:
> 
> +++ infrastructure/trunk/acreq/new-account-reqs.txt [utf-8] Thu May  4 
> 14:29:35 2023
> @@ -21,3 +21,4 @@
>  ##
>  ##  new account requests
>  ##
> +kbeedkar;Kaustubh Beedkar;kbeed...@gmail.com 
> <mailto:kbeed...@gmail.com>;incubator;incubator;05-04-2023;yes;yes;no
> 
> I'm very sure that wayang was specified in secretary workbench. Is the 
> podling not ready to accept new committers? It's two plus years old already...
> 
> Thanks
> Craig
> 
>> Begin forwarded message:
>> 
>> From: Greg Stein mailto:gst...@gmail.com>>
>> Subject: Re: Kaustubh Beedkar added to Wayang committers
>> Date: May 6, 2023 at 20:09:55 PDT
>> To: Craig Russell mailto:apache@gmail.com>>, 
>> Christofer Dutz mailto:cd...@apache.org>>, Craig Russell 
>> mailto:c...@apache.org>>
>> 
>> On Sat, May 6, 2023 at 10:04 PM Greg Stein > <mailto:gst...@gmail.com>> wrote:
>> >...
>> There certainly hasn't been a change on the Infra side. Our account creation 
>> script just looks at what project was selected, and puts the person into 
>> that group. In this case, it saw "incubator".
>> 
>> Sorry, my language was imprecise. Not "selected" but "specified/committed 
>> into the workflow". See the commit for the account request here: 
>> https://lists.apache.org/thread/2qn3ngn9w710rms9nhsqx1x7mn882owb 
>> <https://lists.apache.org/thread/2qn3ngn9w710rms9nhsqx1x7mn882owb>
>> 
>> Cheers,
>> -g
>> 
> 
> Craig L Russell
> c...@apache.org <mailto:c...@apache.org>
> 

Craig L Russell
c...@apache.org

Fwd: Kaustubh Beedkar added to Wayang committers

[Craig Russell]

Hi,

Is secretary workbench broken?

The ICLA was filed and an account was requested. But instead of "wayang" being 
in the new account request, it was incubator. Pasted here from the commit to 
acreq:

+++ infrastructure/trunk/acreq/new-account-reqs.txt [utf-8] Thu May  4 14:29:35 
2023
@@ -21,3 +21,4 @@
 ##
 ##  new account requests
 ##
+kbeedkar;Kaustubh 
Beedkar;kbeed...@gmail.com;incubator;incubator;05-04-2023;yes;yes;no

I'm very sure that wayang was specified in secretary workbench. Is the podling 
not ready to accept new committers? It's two plus years old already...

Thanks
Craig

> Begin forwarded message:
> 
> From: Greg Stein 
> Subject: Re: Kaustubh Beedkar added to Wayang committers
> Date: May 6, 2023 at 20:09:55 PDT
> To: Craig Russell , Christofer Dutz , 
> Craig Russell 
> 
> On Sat, May 6, 2023 at 10:04 PM Greg Stein  <mailto:gst...@gmail.com>> wrote:
> >...
> There certainly hasn't been a change on the Infra side. Our account creation 
> script just looks at what project was selected, and puts the person into that 
> group. In this case, it saw "incubator".
> 
> Sorry, my language was imprecise. Not "selected" but "specified/committed 
> into the workflow". See the commit for the account request here: 
> https://lists.apache.org/thread/2qn3ngn9w710rms9nhsqx1x7mn882owb 
> <https://lists.apache.org/thread/2qn3ngn9w710rms9nhsqx1x7mn882owb>
> 
> Cheers,
> -g
> 

Craig L Russell
c...@apache.org

Promote committer to new PMC member

[Craig Russell]

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. 

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

Fwd: [whimsy] branch clr-apache-update-new-pmc-member updated: Update mod.js.rb

[Craig Russell]

Hi Sebb,

Please take a look.

I'm not sure how to create the link to lists.apache.org that will open in a 
separate tab without the user explicitly asking for it.

I don't know how to create the variable votelink so that it is transmitted to 
back end.

I don't know how to verify that the votelink matches the pattern 
"https://lists.apache.org*;

I'll need to update the back end to create and send the NOTICE email to board 
when processing the update of committee-info.txt.

Any assistance is appreciated.

Thanks,
Craig

> Begin forwarded message:
> 
> From: c...@apache.org
> Subject: [whimsy] branch clr-apache-update-new-pmc-member updated: Update 
> mod.js.rb
> Date: April 23, 2023 at 16:19:27 PDT
> To: "comm...@whimsical.apache.org" 
> Reply-To: dev@whimsical.apache.org
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> clr pushed a commit to branch clr-apache-update-new-pmc-member
> in repository https://gitbox.apache.org/repos/asf/whimsy.git
> 
> 
> The following commit(s) were added to 
> refs/heads/clr-apache-update-new-pmc-member by this push:
> new c96a2087 Update mod.js.rb
> c96a2087 is described below
> 
> commit c96a2087fe564de6b6df6f94258637fe86f7393e
> Author: Craig L Russell 
> AuthorDate: Sun Apr 23 16:19:23 2023 -0700
> 
>Update mod.js.rb
> 
>update modify role to include link to VOTE or consensus thread
> ---
> www/roster/views/pmc/mod.js.rb | 14 +-
> 1 file changed, 9 insertions(+), 5 deletions(-)
> 
> diff --git a/www/roster/views/pmc/mod.js.rb b/www/roster/views/pmc/mod.js.rb
> index feae2411..6b31b470 100644
> --- a/www/roster/views/pmc/mod.js.rb
> +++ b/www/roster/views/pmc/mod.js.rb
> @@ -46,13 +46,17 @@ class PMCMod < Vue
> _br
> _b do
>   _ 'Before adding a new PMC member, '
> -  _a 'email notification must have been received by the 
> Board mailing list',
> -href: 
> 'https://www.apache.org/dev/pmc.html#send-the-board-a-notice-of-the-vote-to-add-someone'
> -  _ ' (cc: the PMC private@ mailing list).'
> +  _a 'the PMC must approve the new member by VOTE or 
> consensus.',
> +  _a 'a VOTE thread or consensus decistion must be made on 
> the private mail list',
> +href: 'https://www.apache.org/dev/pmc.html#newpmc'
> +  _a 'You can use the following link to find the thread on 
> the private list'
> +  _a 'and copy it into the text field below.'
> +href: 'https://lists.apache.org/list?private@' + 
> @@project.display.name + '.apache.org:lte=6M:'
> +  _ ' (the PMC private@ mailing list).'  
> end
> _label do
> -  _span 'Has the NOTICE email been received by the board 
> list?'
> -  _input type: 'checkbox', checked: @notice_elapsed
> +  _span 'Enter the link to the approval VOTE or consensus 
> thread:'
> +  _input type: 'text', value:@votelink
> end
>   end
> end
> 

Craig L Russell
c...@apache.org

I need some help with tooling

[Craig Russell]

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

Error in secretary workbench

[Craig Russell]

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

Update email addresses in whimsy/committer

[Craig Russell]

I see that I can add/update/delete email addresses using id.apache.org:
Forwarding email address:
Alias addresses:

In whimsy, there are three categories:
Email forwarded to:
Email (alt):
Email (other):

It seems that whimsy allows updates to forwarded to and (alt) but not (other).

So:
What/why is there an (alt) address in whimsy?
Why can whimsy not update email (other)
What is (other) used for? 

Thanks,
Craig

Craig L Russell
c...@apache.org

Conversions of uncommon vowels are incorrect: ươễ

[Craig Russell]

These vowels are incorrectly converted by workbench.

These: ươễ should be converted to uoe.

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

Craig

Craig L Russell
c...@apache.org

Re: Secretary workbench is down

[Craig Russell]

Thanks!

> On Jan 28, 2023, at 15:09, sebb  wrote:
> 
> 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
>> 

Craig L Russell
c...@apache.org

Secretary workbench is down

[Craig Russell]

NameError at /secretary/workbench/
undefined local variable or method `empty' for #

Craig L Russell
c...@apache.org

Re: Error in secretary workbench

[Craig Russell]

Hi Sebb,

Yes, it seems to work now.

Thanks,
Craig

> On Jan 17, 2023, at 16:33, sebb  wrote:
> 
> 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
>> 

Craig L Russell
c...@apache.org

Re: Error in secretary workbench

[Craig Russell]

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

Error in secretary workbench

[Craig Russell]

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 '
  /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

Exception - Internal Server Error every. time.

[Craig Russell]

Secretary workbench displays this error every time it is loaded or reloaded.

What's going on?

Craig L Russell
c...@apache.org

Fwd: Trouble with secretary workbench

[Craig Russell]

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. If 
there is supposed to be a specific format name here, then whimsy should fill it 
and not allow it to be changed.

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

[Craig Russell]

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)
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: (Copy) button on secretary workbench icla form

[Craig Russell]

Truth is, it is much less time on secretary's part to request the account 
compared to multiple messages with the PMC to tell them what they have to do.

The PMCs cannot even be counted on to properly document the result of the vote. 
Explaining what they need to do to request the account is time consuming and 
painful.

That's why bother.

Craig

> On Jul 23, 2022, at 16:35, sebb  wrote:
> 
> On Sat, 23 Jul 2022 at 23:55, Craig Russell  wrote:
>> 
>> When filing an ICLA, I often copy the public name (and if needed, the full 
>> name) so I can then find the PMC vote approving the committer.
> 
> Why bother?
> 
> Seems to me the Secretary role is to file the ICLA.
> End of.
> 
> It is up to the PMC to complete the process.
> 
>> This involves a non-trivial select the field, copy the data. Non-trivial 
>> because selecting the field is a double-click and a cursor movement to 
>> exactly the place where the entire field is highlighted.
>> 
>> I have seen other web pages with an icon to copy the field. I cannot figure 
>> out how to add this to the ICLA form for the full and public names. Here is 
>> how it might look:
>> Full Name: ✂ Mao Zedong
>> Public Name: ✂ Mao Zedong
>> 
>> And it would be nice to add tooltips to some of the form fields...
>> 
>> I found this on the internets but don't know exactly how it applies:
>> /* Copy the text inside the text field */
>>  navigator.clipboard.writeText(copyText.value);
>> 
>> Any ideas?
>> 
>> Thanks,
>> Craig
>> 
>> 
>> 
>>  Copy to clipboard
>>  ✂
>>  
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

(Copy) button on secretary workbench icla form

[Craig Russell]

When filing an ICLA, I often copy the public name (and if needed, the full 
name) so I can then find the PMC vote approving the committer.

This involves a non-trivial select the field, copy the data. Non-trivial 
because selecting the field is a double-click and a cursor movement to exactly 
the place where the entire field is highlighted.

I have seen other web pages with an icon to copy the field. I cannot figure out 
how to add this to the ICLA form for the full and public names. Here is how it 
might look:
Full Name: ✂ Mao Zedong
Public Name: ✂ Mao Zedong

And it would be nice to add tooltips to some of the form fields...

I found this on the internets but don't know exactly how it applies:
/* Copy the text inside the text field */
  navigator.clipboard.writeText(copyText.value);

Any ideas?

Thanks,
Craig



  Copy to clipboard
  ✂
  

Craig L Russell
c...@apache.org

Re: Trouble filing ICLA from Jacek

[Craig Russell]

So, we have addressed this issue before but the message isn't complete without 
extra information.

> With this message, the Whimsy PMC has been notified that your ICLA has been 
> filed. 
> 
> ** Please contact the Apache Whimsy PMC with any further questions, not the 
> Secretary. Thanks. **
> 
> Please provide the Apache Whimsy PMC (copied) with a valid Apache id. 
> 
> The id must not already be in use. See 
> https://people.apache.org/committer-index.html
> Note that some existing ids include '-' and '_'. These characters are no 
> longer permitted in ids.
> 
> The id must consist of lowercase alphanumeric characters only, starting with 
> an alphabetic character.
> Minimum length 3 characters. No special characters.
> 
If you go to the page https://people.apache.org/committer-index.html you will 
not find the reserved ids listed.

I suggested earlier:
>>> Can we add reserved names to https://people.apache.org/committer-index.html 
>>> <https://people.apache.org/committer-index.html> which is where we send 
>>> people to check if their preferred id is already available?
>>> Perhaps entries like this:
>>> SVN ID Name
>>> jacek 

>> 

But given that there are literally hundreds of reserved ids, it is not 
practical to list them. But given that the requested id does not have any 
embedded "_" or "-" we should try to make it easier for the submitter to figure 
out that the id is simply reserved.

I'll propose a patch to www/secretary/workbench/templates/icla-invalid-id.erb 
that  may clarify that the id is reserved.

Craig

> On Jul 7, 2022, at 12:00, Craig Russell  wrote:
> 
> 
> 
>> On Jul 7, 2022, at 07:18, sebb mailto:seb...@gmail.com>> 
>> wrote:
>> 
>> On Thu, 7 Jul 2022 at 14:24, Craig Russell > <mailto:apache@gmail.com>> wrote:
>>> 
>>> 
>>> 
>>> On Jul 7, 2022, at 06:21, sebb mailto:seb...@gmail.com>> 
>>> wrote:
>>> 
>>> On Thu, 7 Jul 2022 at 14:11, Craig Russell >> <mailto:apache@gmail.com>> wrote:
>>> 
>>> 
>>> Hi Sebb,
>>> 
>>> I don't think my message was understood.
>>> 
>>> On Jul 7, 2022, at 04:22, sebb mailto:seb...@gmail.com>> 
>>> wrote:
>>> 
>>> On Thu, 7 Jul 2022 at 03:52, Craig Russell >> <mailto:apache@gmail.com>> wrote:
>>> 
>>> 
>>> I'm happy to write a patch if you can give me a hint where the code is that 
>>> looks at reserved-ids so I can write an update to the red box.
>>> 
>>> 
>>> Note that re-using a reserved ID could mess up code provenance -
>>> effectively it means someone can take over someone else's ID.
>>> Not exactly identity theft, but with many of the same potential 
>>> consequences.
>>> 
>>> 
>>> I understand that a reserved id cannot be used again. That was not what I 
>>> was asking for.
>>> 
>>> 
>>> OK
>>> 
>>> 
>>> Sorry, but I see no valid reason to differentiate why an id is
>>> disallowed, so doing research on it is work I don't wish to undertake.
>>> 
>>> 
>>> Again, I am not asking for the reason that an id is reserved, just the fact 
>>> that it is.
>>> 
>>> 
>>> If you wish to know personally whether an entry is in the reserved
>>> list or not, just look at the file which I think is a sibling to
>>> iclas.txt.
>>> 
>>> 
>>> All i'm asking for is that if a user requests an id that is reserved, that 
>>> the secretary tool add a line to the response "The id requested is not 
>>> available. Please contact the (P)PMC with a different id." and add a red 
>>> box "The id is not available. Continue?"
>>> 
>>> The secretary tool is supposed to be a help to the secretary/assistant. 
>>> Having mysterious red boxes with no obvious way for the user to tell what 
>>> is happening is a bug.
>>> 
>>> 
>>> Regardless of whether the id is reserved or is currently in use, the
>>> user must choose a new id.
>>> 
>>> Why does the user need to know the exact reason?
>>> 
>>> 
>>> Again, I'm not asking to know the exact reason or to tell the submitter the 
>>> exact reason. My suggested message (see above) is
>>> 
>>> "The id requested is not available. Please contact the (P)PMC with a 
>>> different id."
>> 
>> So why do you need to know where the reserved ids are chec

Re: Trouble filing ICLA from Jacek

[Craig Russell]

> On Jul 7, 2022, at 07:18, sebb  wrote:
> 
> On Thu, 7 Jul 2022 at 14:24, Craig Russell  <mailto:apache@gmail.com>> wrote:
>> 
>> 
>> 
>> On Jul 7, 2022, at 06:21, sebb  wrote:
>> 
>> On Thu, 7 Jul 2022 at 14:11, Craig Russell  wrote:
>> 
>> 
>> Hi Sebb,
>> 
>> I don't think my message was understood.
>> 
>> On Jul 7, 2022, at 04:22, sebb  wrote:
>> 
>> On Thu, 7 Jul 2022 at 03:52, Craig Russell  wrote:
>> 
>> 
>> I'm happy to write a patch if you can give me a hint where the code is that 
>> looks at reserved-ids so I can write an update to the red box.
>> 
>> 
>> Note that re-using a reserved ID could mess up code provenance -
>> effectively it means someone can take over someone else's ID.
>> Not exactly identity theft, but with many of the same potential consequences.
>> 
>> 
>> I understand that a reserved id cannot be used again. That was not what I 
>> was asking for.
>> 
>> 
>> OK
>> 
>> 
>> Sorry, but I see no valid reason to differentiate why an id is
>> disallowed, so doing research on it is work I don't wish to undertake.
>> 
>> 
>> Again, I am not asking for the reason that an id is reserved, just the fact 
>> that it is.
>> 
>> 
>> If you wish to know personally whether an entry is in the reserved
>> list or not, just look at the file which I think is a sibling to
>> iclas.txt.
>> 
>> 
>> All i'm asking for is that if a user requests an id that is reserved, that 
>> the secretary tool add a line to the response "The id requested is not 
>> available. Please contact the (P)PMC with a different id." and add a red box 
>> "The id is not available. Continue?"
>> 
>> The secretary tool is supposed to be a help to the secretary/assistant. 
>> Having mysterious red boxes with no obvious way for the user to tell what is 
>> happening is a bug.
>> 
>> 
>> Regardless of whether the id is reserved or is currently in use, the
>> user must choose a new id.
>> 
>> Why does the user need to know the exact reason?
>> 
>> 
>> Again, I'm not asking to know the exact reason or to tell the submitter the 
>> exact reason. My suggested message (see above) is
>> 
>> "The id requested is not available. Please contact the (P)PMC with a 
>> different id."
> 
> So why do you need to know where the reserved ids are checked?
> 
> It's really not clear what you are asking.
> 
> How do you currently deal with ICLAs that request an invalid id, for
> example with _ or - in them?
> Can you not use the same approach in this case?

This is currently a difficult issue for Secretary. There is no automated way to 
tell a newly-elected committer that the id they have chosen is not legal.

So, yes we should use the same approach for all such cases instead of waiting 
for the inevitable back-n-forth with the PMC and committer regarding why the 
committer and PMC need to take additional action to get the account created.

Craig
> 
>> 
>> Craig
>> 
>> 
>> Regards,
>> Craig
>> 
>> 
>> Thanks,
>> Craig
>> 
>> On Jul 6, 2022, at 16:05, sebb  wrote:
>> 
>> On Wed, 6 Jul 2022 at 23:53, Craig Russell  wrote:
>> 
>> 
>> Thanks for the explanation. How do we prevent it in future?
>> 
>> 
>> How often does it occur?
>> 
>> Can we add reserved names to https://people.apache.org/committer-index.html 
>> which is where we send people to check if their preferred id is already 
>> available?
>> Perhaps entries like this:
>> SVN ID Name
>> jacek 
>> 
>> And surely we can add a red box warning for the secretary to understand that 
>> this is a reserved name? Warning: the requested id is in the 
>> reserved-ids.yml list.
>> (Proceed anyway?)
>> 
>> 
>> Does it really matter why the id is invalid?
>> 
>> Whatever the reason, it cannot be used.
>> 
>> Seems like completely unnecessary work, given how infrequent this is.
>> 
>> Thanks,
>> Craig
>> 
>> On Jul 6, 2022, at 14:48, sebb  wrote:
>> 
>> Because it is not allowed.
>> 
>> See reserved-ids.yml
>> 
>> On Wed, 6 Jul 2022 at 19:14, Craig Russell  wrote:
>> 
>> 
>> I filled the form and the committer id should be jacek. But the field is red 
>> and it does not try to request the account.
>> 
>> Any ideas?
>> 
>> Thanks,
>> Craig
>> 
>> Craig L Russell
>> Assistant Secretary, Apache Software Foundation
>> c...@apache.org http://db.apache.org/jdo
>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 
>> 
>> Craig L Russell
>> c...@apache.org

Craig L Russell
c...@apache.org

Re: Trouble filing ICLA from Jacek

[Craig Russell]

> On Jul 7, 2022, at 06:21, sebb  wrote:
> 
> On Thu, 7 Jul 2022 at 14:11, Craig Russell  <mailto:apache@gmail.com>> wrote:
>> 
>> Hi Sebb,
>> 
>> I don't think my message was understood.
>> 
>>> On Jul 7, 2022, at 04:22, sebb  wrote:
>>> 
>>> On Thu, 7 Jul 2022 at 03:52, Craig Russell  wrote:
>>>> 
>>>> I'm happy to write a patch if you can give me a hint where the code is 
>>>> that looks at reserved-ids so I can write an update to the red box.
>>> 
>>> Note that re-using a reserved ID could mess up code provenance -
>>> effectively it means someone can take over someone else's ID.
>>> Not exactly identity theft, but with many of the same potential 
>>> consequences.
>> 
>> I understand that a reserved id cannot be used again. That was not what I 
>> was asking for.
> 
> OK
> 
>>> 
>>> Sorry, but I see no valid reason to differentiate why an id is
>>> disallowed, so doing research on it is work I don't wish to undertake.
>> 
>> Again, I am not asking for the reason that an id is reserved, just the fact 
>> that it is.
>>> 
>>> If you wish to know personally whether an entry is in the reserved
>>> list or not, just look at the file which I think is a sibling to
>>> iclas.txt.
>> 
>> All i'm asking for is that if a user requests an id that is reserved, that 
>> the secretary tool add a line to the response "The id requested is not 
>> available. Please contact the (P)PMC with a different id." and add a red box 
>> "The id is not available. Continue?"
>> 
>> The secretary tool is supposed to be a help to the secretary/assistant. 
>> Having mysterious red boxes with no obvious way for the user to tell what is 
>> happening is a bug.
> 
> Regardless of whether the id is reserved or is currently in use, the
> user must choose a new id.
> 
> Why does the user need to know the exact reason?

Again, I'm not asking to know the exact reason or to tell the submitter the 
exact reason. My suggested message (see above) is 
> "The id requested is not available. Please contact the (P)PMC with a 
> different id."

Craig
> 
>> Regards,
>> Craig
>>> 
>>>> Thanks,
>>>> Craig
>>>> 
>>>> On Jul 6, 2022, at 16:05, sebb  wrote:
>>>> 
>>>> On Wed, 6 Jul 2022 at 23:53, Craig Russell  wrote:
>>>> 
>>>> 
>>>> Thanks for the explanation. How do we prevent it in future?
>>>> 
>>>> 
>>>> How often does it occur?
>>>> 
>>>> Can we add reserved names to 
>>>> https://people.apache.org/committer-index.html which is where we send 
>>>> people to check if their preferred id is already available?
>>>> Perhaps entries like this:
>>>> SVN ID Name
>>>> jacek 
>>>> 
>>>> And surely we can add a red box warning for the secretary to understand 
>>>> that this is a reserved name? Warning: the requested id is in the 
>>>> reserved-ids.yml list.
>>>> (Proceed anyway?)
>>>> 
>>>> 
>>>> Does it really matter why the id is invalid?
>>>> 
>>>> Whatever the reason, it cannot be used.
>>>> 
>>>> Seems like completely unnecessary work, given how infrequent this is.
>>>> 
>>>> Thanks,
>>>> Craig
>>>> 
>>>> On Jul 6, 2022, at 14:48, sebb  wrote:
>>>> 
>>>> Because it is not allowed.
>>>> 
>>>> See reserved-ids.yml
>>>> 
>>>> On Wed, 6 Jul 2022 at 19:14, Craig Russell  wrote:
>>>> 
>>>> 
>>>> I filled the form and the committer id should be jacek. But the field is 
>>>> red and it does not try to request the account.
>>>> 
>>>> Any ideas?
>>>> 
>>>> Thanks,
>>>> Craig
>>>> 
>>>> Craig L Russell
>>>> Assistant Secretary, Apache Software Foundation
>>>> c...@apache.org http://db.apache.org/jdo
>>>> 
>>>> 
>>>> Craig L Russell
>>>> c...@apache.org
>>>> 
>>>> 
>>>> Craig L Russell
>>>> c...@apache.org
>>>> 
>> 
>> Craig L Russell
>> c...@apache.org

Craig L Russell
c...@apache.org

Re: Trouble filing ICLA from Jacek

[Craig Russell]

Hi Sebb,

I don't think my message was understood.

> On Jul 7, 2022, at 04:22, sebb  wrote:
> 
> On Thu, 7 Jul 2022 at 03:52, Craig Russell  wrote:
>> 
>> I'm happy to write a patch if you can give me a hint where the code is that 
>> looks at reserved-ids so I can write an update to the red box.
> 
> Note that re-using a reserved ID could mess up code provenance -
> effectively it means someone can take over someone else's ID.
> Not exactly identity theft, but with many of the same potential consequences.

I understand that a reserved id cannot be used again. That was not what I was 
asking for.
> 
> Sorry, but I see no valid reason to differentiate why an id is
> disallowed, so doing research on it is work I don't wish to undertake.

Again, I am not asking for the reason that an id is reserved, just the fact 
that it is.
> 
> If you wish to know personally whether an entry is in the reserved
> list or not, just look at the file which I think is a sibling to
> iclas.txt.

All i'm asking for is that if a user requests an id that is reserved, that the 
secretary tool add a line to the response "The id requested is not available. 
Please contact the (P)PMC with a different id." and add a red box "The id is 
not available. Continue?"

The secretary tool is supposed to be a help to the secretary/assistant. Having 
mysterious red boxes with no obvious way for the user to tell what is happening 
is a bug.

Regards,
Craig
> 
>> Thanks,
>> Craig
>> 
>> On Jul 6, 2022, at 16:05, sebb  wrote:
>> 
>> On Wed, 6 Jul 2022 at 23:53, Craig Russell  wrote:
>> 
>> 
>> Thanks for the explanation. How do we prevent it in future?
>> 
>> 
>> How often does it occur?
>> 
>> Can we add reserved names to https://people.apache.org/committer-index.html 
>> which is where we send people to check if their preferred id is already 
>> available?
>> Perhaps entries like this:
>> SVN ID Name
>> jacek 
>> 
>> And surely we can add a red box warning for the secretary to understand that 
>> this is a reserved name? Warning: the requested id is in the 
>> reserved-ids.yml list.
>> (Proceed anyway?)
>> 
>> 
>> Does it really matter why the id is invalid?
>> 
>> Whatever the reason, it cannot be used.
>> 
>> Seems like completely unnecessary work, given how infrequent this is.
>> 
>> Thanks,
>> Craig
>> 
>> On Jul 6, 2022, at 14:48, sebb  wrote:
>> 
>> Because it is not allowed.
>> 
>> See reserved-ids.yml
>> 
>> On Wed, 6 Jul 2022 at 19:14, Craig Russell  wrote:
>> 
>> 
>> I filled the form and the committer id should be jacek. But the field is red 
>> and it does not try to request the account.
>> 
>> Any ideas?
>> 
>> Thanks,
>> Craig
>> 
>> Craig L Russell
>> Assistant Secretary, Apache Software Foundation
>> c...@apache.org http://db.apache.org/jdo
>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Re: Trouble filing ICLA from Jacek

[Craig Russell]

I'm happy to write a patch if you can give me a hint where the code is that 
looks at reserved-ids so I can write an update to the red box.

Thanks,
Craig

> On Jul 6, 2022, at 16:05, sebb  wrote:
> 
> On Wed, 6 Jul 2022 at 23:53, Craig Russell  <mailto:apache@gmail.com>> wrote:
>> 
>> Thanks for the explanation. How do we prevent it in future?
> 
> How often does it occur?
> 
>> Can we add reserved names to https://people.apache.org/committer-index.html 
>> which is where we send people to check if their preferred id is already 
>> available?
>> Perhaps entries like this:
>> SVN ID Name
>> jacek 
>> 
>> And surely we can add a red box warning for the secretary to understand that 
>> this is a reserved name? Warning: the requested id is in the 
>> reserved-ids.yml list.
>> (Proceed anyway?)
> 
> Does it really matter why the id is invalid?
> 
> Whatever the reason, it cannot be used.
> 
> Seems like completely unnecessary work, given how infrequent this is.
> 
>> Thanks,
>> Craig
>> 
>>> On Jul 6, 2022, at 14:48, sebb  wrote:
>>> 
>>> Because it is not allowed.
>>> 
>>> See reserved-ids.yml
>>> 
>>> On Wed, 6 Jul 2022 at 19:14, Craig Russell  wrote:
>>>> 
>>>> I filled the form and the committer id should be jacek. But the field is 
>>>> red and it does not try to request the account.
>>>> 
>>>> Any ideas?
>>>> 
>>>> Thanks,
>>>> Craig
>>>> 
>>>> Craig L Russell
>>>> Assistant Secretary, Apache Software Foundation
>>>> c...@apache.org http://db.apache.org/jdo
>>>> 
>> 
>> Craig L Russell
>> c...@apache.org

Craig L Russell
c...@apache.org

Re: Trouble filing ICLA from Jacek

[Craig Russell]

Thanks for the explanation. How do we prevent it in future?

Can we add reserved names to https://people.apache.org/committer-index.html 
which is where we send people to check if their preferred id is already 
available?

Perhaps entries like this:
SVN IDName
jacek

And surely we can add a red box warning for the secretary to understand that 
this is a reserved name? Warning: the requested id is in the reserved-ids.yml 
list.
(Proceed anyway?)

Thanks,
Craig

> On Jul 6, 2022, at 14:48, sebb  wrote:
> 
> Because it is not allowed.
> 
> See reserved-ids.yml
> 
> On Wed, 6 Jul 2022 at 19:14, Craig Russell  wrote:
>> 
>> I filled the form and the committer id should be jacek. But the field is red 
>> and it does not try to request the account.
>> 
>> Any ideas?
>> 
>> Thanks,
>> Craig
>> 
>> Craig L Russell
>> Assistant Secretary, Apache Software Foundation
>> c...@apache.org http://db.apache.org/jdo
>> 

Craig L Russell
c...@apache.org

Trouble filing ICLA from Jacek

[Craig Russell]

I filled the form and the committer id should be jacek. But the field is red 
and it does not try to request the account.

Any ideas?

Thanks,
Craig

Craig L Russell
Assistant Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo

Re: E_NO_CARE

[Craig Russell]

> On Jun 12, 2022, at 03:08, sebb  wrote:
> 
> On Sun, 12 Jun 2022 at 01:49, Craig Russell  <mailto:apache@gmail.com>> wrote:
>> 
>> While looking at the secretary workbench process to reject a document, there 
>> was at the same time a document that has no relevance to the job of 
>> secretary.
>> 
>> I'm thinking of adding a new reason to reject a document.
>> 
>> @not_relevant; ' not relevant', ' this document is not relevant to the work 
>> of the Foundation'
>> 
>> We "often" get documents (like those from Abdulrahman) that we will never 
>> file. As it is, I sometimes just delete it from secretary workbench but 
>> sometimes I feel like I should tell them that it just is not relevant to our 
>> job here.
>> 
>> Sebbgestions?
> 
> Interesting typo ...
> 
> Easy enough to add that as another failure type.

Yeah, just wanted to know if anyone else thought it was worthwhile.
> 
> However it's already possible to reply to the email from your own
> copy, and just delete the email from the workbench.

That is what I have been doing. I was not sure whether any others on the team 
thought there could be a more formal solution.
> 
> Note that the workbench only shows emails with attachments, so the
> Secretary still has to deal with other emails locally.

Right. Back to regular programming...

Craig

> 
>> Craig
>> 
>> Craig L Russell
>> c...@apache.org <mailto:c...@apache.org>
Craig L Russell
c...@apache.org

E_NO_CARE

[Craig Russell]

While looking at the secretary workbench process to reject a document, there 
was at the same time a document that has no relevance to the job of secretary.

I'm thinking of adding a  new reason to reject a document.

@not_relevant; ' not relevant', ' this document is not relevant to the work of 
the Foundation'

We "often" get documents (like those from Abdulrahman) that we will never file. 
As it is, I sometimes just delete it from secretary workbench but sometimes I 
feel like I should tell them that it just is not relevant to our job here.

Sebbgestions?

Craig

Craig L Russell
c...@apache.org

Re: Awkward dependency of parts.js.rb and incomplete.json.rb

[Craig Russell]

Hi Sebb,

Thanks for taking the time to respond.

I guess it would be possible to compose the list of reasons on the front end 
and pass them to the back end to compose the email. There would be a bit more 
network traffic because the entire text of the reasons would have to be sent.

I admit I missed the comment at the beginning of the reject section which 
specifically refers to corresponding changes needed in incomplete.json.rb.

It is a bit awkward to stitch together changes from multiple files into one 
branch/PR but that's just me. 

All told it's probably not worth spending more energy on this.

Regards,
Craig

> On Jun 11, 2022, at 03:57, sebb  wrote:
> 
> On Sat, 11 Jun 2022 at 00:15, Craig Russell  wrote:
>> 
>> When parts.js.rb is updated to add more reasons to reject a document, a 
>> corresponding change must be made to incomplete.json.rb.
>> 
>> Is there an easy way for incomplete.json.rb to somehow pick up the changes, 
>> perhaps by redefining the structure of the reasons to include all of the 
>> parts: the name of the variable, the text to be displayed on the tool, and 
>> the text to be inserted into the email?
>> 
> 
> Note that parts.js.rb is converted to Javascript, and runs in the
> browser, whereas incomplete.json.rb runs as a script on the server.
> 
>> Just asking because I had this same issue last time I updated the checkboxes 
>> and didn't update the email text.
>> 
>> Thinking out loud, each reason would be e.g.
>> reason[1] = [@unsigned, ' unsigned', ' the document appears to be unsigned']
>> reason[2] = [@script_font, ' script font', ' a name typed in a script font 
>> is not a signature']
>> 
>> But maybe it would help if the parts.js.rb would calculate the reasons 
>> before invoking the incomplete message processing? In other words, just move 
>> the message calculation from incomplete.json.rb to parts.js.rb.
> 
> Maybe; I'm not convinced that the effort is worthwhile compared with
> (say) ensuring that the code has comments reminding maintainers what
> to do.
> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Awkward dependency of parts.js.rb and incomplete.json.rb

[Craig Russell]

 When parts.js.rb is updated to add more reasons to reject a document, a 
corresponding change must be made to incomplete.json.rb. 

Is there an easy way for incomplete.json.rb to somehow pick up the changes, 
perhaps by redefining the structure of the reasons to include all of the parts: 
the name of the variable, the text to be displayed on the tool, and the text to 
be inserted into the email?

Just asking because I had this same issue last time I updated the checkboxes 
and didn't update the email text.

Thinking out loud, each reason would be e.g.
reason[1] = [@unsigned, ' unsigned', ' the document appears to be unsigned']
reason[2] = [@script_font, ' script font', ' a name typed in a script font is 
not a signature']

But maybe it would help if the parts.js.rb would calculate the reasons before 
invoking the incomplete message processing? In other words, just move the 
message calculation from incomplete.json.rb to parts.js.rb.

Craig L Russell
c...@apache.org

Re: Secretary workbench has nothing to do

[Craig Russell]

That would explain it. Case closed. Thanks for analyzing the logs. 

Craig

> On Jun 8, 2022, at 07:13, sebb  wrote:
> 
> Infra made a change to a mailbox size limit which caused problems for
> the mail system.
> 
> The Whimsy mail.log has lots of messages such as:
> 
> fatal: main.cf configuration error: mailbox_size_limit is smaller
> than message_size_limit
> 
> These errors started at Jun  6 02:26:54 and stopped at Jun  7 18:38:26
> 
> AFAICT this allowed messages to be delivered to Whimsy, but they could
> not be forwarded to the mailbox.
> 
> It appears that the mail system did eventually deliver the messages to
> the Whimsy process.
> 
> I think this is  the cause of the delayed appearance of the mails.
> 
> On Wed, 8 Jun 2022 at 14:54, Craig Russell  wrote:
>> 
>> Hi Sebb,
>> 
>> I've privately forwarded the four ICLAs mentioned in my previous email. 
>> These did eventually show up  in secretary workbench after more than a day.
>> 
>>> Apache Linkis Committer ICLA 03:29 5.4 MB
>>> Filled example 05:22 98KB (detached signature)
>>> ICLA 05:56 85KB
>>> Invitation to become Linkis committer:  08:44 254KB (script 
>>> signature)
>> 
>> I hope you can figure out what happened.
>> 
>> Thanks,
>> Craig
>> 
>> 
>>> On Jun 8, 2022, at 02:52, sebb  wrote:
>>> 
>>> AFAICT the new entries in the workbench were all created recently.
>>> 
>>> When I wrote, I'm pretty sure that there were no outstanding emails.
>>> Unfortunately I did not keep the data I used.
>>> Maybe there was a delay in sending some of the mails.
>>> 
>>> If you have got some examples that you think should have been
>>> displayed, please send me details (privately, or to secretary@) and I
>>> will have a look.
>>> 
>>> Sebb
>>> 
>>> On Tue, 7 Jun 2022 at 21:19, Craig Russell  wrote:
>>>> 
>>>> After 30 hour outage, the workbench is back.
>>>> 
>>>> What happened?
>>>> 
>>>> Craig
>>>> 
>>>>> On Jun 7, 2022, at 13:13, Craig Russell  wrote:
>>>>> 
>>>>> Maybe we should consider sending secretary workbench over to infra...
>>>>> 
>>>>> Craig
>>>>> 
>>>>>> On Jun 7, 2022, at 11:33, Craig Russell  wrote:
>>>>>> 
>>>>>> Sorry for not replying all...
>>>>>> 
>>>>>> There is still nothing in the workbench and more ICLAs have come in 
>>>>>> since yesterday.
>>>>>> 
>>>>>> I cannot troubleshoot this one...
>>>>>> 
>>>>>> Craig
>>>>>> 
>>>>>> 
>>>>>>> On Jun 6, 2022, at 16:14, Craig Russell  wrote:
>>>>>>> 
>>>>>>> Hi Sebb,
>>>>>>> 
>>>>>>> I see these in my inbox to secretary:
>>>>>>> 
>>>>>>> subject/date (PDT)/size
>>>>>>> 
>>>>>>> Apache Linkis Committer ICLA 03:29 5.4 MB
>>>>>>> Filled example 05:22 98KB (detached signature)
>>>>>>> ICLA 05:56 85KB
>>>>>>> Invitation to become Linkis committer:  08:44 254KB 
>>>>>>> (script signature)
>>>>>>> 
>>>>>>> Have these been handled, or are they missing from others' inboxes? Is 
>>>>>>> there a mail trail to follow? I can send headers if that will help...
>>>>>>> 
>>>>>>> Craig
>>>>>>> 
>>>>>>>> On Jun 6, 2022, at 15:45, sebb  wrote:
>>>>>>>> 
>>>>>>>> On Mon, 6 Jun 2022 at 23:08, Craig Russell  
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> while several ICLAs have been received.
>>>>>>>> 
>>>>>>>> The workbench only displays emails that have attachments and that are
>>>>>>>> not marked as deleted.
>>>>>>>> 
>>>>>>>> AFAICT there are no such emails.
>>>>>>>> 
>>>>>>>>> Craig L Russell
>>>>>>>>> c...@apache.org
>>>>>>>>> 
>>>>>>> 
>>>>>>> Craig L Russell
>>>>>>> c...@apache.org
>>>>>>> 
>>>>>> 
>>>>>> Craig L Russell
>>>>>> c...@apache.org
>>>>>> 
>>>>> 
>>>>> Craig L Russell
>>>>> c...@apache.org
>>>>> 
>>>> 
>>>> Craig L Russell
>>>> c...@apache.org
>>>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Re: Secretary workbench has nothing to do

[Craig Russell]

Hi Sebb,

I've privately forwarded the four ICLAs mentioned in my previous email. These 
did eventually show up  in secretary workbench after more than a day.

> Apache Linkis Committer ICLA 03:29 5.4 MB
> Filled example 05:22 98KB (detached signature)
> ICLA 05:56 85KB
> Invitation to become Linkis committer:  08:44 254KB (script 
> signature)

I hope you can figure out what happened.

Thanks,
Craig


> On Jun 8, 2022, at 02:52, sebb  wrote:
> 
> AFAICT the new entries in the workbench were all created recently.
> 
> When I wrote, I'm pretty sure that there were no outstanding emails.
> Unfortunately I did not keep the data I used.
> Maybe there was a delay in sending some of the mails.
> 
> If you have got some examples that you think should have been
> displayed, please send me details (privately, or to secretary@) and I
> will have a look.
> 
> Sebb
> 
> On Tue, 7 Jun 2022 at 21:19, Craig Russell  wrote:
>> 
>> After 30 hour outage, the workbench is back.
>> 
>> What happened?
>> 
>> Craig
>> 
>>> On Jun 7, 2022, at 13:13, Craig Russell  wrote:
>>> 
>>> Maybe we should consider sending secretary workbench over to infra...
>>> 
>>> Craig
>>> 
>>>> On Jun 7, 2022, at 11:33, Craig Russell  wrote:
>>>> 
>>>> Sorry for not replying all...
>>>> 
>>>> There is still nothing in the workbench and more ICLAs have come in since 
>>>> yesterday.
>>>> 
>>>> I cannot troubleshoot this one...
>>>> 
>>>> Craig
>>>> 
>>>> 
>>>>> On Jun 6, 2022, at 16:14, Craig Russell  wrote:
>>>>> 
>>>>> Hi Sebb,
>>>>> 
>>>>> I see these in my inbox to secretary:
>>>>> 
>>>>> subject/date (PDT)/size
>>>>> 
>>>>> Apache Linkis Committer ICLA 03:29 5.4 MB
>>>>> Filled example 05:22 98KB (detached signature)
>>>>> ICLA 05:56 85KB
>>>>> Invitation to become Linkis committer:  08:44 254KB (script 
>>>>> signature)
>>>>> 
>>>>> Have these been handled, or are they missing from others' inboxes? Is 
>>>>> there a mail trail to follow? I can send headers if that will help...
>>>>> 
>>>>> Craig
>>>>> 
>>>>>> On Jun 6, 2022, at 15:45, sebb  wrote:
>>>>>> 
>>>>>> On Mon, 6 Jun 2022 at 23:08, Craig Russell  wrote:
>>>>>>> 
>>>>>>> while several ICLAs have been received.
>>>>>> 
>>>>>> The workbench only displays emails that have attachments and that are
>>>>>> not marked as deleted.
>>>>>> 
>>>>>> AFAICT there are no such emails.
>>>>>> 
>>>>>>> Craig L Russell
>>>>>>> c...@apache.org
>>>>>>> 
>>>>> 
>>>>> Craig L Russell
>>>>> c...@apache.org
>>>>> 
>>>> 
>>>> Craig L Russell
>>>> c...@apache.org
>>>> 
>>> 
>>> Craig L Russell
>>> c...@apache.org
>>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Re: Secretary workbench has nothing to do

[Craig Russell]

After 30 hour outage, the workbench is back.

What happened?

Craig

> On Jun 7, 2022, at 13:13, Craig Russell  wrote:
> 
> Maybe we should consider sending secretary workbench over to infra...
> 
> Craig
> 
>> On Jun 7, 2022, at 11:33, Craig Russell  wrote:
>> 
>> Sorry for not replying all...
>> 
>> There is still nothing in the workbench and more ICLAs have come in since 
>> yesterday.
>> 
>> I cannot troubleshoot this one...
>> 
>> Craig
>> 
>> 
>>> On Jun 6, 2022, at 16:14, Craig Russell  wrote:
>>> 
>>> Hi Sebb,
>>> 
>>> I see these in my inbox to secretary:
>>> 
>>> subject/date (PDT)/size
>>> 
>>> Apache Linkis Committer ICLA 03:29 5.4 MB
>>> Filled example 05:22 98KB (detached signature)
>>> ICLA 05:56 85KB
>>> Invitation to become Linkis committer:  08:44 254KB (script 
>>> signature)
>>> 
>>> Have these been handled, or are they missing from others' inboxes? Is there 
>>> a mail trail to follow? I can send headers if that will help...
>>> 
>>> Craig
>>> 
>>>> On Jun 6, 2022, at 15:45, sebb  wrote:
>>>> 
>>>> On Mon, 6 Jun 2022 at 23:08, Craig Russell  wrote:
>>>>> 
>>>>> while several ICLAs have been received.
>>>> 
>>>> The workbench only displays emails that have attachments and that are
>>>> not marked as deleted.
>>>> 
>>>> AFAICT there are no such emails.
>>>> 
>>>>> Craig L Russell
>>>>> c...@apache.org
>>>>> 
>>> 
>>> Craig L Russell
>>> c...@apache.org
>>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 
> 
> Craig L Russell
> c...@apache.org
> 

Craig L Russell
c...@apache.org

Re: Secretary workbench has nothing to do

[Craig Russell]

Maybe we should consider sending secretary workbench over to infra...

Craig

> On Jun 7, 2022, at 11:33, Craig Russell  wrote:
> 
> Sorry for not replying all...
> 
> There is still nothing in the workbench and more ICLAs have come in since 
> yesterday.
> 
> I cannot troubleshoot this one...
> 
> Craig
> 
> 
>> On Jun 6, 2022, at 16:14, Craig Russell  wrote:
>> 
>> Hi Sebb,
>> 
>> I see these in my inbox to secretary:
>> 
>> subject/date (PDT)/size
>> 
>> Apache Linkis Committer ICLA 03:29 5.4 MB
>> Filled example 05:22 98KB (detached signature)
>> ICLA 05:56 85KB
>> Invitation to become Linkis committer:  08:44 254KB (script 
>> signature)
>> 
>> Have these been handled, or are they missing from others' inboxes? Is there 
>> a mail trail to follow? I can send headers if that will help...
>> 
>> Craig
>> 
>>> On Jun 6, 2022, at 15:45, sebb  wrote:
>>> 
>>> On Mon, 6 Jun 2022 at 23:08, Craig Russell  wrote:
>>>> 
>>>> while several ICLAs have been received.
>>> 
>>> The workbench only displays emails that have attachments and that are
>>> not marked as deleted.
>>> 
>>> AFAICT there are no such emails.
>>> 
>>>> Craig L Russell
>>>> c...@apache.org
>>>> 
>> 
>> Craig L Russell
>> c...@apache.org
>> 
> 
> Craig L Russell
> c...@apache.org
> 

Craig L Russell
c...@apache.org

Re: Secretary workbench has nothing to do

[Craig Russell]

Sorry for not replying all...

There is still nothing in the workbench and more ICLAs have come in since 
yesterday.

I cannot troubleshoot this one...

Craig


> On Jun 6, 2022, at 16:14, Craig Russell  wrote:
> 
> Hi Sebb,
> 
> I see these in my inbox to secretary:
> 
> subject/date (PDT)/size
> 
> Apache Linkis Committer ICLA 03:29 5.4 MB
> Filled example 05:22 98KB (detached signature)
> ICLA 05:56 85KB
> Invitation to become Linkis committer:  08:44 254KB (script 
> signature)
> 
> Have these been handled, or are they missing from others' inboxes? Is there a 
> mail trail to follow? I can send headers if that will help...
> 
> Craig
> 
>> On Jun 6, 2022, at 15:45, sebb  wrote:
>> 
>> On Mon, 6 Jun 2022 at 23:08, Craig Russell  wrote:
>>> 
>>> while several ICLAs have been received.
>> 
>> The workbench only displays emails that have attachments and that are
>> not marked as deleted.
>> 
>> AFAICT there are no such emails.
>> 
>>> Craig L Russell
>>> c...@apache.org
>>> 
> 
> Craig L Russell
> c...@apache.org
> 

Craig L Russell
c...@apache.org

Secretary workbench has nothing to do

[Craig Russell]

while several ICLAs have been received.

Craig L Russell
c...@apache.org

ECCN contact information is volatile

[Craig Russell]

I understand that the ECCN matrix file eccnmatrix.yaml located in the 
repository https://gitbox.apache.org/repos/asf/www-eccn.git has a contact for 
each entry, which should be the PMC chair.

I'm thinking that whatever process we use to change the chair should also 
change the contact in the project eccn file.

I'm not volunteering because I do not know the process. There may be some 
whimsical process but I cannot find anything in the PMC part of the roster to 
change the chair. 

If interested, I can open a whimsy JIRA to add this functionality.

Craig

Craig L Russell
c...@apache.org

Comparing branches

[Craig Russell]

Hi,

I'm trying to understand the git compare branches function. The most recent 
branch I created has a few changes that were merged to master. But comparing 
them shows a difference between master and the branch.

https://github.com/apache/whimsy/compare/master...signature_not_armored

When I go to the master branch I can see the merged changes.

What am I missing?

Thanks,
Craig

Craig L Russell
c...@apache.org

Returning Emeritus members process

[Craig Russell]

I don't think secretary workbench properly handles returning emeritus members.

IIUC, what we need to do is to:

1. create a new directory in documents/member_apps/availid
2. move the existing availid.pdf to member_apps/availid/member_app1.pdf
3. file the new member app in member_apps/availid/member_app2.pdf
4. find the member's existing entry in members.txt and move it from emeritus 
section to active section
5. subscribe returning member's email to members@ and members-notify@

For now, I guess this needs to be done manually...

Craig L Russell
c...@apache.org

Re: Signature files ending with .gpg

[Craig Russell]

Hi Sebb,

> On Mar 29, 2022, at 2:58 PM, sebb  wrote:
> 
> It's not a detached signature, and is not in text format as required.
> 
> I suggest it is rejected.

Thanks, that is the expertise I was looking for. As you explained to the 
submitter:
The .asc means ascii armored so it is the only format for a signature that we 
accept.

I made a pull request to add a reject button specifically for this case. Is it 
good enough to merge?

Thanks,
Craig

> 
> Sebb
> On Tue, 29 Mar 2022 at 20:31, Craig Russell  wrote:
>> 
>> Hi,
>> 
>> We have a membership application digitally signed with a signature file 
>> whose name ends in .gpg. Secretary workbench does not recognize this file as 
>> a signature.
>> 
>> Our instructions are to digitally sign and attach the detached .asc file to 
>> the email.
>> 
>> It would be a real PITA to manually fix this problem. Are there any easy 
>> fixes to allow the .gpg file to be treated as a signature? (I don't even 
>> know if this file is a signature...)
>> 
>> Thanks,
>> Craig
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Signature files ending with .gpg

[Craig Russell]

Hi,

We have a membership application digitally signed with a signature file whose 
name ends in .gpg. Secretary workbench does not recognize this file as a 
signature.

Our instructions are to digitally sign and attach the detached .asc file to the 
email.

It would be a real PITA to manually fix this problem. Are there any easy fixes 
to allow the .gpg file to be treated as a signature? (I don't even know if this 
file is a signature...)

Thanks,
Craig

Craig L Russell
c...@apache.org

Fwd: board: r106225 - /foundation/board/board_agenda_2022_03_16.txt

[Craig Russell]

I think we need to disable write access to the board agenda once the meeting 
starts, or perhaps some time earlier?

Craig

> Begin forwarded message:
> 
> From: kishorvpa...@apache.org
> Subject: board: r106225 - /foundation/board/board_agenda_2022_03_16.txt
> Date: March 16, 2022 at 7:53:40 PM PDT
> To: board-...@apache.org
> Reply-To: bo...@apache.org
> 
> Author: kishorvpatil
> Date: Thu Mar 17 02:53:40 2022
> New Revision: 106225
> 
> Log:
> Publishing report for storm via Reporter
> 
> Modified:
>foundation/board/board_agenda_2022_03_16.txt
> 
> Modified: foundation/board/board_agenda_2022_03_16.txt
> ==
> --- foundation/board/board_agenda_2022_03_16.txt [utf-8] (original)
> +++ foundation/board/board_agenda_2022_03_16.txt [utf-8] Thu Mar 17 02:53:40 
> 2022
> @@ -4777,6 +4777,30 @@ Paul Stead (pds) 23 March 2021
> -
> Attachment BM: Report from the Apache Storm Project  [Kishor Patil]
> 
> +## Description:
> +The mission of Storm is the creation and maintenance of software related to 
> +Distributed, real-time computation system
> +
> +## Issues:
> +Nothing to report at this point.
> +
> +## Membership Data:
> +Apache Storm was founded 2014-09-16 (8 years ago)
> +There are currently 42 committers and 41 PMC members in this project.
> +The Committer-to-PMC ratio is roughly 1:1.
> +
> +Community changes, past quarter:
> +- No new PMC members. Last addition was Bipin Prasad on 2020-11-15.
> +- No new committers. Last addition was Bipin Prasad on 2020-11-16.
> +
> +## Project Activity:
> +The log4j libraries are updated to address latest CVEs. The team is 
> +currently working on certifying release candidate 2.4.0
> +
> +## Community Health:
> +It's all good. The next release 2.4.0 should be out soon. 
> +There are newer PRs to address upgrading dependencies such as zookeeper.
> +
> 
> -
> Attachment BN: Report from the Apache Submarine Project  [Liu Xun]
> 
> 

Craig L Russell
c...@apache.org

Re: [whimsy] branch master updated: Suppress leading bullet

[Craig Russell]

Wow. I am impressed!

Craig

> On Feb 21, 2022, at 3:23 AM, s...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> sebb 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 841be19  Suppress leading bullet
> new b8c9e42  Merge branch 'master' of https://github.com/apache/whimsy
> 841be19 is described below
> 
> commit 841be19bc3cb43085a4ab7efc7d2f5e96f7eaacd
> Author: Sebb 
> AuthorDate: Mon Feb 21 11:23:15 2022 +
> 
>Suppress leading bullet
> ---
> www/secretary/workbench/public/secmail.css | 6 ++
> www/secretary/workbench/views/parts.js.rb  | 2 +-
> 2 files changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/www/secretary/workbench/public/secmail.css 
> b/www/secretary/workbench/public/secmail.css
> index 304cd19..0010ac9 100644
> --- a/www/secretary/workbench/public/secmail.css
> +++ b/www/secretary/workbench/public/secmail.css
> @@ -204,3 +204,9 @@ ul.icla-search li {
> ul.icla-search input[type=radio] {
>   margin-right: 10px;
> }
> +
> +ul.icla-reject li {
> +  list-style: none;
> +  padding: 0;
> +  margin: 0;
> +}
> diff --git a/www/secretary/workbench/views/parts.js.rb 
> b/www/secretary/workbench/views/parts.js.rb
> index 7ea6438..bcca669 100644
> --- a/www/secretary/workbench/views/parts.js.rb
> +++ b/www/secretary/workbench/views/parts.js.rb
> @@ -224,7 +224,7 @@ class Parts < Vue
> end
> 
> # The checked: variable names must be reflected in the file 
> incomplete.json.jb
> -_ul do
> +_ul.icla_reject do # the class is used to suppress the leading 
> bullet
>   _li do
> _label do
>   _input type: 'checkbox', checked: @missing_address,

Craig L Russell
c...@apache.org

Re: Bullet checkbox help for secretary mail form

[Craig Russell]

I found this on the inter webs:


How do I get the list-style-type:none to work in vue?

# The checked: variable names must be reflected in the file 
incomplete.json.jb
_ul do
  _li do
_label do
  _input type: 'checkbox', checked: @missing_address,
  onClick: -> {@missing_address = !@missing_address}
  _span ' missing or partial postal address'
end

Is it as easy as:

# The checked: variable names must be reflected in the file 
incomplete.json.jb
_ul list-style-type: none do
  _li do
_label do
  _input type: 'checkbox', checked: @missing_address,
  onClick: -> {@missing_address = !@missing_address}
  _span ' missing or partial postal address'
end

I don't have the full whimsy dev/test environment installed. Could someone 
please take a look?

Thanks,
Craig

> On Feb 20, 2022, at 4:12 PM, Craig Russell  wrote:
> 
> Hi,
> 
> I'm working on https://issues.apache.org/jira/browse/WHIMSY-379 and have one 
> last issue to solve.
> 
> The rendering of the list of checkboxes at 
> https://github.com/apache/whimsy/blob/master/www/secretary/workbench/views/parts.js.rb
>  line 226 is a bit awkward. It is a bullet list of checkboxes.
> 
> The bullets are extraneous. Is there another unnumbered list that we can use 
> instead, so that just the checkboxes are shown and not the bullets?
> 
> Thanks,
> Craig
> 
> Craig L Russell
> c...@apache.org
> 

Craig L Russell
c...@apache.org

Bullet checkbox help for secretary mail form

[Craig Russell]

Hi,

I'm working on https://issues.apache.org/jira/browse/WHIMSY-379 and have one 
last issue to solve.

The rendering of the list of checkboxes at 
https://github.com/apache/whimsy/blob/master/www/secretary/workbench/views/parts.js.rb
 line 226 is a bit awkward. It is a bullet list of checkboxes.

The bullets are extraneous. Is there another unnumbered list that we can use 
instead, so that just the checkboxes are shown and not the bullets?

Thanks,
Craig

Craig L Russell
c...@apache.org

Re: Secretary workbench doesn't remove rejected items

[Craig Russell]

I generally like the new layout of the actions.

But the (o) upload public key belongs in its own section parallel to the other 
"file this" items, and not in the reject category.

Thanks,
Craig


> On Feb 18, 2022, at 7:33 AM, sebb  wrote:
> 
> On Fri, 18 Feb 2022 at 14:52, sebb  wrote:
>> 
>> On Fri, 18 Feb 2022 at 03:25, Craig Russell  wrote:
>>> 
>>> To recap:
>>> 
>>> There are three possible resolutions for submitted documents:
>>> defer: upload public key
>>> file: valid document
>>> reject: bad signature, missing stuff, not signed by officer, etc.
>>> 
>>> This seems not to be reflected in the workflow...
>> 
>> Having reverted to before the menu update, every single action now
>> results in marking the email as deleted as part of the flow.
>> 
>> AFAICT the handling of upload has always been wrong.
> 
> Scrap that; mistake in testing.
> upload does change the status, but does not delete the entry
> 
>>> Craig
>>> 
>>>> On Feb 17, 2022, at 5:49 PM, Craig Russell  wrote:
>>>> 
>>>> The recent change to add more reject options seems to have broken the 
>>>> reject flow.
>>>> 
>>>> Upload public key should not be in the reject tab because the file can 
>>>> still be processed. But other reasons in the reject tab should remove the 
>>>> item, and the accept icla should remove the item.
>>>> 
>>>> Can you please review the logic to be sure it didn't change anything it 
>>>> should not?
>>>> 
>>>> Thanks,
>>>> Craig
>>>> 
>>>> Craig L Russell
>>>> c...@apache.org
>>>> 
>>> 
>>> Craig L Russell
>>> c...@apache.org
>>> 

Craig L Russell
c...@apache.org

Re: Secretary workbench doesn't remove rejected items

[Craig Russell]

To recap:

There are three possible resolutions for submitted documents:
defer: upload public key
file: valid document
reject: bad signature, missing stuff, not signed by officer, etc.

This seems not to be reflected in the workflow...

Craig

> On Feb 17, 2022, at 5:49 PM, Craig Russell  wrote:
> 
> The recent change to add more reject options seems to have broken the reject 
> flow.
> 
> Upload public key should not be in the reject tab because the file can still 
> be processed. But other reasons in the reject tab should remove the item, and 
> the accept icla should remove the item.
> 
> Can you please review the logic to be sure it didn't change anything it 
> should not?
> 
> Thanks,
> Craig
> 
> Craig L Russell
> c...@apache.org
> 

Craig L Russell
c...@apache.org

Secretary workbench doesn't remove rejected items

[Craig Russell]

The recent change to add more reject options seems to have broken the reject 
flow.

Upload public key should not be in the reject tab because the file can still be 
processed. But other reasons in the reject tab should remove the item, and the 
accept icla should remove the item.

Can you please review the logic to be sure it didn't change anything it should 
not?

Thanks,
Craig

Craig L Russell
c...@apache.org

Re: [whimsy] branch master updated: Show rejects in separate tab

[Craig Russell]

Hi Sebb,

This is a big improvement (once I figured out you made a change... ;-)

I'll work on PR to add some other "reject" buttons.

Thanks,
Craig

> On Feb 16, 2022, at 6:06 AM, s...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> sebb 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 6c4fdb0  Show rejects in separate tab
> 6c4fdb0 is described below
> 
> commit 6c4fdb08936f8ee2dc57d3f60661757a7150b130
> Author: Sebb 
> AuthorDate: Wed Feb 16 14:06:25 2022 +
> 
>Show rejects in separate tab
> 
>Gives more space for choices
> ---
> www/secretary/workbench/views/parts.js.rb | 46 +--
> 1 file changed, 26 insertions(+), 20 deletions(-)
> 
> diff --git a/www/secretary/workbench/views/parts.js.rb 
> b/www/secretary/workbench/views/parts.js.rb
> index dd40f9f..2adb240 100644
> --- a/www/secretary/workbench/views/parts.js.rb
> +++ b/www/secretary/workbench/views/parts.js.rb
> @@ -96,9 +96,12 @@ class Parts < Vue
> headers: @headers
> 
>   _ul.nav.nav_tabs do
> -_li class: ('active' unless %i[edit mail].include?(@form)) do
> +_li class: ('active' unless %i[edit mail reject].include?(@form)) do
>   _a 'Categorize', onMousedown: self.tabSelect
> end
> +_li class: ('active' if @form == :reject) do
> +  _a 'Reject', onMousedown: self.tabSelect
> +end
> _li class: ('active' if @form == :edit) do
>   _a 'Edit', onMousedown: self.tabSelect
> end
> @@ -151,6 +154,28 @@ class Parts < Vue
> 
>   _hr
> 
> +  _label do
> +_input type: 'radio', name: 'doctype', value: 'forward',
> +  onClick: -> {@form = Forward}
> +_span 'forward email'
> +  end
> +
> +  _hr
> +
> +  _label do
> +_input type: 'radio', name: 'doctype', value: 'forward',
> +  onClick: -> {@form = Note}
> +if @headers&.secmail&.notes
> +  _span 'edit note'
> +else
> +  _span 'add note'
> +end
> +  end
> +end
> +
> +  elsif @form == :reject
> +
> +_div.doctype do
>   _h4 'Reject email with message:'
> 
>   # reject message with message
> @@ -213,25 +238,6 @@ class Parts < Vue
> 
>   end
> 
> -  _hr
> -
> -  _label do
> -_input type: 'radio', name: 'doctype', value: 'forward',
> -  onClick: -> {@form = Forward}
> -_span 'forward email'
> -  end
> -
> -  _hr
> -
> -  _label do
> -_input type: 'radio', name: 'doctype', value: 'forward',
> -  onClick: -> {@form = Note}
> -if @headers&.secmail&.notes
> -  _span 'edit note'
> -else
> -  _span 'add note'
> -end
> -  end
> end
> 
>   elsif @form == :edit

Craig L Russell
c...@apache.org

Re: Unable to file CCLA

[Craig Russell]

Hi Sebb,

All fixed. Thanks for your incredibly fast response.

Warm regards,
Craig

> On Dec 16, 2021, at 1:01 PM, sebb  wrote:
> 
> Hopefully now fixed
> 
> On Thu, 16 Dec 2021 at 20:16, sebb  wrote:
>> 
>> On Thu, 16 Dec 2021 at 20:00, Craig Russell  wrote:
>>> 
>>> Is this related to the svn permissions issue?
>> 
>> Most likely.
>> 
>> I thought I had found all such references; obviously not.
>> 
>> I'll see what I can do.
>> 
>>> #>> /srv/svn/cclas.txt>
>>> /x1/srv/whimsy/lib/whimsy/asf/svn.rb:983:in `mtime'
>>> /x1/srv/whimsy/lib/whimsy/asf/svn.rb:983:in `getlisting'
>>> /x1/srv/whimsy/lib/whimsy/asf/documents.rb:13:in `listnames'
>>> /x1/srv/whimsy/lib/whimsy/asf/documents.rb:19:in `exist?'
>>> /x1/srv/whimsy/www/secretary/workbench/views/actions/ccla.json.rb:18:in 
>>> `_evaluate'
>>> /x1/srv/whimsy/www/secretary/workbench/server.rb:130:in `block in >> (required)>'
>>> /x1/srv/whimsy/lib/whimsy/asf/rack.rb:222:in `call'
>>> /var/lib/gems/2.7.0/gems/passenger-6.0.5/src/ruby_supportlib/phusion_passenger/rack/out_of_band_gc.rb:48:in
>>>  `call'
>>> /x1/srv/whimsy/lib/whimsy/asf/rack.rb:147:in `call'
>>> /x1/srv/whimsy/lib/whimsy/asf/rack.rb:78:in `call'
>>> /x1/srv/whimsy/lib/whimsy/asf/rack.rb:253:in `call'
>>> /var/lib/gems/2.7.0/gems/passenger-6.0.5/src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:107:in
>>>  `process_request'
>>> /var/lib/gems/2.7.0/gems/passenger-6.0.5/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.5/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:110:in
>>>  `main_loop'
>>> /var/lib/gems/2.7.0/gems/passenger-6.0.5/src/ruby_supportlib/phusion_passenger/request_handler.rb:415:in
>>>  `block (3 levels) in start_threads'
>>> /var/lib/gems/2.7.0/gems/passenger-6.0.5/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

Unable to file CCLA

[Craig Russell]

Is this related to the svn permissions issue?

#
/x1/srv/whimsy/lib/whimsy/asf/svn.rb:983:in `mtime'
/x1/srv/whimsy/lib/whimsy/asf/svn.rb:983:in `getlisting'
/x1/srv/whimsy/lib/whimsy/asf/documents.rb:13:in `listnames'
/x1/srv/whimsy/lib/whimsy/asf/documents.rb:19:in `exist?'
/x1/srv/whimsy/www/secretary/workbench/views/actions/ccla.json.rb:18:in 
`_evaluate'
/x1/srv/whimsy/www/secretary/workbench/server.rb:130:in `block in '
/x1/srv/whimsy/lib/whimsy/asf/rack.rb:222:in `call'
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/ruby_supportlib/phusion_passenger/rack/out_of_band_gc.rb:48:in
 `call'
/x1/srv/whimsy/lib/whimsy/asf/rack.rb:147:in `call'
/x1/srv/whimsy/lib/whimsy/asf/rack.rb:78:in `call'
/x1/srv/whimsy/lib/whimsy/asf/rack.rb:253:in `call'
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:107:in
 `process_request'
/var/lib/gems/2.7.0/gems/passenger-6.0.5/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.5/src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:110:in
 `main_loop'
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/ruby_supportlib/phusion_passenger/request_handler.rb:415:in
 `block (3 levels) in start_threads'
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/ruby_supportlib/phusion_passenger/utils.rb:113:in
 `block in create_thread_and_abort_on_exception'
Craig L Russell
c...@apache.org

Re: Impossible duplicate found

[Craig Russell]

Hi Sebb,

From: "zcq" Subject: Re: SIGN ICLADate: 2021-11-09 21:47 
-08:00



From: Guillermo Cruz Subject: Re: 
Invitation to become Allura committer and PMC memberDate:
> 2021-10-27 08:52 -07:00


I don't recall the "duplicate" ICLA that was found. My guess is that only the 
first possible duplicate is displayed.

Would it be possible to make a log entry with the possible duplicates so we can 
more easily figure out what's going on?

Perhaps we can discuss the algo that you use to detect possible duplicates. Has 
it changed recently?

Thanks,
Craig

> On Nov 9, 2021, at 3:21 PM, sebb  wrote:
> 
> On Tue, 9 Nov 2021 at 22:47, Craig Russell  wrote:
>> 
>> Hi,
>> 
>> While filing a new ICLA, I got:
>> Warning: Found possible duplicate ICLAs:
>> Zhu Zhu
>> 
>> There is no reason for this to be flagged as a possible duplicate. Maybe the 
>> possible duplicate check needs some tweaking?
> 
> You'll need to provide a bit more context in order to investigate.
> For example the exact timestamp of the email, or the hex hash used by
> the secretary workbench.
> I don't think either of them reveal any PII.
> 
> Note also that the check is deliberately cautious: it is better to
> flag a possible duplicate than to ignore an actual duplicate.
> 
>> Regards,
>> Craig
>> 
>> Craig L Russell
>> c...@apache.org
>> 

Craig L Russell
c...@apache.org

Re: Emeritus requests no longer link to roster/committer

[Craig Russell]

Hi Sebb,

Thanks for fixing this. I've processed the pending emeritus request.

Can you please remind me how long it takes for whimsy/roster/committers to show 
the changed status?

Thanks,
Craig

> On Nov 10, 2021, at 2:55 PM, sebb  wrote:
> 
> On Wed, 10 Nov 2021 at 01:39, Craig Russell  <mailto:apache@gmail.com>> wrote:
>> 
>> Hi,
>> 
>> When we first set up emeritus request handling, a filed emeritus request 
>> would be presented in the secretary workbench as a line item which when 
>> clicked, would jump to the roster/committer page for the emeritus requestor.
>> 
>> It no longer does this, but requires the secretary to manually jump off the 
>> workbench to make the request.
>> 
>> Can the old behavior please be restored?
> 
> Not sure how this happened, but the date value was missing, so
> although the link was present, there was nothing to click.
> Should be OK now.
> 
>> Thanks,
>> Craig
>> 
>> Craig L Russell
>> c...@apache.org <mailto:c...@apache.org>
Craig L Russell
c...@apache.org

Emeritus requests no longer link to roster/committer

[Craig Russell]

Hi,

When we first set up emeritus request handling, a filed emeritus request would 
be presented in the secretary workbench as a line item which when clicked, 
would jump to the roster/committer page for the emeritus requestor.

It no longer does this, but requires the secretary to manually jump off the 
workbench to make the request.

Can the old behavior please be restored?

Thanks,
Craig

Craig L Russell
c...@apache.org

Impossible duplicate found

[Craig Russell]

Hi,

While filing a new ICLA, I got:
Warning: Found possible duplicate ICLAs: 
Zhu Zhu

There is no reason for this to be flagged as a possible duplicate. Maybe the 
possible duplicate check needs some tweaking?

Regards,
Craig

Craig L Russell
c...@apache.org

Fwd: foundation: r104179 - /foundation/emeritus-request.txt

[Craig Russell]

Hi Sebb,

Details, please. What bit of whimsy uses this file?

Thanks,
Craig

> Begin forwarded message:
> 
> From: s...@apache.org
> Subject: foundation: r104179 - /foundation/emeritus-request.txt
> Date: October 28, 2021 at 3:35:37 PM PDT
> To: foundation-comm...@apache.org
> Reply-To: bo...@apache.org
> 
> Author: sebb
> Date: Thu Oct 28 22:35:37 2021
> New Revision: 104179
> 
> Log:
> Restore file needed by WHimsy
> 
> Added:
>foundation/emeritus-request.txt
>  - copied unchanged from r103518, foundation/emeritus-request.txt
> 

Craig L Russell
c...@apache.org

Subprojects not listed at https://whimsy.apache.org/site/

[Craig Russell]

The policy https://www.apache.org/foundation/marks/pmcs#navigation refers to 
subprojects as well as projects.

> Whatever main navigation system your project website uses, it must feature 
> certain text links back to key pages on the main www.apache.org website. 
> These links can appear in whatever main navigation system your site uses on 
> all top level pages for the project or subproject.

I looked at the source code for the page which refers to code on 
https://github.com/apache/whimsy/blob/master/lib/whimsy/sitestandards.rb but I 
cannot see how to get the code to look at subprojects.

For example, https://db.apache.org/jdo/ is clearly the top level page for the 
DB JDO subproject. How do we include this page in the web site compliance scan?

We might need some additional metadata for the 100 or so subprojects that do 
not appear in committee-info.txt.

Thanks,
Craig

Craig L Russell
c...@apache.org

Bug/feature in secretary workbench

[Craig Russell]

We received a document containing two different images with the same name 
image.jpeg.

When processing via "pdf-ize" both images again have the same name image.pdf. 
The images cannot be combined and there is no option to rename one of the 
images.

Craig

Craig L Russell
c...@apache.org

Re: Invitation to become Mesos committer and PMC member: Charles-François Natali

[Craig Russell]

Can we get this (*) information opened up to PMC members of the project, or if 
that's just too much, at least open to the PMC chair of the project?

It's important information for the PMC members to know.

Thanks,
Craig

> On Aug 10, 2021, at 1:28 PM, sebb  wrote:
> 
> Currently only ASF members can see this information
> 
> On Tue, 10 Aug 2021 at 14:45, Craig Russell  wrote:
> 
>> Qian (PMC chair) is having trouble seeing the member(*) flags for members
>> not subscribed to the mesos private@ mail list.
>> 
>> Is this information not visible to PMC chairs?
>> 
>> Thanks,
>> Craig
>> 
>> 

Craig L Russell
c...@apache.org

Fwd: Invitation to become Mesos committer and PMC member: Charles-François Natali

[Craig Russell]

Qian (PMC chair) is having trouble seeing the member(*) flags for members not 
subscribed to the mesos private@ mail list.

Is this information not visible to PMC chairs? 

Thanks,
Craig

> Begin forwarded message:
> 
> From: Qian Zhang 
> Subject: Re: Invitation to become Mesos committer and PMC member: 
> Charles-François Natali
> Date: August 10, 2021 at 1:42:22 AM PDT
> To: Craig Russell 
> 
> Hi Craig,
> 
> I have logged in https://whimsy.apache.org/roster/committee/mesos 
> <https://whimsy.apache.org/roster/committee/mesos>.
> 
> 
> 
> And after logging in, this is what I see:
> 
> 
> 
> Regards,
> Qian Zhang
> 



Craig L Russell
c...@apache.org

Re: [GitHub] [whimsy] sebbASF commented on pull request #120: Family First support in secretary workbench

[Craig Russell]

tl;dr This patch is ready to merge but sebb wants to veto it.

https://github.com/apache/whimsy/pull/120

The family-first checkbox and family-first form field in secretary workbench 
are useful for us to detect earlier than we do today a possible conflict in 
names of ICLA submitters. 

This handy tool (thanks, sebb) shows that there are many cases where we have 
accepted ICLAs from people ostensibly with the same names:
https://whimsy.apache.org/secretary/icla-dupes

We have not had a consistent policy for handling people with the same names, 
and we should do so. I'd suggest a different thread for that discussion.

But not having a policy is not a good reason to not know that we have a 
conflict.

I've commented out the visible part of the tool that initializes LDAP fields 
from the public name, in case we sometime in future want to provide better 
values than what we do now.

As it is now, we have hundreds of cases where the LDAP name fields are 
inexplicable. This patch does not fix these cases.

Please discuss.

Craig

> On Aug 7, 2021, at 3:03 PM, GitBox  wrote:
> 
> 
> sebbASF commented on pull request #120:
> URL: https://github.com/apache/whimsy/pull/120#issuecomment-894711513
> 
> 
>   In case it is not obvious, I am -1 on applying this PR without a clear 
> explanation of the benefit.
> 
> 
> -- 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
> 
> To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org
> 
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> 
> 

Craig L Russell
c...@apache.org

Re: [GitHub] [whimsy] clr-apache commented on pull request #120: Family First support in secretary workbench

[Craig Russell]

I'd appreciate it if you all could take a look at the changes to secretary 
workbench.

If you're on the family-first branch I've been testing using config/setupmymac 
and the code works just as I like it to.

Future improvements can include delegating the LDAP sn and givenName to methods 
in lib/person.rb. 

But the family-first branch includes all the code necessary to properly handle 
the family first check box in the proposed ICLA.

Please review and comment. Unless there are other conflicts, this is ready to 
squash and merge.

Thanks,
Craig


> On Aug 7, 2021, at 1:20 PM, GitBox  wrote:
> 
> 
> clr-apache commented on pull request #120:
> URL: https://github.com/apache/whimsy/pull/120#issuecomment-894702891
> 
> 
>   The family first flag allows for the ICLA submitter to tell secretary that 
> the names are culturally consistent. Secretary can then create the file name 
> consistent with the current standard -. And in 
> future, when secretary can directly create accounts, the givenName and sn can 
> be consistent.
> 
>   Craig
> 
>> On Aug 7, 2021, at 1:17 PM, sebbASF ***@***.***> wrote:
>> 
>> 
>> What is the use-case for this, now that the workbench does checks for name 
>> clashes?
>> 
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub 
>> , or 
>> unsubscribe 
>> .
>> Triage notifications on the go with GitHub Mobile for iOS 
>> 
>>  or Android 
>> .
>> 
> 
>   Craig L Russell
>   ***@***.***
> 
> 
> 
> 
> -- 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
> 
> To unsubscribe, e-mail: dev-unsubscr...@whimsical.apache.org
> 
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> 
> 

Craig L Russell
c...@apache.org

Re: Testing secretary workbench

[Craig Russell]

Good news. Thanks to Sam for working with me to get my local environment back 
to where I can usefully test the family-first ICLA. I still have 
issues/questions that I'll raise in another thread.

I also will try Sebb's suggestions to import new test ICLAs into my testing 
environment.

Thanks,
Craig

> On Aug 5, 2021, at 9:42 AM, Sam Ruby  wrote:
> 
> Perhaps at some point we should have a zoom call and you can share
> your screen and we can explore it together.  Ping me on slack if this
> interests you.
> 
> Meanwhile, did setupmymac complete successfully?
> 
> Can you try the following command from the
> /srv/whimsy/www/secretary/workbench directory?
> 
> $ bundle update
> 
> If that doesn't work, you won't have the gems installed you need to
> run the workbench.
> 
> ---
> 
> Some background on the "auto update issue".
> 
> Bundle update will update you to nokogiri 1.12.2 (which was recently
> updated to include nokogumbo) and no separate nokogumbo.
> Unfortunately, wunderbar version 1.4.5 still looks for nokogumbo and
> will fail if it isn't present.  Solutions are to either pin nokogiri
> to 1.11 (NOT RECOMMENDED) or to update wunderbar to 1.5.0
> (RECOMMENDED).
> 
> This is the danger of doing bundle update to get the latest of most
> things, but selectively pinning other things.  Eventually, you will
> get out of sync.
> 
> There are two sane approaches to this problem: (1) have the server run
> bundle update, try to stay up to date, report and regressions promptly
> and see to it that the regressions are added to the test suite, or (2)
> have the server run bundle install, check in Gemfile.lock and don't
> allow any updates (including security updates!) until a whimsy
> developer runs bundle update on their machine and checks in the
> updated Gemfile.lock file.
> 
> I prefer the first option as getting a bug report that "version n
> released yesterday introduced a regression" is much easier to debug
> than "some version released in the past n months introduced a
> regression".  But honestly, either approach is preferable to the
> broken approach that whimsy had been using since late last year.
> 
> - Sam Ruby
> 
> On Wed, Aug 4, 2021 at 11:14 PM Craig Russell  <mailto:apache@gmail.com>> wrote:
>> 
>> Still looking for some help here. The error reported from the completion of 
>> setupmymac points to ruby2js strange error. Is this perhaps related to the 
>> auto-update issue being discussed else-thread?
>> 
>> Is there some reason that ruby2js must be === 3.6.0?
>> Raw Bundler exception
>> 
>> Exception message:
>> 
>> Could not find gem 'ruby2js (= 3.6.0)' in rubygems repository 
>> https://rubygems.org/ or installed locally.
>> The source contains the following versions of 'ruby2js': 3.2.0, 4.1.4 
>> (Bundler::GemNotFound)
>> Any help will be rewarded in kind(ness).
>> Craig
>> 
>>> On Aug 3, 2021, at 7:57 PM, Craig Russell  wrote:
>>> 
>>> I think Apple has indicated their intent to discontinue ruby as a 
>>> system-provided tool.
>>> 
>>> macOS Catalina 10.15 Release Notes
>>> Scripting Language Runtimes
>>> Deprecations
>>> Scripting language runtimes such as Python, Ruby, and Perl are included in 
>>> macOS for compatibility with legacy software. Future versions of macOS 
>>> won’t include scripting language runtimes by default, and might require you 
>>> to install additional packages. If your software depends on scripting 
>>> languages, it’s recommended that you bundle the runtime within the app. 
>>> (49764202)
>>> 
>>> 
>>> 
>>>> On Aug 3, 2021, at 3:25 PM, Sam Ruby >>> <mailto:ru...@intertwingly.net> <mailto:ru...@intertwingly.net 
>>>> <mailto:ru...@intertwingly.net>>> wrote:
>>>> 
>>>> On Tue, Aug 3, 2021 at 3:32 PM Craig Russell >>> <mailto:apache@gmail.com> <mailto:apache@gmail.com 
>>>> <mailto:apache@gmail.com>>> wrote:
>>>>> 
>>>>> [MacBook-Pro-10:~] clr% head -1 `which bundle`
>>>>> #!/usr/local/opt/ruby/bin/ruby
>>>>> [MacBook-Pro-10:~] clr% head -1 `which gem`
>>>>> #!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
>>>> 
>>>> Unless you have a reason to want two versions of Ruby, I would
>>>> recommend that you stick with the system installed version.  You
>>>> should be able to remove the non-system installed Ruby using:
>>>> 
>>>> $ brew uninstall ruby
>>>> 
>>>> Whether or not you want to do that (and whether or not removing it
>>>> works) Try to install/overwrite bundler:
>>>> 
>>>> $ sudo gem install bundler
>>>> 
>>>> If this works (i.e., the two commands at the top of this email
>>>> starting with "head -1" now return the same results), try rerunning
>>>> setupmymac.
>>> 
>>> I'll try that. I guess if Apple ever does get rid of ruby I can easily 
>>> reinstall it.
>>> 
>>> Craig
>>>> 
>>>> - Sam Ruby
>>> 
>>> Craig L Russell
>>> c...@apache.org <mailto:c...@apache.org> <mailto:c...@apache.org 
>>> <mailto:c...@apache.org>>
>> Craig L Russell
>> c...@apache.org <mailto:c...@apache.org>
Craig L Russell
c...@apache.org

Re: Testing secretary workbench

[Craig Russell]

Hi Sam,

> On Aug 5, 2021, at 9:42 AM, Sam Ruby  wrote:
> 
> Perhaps at some point we should have a zoom call and you can share
> your screen and we can explore it together.  Ping me on slack if this
> interests you.

That sounds like a great idea. I've sent you a DM on Slack.
> 
> Meanwhile, did setupmymac complete successfully?

No. It runs for an hour and then fails.
> 
> Can you try the following command from the
> /srv/whimsy/www/secretary/workbench directory?
> 
> $ bundle update

No luck there either. 
> 
> If that doesn't work, you won't have the gems installed you need to
> run the workbench.

Seems to be a theme:
vi 
/private/var/whimsy/whimsy/www/secretary/workbench/vendor/bundle/ruby/2.6.0/extensions/universal-darwin-19/2.6.0/ffi-1.15.3/mkmf.log

"pkg-config --exists libffi"
| pkg-config --libs libffi
=> "-L/opt/local/lib -lffi \n"
"xcrun clang -o conftest 
-I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin19
 
-I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/backward
 
-I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0
 -I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT 
   -g -Os -pipe -DHAVE_GCC_ATOMIC_BUILTINS conftest.c  -L. 
-L/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib -L. 
-L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.Internal.sdk/usr/local/lib
   -arch x86_64   -lruby.2.6   "
In file included from conftest.c:1:
In file included from 
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby.h:33:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:24:10:
 fatal error: 'ruby/config.h' file not found
#include "ruby/config.h"
 ^~~
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:24:10:
 note: did not find header 'config.h' in framework 'ruby' (loaded from 
'/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks')
1 error generated.
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main(int argc, char **argv)
4: {
5:   return 0;
6: }
/* end */
> 
> ---
> 
> Some background on the "auto update issue".
> 
> Bundle update will update you to nokogiri 1.12.2 (which was recently
> updated to include nokogumbo) and no separate nokogumbo.
> Unfortunately, wunderbar version 1.4.5 still looks for nokogumbo and
> will fail if it isn't present.  Solutions are to either pin nokogiri
> to 1.11 (NOT RECOMMENDED) or to update wunderbar to 1.5.0
> (RECOMMENDED).
> 
> This is the danger of doing bundle update to get the latest of most
> things, but selectively pinning other things.  Eventually, you will
> get out of sync.
> 
> There are two sane approaches to this problem: (1) have the server run
> bundle update, try to stay up to date, report and regressions promptly
> and see to it that the regressions are added to the test suite, or (2)
> have the server run bundle install, check in Gemfile.lock and don't
> allow any updates (including security updates!) until a whimsy
> developer runs bundle update on their machine and checks in the
> updated Gemfile.lock file.
> 
> I prefer the first option as getting a bug report that "version n
> released yesterday introduced a regression" is much easier to debug
> than "some version released in the past n months introduced a
> regression".  But honestly, either approach is preferable to the
> broken approach that whimsy had been using since late last year.
> 
> - Sam Ruby
> 
> On Wed, Aug 4, 2021 at 11:14 PM Craig Russell  <mailto:apache@gmail.com>> wrote:
>> 
>> Still looking for some help here. The error reported from the completion of 
>> setupmymac points to ruby2js strange error. Is this perhaps related to the 
>> auto-update issue being discussed else-thread?
>> 
>> Is there some reason that ruby2js must be === 3.6.0?
>> Raw Bundler exception
>> 
>> Exception message:
>> 
>> Could not find gem 'ruby2js (= 3.6.0)' in rubygems repository 
>> https://rubygems.org/ or installed locally.
>> The source contains the following versions of 'ruby2js': 3.2.0, 4.1.4 
>> (Bundler::GemNotFound)
>> Any help will be rewarded in kind(ness).
>> Craig
>> 
>>> On Au

Re: Testing secretary workbench

[Craig Russell]

Still looking for some help here. The error reported from the completion of 
setupmymac points to ruby2js strange error. Is this perhaps related to the 
auto-update issue being discussed else-thread?

Is there some reason that ruby2js must be === 3.6.0?
Raw Bundler exception

Exception message:

Could not find gem 'ruby2js (= 3.6.0)' in rubygems repository 
https://rubygems.org/ or installed locally.
The source contains the following versions of 'ruby2js': 3.2.0, 4.1.4 
(Bundler::GemNotFound)
Any help will be rewarded in kind(ness).
Craig

> On Aug 3, 2021, at 7:57 PM, Craig Russell  wrote:
> 
> I think Apple has indicated their intent to discontinue ruby as a 
> system-provided tool.
> 
> macOS Catalina 10.15 Release Notes
> Scripting Language Runtimes
> Deprecations
> Scripting language runtimes such as Python, Ruby, and Perl are included in 
> macOS for compatibility with legacy software. Future versions of macOS won’t 
> include scripting language runtimes by default, and might require you to 
> install additional packages. If your software depends on scripting languages, 
> it’s recommended that you bundle the runtime within the app. (49764202)
> 
> 
> 
>> On Aug 3, 2021, at 3:25 PM, Sam Ruby > <mailto:ru...@intertwingly.net>> wrote:
>> 
>> On Tue, Aug 3, 2021 at 3:32 PM Craig Russell > <mailto:apache@gmail.com>> wrote:
>>> 
>>> [MacBook-Pro-10:~] clr% head -1 `which bundle`
>>> #!/usr/local/opt/ruby/bin/ruby
>>> [MacBook-Pro-10:~] clr% head -1 `which gem`
>>> #!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
>> 
>> Unless you have a reason to want two versions of Ruby, I would
>> recommend that you stick with the system installed version.  You
>> should be able to remove the non-system installed Ruby using:
>> 
>> $ brew uninstall ruby
>> 
>> Whether or not you want to do that (and whether or not removing it
>> works) Try to install/overwrite bundler:
>> 
>> $ sudo gem install bundler
>> 
>> If this works (i.e., the two commands at the top of this email
>> starting with "head -1" now return the same results), try rerunning
>> setupmymac.
> 
> I'll try that. I guess if Apple ever does get rid of ruby I can easily 
> reinstall it.
> 
> Craig
>> 
>> - Sam Ruby
> 
> Craig L Russell
> c...@apache.org <mailto:c...@apache.org>
Craig L Russell
c...@apache.org

Error starting web application secretary workbench

[Craig Russell]

Anyone else seeing this on https://whimsy.apache.org/secretary/workbench/ ?

Error starting web application

The Phusion Passenger application server tried to start the web application. 
But the application itself (and not Passenger) encountered an internal error.

Error details:

cannot load such file -- nokogumbo (LoadError)
  /var/lib/gems/2.7.0/gems/wunderbar-1.4.5/lib/wunderbar/render.rb:9:in 
`require'
  /var/lib/gems/2.7.0/gems/wunderbar-1.4.5/lib/wunderbar/render.rb:9:in `'
  /var/lib/gems/2.7.0/gems/wunderbar-1.4.5/lib/wunderbar/vue.rb:1:in `require'
  /var/lib/gems/2.7.0/gems/wunderbar-1.4.5/lib/wunderbar/vue.rb:1:in `'
  /x1/srv/whimsy/www/secretary/workbench/server.rb:7:in `require'
  /x1/srv/whimsy/www/secretary/workbench/server.rb:7:in `'
  config.ru:1:in `require'
  config.ru:1:in `block in '
  /var/lib/gems/2.7.0/gems/rack-2.2.3/lib/rack/builder.rb:125:in `instance_eval'
  /var/lib/gems/2.7.0/gems/rack-2.2.3/lib/rack/builder.rb:125:in `initialize'
  config.ru:1:in `new'
  config.ru:1:in `'
  
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:101:in
 `eval'
  
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:101:in
 `preload_app'
  
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:189:in
 `block in '
  
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/ruby_supportlib/phusion_passenger/loader_shared_helpers.rb:378:in
 `run_block_and_record_step_progress'
  
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:188:in
 `'
  
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:30:in
 `'
  
/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:29:in
 `'
The stdout/stderr output of the subprocess so far is:

Error: The application encountered the following error: cannot load such file 
-- nokogumbo (LoadError)
/var/lib/gems/2.7.0/gems/wunderbar-1.4.5/lib/wunderbar/render.rb:9:in 
`require'
/var/lib/gems/2.7.0/gems/wunderbar-1.4.5/lib/wunderbar/render.rb:9:in `'
/var/lib/gems/2.7.0/gems/wunderbar-1.4.5/lib/wunderbar/vue.rb:1:in `require'
/var/lib/gems/2.7.0/gems/wunderbar-1.4.5/lib/wunderbar/vue.rb:1:in `'
/x1/srv/whimsy/www/secretary/workbench/server.rb:7:in `require'
/x1/srv/whimsy/www/secretary/workbench/server.rb:7:in `'
config.ru:1:in `require'
config.ru:1:in `block in '
/var/lib/gems/2.7.0/gems/rack-2.2.3/lib/rack/builder.rb:125:in 
`instance_eval'
/var/lib/gems/2.7.0/gems/rack-2.2.3/lib/rack/builder.rb:125:in `initialize'
config.ru:1:in `new'
config.ru:1:in `'

/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:101:in
 `eval'

/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:101:in
 `preload_app'

/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:189:in
 `block in '

/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/ruby_supportlib/phusion_passenger/loader_shared_helpers.rb:378:in
 `run_block_and_record_step_progress'

/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:188:in
 `'

/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:30:in
 `'

/var/lib/gems/2.7.0/gems/passenger-6.0.5/src/helper-scripts/rack-preloader.rb:29:in
 `'
This website is powered by Phusion Passenger®, the smart application server 
built by Phusion®.
Craig L Russell
c...@apache.org

Re: Testing secretary workbench

[Craig Russell]

Thanks for the suggestion. My .cshrc was pointing to PATH 
/usr/local/opt/ruby/bin:/usr/local/lib/ruby/gems/2.7.0/bin so I removed them 
from PATH. Now both gem and bundler are coming from the system.

Still no joy. [1]

Many errors after that one, with the errors not making sense. For example,
An error occurred while installing redcarpet (3.5.1), and Bundler cannot 
continue.

In Gemfile:
  redcarpet
Fetching gem metadata from https://rubygems.org/...
Resolving dependencies...
Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
bundler (~> 1.3)

  Current Bundler version:
bundler (2.2.25)

Your bundle requires a different version of Bundler than the one you're running.
Install the necessary version with `gem install bundler:1.17.3` and rerun 
bundler using `bundle _1.17.3_ update`

Any ideas?

Thanks,
Craig

[1]
Last login: Tue Aug  3 12:28:24 on ttys020
[MacBook-Pro-10:~] clr% head -1 `which gem`
#!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
[MacBook-Pro-10:~] clr% head -1 `which bundle`
#!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
[MacBook-Pro-10:~] clr% cd /srv/whimsy
whimsy-so-old/ whimsy/
[MacBook-Pro-10:~] clr% cd /srv/whimsy
[MacBook-Pro-10:/srv/whimsy] clr% git pull
Enter passphrase for key '/Users/clr/.ssh/id_rsa': 
remote: Enumerating objects: 61, done.
remote: Counting objects: 100% (61/61), done.
remote: Compressing objects: 100% (34/34), done.
remote: Total 61 (delta 44), reused 44 (delta 27), pack-reused 0
Unpacking objects: 100% (61/61), done.
From github.com:apache/whimsy
   a28206d9..f95c56af  master -> origin/master
Already up to date.
[MacBook-Pro-10:/srv/whimsy] clr% config/setupmymac 
CONFIGURE.md   DOCKER.md  MACOSX.md  Rakefile   
UBUNTU.md  config/examples/  repository.yml 
tools/ wunderbar.version 
DEPLOYMENT.md  GemfileNOTICE SETUPMYMAC.md  
asf.gemspecdoap_Whimsy.rdfimages/ruby2js.version
vagrant/   www/
DEVELOPMENT.md LICENSEREADME.md  TODOS.md   
asf.versiondocker/lib/   secmail.py 
vendor/
[MacBook-Pro-10:/srv/whimsy] clr% config/setupmymac 

$ rake update
Fetching gem metadata from https://rubygems.org/...
Resolving dependencies...
Using builder 3.2.4
Using bundler 2.2.25
Using concurrent-ruby 1.1.9
Using rack 2.2.3
Using rdoc 6.3.2
Fetching json 2.5.1
Using tzinfo 2.0.4
Fetching racc 1.5.2
Fetching ruby-ldap 0.9.20
Using tzinfo-data 1.2021.1
Installing ruby-ldap 0.9.20 with native extensions
Installing json 2.5.1 with native extensions
Installing racc 1.5.2 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

current directory: 
/private/var/whimsy/whimsy/tools/vendor/bundle/ruby/2.6.0/gems/json-2.5.1/ext/json/ext/generator
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby -I 
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0 -r 
./siteconf20210804-96155-1idqfwm.rb extconf.rb
creating Makefile

current directory: 
/private/var/whimsy/whimsy/tools/vendor/bundle/ruby/2.6.0/gems/json-2.5.1/ext/json/ext/generator
make "DESTDIR=" clean

current directory: 
/private/var/whimsy/whimsy/tools/vendor/bundle/ruby/2.6.0/gems/json-2.5.1/ext/json/ext/generator
make "DESTDIR="
compiling generator.c
In file included from generator.c:1:
In file included from ./../fbuffer/fbuffer.h:5:
In file included from 
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby.h:33:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:24:10:
 fatal error: 'ruby/config.h' file not found
#include "ruby/config.h"
 ^~~
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:24:10:
 note: did not find header 'config.h' in framework
'ruby' (loaded from 
'/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks')
1 error generated.
make: *** [generator.o] Error 1

make failed, exit code 2

Gem files will remain installed in 
/private/var/whimsy/whimsy/tools/vendor/bundle/ruby/2.6.0/gems/json-2.5.1 for 
inspection.
Results logged to 
/private/var/whimsy/whimsy/tools/vendor/bundle/ruby/2.6.0/extensions/universal-darwin-19/2.6.0/json-2.5.1/gem_make.out


> On Aug 2, 2021, at 12:42 PM, Sam Ruby  wrote:
> 
> On Mon, Aug 2, 2021 at 2:10 PM Roy T. Fielding  wrote:
>> 
>> On Aug 1, 2021, at 4:47 PM, Sam Ruby  wrote:
>>> My experience is that reinstalling xcode-select is sometimes
>>> necessary, but solves the problem.  Unfortunately, this hasn't worked
>>> for you.
>> 
>> I had to do that recently as well in order to get brew 

Re: Testing secretary workbench

[Craig Russell]

I think Apple has indicated their intent to discontinue ruby as a 
system-provided tool.

macOS Catalina 10.15 Release Notes
Scripting Language Runtimes
Deprecations
Scripting language runtimes such as Python, Ruby, and Perl are included in 
macOS for compatibility with legacy software. Future versions of macOS won’t 
include scripting language runtimes by default, and might require you to 
install additional packages. If your software depends on scripting languages, 
it’s recommended that you bundle the runtime within the app. (49764202)



> On Aug 3, 2021, at 3:25 PM, Sam Ruby  wrote:
> 
> On Tue, Aug 3, 2021 at 3:32 PM Craig Russell  wrote:
>> 
>> [MacBook-Pro-10:~] clr% head -1 `which bundle`
>> #!/usr/local/opt/ruby/bin/ruby
>> [MacBook-Pro-10:~] clr% head -1 `which gem`
>> #!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
> 
> Unless you have a reason to want two versions of Ruby, I would
> recommend that you stick with the system installed version.  You
> should be able to remove the non-system installed Ruby using:
> 
> $ brew uninstall ruby
> 
> Whether or not you want to do that (and whether or not removing it
> works) Try to install/overwrite bundler:
> 
> $ sudo gem install bundler
> 
> If this works (i.e., the two commands at the top of this email
> starting with "head -1" now return the same results), try rerunning
> setupmymac.

I'll try that. I guess if Apple ever does get rid of ruby I can easily 
reinstall it.

Craig
> 
> - Sam Ruby

Craig L Russell
c...@apache.org

Re: Testing secretary workbench

[Craig Russell]

[MacBook-Pro-10:~] clr% head -1 `which bundle`
#!/usr/local/opt/ruby/bin/ruby
[MacBook-Pro-10:~] clr% head -1 `which gem`
#!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby


So it looks like I'm running mismatched bundle and gem.

Meanwhile, docker install fails. [1]

Recommendations?

Thanks
Craig

[1]Last login: Fri Jul 30 18:18:02 on ttys019
[MacBook-Pro-10:~] clr% mkdir docker-whimsy
[MacBook-Pro-10:~] clr% cd docker-whimsy/
[MacBook-Pro-10:~/docker-whimsy] clr% echo ":root: ." >.whimsy
[MacBook-Pro-10:~/docker-whimsy] clr% cat .whimsy
:root: .
[MacBook-Pro-10:~/docker-whimsy] clr% git clone 
g...@github.com:apache/whimsy.git
Cloning into 'whimsy'...
Enter passphrase for key '/Users/clr/.ssh/id_rsa': 
remote: Enumerating objects: 47694, done.
remote: Counting objects: 100% (1298/1298), done.
remote: Compressing objects: 100% (589/589), done.
remote: Total 47694 (delta 901), reused 1077 (delta 706), pack-reused 46396
Receiving objects: 100% (47694/47694), 8.17 MiB | 4.65 MiB/s, done.
Resolving deltas: 100% (35620/35620), done.
[MacBook-Pro-10:~/docker-whimsy] clr% cd whimsy/
[MacBook-Pro-10:~/docker-whimsy/whimsy] clr% rake docker:update svn:update 
git:pull
docker-compose build web
Building web
[+] Building 888.6s (13/13) FINISHED

   
 => [internal] load build definition from Dockerfile

   0.2s
 => => transferring dockerfile: 2.49kB  

   0.0s
 => [internal] load .dockerignore   

   0.2s
 => => transferring context: 159B   

   0.0s
 => [internal] load metadata for docker.io/library/ubuntu:20.04 

   2.1s
 => [1/8] FROM 
docker.io/library/ubuntu:20.04@sha256:82becede498899ec668628e7cb0ad87b6e1c371cb8a1e597d83a47fac21d6af3
  
8.3s
 => => resolve 
docker.io/library/ubuntu:20.04@sha256:82becede498899ec668628e7cb0ad87b6e1c371cb8a1e597d83a47fac21d6af3
  
0.0s
 => => sha256:1318b700e415001198d1bf66d260b07f67ca8a552b61b0da02b3832c778f221b 
1.46kB / 1.46kB 
0.0s
 => => sha256:16ec32c2132b43494832a05f2b02f7a822479f8250c173d0ab27b3de78b2f058 
28.57MB / 28.57MB   
6.1s
 => => sha256:82becede498899ec668628e7cb0ad87b6e1c371cb8a1e597d83a47fac21d6af3 
1.42kB / 1.42kB 
0.0s
 => => sha256:1e48201ccc2ab83afc435394b3bf70af0fa0055215c1e26a5da9b50a1ae367c9 
529B / 529B 
0.0s
 => => extracting 
sha256:16ec32c2132b43494832a05f2b02f7a822479f8250c173d0ab27b3de78b2f058 

 1.4s
 => [internal] load build context   

   0.0s
 => => transferring context: 13.20kB

   0.0s
 => [2/8] RUN apt-get update && apt-get install -y curl 
software-properties-common apt-utils && curl -sL 
https://deb.nodesource.com/setup_12.x | bash - && echo "deb http://opensou  
821.7s
 => [3/8] RUN echo 'SetEnv GEM_HOME /srv/gems' > 
/etc/apache2/conf-enabled/gemhome.conf  
  0.7s
 => [4/8] RUN DEBIAN_FRONTEND='noninteractive' apt-get install -y vim   

   9.4s 
 => [5/8] RUN DEBIAN_FRONTEND='noninteractive' apt-get install -y ldap-utils
   

Re: Testing secretary workbench

[Craig Russell]

So I had a very old checkout of whimsy in my /srv repository. I cloned a new 
copy and it started the server and opened a web page to whimsy.local. I went to 
secretary/workbench and now just have one small issue. I don't recall how I got 
wunderbar but maybe it's now installed in the wrong place? [2]

And bundle update fails. [1]

I really really do not want to upgrade my machine...

Thanks,
Craig

[1] [MacBook-Pro-10:/srv/whimsy] clr% bundle update
Fetching gem metadata from https://rubygems.org/...
Resolving dependencies...
Using bundler 2.1.4
Using concurrent-ruby 1.1.9
Fetching json 2.5.1
Installing json 2.5.1 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

current directory: 
/private/var/whimsy/whimsy/vendor/bundle/ruby/2.6.0/gems/json-2.5.1/ext/json/ext/generator
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby -I 
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0 -r 
./siteconf20210801-72324-cjkpud.rb extconf.rb
creating Makefile

current directory: 
/private/var/whimsy/whimsy/vendor/bundle/ruby/2.6.0/gems/json-2.5.1/ext/json/ext/generator
make "DESTDIR=" clean

current directory: 
/private/var/whimsy/whimsy/vendor/bundle/ruby/2.6.0/gems/json-2.5.1/ext/json/ext/generator
make "DESTDIR="
compiling generator.c
In file included from generator.c:1:
In file included from ./../fbuffer/fbuffer.h:5:
In file included from 
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby.h:33:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:24:10:
 fatal error: 'ruby/config.h' file not found
#include "ruby/config.h"
 ^~~
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:24:10:
 note: did not find header 'config.h' in
framework 'ruby' (loaded from 
'/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks')
1 error generated.
make: *** [generator.o] Error 1

make failed, exit code 2

Gem files will remain installed in 
/private/var/whimsy/whimsy/vendor/bundle/ruby/2.6.0/gems/json-2.5.1 for 
inspection.
Results logged to 
/private/var/whimsy/whimsy/vendor/bundle/ruby/2.6.0/extensions/universal-darwin-19/2.6.0/json-2.5.1/gem_make.out

An error occurred while installing json (2.5.1), and Bundler cannot continue.
Make sure that `gem install json -v '2.5.1' --source 'https://rubygems.org/'` 
succeeds before bundling.

In Gemfile:
  whimsy-asf was resolved to 0.0.77, which depends on
wunderbar was resolved to 1.4.5, which depends on
  json
[2]
Bundler was unable to find one of the gems defined in the Gemfile
Most common causes  Solution finder
You may not have installed all the gems that this application needs.Read 
solution <>
If the necessary gems are installed, but Bundler may not have permissions to 
access them. 
Bundler tried to load the gems from #.Read 
solution <>
The application may be run under the wrong user account or execution 
environment. 
It is currently running as _www.Read solution <>
The application may be run under the wrong Ruby interpreter. 
It is currently being run under 
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby.Read 
solution <>
Raw Bundler exception

Exception message:

Could not find gem 'wunderbar (= 1.4.5)' in any of the gem sources listed in 
your Gemfile. (Bundler::GemNotFound)


> On Jul 30, 2021, at 8:55 PM, Sam Ruby  wrote:
> 
> On Fri, Jul 30, 2021 at 11:05 PM Craig Russell  wrote:
>> 
>> The setupmymac does run to completion with a bunch of errors but it starts 
>> the server and opens a browser to whimsy.local. From there, I select 
>> secretary workbench and it gives me six emails from 7/14/2020 to 7/17/2020.
> 
> Try the following commands:
> 
> cd /srv/whimsy/www/secretary/workbench
> rake fetch
> 
>> I select one of the messages and it gives me the message processing page and 
>> when I select category (icla) it gives me the icla screen. I know that this 
>> is using very old code because the category has (0) incomplete form but none 
>> of the checkboxes that indicate what is incomplete.
>> 
>> So where it this code getting the icla.js.rb?
> 
> /srv/whimsy/www/secretary/workbench//views/forms/icla.js.rb
> 
> - Sam Ruby
> 
>> 
>> 
>>> On Jul 30, 2021, at 6:06 PM, Sam Ruby  wrote:
>>> 
>>> While I am currently running 11.4, setupmymac was developed using
>>> prior versions of MacOSX.
>>> 
>>> What does "xcode-select -p" return?
>> 
>> 
>> [MacBook-Pro-10:~/apache/foundation