On Fri, Jun 13, 2008 at 12:07 PM, Phil Christensen <<a href="mailto:phil@bubblehouse.org">phil@bubblehouse.org</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Jun 13, 2008, at 12:04 PM, Johan Euphrosine wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As part of a freelance job, I'm asked to glue twisted with other<br>
technologies together as a proof of concept of what be done (and how),<br>
in the context of a service communicating with C++ games.<br>
<br>
As it may be useful to someone else, I'm pushing the source here:<br>
<a href="http://proppy.aminche.com/hg/service-test/" target="_blank">http://proppy.aminche.com/hg/service-test/</a><br>
</blockquote></div>
[snip]<div class="Ih2E3d"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I wonder if it is worth contributing on its own, to the newly created TX<br>
project.<br>
<br>
Maybe some parts of it could be extracted, and made into a more<br>
submittable (and useful) shape.<br>
</blockquote>
<br></div>
The great thing about the Twisted Community Code project is that you don't need any particular approval from anyone to add your code. If you think what you have might be of use to someone, whether it's for production use or just as a learning tool, you should consider creating a TX subproject.<br>
<br>
There are other options as well. If you feel your code doesn't warrant the overhead of a full project (e.g., you don't see yourself having time to respond to bug requests or create blueprints, etc.), you should be able to create a personal Bazaar branch to store your code in, which you can then assign to the TX superproject.<br>
<br>
This probably won't get as many eyeballs, since it won't be on the subproject list, but it's a good way to get your code out there in an easily accessible place. Plus, given the nature of Bazaar, anyone who wishes will be able to work with your code in their own branch.<br>
<font color="#888888">
<br>
-phil</font><div><div></div><div class="Wj3C7c"><br>
</div></div></blockquote><div><br></div></div>BTW, Phil, are there any established guidelines/conventions for the "TX" packages other than "start your project name with a 'tx'"?<br><br>Any suggestions or guidelines on how such packages should leverage setuptools, stuff like that?<br>
<br>I think it would be very useful to have all of these packages install in a similar fashion, though of course, it wouldn't be practical (or advisable) to try and enforce this in any way. But I do think it would be good to have a set of guidelines posted someplace saying "here is the recommended way to set up a TX package".<br>
<br>Kevin Horn<br>