Hey,<div><br></div><div>I think that the list could become really large...</div><div><br></div><div>megrok.* : <a href="http://pypi.python.org/pypi?:action=search&term=megrok&submit=search">http://pypi.python.org/pypi?:action=search&term=megrok&submit=search</a></div>
<div>hurry.* : <a href="http://pypi.python.org/pypi?:action=search&term=hurry&submit=search">http://pypi.python.org/pypi?:action=search&term=hurry&submit=search</a></div><div>dolmen.* <a href="http://pypi.python.org/pypi?:action=search&term=dolmen&submit=search">http://pypi.python.org/pypi?:action=search&term=dolmen&submit=search</a></div>
<div><br></div><div>or the idea it's to include just some of those packages??</div><div><br></div><div>Maybe we should use something similar to the Plone Software Center, but simpler. A basic content type with the following fields</div>
<div><br></div><div>- Library Name</div><div>- Description</div><div>- Dependencies</div><div>- License</div><div>- Latest release date</div><div>- Pypi url</div><div>- Sources url</div><div><br></div><div>By using keywords, we could define: "Static resources", "File storage", "Relational Database", "Url dispatch", "Workflow", etc., and show each of these as Collections of something...</div>
<div><br></div><div>just an idea...</div><div><br></div><div>Best Regards</div><div><br><div class="gmail_quote">On Thu, Nov 19, 2009 at 7:33 AM, Souheil CHELFOUH <span dir="ltr"><<a href="mailto:trollfot@gmail.com">trollfot@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Well, I have a lot of things to add on that page<br>
How can we make it easy to work together on description ?<br>
What about a SVN repository with some RST docs, so we could work on<br>
that properly ?<br>
Not that I want to push my work forward, but I can at least add all<br>
the Dolmen libraries I coded<br>
<br>
2009/11/19 Sebastian Ware <<a href="mailto:sebastian@urbantalk.se">sebastian@urbantalk.se</a>>:<br>
<div><div></div><div class="h5">> Fantastic list! I have allready found stuff I wasn't aware existed and<br>
> that I will probably have use for soon.<br>
><br>
> 19 nov 2009 kl. 05.55 skrev Steve Schmechel:<br>
><br>
>> It was rather sad to note that most of the "useful" libraries are<br>
>> not covered in the Grok how-to's and tutorials. Seems peculiar and<br>
>> maybe we should think of ways to address that.<br>
><br>
><br>
> I don't think we should get too worried about this right now. In it's<br>
> current state, Grok suits developers who don't mind looking at the<br>
> documentation availble in doctests and readme.txt files. I think we<br>
> should be quite open with that.<br>
><br>
> I don't see it as a flaw, but rather a characteristic of the framework.<br>
><br>
> It is like unix, if you don't feel comfortable with a command prompt,<br>
> you won't appreciate unix.<br>
><br>
> Mvh Sebastian<br>
><br>
> _______________________________________________<br>
> Grok-dev mailing list<br>
> <a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
> <a href="https://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">https://mail.zope.org/mailman/listinfo/grok-dev</a><br>
><br>
_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
<a href="https://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">https://mail.zope.org/mailman/listinfo/grok-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Santiago Videla<br><a href="http://www.linkedin.com/in/svidela">http://www.linkedin.com/in/svidela</a><br><br>Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que l@s tod@s somos.<br>
</div>