[Twisted-Python] Twisted easy bugs, and other thoughts about getting people involved in Twisted
I ran into David Reid at PyCon a few weeks ago, and I showed him an index of "easy" and "bitesize" bugs I'm putting on the web at https://openhatch.org/search/. He told me that the Twisted team tags bugs as "easy" in Trac. So all you might like to see https://openhatch.org/search/?q=Twisted&toughness=bitesize -- it's the result of search for bugs whose full text or project matches "Twisted", constrained to only include the bugs that are "easy". This is the same query as http://twistedmatrix.com/trac/query?status=new&status=assigned&status=reopened&keywords=~easy&order=priority -- the same 18 tickets -- but cached in our index. The OpenHatch website aims to show helpful, friendly things to potential new contributors. A list of bugs isn't always adequate, so I'm really happy jesstess wrote some tips on the OpenHatch project page regarding getting involved in Twisted: https://openhatch.org/+projects/Twisted The "Relatedly" sidebox on that project page has other helpful links: potential mentors, namely people who have signed into OpenHatch and said they can mentor in Python or Twisted. So that's a quick tour of some of relevant things to you guys. I have a few questions for you guys, if you're game: * Of these things, what are the most interesting or useful? the least? * Are there other tickets from the Twisted Trac that would be good to pull in? * Would you like me to ping the list if we come up with anything else I think you might find interesting? * Do any of you want to re-use some of this data -- can we make that easier? We're pretty interested in helping projects convert users to contributors (in code, testing, documentation, whatever!) across free software. I wonder if there is a website widget that we could make for you to put on twistedmatrix.com -- a big box talking about how "You TOO can contribute to Twisted -- there are mentors, easy bugs, and everything!" This email has gotten fairly long, so I'll stop here for now. I don't mean to barge in; let me know if I'm unwelcome, and I'll wander off. I find myself in a maze of Twisted developers, none of whom are alike. Thanks! I'll be hanging out on #twisted as myself, paulproteus. -- Asheesh. P.S. If you think this is interesting, stay in touch with us: IRC (freenode): #openhatch Twitter/Identi.ca: @openhatchery blog: https://openhatch.org/blog/ email and more: https://openhatch.org/contact/ P.S. The OpenHatch website has its source in git and shared under a free license -- https://openhatch.org/source-code-etc/ -- "World conquerors sometimes become fools, but fools never become world conquerors." -- "The Outer Limits: The Invisibles"
On Thu, Mar 11, 2010 at 6:02 PM, Asheesh Laroia <twisted@asheesh.org> wrote:
So that's a quick tour of some of relevant things to you guys. I have a few questions for you guys, if you're game:
* Of these things, what are the most interesting or useful? the least?
If OpenHatch has users, the most interesting thing is simply that they will be looking at these lists :).
* Are there other tickets from the Twisted Trac that would be good to pull
in?
For new contributors? Not that I can think of.
* Would you like me to ping the list if we come up with anything else I think you might find interesting?
Sure.
* Do any of you want to re-use some of this data -- can we make that easier?
Isn't this all data that we're providing to *you*? I don't understand why we'd want to be pulling things back out of OpenHatch. Perhaps I've misunderstood.
We're pretty interested in helping projects convert users to contributors (in code, testing, documentation, whatever!) across free software. I wonder if there is a website widget that we could make for you to put on twistedmatrix.com -- a big box talking about how "You TOO can contribute to Twisted -- there are mentors, easy bugs, and everything!"
Anything that would help us organize that information to appeal to potential contributors would be helpful.
I don't mean to barge in; let me know if I'm unwelcome, and I'll wander off. I find myself in a maze of Twisted developers, none of whom are alike. Thanks! I'll be hanging out on #twisted as myself, paulproteus.
Please feel free to stay in touch. Getting more people involved in Twisted development is always of interest.
On Sat, 13 Mar 2010, Glyph Lefkowitz wrote:
On Thu, Mar 11, 2010 at 6:02 PM, Asheesh Laroia <twisted@asheesh.org> wrote: So that's a quick tour of some of relevant things to you guys. I have a few questions for you guys, if you're game:
* Of these things, what are the most interesting or useful? the least?
If OpenHatch has users, the most interesting thing is simply that they will be looking at these lists :).
All right! (-:
* Are there other tickets from the Twisted Trac that would be good to pull in?
For new contributors? Not that I can think of.
I did just notice there's a documentation tag. Is that something that you'd want us to pull in, too? I imagine you'll say yes -- I'm mostly asking to get your creative juices flowing and see if there's anything else....
* Would you like me to ping the list if we come up with anything else I think you might find interesting?
Sure.
Yay.
* Do any of you want to re-use some of this data -- can we make that easier?
Isn't this all data that we're providing to you? I don't understand why we'd want to be pulling things back out of OpenHatch. Perhaps I've misunderstood.
I'm mostly referring to things like jesstess's "How to get involved" answers. One more thing -- pulling data out of Trac isn't actually super easy (-:. So if you want us to re-export that in some really simple format like a big JSON list, that's something else we can do.
We're pretty interested in helping projects convert users to contributors (in code, testing, documentation, whatever!) across free software. I wonder if there is a website widget that we could make for you to put on twistedmatrix.com -- a big box talking about how "You TOO can contribute to Twisted -- there are mentors, easy bugs, and everything!"
Anything that would help us organize that information to appeal to potential contributors would be helpful.
Here's a dream: A big and colorful box sits on the Twisted homepage. It says "Want to help Twisted out, but feel shy about getting your feet wet? There are five mentors standing by to help you dive in, 18 easy bugs, and 25 requests for documentation." (Only maybe somehow it could use less words?) That might take the person to the OpenHatch project page for Twisted, where all that information is listed or available a click away. The widget on the Twisted home page could pull data from OpenHatch's project page. I don't know that *we* would get around to it soon, but certainly we can provide the data pretty quickly. We might also get around to it sometime. In fact, I just filed a bug with the above text -- https://openhatch.org/bugs/issue35
I don't mean to barge in; let me know if I'm unwelcome, and I'll wander off. I find myself in a maze of Twisted developers, none of whom are alike. Thanks! I'll be hanging out on #twisted as myself, paulproteus.
Please feel free to stay in touch. Getting more people involved in Twisted development is always of interest.
Great! (-: -- Asheesh. -- Ours is a world of nuclear giants and ethical infants. -- General Omar N. Bradley
On 14 Mar, 04:53 pm, twisted@asheesh.org wrote:
One more thing -- pulling data out of Trac isn't actually super easy (-:. So if you want us to re-export that in some really simple format like a big JSON list, that's something else we can do.
How do you mean? It's actually pretty straightforward to get data out; you can have it as rss, csv, or tsv in most cases. This leads me to wonder how you grabbed the "easy" tickets from the tracker. Surely this is an automated process which is reading the csv format of a trac "tickets with `easy` keyword" query page? If not, how does the OpenHatch listing stay up to date? Jean-Paul
On Mon, 15 Mar 2010, exarkun@twistedmatrix.com wrote:
On 14 Mar, 04:53 pm, twisted@asheesh.org wrote:
One more thing -- pulling data out of Trac isn't actually super easy (-:. So if you want us to re-export that in some really simple format like a big JSON list, that's something else we can do.
How do you mean? It's actually pretty straightforward to get data out; you can have it as rss, csv, or tsv in most cases.
Yeah -- but (see below)
This leads me to wonder how you grabbed the "easy" tickets from the tracker. Surely this is an automated process which is reading the csv format of a trac "tickets with `easy` keyword" query page? If not, how does the OpenHatch listing stay up to date?
It is doing just that to find the IDs to look at. Then it actually scrapes the Trac-rendered HTML because the CSV export (as far as I know) can't tell us answers to questions like, "How many people were active on this bug?" I find that's a useful thing to show off. So it's a combination of both, and we end up with a little more data than the Trac API exports. I'll probably start serving out JSON dumps soon. -- Asheesh. -- "No one gets too old to learn a new way of being stupid."
On Wednesday 17 March 2010, Asheesh Laroia wrote:
Then it actually scrapes the Trac-rendered HTML because the CSV export (as far as I know) can't tell us answers to questions like, "How many people were active on this bug?" I find that's a useful thing to show off.
Not sure if it helps in your case, but I once made a script that produced a table of tickets associated with a milestone, to include with release notes. It needed the 1-line summary, which was not included in the CSV export. I thought I would have to resort to scraping the HTML, but then found that the RSS feed contained all the info I needed. Bye, Maarten
participants (4)
-
Asheesh Laroia -
exarkun＠twistedmatrix.com -
Glyph Lefkowitz -
Maarten ter Huurne