Hi Jorge,
> seriously please consider the argument. your wiki homepage says django > 3 times and it doesn't even has a link to pylons. From a quick look > the only thing it has in comming with pylons is that they both use > paste, which as you know using paste is normally using less than 10% > of it's tools. > > So as Ben said, if you guys at least have some examples on how to use > your django toolkit on top of pylons (or at least a list of reasons > why it could be a good idea) then this post doesn't belongs here. I know that my wiki page suck. I have very little budget and resources. notmm is not funded in any ways, and doesn't make the news quite often. But I like working and contributing to open source projects. Despite this, I've found that raising a open source project from scratch can be painful. Bigger projects attracts larger pools or developers and therefore are more easily visible, gets more funding, and so forth. So, if bigger projects like Pylons or Django don't even let smaller embryonic projects evolves, I can understand very well why theses projects are so popular, and lesser known projects gets very little visibility. Sorry about the wiki page. I'll try to write something on Pylons shortly. Thanks, Etienne --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
