Showing posts with label maintenance. Show all posts
Showing posts with label maintenance. Show all posts

Friday, July 19, 2013

July Report

This will be my last report, until the beginning of September. I have, for many years, been a volunteer at the Edmonton Folk Music Festival. For the next month, I will be busy setting it up (and then taking it down, and so will not have time to devote to twisted.

This month, 23 tickets got some attention that they would not have received without the sponsored development. The result was 5 closed tickets and 11 other tickets unblocked for other developers to resume work on.

This month, I made a number of improvements to the buildobt:

  • Switched most of the buildslaves to use git to checkout the source.
  • All the git-using builders merge to trunk, before running tests, so the tests results reflect the code as it would be merged. In particular, all the lint steps should now accurately report only the regressions relative to current trunk of the merged result.
  • I added a bunch of new builders on VMs provided by Rackspace (thanks to Jesse Noller) and the Fedora Project (thanks to Seth Vidal). These cover all recent versions of Debian, Fedora, Ubuntu and RHEL. As part of this, I automated the deployment of buildslaves, (currently only Debian and Fedora derivatives are supported).

This work is made possible by the sponsorship of individuals and organizations which have donated to the Twisted project, part of the Software Freedom Conservancy, a not-for-profit organization that helps promote, improve, and develop open source software. Thanks!

The tickets I reviewed, that have now been closed:

Other tickets I have reviewed:

Tickets I have worked on:

Thursday, March 28, 2013

Report the Third

During the past three weeks, 23 tickets got some attention that they would not have received without the sponsored development. The result was 9 closed tickets and 8 other tickets unblocked for other developers to resume work on.

I also spent some time working on getting newly donated slaves setup, as well as documenting the setup of the main twistedmatrix.com server, in preparation for automating the redeployment of services to new hardware.

This work is made possible by the sponsorship of individuals and organizations which have donated to the Twisted project, part of the Software Freedom Conservancy, a not-for-profit organization that helps promote, improve, and develop open source software. Thanks!

The tickets I reviewed, that have now been closed:

Other tickets I have reviewed:

Tickets I have closed:

Other tickets I have worked on:

Thursday, March 7, 2013

Second Fellowship Report

I've completed my second two weeks of development. I again spent a large amount of my time reviewing tickets. In addition, I did some development work, as well as buildbot improvements.

All told, 42 tickets got some attention that they would not have received without the sponsored development. The result was 23 closed tickets and 14 other tickets unblocked for other developers to resume work on.

Buildbot improvements

  • Added a pyflakes builder.
  • Improved lint-like builders to only show new warnings/errors introduced in the branch, rather than relative to the tip of trunk
  • Added a form to the build results page to allow switching branches and forcing builds.
  • Added an easy way to look at the history of the unsupported builders.
  • Removed links to some useless views.

This work is made possible by the sponsorship of individuals and organizations which have donated to the Twisted project, part of the Software Freedom Conservancy, a not-for-profit organization that helps promote, improve, and develop open source software. Thanks!

The tickets I reviewed, that have now been closed:

Other tickets I have reviewed:

Tickets I have closed:

Other tickets I have worked on:

Friday, December 14, 2012

Seeking a Motivated Maintainer for Twisted

The Twisted project, via the Software Freedom Conservancy, is seeking to recruit a full-time paid maintainer. We've got a fellowship proposal published on the wiki, but here are some highlights:
  • You will be working on an open source project and your contributions will be consumed by companies such as Google, Canonical, Lucasfilm/Disney, Rackspace, and Justin.TV to name a few.
  • We want to hire a full-time maintainer who will assist with the continued growth of the Twisted project.
  • Thanks to the meticulous work of your predecessors, we have a clear view of what your average week would look like in terms of tasks and responsibilities (more below).
Desired qualifications in a maintainer:
  • The ability to review code for suitability, stability, and clarity; to point out meritable work, and provide actionable feedback on how to improve the code when necessary. 
  • The ability to implement features in the Twisted library. 
  • A positive presence in Twisted's online community on IRC and the mailing list. 
  • Have familiarity with the infrastructure of the Twisted project (including trac and buildbot). 
  • Work to provide education or outreach on Twisted in other forums such as workshops, conferences, and user groups. 
We will strongly consider someone with experience maintaining other open source projects, but with just a little Twisted experience, as long as such an applicant is passionate about and committed to becoming a Twisted expert.

During an average work week, the maintainer will distribute their work along these lines:
  • Code review (55%) Review code, apply patches, and set and enforce standards for code quality. Improve documentation and code test coverage. 
  • Mailing list and IRC participation (10%) Encourage and participate in discussions on Twisted's mailing lists and IRC channels. 
  • Bug report triage (5%) Supervise Twisted's ticket workflow to ensure that bug tickets are addressed and closed. 
  • New feature development (30%) Serve as architect for the development and implementation of new features. 
Furthermore, the Maintainer will provide a forthnightly written report of their progress to the Conservancy and the Twisted community.

Information on whom to contact in the event of your interest is provided at the bottom of the page.

We look forward to hearing from you!