On Monday February 2, 2009 16:41:07 Christoph Zwerschke wrote: > How about "repoze.auth-quickconf"? That would be less confusing.
+1, I like it better. :) Although, I'd prefer to change it once repoze.what v2 is out, or when we're getting close. Right now r.what v1 is not the de facto authorization framework in the Repoze project (there's repoze.decsec and repoze.bfg uses its own framework), so I think it'd make more sense to have "repoze.auth-quickconf" if it configures the de facto authentication and authorization frameworks for the Repoze project -- and I think there are chances for repoze.what v2 to become that authorization framework. > Also, I'd like to see repoze.who.plugins.sa and repoze.what.plugins.sql > use the same suffix (either sa or sql), since they both use SQLAlchemy. > Maybe even merge them into a "repoze.auth-sql" package? I don't think that the fact that both use SQLAlchemy is enough to consider merging them. What would be the advantage? I can see other issues though: * Our goal is not to mix authentication and authorization, not even in the plugins. * repoze.what's userbase is small (it's new after all), compared to repoze.who's. People using repoze.who only don't need and don't want to know about repoze.what's SQL-based adapters. I think these people should not be bothered to update some of their imports because repoze.who.plugins.sa is superseded by a new package whose improvement (the inclusion of repoze.what SQL adapters) is useless for them. * What would be its dependencies in addition to SA? repoze.who? repoze.what? repoze.who and repoze.what? What if they only want one of them? OK, I may exclude both r.what and r.who from the dependencies, but what if later on a new release requires at least version X.Y of repoze.who/what? * "repoze.auth-sql" may not work because there's already a SQL plugin for r.who and it's official, which would leave us with "repoze.auth-sqlalchemy" or "repoze.auth-sa". I mean, I'm open to merge them if I see a problem with their current state. But that they share a main dependency is not a problem from my point of view. Cheers! -- Gustavo Narea <http://gustavonarea.net/>. Get rid of unethical constraints! Get freedomware: http://www.getgnulinux.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
