-
Notifications
You must be signed in to change notification settings - Fork 317
TasksForNewContributors
h1. Tasks for New and Casual Contributors
We've tagged tasks that we think are suitable for new and casual PortAudio contributors with the STARTER or STARTER-PLUS keywords. You can get a list of active tasks here:
url:http://www.assembla.com/spaces/portaudio/tickets
-
STARTER tickets involve a small code or documentation change, or a number of repeated similar code changes. They may also be QA type tasks such as compiling and running a set of tests against a particular host API.
-
STARTER-PLUS tickets may require some study of the code to work out how to implement the ticket. Usually there's existing code in another host API you can refer to.
If you'd like to work on one of these tickets let us know on the mailing list so we can assign the ticket to you, help you out and answer your questions, review your work and commit the results.
We've tried to annotate each starter ticket with enough information to make it clear what needs to be done. Please ask for more info on the mailing list if a ticket doesn't make sense to you, or doesn't have enough detail for you to act on.
h2. Time estimates with the TIME keyword
These tickets also have a TIME keyword to indicate how long we think it might take you to finish the task. (TIME-1H means one hour, TIME-2D means two full days). These are very rough estimates but should give you a quick idea about the relative complexity of the tasks -- if you think we're way off let us know.
h2. Guidelines for developers tagging new STARTER tickets
If you find other tasks that belong here please tag them or post to the mailing list to discuss.
Make sure the task can be done by a competent developer with minimal experience with the PortAudio source code. Use STARTER for short tasks and STARTER-PLUS for tasks that might require a bit more stamina or investment of time and research. Make sure the ticket includes a description and comments sufficient for the contributor to understand what needs to be done. Include a TIME-XX keyword to indicate how long it might take to complete the task. TIME-XH for hours, TIME-XD for days.