Thanks, Tom. 

Is there a limit to the smallness of the proposed changes?  For example, if I had a possible two-line change to https://twistedmatrix.com/documents/current/api/twisted.internet.wxreactor.html (which looks like it would be done in the docstring), is it okay to just have a PR for that or does it need to be bundled with more changes?

Thanks,

Jeff


On Wed, Nov 21, 2018 at 1:31 AM Tom Most <twm@freecog.net> wrote:
On Mon, Nov 19, 2018, at 3:06 PM, Jeff Grimmett wrote:
Glyph,

Belated (I was in the thick of a few unrelated crises) thanks - it helps to understand a little bit of the background on the way it works.  I have made adjustments and everything works the way I was hoping for now. 

I wish I understood it a little better, if for no other reason than to contribute some documentation tweaks.  Just how would that work, anyway? The contribution model for Twisted is a little opaque from where I am sitting. I'd love to help in areas where I am actually capable of doing :)

Regards,

Jeff

Hi Jeff,

The Twisted development process is documented here on the wiki. It boils down to:

1. Create a ticket (on Trac)
2. Create a pull request (on GitHub)
3. Wait for a review (and address any feedback the reviewer gives)

There is more on the wiki. The same process applies to code and documentation.

Documentation changes are really helpful, especially because it is difficult for the experienced to see the rough edges that catch new users. Your confusion is a bug, and particularly with respect to the Resource model, a not uncommon one. Let's fix it!

---Tom



_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python