Infrastructure/Get a Developer Account: Difference between revisions

Latest revision as of 16:15, 1 April 2024

Information

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 GitLab instead.

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.

@@ Line 1: / Line 1: @@
-This tutorial is about how to apply for a commit account for KDE so that you may change files (code, documentation files, art, etc.) in KDE's git and svn repositories.
+{{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.}}
-== Read-only access to Git or Subversion ==
+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:
-All KDE repositories can be cloned or checked out anonymously, without needing any account.
+# 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
-== KDE Identity Account ==
+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.
-In order to submit merge requests with [[Infrastructure/GitLab|GitLab]], you'll need a '''KDE Identity Account'''.
+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.
-These can be registered using the self-service [https://identity.kde.org/ KDE Identity] site. As part of this process, you will need to provide a name and email address, which has to be your own. Please note that these details '''will be made publicly visible on Gitlab''' once you have logged in there. You may therefore receive some spam as an unfortunate consequence of this.
+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.
-When selecting your username, please ensure you select something which has a relation to your real name.
+KDE's sysadmins have the last word about whether or not to approve a KDE Developer account for somebody.
-'''A Developer Account is not needed to fork repositories and submit merge requests on Gitlab.'''
-Also note that this email address should be the same one that you use on [http://bugs.kde.org bugs.kde.org]. If you don't have an account in [http://bugs.kde.org bugs.kde.org], please create one so that it can be given usual developer rights. Closing bug reports with keywords in commit comments only works if the email address associated with your KDE Developer account and [http://bugs.kde.org bugs.kde.org] accounts match.
-== How to get read-write access to Git (Gitlab) (or SVN for translators) ==
-Please note that a KDE Developer account is not needed to submit merge requests on Gitlab. This can be done by anyone who holds a KDE Identity account.
-In most cases people will be encouraged by existing developers to apply for a KDE Developer account, although it is not required.
-When you are ready to apply for a KDE Developer account, you should visit the [https://identity.kde.org/index.php?r=developerApplication Developer Application page] to submit your application.
-This form 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, like for example developing a certain application, making documentations or being the team leader of a translation.
-Also note that the form will ask you who has encouraged you to apply. They will also get an email to verify your request.
-== Who Can Apply For a KDE Developer Account? ==
-Normally, any developer who has done some work on projects hosted by KDE can apply for a KDE Developer account.
-Translators should get approval from their team leader so that they can organize how the work is being done in his/her team. Please mention the approval from the team leader when requesting the account.
-Please also [[Policies/Commit Policy|read the KDE commit policy]]. You must accept these rules 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 exposes our values.
-Also please apply for an account only if you think that you will work on KDE for a somewhat longer time. If you know that you will only work for a couple of weeks and then never again, please consider not applying for a KDE Developer account but instead continue to send patches directly to developers.
-The limitations are not there to exclude anyone - they are there to ensure that the maintenance of accounts remains reasonable.
-Of course, to be clear: ''the KDE's sysadmins have the last word about whether or not to create a KDE Developer account for somebody''.