Sorting Out Work

Looking to get a sense of what various co-maintainers are looking to contribute. As an API, this will need to be very stable, have well thought out public functions, and good unit testing. As an API it will also need to have modules that leverage it, even if they are proof of concept modules. As it will be leveraged by authentication and authorization modules it should be fairly well tested for security.

So what roles are people intereted in playing?

- writing simple tests
- specing out the api itself. I already have an alpha but it needs a good look
- documentation
- getting other ldap modules to leverage it.
- exportables and patterns support
- ...oh and coding the api module itself

Late next week I'd like to skype or irc with whomever is interested in contributing or being co-maintainers to get things going. I have a deadline coming up middle of this week, but may get code cleaned up and posted before then.

Please be sure to take a look at the scope of the api module itself on the project page (6 points). I'm flexible on this, but am not interested in large amounts of philosophical/scope discussion. That is I would like to have a good discussion about the functionality and architecture of the module, then get to work on the unit tests and write the module.