im.py: a python communications tool

Demian Brecht demianbrecht at gmail.com
Fri Apr 5 20:52:47 EDT 2013


Thanks for sharing some of your work with the community. However...

Speaking to the sharing aspect: Why would you post a block of code in an
email? If you're looking for people to contribute, it would likely be a
much better idea to post it on github (which was built for collaborative
work).

As for the code itself, if you /know/ it sucks and are advertising it as
such, you're not really enticing people to work on it. In its current
state, it looks like a non-extensible prototype, just poking around to see
how you can achieve a p2p connectivity, without doing /any/ research
(supporting modules, etc) or design before just starting to throw something
together.

I'd venture to say that the chances of actually getting anyone to
contribute to this in its current state (especially purely over a mailing
list) would be slim to none. People generally tend to want to see that
there's actually effort and thought put into something before they put
/their/ own time into it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20130405/05a3ed92/attachment.html>


More information about the Python-list mailing list