I’m interested in using web2py for some business/enterprise applications, but other collaborators of mine have reservations about web2py because it is a new framework, and that there is no explicit long-term roadmap. Some of you may have a similar experience.
I think the community would benefit greatly from having a discussion about milestones and the roadmap. My opinion is that web2py will be adopted faster by businesses if the planning was clear and documented. Also we can speed-up releases by concentrating our efforts. Maybe I can begin this discussion by asking: A. What are some of the priorities, either regarding architecture, features, or performance that each of you would like to see in the coming releases of web2py? B. What are the goals for v2.0 and v3.0? Thanks! Lucas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
