« Projects

cue2toc

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

    • [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?

    • [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 cue2toc 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 cue2toc

(logo)

converts CUE files to cdrdao's TOC format

from the profile of mpiroc

People who want to help (none listed yet)

Volunteer opportunities, etc.

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

No one on OpenHatch has signed up as a mentor for cue2toc. Can you? Add the tag.

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