On Sun, Feb 28, 2016 at 8:28 PM, sebb wrote:
> On 29 February 2016 at 01:04, Sam Ruby wrote:
>> On Sun, Feb 28, 2016 at 7:41 PM, sebb wrote:
>>>
>>> I thought I *had* configured www/roster; see my posting from 21:07
>>> (else-thread)
>>>
>>> How should I have done it?
>>
>> I went back and look
On 29 February 2016 at 01:04, Sam Ruby wrote:
> On Sun, Feb 28, 2016 at 7:41 PM, sebb wrote:
>> On 29 February 2016 at 00:17, Sam Ruby wrote:
>>> On Sun, Feb 28, 2016 at 4:56 PM, sebb wrote:
On 28 February 2016 at 21:28, Sam Ruby wrote:
> So you went straight for the advanced instruct
On Sun, Feb 28, 2016 at 7:41 PM, sebb wrote:
> On 29 February 2016 at 00:17, Sam Ruby wrote:
>> On Sun, Feb 28, 2016 at 4:56 PM, sebb wrote:
>>> On 28 February 2016 at 21:28, Sam Ruby wrote:
So you went straight for the advanced instructions. Cool.
Did you try rake server?
>>>
>>
On 29 February 2016 at 00:17, Sam Ruby wrote:
> On Sun, Feb 28, 2016 at 4:56 PM, sebb wrote:
>> On 28 February 2016 at 21:28, Sam Ruby wrote:
>>> So you went straight for the advanced instructions. Cool.
>>>
>>> Did you try rake server?
>>
>> No.
>>
>> I did not understand what constituted a Rac
On Sun, Feb 28, 2016 at 4:56 PM, sebb wrote:
> On 28 February 2016 at 21:28, Sam Ruby wrote:
>> So you went straight for the advanced instructions. Cool.
>>
>> Did you try rake server?
>
> No.
>
> I did not understand what constituted a Rack application.
> But I see that www/roster has a Rakefile
On 28 February 2016 at 21:28, Sam Ruby wrote:
> So you went straight for the advanced instructions. Cool.
>
> Did you try rake server?
No.
I did not understand what constituted a Rack application.
But I see that www/roster has a Rakefile so I have just tried
cd /www/roster
rake server
and I ca
So you went straight for the advanced instructions. Cool.
Did you try rake server?
Which index page are you referring to? The problem looks to be one that
can be solved be the use of relative URLs. If you tell me which index
page, I'll take a look when I get back home.
I do have a vagrant imag
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
> Committer: Sam Ruby
On 28 February 2016 at 20:11, Sam Ruby wrote:
> Whatever is blocking you from testing this change is the bug I would like
> to work on.
I cannot get Whimsy working locally.
I have got as far as seeing the index page but nothing else works.
e.g.
The requested URL /roster/committer/ was not foun
Whatever is blocking you from testing this change is the bug I would like
to work on.
On Feb 28, 2016 2:21 PM, "sebb" 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.js.rb
> b/w
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
+++ b/www/roster/views/committer.js.r
On Sun, Feb 28, 2016 at 1:55 PM, sebb wrote:
> 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 ca
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 the
On Sun, Feb 28, 2016 at 1:26 PM, sebb wrote:
> 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.
Agreed.
> Any objections if I replace the ones that have crept in?
Please do.
> I
I've updated the roster tool based on the discussion and resolution of
the following issue:
https://issues.apache.org/jira/browse/INFRA-9250
---
Usage:
First find and navigate to your committer page:
https://whimsy.apache.org/roster/committer/
Scroll down to the Spam Assassin Score line a
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.
[
https://issues.apache.org/jira/browse/WHIMSY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Ruby updated WHIMSY-47:
---
Assignee: (was: Sam Ruby)
> PMC creation missing from board reports
> -
[
https://issues.apache.org/jira/browse/WHIMSY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Corey moved INFRA-8354 to WHIMSY-47:
-
Security: (was: public)
Workflow: jira (was: INFRA Workflow)
18 matches
Mail list logo
