« Projects


  • Q: I'd like to participate. How do I begin?

    • 2

      Hop on #pyblosxom on Freenode.net and hang out with us. We talk about plugins, pyblosxom core, bugs, features, and how people are using PyBlosxom on their own systems.

      These discussions lead to development and testing which leads to new versions of things.

         — Will Kahn-Greene (willkahngreene) · 9 years ago
    • [X]
      • Tip:

        Talk about diverse kinds of contributions. Include URLs if relevant (we'll automatically linkify them).

      • Examples:

        Here's how to download and patch our codes…

        Read about our death-defying mailing list and momentous IRC channel at http://lobstermag.net.

  • Q: Other than writing code, how can I contribute?

    • 1
      documentation feedback

      I work on the documentation in spurts, generally after someone has provided feedback. It's really hard to build quality comprehensive documentation without feedback from users and other people who have read bits of the documentation. Feedback could include things you found confusing, diagrams that would really help to have, examples that are incorrect, other things that need explaining.

      We hang out on #pyblosxom on Freenode.net. Hop on and let us know what you think could be better.

         — Will Kahn-Greene (willkahngreene) · 9 years ago
    • [X]
      • Tip:

        Discuss documentation, testing, webmastering, and/or publicity.

        Include URLs if relevant (we'll automatically linkify them).

      • Example:

        We need people to download version 0.4.5 and make sure the frobulator still frobulates correctly.

  • Q: What's a good bug for a newcomer to tackle?

    • [X]
      • Tip:

        Many projects have good small tasks that can teach newcomers how the project works. Now's your chance to share one of them!

        Include URLs if relevant (we'll automatically linkify them).

      • Example:

        Someone could improve the photo upload dialog box so that it lets you resize the photo before sending it to the web.

  • Q: What is a bug or issue with PyBlosxom that you've been putting off, neglecting, or just plain avoiding?

    • [X]
      • Examples:

        I don't know how to get started with internationalizing my app.

        Bug 392 about printing was filed five years ago, and I don't even know if printing still works.

        I want help from a C coder writing a Maildir patch for Alpine.

      • Note:

        If this issue was formally filed on the web, be sure to include the URL.

What else do you want to talk about?

About PyBlosxom


PyBlosxom is a lightweight file-based weblog system written originally in the spirit of Blosxom (but in Python), but has since evolved into its own project. It has flavours and plugins and a variety of ways to fit into your workflow and your website.

from the profile of Will Kahn-Greene (willkahngreene)

The code is mostly written in Python.

People who want to help (29)

The following people are interested in helping. Send them an email! (tips)

You can use this page to track who has been contacted if you log in. There will be a checkbox next to their name. When you check it, the page will publish today's date and your username.

Volunteer opportunities, etc.

No volunteer opportunities in PyBlosxom indexed here yet. Add a bug tracker.

There is 1 person who can mentor in PyBlosxom.

There are 326 people who can mentor in Python, PyBlosxom's primary language.

You can embed the "I want to help" button on your website. (More about this.)