[ckan-dev] HRI Lockdown

[David Read]

Hi Friedrich,

The release is on a release branch: 1.3.2, so there's no problem with
committing into default.

BTW obviously your requirement goes a bit further than this, but we've
also done some work on authorization as well this week that might be
of interest - configuring the default permissions for new packages
etc. and extending your authztool to do operations on all packages. So
with this you can change visitor and logged-in edit permissions to
read-only, requiring all changes to be done by sysadmins only.
http://trac.ckan.org/ticket/1025

David

On 9 March 2011 21:51, Friedrich Lindenberg
<friedrich.lindenberg at okfn.org> wrote:
> Hi James,
>
> I've just pushed the authorization lockdown changes required by HRI to
> feature-1024-lockdown (includes #1024, #1027, #1017, OpenID, ApiKey
> page removed). Since James mentioned on Monday that we should be
> careful with default at the moment I'm wondering on how to proceed:
> shall I try to merge this or deploy the feature branch to HRI?
>
> They've asked for things to be in place before Monday.
>
> - Friedrich
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>