Taking Ben's suggestion, I just went ahead created a new thread. Mike Orr said: """ I have started a Talking Points wiki page to gather the essential points. Please add anything that's missing.
http://wiki.pylonshq.com/display/pylonscommunity/Talking+Points """ Thanks Mike, what do you and the other core team propose we do from here with this starting point? It is probably the area where I can most helpfully contribute to Pylons, as I've done a fair bit of sales/marketing stuff and as I mentioned, I feel I have a real vested interest in making sure that clients feel good about the future viability of Pylons ( and Repoze, Pypes, etc ). As cheesy as it sounds ( and we don't have to call it that ), I think we need a clear "Pylons Vision Statement". The purpose and future goals of Pylons distilled into a few very clear sentences that help separate it from competition, but in a realistic and accurate manner. IMHO, I believe this has been one the main problems for TG, no real clear vision on what the framework was trying to provide and for whom. Some wanted it to be a django-competitor, others something different, and that has been an elephant in the room for too long now. iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
