On Fri, Jun 23, 2017 at 7:32 PM, sebb wrote:
> error is Authentication failed
>
> I think this may need root karma to solve?
Fixed. It looks like some svn operation doesn't specify
--no-auth-cache. This wasn't a problem on whimsy-vm3, and it appears
that the mode there didn't permit write opera
error is Authentication failed
I think this may need root karma to solve?
[
https://issues.apache.org/jira/browse/WHIMSY-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061574#comment-16061574
]
Sebb commented on WHIMSY-109:
-
Yes, I know the original working directory is restored at the e
[
https://issues.apache.org/jira/browse/WHIMSY-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061518#comment-16061518
]
Sam Ruby commented on WHIMSY-109:
-
Can I get you to state what your concern is?
Note that
[
https://issues.apache.org/jira/browse/WHIMSY-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061495#comment-16061495
]
Sebb commented on WHIMSY-109:
-
Turns out it's trivial to do:
{code}
Open3.capture3(*%(git con
[
https://issues.apache.org/jira/browse/WHIMSY-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061118#comment-16061118
]
Sebb commented on WHIMSY-109:
-
I'm looking into whether it's possible to tell the command shel
Sebb created WHIMSY-109:
---
Summary: Code uses Dir.chdir and Dir.pwd without sync
Key: WHIMSY-109
URL: https://issues.apache.org/jira/browse/WHIMSY-109
Project: Whimsy
Issue Type: Bug
Reporte
[
https://issues.apache.org/jira/browse/WHIMSY-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061070#comment-16061070
]
Sebb commented on WHIMSY-108:
-
There are other scripts that use ASF::Group methods.
These will
Sebb created WHIMSY-108:
---
Summary: Plan for removal of LDAP groups and pmcs
Key: WHIMSY-108
URL: https://issues.apache.org/jira/browse/WHIMSY-108
Project: Whimsy
Issue Type: Bug
Reporter: S
On Fri, Jun 23, 2017 at 7:54 AM, Shane Curcuru wrote:
> Separately: we should include a short help text that defines who's
> supposed to be able to do add/delete/change operations, along with links
> to the specific PMC how to documentation. Especially if we end up with
> an auth where members co
Separately: we should include a short help text that defines who's
supposed to be able to do add/delete/change operations, along with links
to the specific PMC how to documentation. Especially if we end up with
an auth where members could technically do things that socially they
shouldn't (i.e. fo
Since most whimsy tools require a login, is it wrong for us to track the
actual user name? Or should we maintain our own internal RUM database?
Action tracking events are generally not that complicated.
For conversion, since we have paths, it should be easy enough to track who
was doing what in t
As we start building parts of whimsy that are becoming key parts of
organizational processes - like PMC updates - should we start tracking
actual usage of various tools to see 1) which tools are widely used, and
should be managed more carefully, and 2) tools that aren't used but
might be valuable i
13 matches
Mail list logo
