> For now, I just wanted to list some of the features that are on the table >> for upcoming releases, and give the Bloodhound community the chance to >> comment on what might be most important to tackle for upcoming releases. I >> will consider focusing my efforts according to whatever feedback I >> receive. >> The following is a list that I've loosely prioritized according to my >> current thinking: >> 1. #10747: Allow accounts to be created from the command line by >> implementing IAdminCommandProvider interface, and consider other commands >> to implement >> 2. #10002: Allow accounts to be manually locked >> 3. #1001: Implement an extensive XmlRpc interface >> 4. #3113: Implement more extensive password policy checks >> 5. Integrate the UserManagerPlugin (I've taken over maintenance of this >> plugin and will provide more info on what this plugin provides once I get >> more up to speed on the codebase). >> 6. #9947: Integrate functionality of FineGrainedPageAuthzEditorPlugin >> 7. Integrate the HtGroupsEditPlugin >> 8. #9943: Add group-based and preference-based configurable login page >> 9. Integrate the PermRedirectPlugin >> 10. Enhance the plugin's macros by integrating the UserStatsMacro and >> WikiStatsMacro. >> > > There is one thing that I am missing from this list that should probably > be number 1: Bloodhound multiproduct awareness > I must admit that I am not familiar enough with AccountManager plugin and > Trac's security model at the moment to form a proper feature request. > > I will look into both to get an idea what we want/need here. If it turns > out that BH requires some BH multiproduct specific changes to be useful to > us, do we have any idea how plugin author would see such a request? > >
I had a look at the AccountMangerPlugin and if I did not miss something, plugin does not concern itself with permissions at all. Would that be correct? If this is in fact so, it is a good news to me as it means that no special support for multiproducts is required.
