The IRC channel is #sakai on the freenode network, you can join using a web 
client at http://webchat.freenode.net/?channels=sakai and you can view the 
complete logs at http://sakai.iriscouch.com/irc/_design/viewer/index.html

16:47 <SakaiGithub> [3akai-ux] arwhyte tagged 1.4.1-release-tag at 
org.sakaiproject.nakamura.uxloader-1.4.1-RC1: http://git.io/hJwlYw
16:47 <SakaiGithub> [3akai-ux/1.4.1-release-tag] release_pre_process: Moving 
config files from 1.4.1-SNAPSHOT to 1.4.1 - Anthony Whyte
16:47 <SakaiGithub> [3akai-ux/1.4.1-release-tag] [maven-release-plugin] prepare 
release 1.4.1-release-tag - Anthony Whyte
17:13 <zacht> mrvisser Is there a Jira for the JDO promotion?
17:13 <zacht> mrvisser I want to make it a child of KERN-3145
17:14 <mrvisser> zacht: nope
17:15 <zacht> sakai-bot wassup?
17:15 <mrvisser> zacht: I can create a ticket if you aren't already in the 
process.
17:16 <zacht> yes, please. mrvisser++
17:19 <mrvisser> zacht https://jira.sakaiproject.org/browse/KERN-3157
17:26 <zacht> Hey duffy, did you see my comment on 
https://jira.sakaiproject.org/browse/KERN-3153
17:29 <duffy> zacht: yup
17:30 <duffy> zacht: currently going through all the checks for User.ADMIN_USER 
to map out the implications of checking for membership in "administrators" 
group as well
17:31 <duffy> zacht: I'm going to convert the logic for all of such locations, 
but want to record what the implications are. For example, anyone in the 
"administrators" group would be have no user-based restrictions on search 
results and would be able to impersonate any user
17:47 <zacht> mrvisser too bad about perf4j possibly slowing things down.
17:49 <mrvisser> zacht: yea, that would be unfortunate. we'll see how things 
pan out after the tests.
18:05 <thecarlhall> zacht!
18:05 <zacht> thecarlhall yo.
18:05 <thecarlhall> zacht, I'd like to reconvene on the files impl work when 
you get some time
18:05 <thecarlhall> zacht, versioning is an interesting beast that has never 
really been done right
18:06 <zacht> thecarlhall I believe that.
18:07 <zacht> thecarlhall I need to get some food. Can I flag you down when I 
get back?
18:07 <thecarlhall> zacht, sure thing. take your time
18:33 <zacht> thecarlhall Skype?
18:33 <thecarlhall> zacht, sure
20:56 <GitHub20> [nakamura] thecarlhall pushed 2 new commits to master: 
http://git.io/VyajGw
20:56 <GitHub20> [nakamura/master] KERN-3156 Reference 
cleVirtualToolDataProvider       ["Unsatisfied","Service Name: 
org.sakaiproject.nakamura.basiclti.CLEVirtualToolDataProvider","Multiple: 
single","Optional: mandatory","Policy: static","No Services bound"] - Lance 
Speelmon
20:56 <GitHub20> [nakamura/master] Merge pull request #990 from 
lancespeelmon/kern-3156 - Carl Hall
21:32 <zacht> mrvisser You don't happen to use IntelliJ IDEA, do you?
21:32 <mrvisser> zacht nope
21:33 <zacht> mrvisser ok. I'm trying to get it to use the aspectj compiler. I 
point it at aspectj-1.7.0.jar and it's telling me "Not a valid AspectJ 
compiler" Does that ring any bells?
21:34 <zacht> Maybe I need to go back a version.
21:35 <mrvisser> zacht: maybe. we changed it back to 1.6.11
21:45 <duffy> ping zacht
21:45 <zacht> duffy Hey.
21:46 <duffy> hey, zacht. for KERN-3153 I've basically worked through the admin 
privileges checks and have commits to alter sparse and nakamura…. only one snag 
though - which version of sparse should I be working from?
21:46 <duffy> nakamura won't work against the HEAD (1.5.1)
21:46 <duffy> (of sparse)
21:46 <zacht> duffy we're on the 1.3 branch.
21:46 <duffy> cool. I've locally revved to 1.3.8-SNAPSHOT
21:47 <duffy> sounds like I'm on the right track then (?)
21:47 <zacht> duffy in a few days, we'll cut a 1.3.7 release, and your work 
will go into 1.3.8. Yeah, you're on the right track.
21:48 <duffy> thanks :)
21:50 <zacht> duffy One thing I'm not sure of is what kind of search results 
people are going to see if they're admins. I'm guessing they'll start seeing 
everything.
21:50 <zacht> duffy In other words, private content, etc. No more constraints 
will be applied, which might be the intended behavior.
21:53 <duffy> zacht: right, that was my comment this morning. I'm not sure if 
there should be any difference b/n Admin and a user who is in Administrators 
group. Search results was one of the places I was curious about
21:54 <zacht> duffy presumably, people who are admins still want to go around 
and do "regular" stuff.
21:54 <duffy> zacht: another is updating content. The Admin user can update 
content without updating timestamp. I've made the arbitrary decision that 
members of the Admin group cannot
21:54 <duffy> agreed. and I don't know the full impact of some of this stuff
21:55 <duffy> zacht: I think the right thing to do is to PR this with extensive 
annotations on the diff. then to get Alan (and others?) to review with an eye 
toward the greater impact
21:55 <mrvisser> heya froese, are you familiar with the ehcache configuration 
for OAE?
21:56 <froese> mrvisser, just the peers really
21:56 <duffy> zacht: to some degree this is a judgement call. Ie. what do we 
want the experience for Admin group members to be?
21:56 <mrvisser> froese: so you aren't familiar with the rationale behind the 
properties, like replicatePuts=false, etc...
21:57 <froese> not so much
21:57 <froese> sorry
21:59 <mrvisser> no worries
22:59 <lancespeelmon> duffy: there is a bug related to admin not being able to 
see all content
22:59 <lancespeelmon> everyone expects that when you are admin, you can see 
everything in the system
22:59 <lancespeelmon> that would actually help support the system better
23:05 <duffy> lancespeelmon: I'll see if I can isolate what's going on there as 
I go through KERN-3153. But that might be a larger issue than "provide admin 
user level access to members of the admin group"
23:05 <duffy> s/larger/different/g

_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev

Reply via email to