[Collaboa] RESTful Collaboa Brainstorm

[Piotr Banasik]

A couple of months back I discussed a user overhaul with Jason ... Here is a
quick synopsis ..

We wanted to make user registrations required (+email confirmation), that
would be a sure way to stop spam, and guarantee a valid email.

We wanted to introduce the idea of user groups, this way, ther's a cleaner
way to globally affect settings for these users who sign up (they'd all
belong to a "registered users" group or something). The idea here is to
basically move the relationship between users <-> projects, to users <->
groups <-> projects.

Anonymous mode could still be supported by the "anonymous" group .. but by
default it could have all posting disabled .. if someone has a secure
environment they can enable anonymous posting if they need it.

Since you're considering replacing the login system, this may as well be
thrown on the table.

I don't see anything wrong with replacing the login system, I wouldn't mind
seeing login work transparently between html forms and http authentication,
this has great potential for having authenticated rss feeds with info on
stuff that the particular user has access to.

-p

On 12/14/06, Oliver Legg <ollylegg at gmail.com> wrote:
>
> With the approach of Rails 1.2 and all its restful goodies. I was
> wondering how to go about introducing REST into Collaboa.
>
> Firstly, for all user management and login, I would recommend Rick
> Olson's Restful Authentication plugin (http://svn.techno-weenie.net/
> projects/plugins/restful_authentication/). This would replace the
> login and user controllers.
>
> With regards to the user login, I would like to propose a
> relationship, where User <-> Permissions <-> Projects (I think this
> can be accomplished through a has_many :though relationship, although
> I'm not sure). This would allow each user to be assigned different
> permissions to each project.
>
> Secondly, I reckon that the milestones, projects, search controllers
> would translate to a restful approach quite easily.
>
> Thirdly, a restful approach would remove the need for the rss
> controller.
>
> Fourthly, I think that the repository and tickets controllers might
> need to be split up into multiple controllers. After a brief look, I
> would propose the repository controller be split into a changesets
> and repository controller. And the tickets controller being split
> into a tickets, ticket changes (possibly renamed) and an attachments
> controller.
>
> Finally, I think there needs to be a think about how the admin
> controller can best be fitted into this approach. Personally I want
> to use REST as a free way to get an API, so that I can extend
> functions to my repositories (possibly integrating Collaboa with
> mod_dav_svn authentication, to provide a nice interface for that; or
> allowing changesets to be added from a remote machine). For the api
> to work nicely a combined controller would be ideal. Although this
> might make managing permissions harder (or even easier, if you want
> permissions for everything).
>
> These are just my thoughts, and I would to implement some of them.
> But I would like to see what ideas the commiters and community have.
>
> Olly
> _______________________________________________
> Collaboa-talk mailing list
> Collaboa-talk at lists.collaboa.org
> http://lists.collaboa.org/mailman/listinfo/collaboa-talk
>



-- 
Piotr Banasik
www.t-p-l.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.collaboa.org/pipermail/collaboa-talk/attachments/20061214/f52a05f9/attachment.htm