processing / processing/processing4
π Add yourself to the all-contributors list!
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 494
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
We recognize all types of contributions in the README! The Processing project follows the all-contributors specification and the Emoji Key β¨ for contribution types. All the Processing contributors, you all are πβ¨π₯ π
If you have contributed to the Processing project in some way and aren't listed, please add an entry for yourself by commenting with this template @all-contributors please add @YourGitHubHandle for ___ ( '___' can be any of the items listed below, like code, bug, doc). The all-contributors bot supports a variety of contribution types. See the full list in the table below.
For example, if your GitHub username is @AnnieEasley and you have made an artwork with Processing, you can add yourself as example contributor by replying to this issue with the following:
@all-contributors please add @AnnieEasley for example
Look at this cool sketch I made: <link your artwork>
If you have trouble with this, you can comment below and we will make sure to add your name.
The README file will get updated based on the .allcontributors-src file each time all-contributors generate is run.
For more information about using the all-contributors bot, see this documentation page.
Contribution types
| Emoji/Type | Represents | Comments (optional) |
|---|---|---|
π audio |
Audio | Podcasts, background music or sound effects |
βΏοΈ a11y |
Accessibility | Reporting or working on accessibility issues |
π bug |
Bug reports | Links to issues reported by the user on this project |
π blog |
Blogposts | Links to the blogpost |
πΌ business |
Business Development | People who execute on the business end |
π» code |
Code | Links to commits by the user on this project |
π content |
Content | e.g. website copy, blog posts are separate |
π£ data |
Data | Links to contributed data for the project (both tests and datasets) |
π doc |
Documentation | Links to commits by the user on this project, Wiki, or other source of documentation |
π¨ design |
Design | Links to the logo/iconography/visual design/etc. |
π‘ example |
Examples | Links to the examples |
π eventOrganizing |
Event Organizers | Links to event page |
π΅ financial |
Financial Support | People or orgs who provide financial support, links to relevant page |
π fundingFinding |
Funding/Grant Finders | People who help find financial support |
π€ ideas |
Ideas & Planning | |
π infra |
Infrastructure | Hosting, Build-Tools, etc. Links to source file (like travis.yml) in repo, if applicable |
π§ maintenance |
Maintenance | People who help in maintaining the repo, links to commits by the user on this project |
π§βπ« mentoring |
Mentoring | People who mentor new contributors, links to the repo home |
π¦ platform |
Packaging | Porting to support a new platform |
π plugin |
Plugin/utility libraries | Links to the repo home |
π projectManagement |
Project Management | |
π£ promotion |
Promotion | |
π¬ question |
Answering Questions | Answering Questions in Issues, Stack Overflow, Gitter, Slack, etc. |
π¬ research |
Research | Literature review. |
π review |
Reviewed Pull Requests | |
π‘οΈ security |
Security | Identify and/or reduce security threats, GDPR, Privacy, etc |
π§ tool |
Tools | Links to the repo home |
π translation |
Translation | Links to the translated content |
β οΈ test |
Tests | Links to commits by the user on this project |
β
tutorial |
Tutorials | Links to the tutorial |
π’ talk |
Talks | Links to the slides/recording/repo/etc |
π userTesting |
User Testing | Links to user test notes |
πΉ video |
Videos | Links to the video |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the contributor section in the README and the .allcontributors-src file described in the issue, then review the all-contributors bot usage documentation. Done means the bot accepts the requested contribution type and the contributor appears in the generated README list.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100