Job Openings

With a family of Open Source projects, there is always work to be done. We need help, in all kinds of areas, for all skill levels.

This is Open Source volunteer work. The pay is zero, but you’ll get your hands dirty in a set of active projects that need all different kinds of help. Perhaps you’re a professional with a little time here and there to donate to the projects. Perhaps you’re new to this, and would like to be active in Open Source, in a friendly community where you can get lots of help, make much-needed contributions, and maybe learn something.

We believe a lot of you would like to join in, but don’t know where to start. We’ll guide you and teach you what you need. Talk to us.

Open Source: Good for the software. Good for the résumé/c.v. Good for the soul.

Issue Manager

Responsibilities

You own the Jira databases for all projects.

This involves:

  • Process new issues: fill in blanks, ask for more details, reject the crazy.
  • Reproduce problems.
  • Combine the duplicates.
  • Assess old issues for relevance.
  • Assign priorities and fix version, where possible.
  • Keeps the tags and versions up to date.
  • Link the related issues.
  • Help with version planning.
  • Advise development on patterns and weaknesses found.
  • Veto for project releases.

Skills Needed

  • Attention to detail.
  • Organization.

Time Commitment

An hour or two a week minimum. Maybe more.

Test Automation

Responsibilities

You own the test suites for all the projects.

This involves:

  • Creating new Python unit tests where necessary.
  • Create new tests from tags in Jira.
  • Refactor bad tests.
  • Combining/reducing existing duplicate tests.
  • Improving test coverage. Taskwarrior was at 90% some time ago, the others we don’t have time to check.
  • Improve release quality.
  • Improve test suite speed.
  • Veto for project releases.
  • Advise development about areas of weakness, feature asymmetry.

Skills Needed

  • Python.
  • Attention to detail.

Time Commitment

Minimally an hour or two a week.

Sound and Fury

Everyone loves a live demo, but we have five-year-old tutorials online, which are not only out of date, but way too long.

Responsibilities

You own the visual demos and tutorials.

This involves:

  • Create good feature-specific demos for YouTube and/or Asciinema.
  • Create demos of interesting new use cases.
  • Organize the demos.
  • Show off the demos on the site and social media.
  • Establish a visual changelog for each release.

Skills Needed

  • Video capture.
  • Narration where needed.

Time Commitment

We don’t know. Demos are hard work.

Technical Community Liaison

Responsibilities

You own the relationships with downstream clients.

This involves:

  • Work with distro package maintainers to pull patches upstream.
  • Nudge distros to update the packages.
  • Make sure distros are doing the right thing with dev/alpha/beta versions.
  • Help us find a Cygwin package maintainer.
  • Advise distros with their documentation.
  • Identify missing distros and make noise.
  • Solve some problems: Debian won’t use our PDFs, or update old GnuTLS libs.
  • Advise development on distro issues, improvements.

Skills Needed

Communication, fearlessness.

Time Commitment

An hour or two a week.

Documentation Manager

Responsibilities

You own all the documentation for all the projects.

This involves:

  • The structure and organization of all the existing documents.
  • The rewriting and combination of existing documents.
  • Consistency issues between man pages and online documents.
  • Visual presentation of the documents.
  • Appropriate examples and screenshots.
  • Remove/replace obsolete documentation.
  • Veto for project releases.

Skills Needed

  • Clear communication.
  • Organization.

Time Commitment

We don’t know. More at first, less over time.

Publishing

The websites are currently handwritten HTML using templates. We wish to move to a markdown-based system, to generate a variety of document types.

Responsibilities

You own the site publishing infrastructure decision.

This involves:

  • Work with us to define requirements for static site generator.
  • Evaluate and select static content generator.
  • Proof of concept.
  • Establish page templates.
  • Migrate site to Markdown.

Skills Needed

Document management.

Time Commitment

A few hours a week at first.