processing / processing/processing4

💙 Add yourself to the all-contributors list!

Ouverte
#839 37 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Langage dominant
Java
Étoiles
494
Forks
183
Merge moyen
4 h 39 min
PR mergées (30 j)
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

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez par la section dédiée aux contributeurs dans le README et le fichier .allcontributors-src décrits dans l’issue, puis consultez la documentation sur l’utilisation du bot all-contributors. C’est terminé lorsque le bot accepte le type de contribution demandé et que le contributeur apparaît dans la liste générée du README.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Domaine
documentation
Type d'issue
Documentation
Difficulté
1/5
Temps estimé
Moins d'une heure
Activité
À l'abandon
Clarté
Clairement spécifiée
Accessibilité débutants
55/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.