Infrastructure/Get a Developer Account: Difference between revisions
Add another benefit |
Re-add mention of translators, who also can benefit from having a developer accounts |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Info|You do not need a KDE Developer account to browse source code, log into https://invent.kde.org, submit merge requests, or participate in other normal development activities. Instead, all you need is a normal '''KDE Identity Account'''; see [[Infrastructure/GitLab|GitLab]] instead.}} | {{Info|You do not need a KDE Developer account to browse source code, log into https://invent.kde.org, submit merge requests, or participate in other normal development activities. Instead, all you need is a normal '''KDE Identity Account'''; see [[Infrastructure/GitLab|GitLab]] instead.}} | ||
When you have been doing development work in KDE for some time and many of your merge requests have been merged without drama, you may be encouraged to apply for a '''KDE Developer account.''' This will grant you the ability to do the following: | When you have been doing development work in KDE for some time and many of your merge requests or translations have been merged without drama, you may be encouraged to apply for a '''KDE Developer account.''' This will grant you the ability to do the following: | ||
# Formally approve other people's merge requests | # Formally approve other people's merge requests | ||
# Set and change milestones and labels on merge requests and issues | # Set and change milestones and labels on merge requests and issues | ||
# Merge other people's approved merge requests, or your own | # Merge other people's approved merge requests, or your own | ||
# Directly push | # Directly push commits to change files in almost all of KDE's git and svn repositories | ||
Before you apply for a KDE Developer account, you must read, understand, and accept [[Policies/Commit Policy|the KDE commit policy]] when using your future KDE Developer account. Please also familiarize yourself with the [http://www.kde.org/code-of-conduct/ KDE Code of Conduct] which describes the social foundations within KDE, and the [https://manifesto.kde.org/ KDE Manifesto] that describes KDE's values. | Before you apply for a KDE Developer account, you must read, understand, and accept [[Policies/Commit Policy|the KDE commit policy]] when using your future KDE Developer account. Please also familiarize yourself with the [http://www.kde.org/code-of-conduct/ KDE Code of Conduct] which describes the social foundations within KDE, and the [https://manifesto.kde.org/ KDE Manifesto] that describes KDE's values. Holders of KDE Developer accounts are expected to uphold the highest ethical standards and not abuse the privileges they have been granted by committing controversial or un-approved changes. | ||
Once you plan to contribute to KDE over the long term, and are ready to assume these responsibilities, visit the [https://identity.kde.org/index.php?r=developerApplication Developer Application page] to submit your application. | Once you plan to contribute to KDE over the long term, and are ready to assume these responsibilities, visit the [https://identity.kde.org/index.php?r=developerApplication Developer Application page] to submit your application. | ||
| Line 14: | Line 14: | ||
The form there will ask you a series of questions, including ''Why do you want an account?'', where you can explain what you want to do with your future KDE Developer account and why it's not enough to let other people merge your merge requests for you. List your sponsor who encouraged you to apply. They will also get an email to verify your request. | The form there will ask you a series of questions, including ''Why do you want an account?'', where you can explain what you want to do with your future KDE Developer account and why it's not enough to let other people merge your merge requests for you. List your sponsor who encouraged you to apply. They will also get an email to verify your request. | ||
KDE's sysadmins have the last word about whether or not to approve a KDE Developer account for somebody | KDE's sysadmins have the last word about whether or not to approve a KDE Developer account for somebody. | ||
Latest revision as of 16:15, 1 April 2024
Information
When you have been doing development work in KDE for some time and many of your merge requests or translations have been merged without drama, you may be encouraged to apply for a KDE Developer account. This will grant you the ability to do the following:
- Formally approve other people's merge requests
- Set and change milestones and labels on merge requests and issues
- Merge other people's approved merge requests, or your own
- Directly push commits to change files in almost all of KDE's git and svn repositories
Before you apply for a KDE Developer account, you must read, understand, and accept the KDE commit policy when using your future KDE Developer account. Please also familiarize yourself with the KDE Code of Conduct which describes the social foundations within KDE, and the KDE Manifesto that describes KDE's values. Holders of KDE Developer accounts are expected to uphold the highest ethical standards and not abuse the privileges they have been granted by committing controversial or un-approved changes.
Once you plan to contribute to KDE over the long term, and are ready to assume these responsibilities, visit the Developer Application page to submit your application.
The form there will ask you a series of questions, including Why do you want an account?, where you can explain what you want to do with your future KDE Developer account and why it's not enough to let other people merge your merge requests for you. List your sponsor who encouraged you to apply. They will also get an email to verify your request.
KDE's sysadmins have the last word about whether or not to approve a KDE Developer account for somebody.