On Aug 23, 2010, at 6:07 PM, BrianTheLion wrote: > At this point in my effort, though, certain questions about the > overall design of fbpylons and its approach to solving the problems at > hand are starting to surface. Hence, my interest in soliciting > feedback and help from others who have also been working on Facebook > apps for a while. I hope this thread will serve as a point of > technical discussion, and well as a launching pad for the Facebook/ > Pylons uber-package of our dreams. > > Now who's with me?
Sounds great! The next version of Pylons is going to include a substantial amount of extension points, which will make it easier to build extension packages. I'm creating a pylonsext namespace package for Official Pylons Extensions as well. Official Pylons Extensions must be: - 100% Unit Tested - Fully Documented - Use the pylonsext.* package namespace This is similar in requirements to Flask extension requirements. Are you volunteering to be the maintainer of the pylons-facebook extension? :) Cheers, Ben -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
