Re: Whimsy down?

I can confirm the problem. Other links that require committer/member creds seem to be OK. However Board is not accepting my LDAP creds On 3 November 2015 at 00:50, John D. Ament wrote: > I just tried to access the board agenda, failed. Confirmed that my LDAP >

Directory listing for /var/www/whimsy/public/ ?

At present, the https://whimsy.apache.org/public directory does not allow its contents to be listed. It would be useful to allow this, and support README/HEADER files Alternatively we could use a hard-coded index.html, but that would have to be maintained.

Re: Additional json files for public directory

On 4 December 2015 at 12:49, Sam Ruby <ru...@intertwingly.net> wrote: > On Fri, Dec 4, 2015 at 5:24 AM, sebb <seb...@gmail.com> wrote: >> The JSON files already in the public directory are now usable by >> Javascript and other apps. >> >> It occurs to me th

Re: New repository and mailing list

On 8 December 2015 at 20:15, Sam Ruby <ru...@intertwingly.net> wrote: > On Tue, Dec 8, 2015 at 1:06 PM, sebb <seb...@gmail.com> wrote: >> On 8 December 2015 at 15:50, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Tue, Dec 8, 2015 at 9:20 AM, Ji

Re: Additional json files for public directory

On 4 December 2015 at 17:04, Sam Ruby <ru...@intertwingly.net> wrote: > On Fri, Dec 4, 2015 at 11:02 AM, sebb <seb...@gmail.com> wrote: >> On 4 December 2015 at 12:49, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Fri, Dec 4, 2015 at 5:24 AM, sebb <seb..

Re: Cross site Javascript access to public json files

On 3 December 2015 at 22:33, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Dec 3, 2015 at 5:15 PM, sebb <seb...@gmail.com> wrote: >> I have been trying to integrate the public/committee-info.json and >> public/member-info.json files into a the Javascript used by t

Re: Input for Whimsy board report

is not yet available > b) whimsical site (via gitpubsub) is not yet set up > c) auto deploy (also via gitpubsub) is not yet set up > d) updated VM (based on Ubuntu 14.04) is available, but set up is not >yet complete. > > 3) Development: > a) updates to

Re: Input for Whimsy board report

so far, see: https://whimsy.apache.org/roster/committee/whimsy > Thanks > Ross > > -Original Message- > From: sebb [mailto:seb...@gmail.com] > Sent: Monday, December 14, 2015 9:25 AM > To: Ross Gardler <ross.gard...@microsoft.com> > Cc: dev@whimsical.apache.org; Ro

Re: ICLA-lint feature: cc: mail aliases

On 23 November 2015 at 20:54, Craig L Russell <craig.russ...@oracle.com> wrote: > >> On Nov 23, 2015, at 9:38 AM, sebb <seb...@gmail.com> wrote: >> >> On 22 November 2015 at 16:14, Craig L Russell <craig.russ...@oracle.com> >> wrote: >>> &g

Re: ICLA-lint feature: cc: mail aliases

On 24 November 2015 at 04:39, Craig L Russell <craig.russ...@oracle.com> wrote: > >> On Nov 23, 2015, at 2:34 PM, sebb <seb...@gmail.com> wrote: >> >> On 23 November 2015 at 20:54, Craig L Russell <craig.russ...@oracle.com> >> wrote: >>> &g

Re: [jira] [Commented] (WHIMSY-34) Spurious data in commitee-info.json

