Forum OpenACS Q&A: Re: Will Dr. OpenACS survive? Or why I stopped worrying and learned to love the .LRN consortium?

Collapse
65: Re: Will Dr. OpenACS survive? Or why I stopped worrying and learned to love the .LRN consortium? (response to 1)
Posted by Jeff Davis on 03/06/05 02:55 PM
John,

I suspect you would find there are far fewer bugs introduced relative to the number fixed if you upgraded. Based on tickets we see for dotlrn that many of the open tickets end up being closed in the new release.

That said, the upgrade process from an older version (particularly if customized locally) is not painless.

It's an area we have worked harder at and I think over time are getting better at (upgradability and reproducible delivery). You are right that it's a pretty intractible problem for a 2-tier architecture although given the persistence layers I have seen that abstract that, it's the problem I would rather have.

Is there a good write-up on the sakai permissioning? I don't think in principle there is anything that prevents us from doing the same.

Collapse
68: Re: Re: Will Dr. OpenACS survive? Or why I stopped worrying and learned to love the .LRN consortium? (response to 65)
Posted by John Norman on 03/06/05 09:01 PM
Jeff

I will try to dig something out, but you can always take a look for yourself at the test site for the impending 1.5 release: http://sakai-stable.mit.edu/ I'm not sure what the plans are for the site, but this morning you could log in with admin and admin to become site admin.

You can also register for a user account and make that an admin account with the above login. There are CRUD permissions at course/project admin level with tick boxes, but then more sophisticated controls in the area called 'realms'.