I've got WordPress roughly working. One of the major kinds of
integration we want is with authentication and permissions.
Anyway, that leaves open some questions. Authentication is easy enough,
but it's not clear how permissions should work. Do we try to inherit
the permissions of the project? I don't think that's right, though;
even an open project probably won't have an open blog. Maybe they will,
but purely inheriting it seems wrong. Do we want to allow even more
restricted permissions? E.g., a setting so only project admins can
post? This is perhaps how something like StreetsBlog would work -- or
if it's an open project, you might allow all members to post and just
not have many members.
I don't know all the permissions in WordPress, and it seems like you can
cut it a lot of different ways by defining and editing roles. So really
there's multiple possible levels. E.g., write and edit drafts, post
live stories, do comment moderation, do blog administration. The last
seems like it should just be restricted to project admins. The other
ones could go a lot of different ways.
One option is that we don't inherit much in terms of permission at all.
Instead, you get authentication from the site (i.e., logins), but blog
permissions are handled inside WordPress. We could potentially set up
initial permissions based on your project settings, but then let them go
out of sync after that.
Sorry if this is a little vague, I don't have a very good feel for WP
permissions yet. Modulo lots of niggling details, blogging is kind of
working at http://opencore.flow.openplans.org/blog/ -- but the admin
side is still kind of broken, so it's a very boring blog. Fixing it
involves either completely overriding the permission system (e.g.,
pulling permissions from the wiki) or... well, just letting them be as
they are in WordPress, and trying to get blogs bootstrapped with useful
initial permissions. So I'm trying to figure out which direction to take.
Ian
--
Archive:
http://www.openplans.org/projects/opencore/lists/opencore-ui/archive/2007/07/1184347501167
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