On 13 January 2016 at 10:55, Sam Ruby <ru...@intertwingly.net> wrote: > On Wed, Jan 13, 2016 at 5:49 AM, Sebb (JIRA) <j...@apache.org> wrote: >> >> [ >> https://issues.apache.org/jira/browse/WHIMSY-34?page=com.atlassian.jira.plugin.system.issuetabpanels:

Drop use of Gem for whimsy code - use RUBYLIB instead

There does not seem to be much (if any) advantage of using a Gem to hold the common Whimsy code. There are some disadvantages: - testing changes to the library code is harder - Gem has to be generated, uploaded and deployed - having the Gem as well as the source code on the same system is

Re: Drop use of Gem for whimsy code - use RUBYLIB instead

On 13 January 2016 at 11:53, Sam Ruby <ru...@intertwingly.net> wrote: > On Wed, Jan 13, 2016 at 6:13 AM, sebb <seb...@gmail.com> wrote: >> There does not seem to be much (if any) advantage of using a Gem to >> hold the common Whimsy code. >> >> There are s

Re: [jira] [Commented] (WHIMSY-34) Spurious data in commitee-info.json

On 13 January 2016 at 11:47, Sam Ruby <ru...@intertwingly.net> wrote: > On Wed, Jan 13, 2016 at 6:04 AM, sebb <seb...@gmail.com> wrote: >> On 13 January 2016 at 10:55, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Wed, Jan 13, 2016 at 5:49 AM,

Re: Drop use of Gem for whimsy code - use RUBYLIB instead

t and > process the file again so it updates > > -Jake > > On Wed, Jan 13, 2016 at 12:44 PM, sebb <seb...@gmail.com> wrote: > >> On 13 January 2016 at 17:33, Daniel Gruno <humbed...@apache.org> wrote: >> > On 01/13/2016 06:28 PM, sebb wrote: >>

Re: https://whimsy.apache.org/roster/committee/ has repeated Chair entries

The repeated chairs have vanished. On 15 June 2016 at 14:11, sebb <seb...@gmail.com> wrote: > The chair is repeated multiple times in the display. > > I cannot reproduce this locally. > > However I notice that the passenger.cgi script fails because it cannot write > >

Re: retiring whimsy-vm2: breakage ahead

On 4 June 2016 at 17:33, Sam Ruby <ru...@intertwingly.net> wrote: > On Sat, Jun 4, 2016 at 8:48 AM, sebb <seb...@gmail.com> wrote: >> On 3 June 2016 at 19:33, Sam Ruby <ru...@intertwingly.net> wrote: >>> This weekend I plan to update the DNS records to make w

Re: [whimsy] branch master updated: tighten scope of email search

On 17 June 2016 at 17:14, wrote: > This is an automated email from the ASF dual-hosted git repository. > > rubys pushed a commit to branch master > in repository https://git-dual.apache.org/repos/asf/whimsy.git > > The following commit(s) were added to refs/heads/master by this

Re: [whimsy.git] [1/1] Commit 5e97b14: return only one copy

On 14 January 2016 at 01:38, Sam Ruby wrote: > Commit 5e97b142358e2aaa8957c0ae1608c79e8fd0bb5a: > return only one copy > > > Branch: refs/heads/master > Author: Sam Ruby > Committer: Sam Ruby > Pusher: rubys

Re: [whimsy.git] [1/1] Commit 5e97b14: return only one copy

On 14 January 2016 at 01:58, Sam Ruby <ru...@intertwingly.net> wrote: > On Wed, Jan 13, 2016 at 8:50 PM, sebb <seb...@gmail.com> wrote: >> On 14 January 2016 at 01:38, Sam Ruby <ru...@apache.org> wrote: >>> Commit 5e97b142358e2aaa8957c0ae1608c79e8f

Gemfile.lock: Side effect of using bundler/setup

The bundler/setup require creates a Gemfile.lock file. AIUI: This records the current actual versions of the Gems available at the time. Once created, it is used in preference to re-evaluating the versions. I think this may cause a problem. If we don't include it in version control, then

Re: Drop use of Gem for whimsy code - use RUBYLIB instead

On 13 January 2016 at 17:16, Sam Ruby <ru...@intertwingly.net> wrote: > On Wed, Jan 13, 2016 at 11:12 AM, sebb <seb...@gmail.com> wrote: >> On 13 January 2016 at 13:09, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Wed, Jan 13, 2016 at 7:29 AM, sebb <seb.

Re: Drop use of Gem for whimsy code - use RUBYLIB instead

On 13 January 2016 at 17:33, Daniel Gruno <humbed...@apache.org> wrote: > On 01/13/2016 06:28 PM, sebb wrote: > >> Matt is stalled on the 3rd phase: >> >> MFA: Unknown, not part of the Apache organisation on GitHub yet. >> >> I have set up Github and

Re: [whimsy.git] [1/1] Commit 5e97b14: return only one copy

On 14 January 2016 at 13:49, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Jan 14, 2016 at 8:33 AM, sebb <seb...@gmail.com> wrote: >> On 14 January 2016 at 13:25, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Thu, Jan 14, 2016 at 6:00 AM, sebb <seb.

Re: ALERT: whimsy-test.apache.org (whimsy-test.apache.org (https)) is DOWN!

Note: the full log is: _INFO Connecting to LDAP server: ldaps://ldap-lb-us.apache.org:636 _INFO [ldap-lb-us.apache.org:636] ldapsearch -x -LLL -b ou=groups,dc=apache,dc=org -s one cn=* dn memberUid modifyTimestamp _WARN [ldap-lb-us.apache.org:636] => # for ldapsearch -x -LLL -b

Re: ALERT: whimsy-test.apache.org (whimsy-test.apache.org (https)) is DOWN!

On 6 February 2016 at 20:35, Sam Ruby wrote: > I'm on my phone so forgive my formatting but here is the log: > > _INFO Connecting to LDAP server: ldaps://ldap-lb-us.apache.org:636 _INFO [ > ldap-lb-us.apache.org:636] ldapsearch -x -LLL -b ou=groups,dc=apache,dc=org > -s

Re: Latest updates file for public json data files

On 11 February 2016 at 01:53, Sam Ruby <ru...@intertwingly.net> wrote: > On Wed, Feb 10, 2016 at 8:23 PM, sebb <seb...@gmail.com> wrote: >> Most of the public json data files have dates in them that show when >> the raw data was last updated. >> The files themselve

Re: [whimsy.git] [1/1] Commit 60f24d0: if all hosts are down, give up

On 4 February 2016 at 19:45, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Feb 4, 2016 at 12:55 PM, sebb <seb...@gmail.com> wrote: >> On 4 February 2016 at 15:31, Sam Ruby <ru...@apache.org> wrote: >>> Commit 60f24d0cab030cf6d64ce75c23d05b1ac33bdda7: &g

Re: [whimsy.git] [1/1] Commit 8745cc5: Cleanup only - no functional changes

On 4 February 2016 at 00:55, Sam Ruby <ru...@intertwingly.net> wrote: > On Wed, Feb 3, 2016 at 7:02 PM, sebb <seb...@gmail.com> wrote: >> On 3 February 2016 at 23:23, Sam Ruby <ru...@apache.org> wrote: >>> Commit 8745cc5399c8bf8a13a20dd5e8a41bc59161d0cf:

Re: Reverse proxied whimsy/public/ to whimsy-test/public/

Meant to say thanks a while back - this has been very useful. On 24 January 2016 at 05:57, Sam Ruby wrote: > https://whimsy.apache.org/public/ now shows the results that are produced on > whimsy-test. > > - Sam Ruby

Re: [whimsy.git] [1/1] Commit 8353413: copy logs when something notable happens

FTR, public_json.rb has been updated to copy non-info level files to the archive/ subdirectory. The level name is appended so that more failed logs are kept (without needing to add a timestamp) On 22 February 2016 at 11:11, sebb <seb...@gmail.com> wrote: > On 19 February 2016 at 15:38,

Tabs not welcome here?

I notice that quite a few source files have mixed tabs and spaces. Since tab stops are not standardised, it's generally a bad idea to use them for indentation. Any objections if I replace the ones that have crept in? It looks like the convention is 2 spaces for indents.

Re: editing committer fields using the roster tool

That looks nice. However it takes too long for changes to propagate. I changed my score in id.a.o and it still has not been updated in Whimsy several minutes later. I tried restarting the browser and using a different browser. Whereas I can see the new score using ldapsearch immediately. Also

Re: PGP keys should display one per line

w developers. > On Feb 28, 2016 2:21 PM, "sebb" <seb...@gmail.com> wrote: > >> I have two PGP keys which display concatenated. >> >> I think the following patch will fix it, but cannot test it: >> >> >> diff --git a/www/roster/views/committer

Re: [whimsy.git] [1/1] Commit a8fc082: update to the latest meeting

Can the date be auto-generated? If not, some docn is needed to tell users what to change On 27 February 2016 at 15:36, Sam Ruby wrote: > Commit a8fc0825c6ec869bb3b9dca1342804b4b06671bc: > update to the latest meeting > > > Branch: refs/heads/master > Author: Sam Ruby

Re: PGP keys should display one per line

home. The main one, i.e. whimsy.apache.org > I do have a vagrant image and a docker image that you can spin up locally. > But you shouldn't need to install the whole site to get one tool working. > That's why I suggest you look at rake server first. > On Feb 28, 2016 4:07 PM, "s

PGP keys should display one per line

I have two PGP keys which display concatenated. I think the following patch will fix it, but cannot test it: diff --git a/www/roster/views/committer.js.rb b/www/roster/views/committer.js.rb index 93ac1af..27856d2 100644 --- a/www/roster/views/committer.js.rb +++

Re: PGP keys should display one per line

On 29 February 2016 at 01:04, Sam Ruby <ru...@intertwingly.net> wrote: > On Sun, Feb 28, 2016 at 7:41 PM, sebb <seb...@gmail.com> wrote: >> On 29 February 2016 at 00:17, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Sun, Feb 28, 2016 at 4:56 PM, sebb <seb..

Re: PGP keys should display one per line

On 29 February 2016 at 00:17, Sam Ruby <ru...@intertwingly.net> wrote: > On Sun, Feb 28, 2016 at 4:56 PM, sebb <seb...@gmail.com> wrote: >> On 28 February 2016 at 21:28, Sam Ruby <ru...@intertwingly.net> wrote: >>> So you went straight for the advanced instruct

Re: PGP keys should display one per line

On 29 February 2016 at 12:22, Sam Ruby <ru...@intertwingly.net> wrote: > On Mon, Feb 29, 2016 at 5:35 AM, sebb <seb...@gmail.com> wrote: >> >> I'm using virtual hosts for different apps (projects, reports, etc) > > Makes sense. Let's plan to update the &

Re: Problems with podlings pages

On 29 February 2016 at 21:56, Sam Ruby <ru...@intertwingly.net> wrote: > On Mon, Feb 29, 2016 at 4:40 PM, sebb <seb...@gmail.com> wrote: >> On 29 February 2016 at 21:37, sebb <seb...@gmail.com> wrote: >>> Main page lists a link for: >>> >>&g

Problems with podlings pages

Main page lists a link for: https://whimsy.apache.org/incubator/podlings/by-age This lists 50 PPMCs https://whimsy.apache.org/roster lists 51PodlingsActive podlings at the ASF => https://whimsy.apache.org/podlings => 404 Not sure where the link is supposed to go or why the pages

Re: Problems with podlings pages

On 29 February 2016 at 21:37, sebb <seb...@gmail.com> wrote: > Main page lists a link for: > > https://whimsy.apache.org/incubator/podlings/by-age > > This lists 50 PPMCs > > https://whimsy.apache.org/roster lists > > 51PodlingsActive podlings at the A

https://whimsy.apache.org/incubator/podlings/by-age - reverse sort?

It might be better to list podlings by reverse order of age so the newer ones get more exposure? Also the links to the podling sites could open in a new window?

Re: Problems with podlings pages

is not as easy to use as it requires auth for most of the information that has traditionally been publicly available from people.a.o. > - Sam Ruby > > On Mon, Feb 29, 2016 at 5:13 PM, sebb <seb...@gmail.com> wrote: >> On 29 February 2016 at 21:56, Sam Ruby <ru...@intertwingly.net

Re: [whimsy.git] [1/1] Commit a01897a: Add podling status if present

On 26 February 2016 at 00:31, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Feb 25, 2016 at 6:26 PM, Sebastian Bazley <s...@apache.org> wrote: >> Commit a01897a8369e8c45fd4eedc2c04e813fe52e056c: >> Add podling status if present >> >> >>

Member Active status no longer displayed in roster/committer/xyz

The committer info page used to show "Member status - Active / Emeritus etc" for all members. It no longer does; instead there is a bold heading (Emeritus/Deceased) for non-Active members. Active members don't have any status heading. I think it's better to be specific rather than rely on the

Re: Member Active status no longer displayed in roster/committer/xyz

On 27 February 2016 at 12:36, Sam Ruby <ru...@intertwingly.net> wrote: > On Sat, Feb 27, 2016 at 6:18 AM, sebb <seb...@gmail.com> wrote: >> The committer info page used to show "Member status - Active / >> Emeritus etc" for all members. >> >> I

Listing dates of ICLA entries

ead the current file (if any), update with any additions/corrections from the backup (*), and then get the dates for any new files. (*) This would allow dates to be corrected if necessary. Thoughts? [1] http://people.apache.org/committer-index.html#unlistedclas [2] http://home.apache.org/~sebb/phoneb

Re: Error in icla-info.json format

On 15 February 2016 at 21:53, sebb <seb...@gmail.com> wrote: > I just had a look at icla-info.json, and noticed that the committers > section looks like this: > > { > "last_updated": "2016-02-15 19:49:41 UTC", > "gem_version": "

Historic copies of cron job logs

The cron jobs write to a log file which is overwritten each time. Errors should be detected and reported promptly by PingMyBox, but since the jobs run frequently, it can be difficult to recover the full log before the next run occurs. Generally the error message is sufficient to debug the issue,

Possible additional tools for Whimsy

Mirror checker --- It would be useful to have an online version of the mirror checking script [1] This would allow mirror providers to check their mirror before submitting it. As well as being useful for the apmirror maintainers. It could start out as a tool for ASF committers

Re: Adding asfext:registered to projects.a.o?

On 11 February 2016 at 12:03, Shane Curcuru wrote: > I need to annotate our structured data set of Apache projects to track > which project names are registered trademarks. This is needed to be > able to properly generate a.o/foundation/marks/list (which is currently >

Re: Latest updates file for public json data files

On 11 February 2016 at 17:34, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Feb 11, 2016 at 10:58 AM, sebb <seb...@gmail.com> wrote: >> On 11 February 2016 at 01:53, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Wed, Feb 10, 2016 at 8:23 PM, sebb

Does Whimsy really need to have a local Git workspace?

AFAICT the only Git files that Whimsy needs to be available locally at runtime are asf-auth and pit-auth. The other Git file it uses (data/common.yaml) is read directly from the server. So it seems a bit wasteful to keep a local clone. One might as well just read the files directly; this will

Re: [OT] Wunderbar html - how to output HTML comment with variable content?

On 17 March 2016 at 20:19, sebb <seb...@gmail.com> wrote: > The Wunderbar docs mention outputting text with markup: > > _{"hello!!!"} > > The following also works: > > _{""} > > However it does not seem to be possible to output an HTML co

Re: Auth required for status/passenger

On 17 March 2016 at 16:14, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Mar 17, 2016 at 11:24 AM, sebb <seb...@gmail.com> wrote: >> On 17 March 2016 at 13:03, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Thu, Mar 17, 2016 at 7:59 AM, sebb <seb...

Re: Wunderbar logger wrapper level and formatter changes

On 14 March 2016 at 14:22, Sam Ruby <ru...@intertwingly.net> wrote: > On Mon, Mar 14, 2016 at 10:10 AM, sebb <seb...@gmail.com> wrote: >> On 14 March 2016 at 12:55, sebb <seb...@gmail.com> wrote: >>> It would be useful to be able to initialise the default lo

Re: Wunderbar logger wrapper level and formatter changes

On 14 March 2016 at 15:27, Sam Ruby <ru...@intertwingly.net> wrote: > On Mon, Mar 14, 2016 at 11:09 AM, sebb <seb...@gmail.com> wrote: >> On 14 March 2016 at 14:22, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Mon, Mar 14, 2016 at 10:10 AM, sebb <seb...@

https://whimsy.apache.org/members/subscriptions/ fails

https://whimsy.apache.org/members/subscriptions/ fails with # /srv/whimsy/www/members/subscriptions.cgi:62:in `readlines' Is this expected?

Re: https://whimsy.apache.org/members/subscriptions/ fails

Similarly for https://whimsy.apache.org/incubator/moderators I get # /srv/whimsy/www/incubator/moderators.cgi:68:in `read' On 16 March 2016 at 00:14, sebb <seb...@gmail.com> wrote: > https://whimsy.apache.org/members/subscriptions/ fails with > > # /home/apmail/subscriptions/me

Re: https://whimsy.apache.org/members/subscriptions/ fails

will likely break (and possibly become > obsolete) once the infrastructure deploys the new mail system. > > - Sam Ruby > > On Tue, Mar 15, 2016 at 8:22 PM, sebb <seb...@gmail.com> wrote: >> Similarly for https://whimsy.apache.org/incubator/moderators >> I get >&

Access to whimsy http logs?

It would be very useful to have access to the Whimsy error log when app errors occur. Probably also the access log. Since the log may contain relatively private info, this should probably be restricted to members, in which case I think it can be achieved by using a suitable symlink under one of

Collate Minutes cannot find ASF::Podling

The collate_minutes job is failing with: collate_minutes.rb:61:in `': uninitialized constant ASF::Podling (NameError) *** Exception NameError : collate_minutes.rb:61:in `' uninitialized constant ASF::Podling *** I don't get that problem when running it in a command shell. The podlings code

Re: Collate Minutes cannot find ASF::Podling

On 14 March 2016 at 02:00, Sam Ruby <ru...@intertwingly.net> wrote: > On Sun, Mar 13, 2016 at 9:43 PM, sebb <seb...@gmail.com> wrote: >> The collate_minutes job is failing with: >> >> collate_minutes.rb:61:in `': uninitialized constant ASF::Podling >> (N

Wunderbar logger wrapper level and formatter changes

It would be useful to be able to initialise the default log level but still allow CLI over-ride. I've found a hacky fix: Wunderbar.log_level = 'info' unless Wunderbar.log_level == 'debug' # don't override command-line level however that relies on knowing that debug (and only debug) is more

Re: [OT] Wunderbar html - how to output HTML comment with variable content?

On 18 March 2016 at 03:28, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Mar 17, 2016 at 4:19 PM, sebb <seb...@gmail.com> wrote: >> The Wunderbar docs mention outputting text with markup: >> >> _{"hello!!!"} >> >> The following

Re: Does Passenger really need ruby 2.3.0? and in /usr/local/bin?

On 17 March 2016 at 13:18, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Mar 17, 2016 at 7:20 AM, sebb <seb...@gmail.com> wrote: >> As the subject says. > > Depends on your definition of require. Ruby >= 2.2.0 will use less > memory and be more responsi

[OT] Wunderbar html - how to output HTML comment with variable content?

The Wunderbar docs mention outputting text with markup: _{"hello!!!"} The following also works: _{""} However it does not seem to be possible to output an HTML comment which contains any variable text, e.g. a date. Is this possible?

Re: Wunderbar logger wrapper level and formatter changes

On 14 March 2016 at 12:55, sebb <seb...@gmail.com> wrote: > It would be useful to be able to initialise the default log level but > still allow CLI over-ride. > > I've found a hacky fix: > > Wunderbar.log_level = 'info' unless Wunderbar.log_level == 'debug' # > don't

Re: Wunderbar class: attribute causes problems for syntax checkers

Just noticed another syntax complaint: _label "Contributor's Name:", for: 'iclaname' The colon after for is flagged as unexpected. The other main complaint is about: onClick: -> {@form = ICLA} On 28 March 2016 at 19:54, sebb <seb...@gmail.com> wrote: > On 28 March 2

Extract SVN and poss. other System commands into a function?

For unit testing purposes it can be useful to be able to disable svn actions and replace them with a log message. And for live running it can be useful to log the system commands that are run. It might therefore be useful to add some utility functions to encapsulate the system calls. WDYT?

Simplify committing new/replacement file to SVN by using svnmucc

I just realised that we could use the svnmucc 'put' command to simplify adding/modifying a file. There is no need to create a temporary checkout of the parent directory. One can even use '-' to put from standard input. Won't be suitable for everything, but might prove useful. Maybe worth

PingMyBox mails and notifications mailing list

Once the notifications mailing list is created, do we want all PingMyBox emails to be sent to it? Or do we want PMB to continue to send to dev@, but drop the WARN level from its reporting and send our own e-mails to the notifications list for WARNings? I think we need to send e-mails anyway for

Re: Monitor.rb and monitors/*.rb - inconsistent symbol/string hash keys

On 6 April 2016 at 11:40, Sam Ruby <ru...@intertwingly.net> wrote: > On Tue, Apr 5, 2016 at 5:43 PM, sebb <seb...@gmail.com> wrote: >> I've started looking into how to quieten down the warnings without >> losing all the info. >> >> The monitors are called

Using anchors to navigate the roster pages

Some of the Roster pages are rather long, so it can be tedious to scroll to the correct place. For example: https://whimsy.apache.org/roster/committee/commons So I added some anchors, e.g. https://whimsy.apache.org/roster/committee/commons#committers I think it would be useful to add some

Re: Error subscribing

Should be fixed now. On 10 April 2016 at 09:42, sebb <seb...@gmail.com> wrote: > Looks like that app has not been fully migrated from the original whimsy host. > > If it's urgent, you could try using whimsy-old.apache.org instead for > that service. > > On 9 April 2016

Re: Changes to PMC membership restricted to current chair

On 11 April 2016 at 02:22, John D. Ament <johndam...@apache.org> wrote: > +1 > You also have the case of AD that may require outside input. AD? Not sure what it has to do with Dungeons and Dragons...! > On Sun, Apr 10, 2016 at 9:21 PM sebb <seb...@gmail.com> wrote: >

Changes to PMC membership restricted to current chair

The pmc chairs LDAP group gives karma to update the LDAP groups for any PMC, not just ones own. However Whimsy only enables the update buttons for the PMC chair. Historically when a PMC chair is unavailable, the rest of PMC has been able to call on another chair to do the update. Maybe this

Re: Difference(s) in public/icla-info_noid.json

Note: the file was updated at the time shown, however the change only affected an e-mail address which is not extracted. It should be possible to suppress change notifications where only the last_updated field has changed. (e.g. redact the values of such fields before comparison) Not sure it's

Re: [whimsy.git] [1/1] Commit 1e101ba: Easier to read

be available. Also plain text is better for use with wget/cURL/diff > - Sam Ruby > >> >> Branch: refs/heads/master >> Author: Sebb <s...@apache.org> >> Committer: Sebb <s...@apache.org> >> Pusher: sebb <s...@a

Show pit groups in public_nonldap_groups.json ?

podlings are effectively only shorthand for the list of names they contain; they are not used directly for auth. So it does not matter if they are the same as an LDAP entry. Though defining a group such as 'clr=rubys,sebb' would be quite confusing!

Re: Does Whimsy really need to have a local Git workspace?

ing for a > slower but more up to date response. > On Mar 18, 2016 5:45 PM, "sebb" <seb...@gmail.com> wrote: > >> AFAICT the only Git files that Whimsy needs to be available locally at >> runtime are asf-auth and pit-auth. >> >> The other Git

Does Passenger really need ruby 2.3.0? and in /usr/local/bin?

As the subject says. MacOS/X comes with 2.0.0 which seems to work for most if not all the code. So is it necessary to specify ruby 2.3.0 in status/Gemfile and /usr/local/bin/ruby2.3.0 in passenger.cgi? In particular it seems wrong to specify that ruby is under /usr/local/bin, even if 2.3.0 is

Auth required for status/passenger

The status page says that passenger status is restricted to "ASF committer only", however the code uses the realm "ASF Members and Officers". Which is correct?

Re: https://whimsy.apache.org/members/subscriptions/ fails

On 16 March 2016 at 01:37, Sam Ruby <ru...@intertwingly.net> wrote: > On Tue, Mar 15, 2016 at 9:28 PM, sebb <seb...@gmail.com> wrote: >> OK, thanks. >> >> Might be useful to have some dummy data for use in testing? >> Just enough to allow the scripts to

Re: Update Whimsy to use Ruby 2.3.0 throughout?

Created branch: sebb-20160321 which I hope is OK On 20 March 2016 at 12:32, Sam Ruby <ru...@intertwingly.net> wrote: > +1 > > - Sam Ruby > > On Sun, Mar 20, 2016 at 5:14 AM, sebb <seb...@gmail.com> wrote: >> At present Passenger uses 2.3.0, but most of the othe

New mailing list for recording various items

There are various items logged in the cron jobs (and elsewhere?) that it would be useful to track historically. For example, LDAP server issues, changes to LDAP files. At present the LDAP warnings are sent to the dev list by PMB. These don't need immediate attention, so don't really need to go

Update Whimsy to use Ruby 2.3.0 throughout?

At present Passenger uses 2.3.0, but most of the other scripts use the default Ruby which is 1.9.3. The Ruby 2.x versions have many improvements and new features (e.g. __dir__ and to_h). It's likely that developers will be using a later version than 1.9.3. This makes it harder to test whether

Re: Whimsy proxy tool

On 21 March 2016 at 20:32, Jim Jagielski wrote: > I do, but I'm still unclear on dealing w/ the GH workflow. > > Can I just do it via svn, or even *our* git and not deal > w/ GH at all? You can certainly just work on a clone of our Git; no need to use GitHub (once you are set

Re: foundation: r66956 - /foundation/Meetings/20160322/proxies-received/goodale.txt

On 23 March 2016 at 01:22, sebb <seb...@gmail.com> wrote: > On 23 March 2016 at 00:39, Craig Russell <craig.russ...@oracle.com> wrote: >> Two comments: >> >> 1. The proxy filing tool is not listed at https://whimsy.apache.org (or am I >> going blind)

Re: Handling availid regex matching

On 23 March 2016 at 22:25, sebb <seb...@gmail.com> wrote: > I've been finding various different regexes being used for > extracting/matching ASF availids. > > So it struck me it might be useful to define the RE string once in the > asf/whimsy library. > > e.g. assuming t

Re: ALERT: whimsy.apache.org (whimsy.apache.org (https)) is DOWN!

That appears to have been caused by the following error: /srv/whimsy/lib/whimsy/asf.rb:14:in `require_relative': cannot load such file -- /srv/whimsy/lib/whimsy/asf/person (LoadError) from /srv/whimsy/lib/whimsy/asf.rb:14:in `' from

Re: foundation: r66956 - /foundation/Meetings/20160322/proxies-received/goodale.txt

On 23 March 2016 at 00:39, Craig Russell wrote: > Two comments: > > 1. The proxy filing tool is not listed at https://whimsy.apache.org (or am I > going blind)? The self-service code for members at https://whimsy.apache.org/members/proxy/ does not seem to be listed; I

Re: Auth required for status/passenger

On 17 March 2016 at 13:03, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Mar 17, 2016 at 7:59 AM, sebb <seb...@gmail.com> wrote: >> The status page says that passenger status is restricted to "ASF >> committer only", however the code uses the realm "

Re: [whimsy.git] [1/1] Commit 6ec6dc3: new board

On 24 March 2016 at 21:01, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Mar 24, 2016 at 4:15 PM, sebb <seb...@gmail.com> wrote: >> This info really needs to be obtained from a canonical source if there is >> one. > > Indeed! > >> If there isn'

Re: /usr/bin/ruby1.9.1 => /usr/bin/ruby

On 7 March 2016 at 11:44, Sam Ruby <ru...@intertwingly.net> wrote: > On Mon, Mar 7, 2016 at 6:33 AM, sebb <seb...@gmail.com> wrote: >> On 7 March 2016 at 00:24, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Sun, Mar 6, 2016 at 6:19 PM, sebb <seb...@gma

Incorrect PMB message (was ALERT: whimsy.apache.org (whimsy.apache.org (https)) is DOWN!)

There is an issue with interpreting logs which have both a warning and an output file update. In this case the output title replaced the data field in the PMB message. This is confusing, and loses useful information. The source log for this report was: -- cut here --

Re: Access to single SVN items - implement caching?

On 4 March 2016 at 00:19, Sam Ruby <ru...@intertwingly.net> wrote: > On Thu, Mar 3, 2016 at 4:35 PM, sebb <seb...@gmail.com> wrote: >> On 3 March 2016 at 21:12, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Thu, Mar 3, 2016 at 3:50 PM, sebb <seb...@gmail.co

Re: Access to single SVN items - implement caching?

On 4 March 2016 at 15:40, Sam Ruby <ru...@intertwingly.net> wrote: > On Fri, Mar 4, 2016 at 10:03 AM, sebb <seb...@gmail.com> wrote: >> On 4 March 2016 at 00:19, Sam Ruby <ru...@intertwingly.net> wrote: >>> On Thu, Mar 3, 2016 at 4:35 PM, sebb <seb...@gmail

  1   2   3   4   5   6   7   8   9   10   >