Re: Announcing MyKDE
Amazing work! Best Piyush Aggarwal On Sat, 3 Oct, 2020, 3:26 pm Carl Schwan, wrote: > Hello folks, > I'm happy to announce the successful deployment of the new identity system > in KDE, codename MyKDE. The new identity system is now available in > https://my.kde.org. You should be able to login into the my.kde.org > website > with your normal KDE credential. > > For the moment, only the wikis are using MyKDE but in the comming months > this should change with more and more services switching to MyKDE. I will > let you all know of the progress of the migration. > > > FAQ: > > > Why the move? > - > > identity.kde.org is using OpenLDAP for user management with a small PHP > frontend allowing the account creation. And we had the following problems > with it: > > * Account removal is hard, requiring significant manual intervention and > effort (several hours work in some instances) > * Account registration takes 30 seconds or more to complete, creating a > poor > user experience > * Groups don't scale effectively > * Anti-spam measures are too crude > > More on that in https://phabricator.kde.org/T8449 > > Will my data be migrated? > - > > Yes, your data are migrated just by login into MyKDE once. This will > migrate > all your group membership (KDE developer, Akademy Team, ...), personal > data and password. > > For users who didn't log into MyKDE during the migration period. If you are > a KDE developer or KDE e.V. member, your account will be imported as a > disabled account and you will need to ask sysadmins to enabled it. For the > rest of the users of identity.kde.org who don't have a membership to > groups, > your account will be removed. We think this is the best solution because > there > is no need to store personal information that we don't need from users who > don't use the system anymore. If you want to conserve your account (and > username), please log at least once. We will send periodic emails reminding > you of migrating your account. > > How do I register a new account in MyKDE? > - > > For the moment the possibility of registering a new account is disabled in > MyKDE and the only possibility is to create an identity.kde.org account > and > then migrate your account. This is due to the fact we don't want some > accounts existing only in MyKDE. This will naturally change when we migrate > fully to MyKDE. > > How to I collect a badge? > - > > MyKDE has the possibility to grant badges to users. For the moment there is > only one badge enabled: KDE developer. This badge is given to every KDE > developer and is displayed on their public profile (if enabled). When the > new Season of KDE website will be deployed, it will be also possible to > have > an SoK mentor and SoK mentee badge. > > I'm interested in ideas of new badges (and badge designs), so please let me > know if you have a genius idea that doesn't gamify KDE contribution (e.g > no made > 100/1000/10 000 commits badge). > > Note that you are in control of that badge get displayed. > > What is the public profile functionality? > - > > One of the new features of MyKDE is the possibility to have a public > profile. > This public profile is opt-in, so you need to explicitly enable it to make > it work and it can display a small bio, your avatar, name, username, social > network account, Liberapay account, and badges earned. > > This is for example how it looks for me: > https://my.kde.org/user/carlschwan/ > > Can I contribute to MyKDE? > -- > > Yes, the source code is hosted in > https://invent.kde.org/websites/my-kde-org > and all the deployment information can be found here: > https://sysadmin-docs.kde.org/services/mykde.html > > Cheers, > Carl Schwan > https://carlschwan.eu > > >
Re: Announcing MyKDE
Super cool stuff! Great work, Carl. Nate On 10/3/20 3:56 AM, Carl Schwan wrote: Hello folks, I'm happy to announce the successful deployment of the new identity system in KDE, codename MyKDE. The new identity system is now available in https://my.kde.org. You should be able to login into the my.kde.org website with your normal KDE credential. For the moment, only the wikis are using MyKDE but in the comming months this should change with more and more services switching to MyKDE. I will let you all know of the progress of the migration. FAQ: Why the move? - identity.kde.org is using OpenLDAP for user management with a small PHP frontend allowing the account creation. And we had the following problems with it: * Account removal is hard, requiring significant manual intervention and effort (several hours work in some instances) * Account registration takes 30 seconds or more to complete, creating a poor user experience * Groups don't scale effectively * Anti-spam measures are too crude More on that in https://phabricator.kde.org/T8449 Will my data be migrated? - Yes, your data are migrated just by login into MyKDE once. This will migrate all your group membership (KDE developer, Akademy Team, ...), personal data and password. For users who didn't log into MyKDE during the migration period. If you are a KDE developer or KDE e.V. member, your account will be imported as a disabled account and you will need to ask sysadmins to enabled it. For the rest of the users of identity.kde.org who don't have a membership to groups, your account will be removed. We think this is the best solution because there is no need to store personal information that we don't need from users who don't use the system anymore. If you want to conserve your account (and username), please log at least once. We will send periodic emails reminding you of migrating your account. How do I register a new account in MyKDE? - For the moment the possibility of registering a new account is disabled in MyKDE and the only possibility is to create an identity.kde.org account and then migrate your account. This is due to the fact we don't want some accounts existing only in MyKDE. This will naturally change when we migrate fully to MyKDE. How to I collect a badge? - MyKDE has the possibility to grant badges to users. For the moment there is only one badge enabled: KDE developer. This badge is given to every KDE developer and is displayed on their public profile (if enabled). When the new Season of KDE website will be deployed, it will be also possible to have an SoK mentor and SoK mentee badge. I'm interested in ideas of new badges (and badge designs), so please let me know if you have a genius idea that doesn't gamify KDE contribution (e.g no made 100/1000/10 000 commits badge). Note that you are in control of that badge get displayed. What is the public profile functionality? - One of the new features of MyKDE is the possibility to have a public profile. This public profile is opt-in, so you need to explicitly enable it to make it work and it can display a small bio, your avatar, name, username, social network account, Liberapay account, and badges earned. This is for example how it looks for me: https://my.kde.org/user/carlschwan/ Can I contribute to MyKDE? -- Yes, the source code is hosted in https://invent.kde.org/websites/my-kde-org and all the deployment information can be found here: https://sysadmin-docs.kde.org/services/mykde.html Cheers, Carl Schwan https://carlschwan.eu
Re: Fundraising in KDE
Hi Ingo, Le 2020-09-27 à 17:29, Ingo Klöcker a écrit : On Sonntag, 27. September 2020 22:54:07 CEST Albert Astals Cid wrote: El diumenge, 27 de setembre de 2020, a les 21:36:46 CEST, Vincent Pinon va escriure: As KDE eV can't allocate money to a specific project (if I understand correctly) That's more a "historically has not wanted" than a "legally can't". As one of the auditors of accounting I'll add that tracking money that is allocated to a specific project will make book keeping much more complicated. I'm not sure whether the simple tracking of income and expenses that we currently do will be sufficient. It's my hope that with the recent KDE eV board public statements about them wanting to help people make out a living out of doing KDE stuff this may change. In my opinion, paying people for doing KDE stuff (reminder: we do already pay quite a few people for doing important KDE stuff) is orthogonal to allocating money to specific projects. Complexity of book keeping would change from O(n) to O(n²). Can you clarify what you mean? Regards, Ingo -- Philippe Cloutier http://www.philippecloutier.com
Re: Announcing MyKDE
Anything supporting TOTP should work. That's the protocol underlying Google Authenticator. On android Google's app is the most instantly recognizable for must people. In fact its pre-installed on some phones. On Sat, Oct 3, 2020, 8:56 AM Raghavendra Kamath wrote: > Hi Shinjo, > > On Saturday, 3 October, 2020 3:40:16 PM IST Shinjo Park wrote: > > Just my 2 cents, on the 2FA registration page I wish there should be > tools > > other than Google Authenticator listed. Not only tools for other platform > > (e.g. Plasma Mobile - do we have one? Sailfish, iOS, ...) but also F/OSS > in > > Android. At least there is Aegis [1] on F-Droid which seems to be an > > actively developed free replacement of Google Authenticator. > > I used Andotp [1] and it worked. It is Free software and is available in > fdroid for android devices. > > Thank you > > [1] https://f-droid.org/en/packages/org.shadowice.flocke.andotp/ > > -- > Raghavendra Kamath > > > >
Re: Fundraising in KDE
Le 2020-09-27 à 04:52, Karl Ove Hufthammer a écrit : Nicolas Fella skreiv 24.09.2020 11:42: I would be cautious about creating a system that allows targeted donations for specific features/requests. I don't want the e.V. to be in a position where work is done/prioritized because it brings in money. I agree. KDE has a list of goals (https://kde.org/goals), which have been selected using a democratic process. While this could perhaps be clarified, those are Goals with a capital "G". KDE obviously also wants to be more performant, lighter, more accessible, more portable, more multilingual, more secure, more stable, etc. There is no way to make an exhaustive list of KDE's goals (in the literal sense). It would, IMHO, be better to say that donations from companies will be used to hire developers to work towards KDE’s goals. Then the companies can decide if they think this a good thing or not. There are really three possibilities – a company wants work done that is a) aligned with KDE’s goals, b) against KDE’s goals or c) orthogonal to KDE’s goals. A company can also want work which is: 1. In KDE's top priorities 2. Half as high as #1 in our priorities. 3. Half as high as #2 in our priorities. 4. Half as high as #3 in our priorities. ...and the list goes on. But we don't care about such categories, except for one thing: we don't want work against our goals. And all it takes to avoid that is realism. Promising work against our goals is unrealistic, since developers will not manage to integrate work against our goals. Just like we shouldn't promise to achieve something in exchange for insufficient funding, we shouldn't promise to achieve something whose net value to KDE is negative. KDE consists in many different individuals with widely different goals. We don't require developers to do work which advances KDE's top priorities. One reason is many developers don't have the necessary skills, but an equally important reason is that developers are volunteers whose priorities are not KDE's, so forcing them to work on KDE's priorities rather than theirs would reduce their motivation. It's understandable that allowing targeted donations requires work, but ignoring that, there is no reason why we should *intentionally* decline donators (whether these are companies, other organizations or individuals) all freedom to choose what they help with. Perhaps donators don't have the necessary expertise to contribute directly, but that is no reason to force them to contribute to our top priorities. We will get way more donations if we allow donators to specify how their donations should be used. On the other hand, we must be aware that we will use the received money less efficiently on average. For example, if a donator gives 10€ for a change which we estimate costs 100€, then it could be that it takes years before we can fund a developer to use that money. And I guess this can create fair challenges; if a donator specified a donation should only be used for an improvement to a specific product, and then that product is officially abandoned/EOL-ed, do we refund the same amount to the donator? [...] -- Philippe Cloutier http://www.philippecloutier.com
Re: Announcing MyKDE
Hi Shinjo, On Saturday, 3 October, 2020 3:40:16 PM IST Shinjo Park wrote: > Just my 2 cents, on the 2FA registration page I wish there should be tools > other than Google Authenticator listed. Not only tools for other platform > (e.g. Plasma Mobile - do we have one? Sailfish, iOS, ...) but also F/OSS in > Android. At least there is Aegis [1] on F-Droid which seems to be an > actively developed free replacement of Google Authenticator. I used Andotp [1] and it worked. It is Free software and is available in fdroid for android devices. Thank you [1] https://f-droid.org/en/packages/org.shadowice.flocke.andotp/ -- Raghavendra Kamath
Re: Announcing MyKDE
Thanks a lot for clarification and positive answer! 2020년 10월 3일 토요일 오후 5시 30분 10초 CEST에 Carl Schwan 님이 쓴 글: > Le samedi, octobre 3, 2020 12:10 PM, Shinjo Park a écrit : > > Just my 2 cents, on the 2FA registration page I wish there should be tools > > other than Google Authenticator listed. Not only tools for other platform > > (e.g. Plasma Mobile - do we have one? Sailfish, iOS, ...) but also F/OSS > > in > > Android. At least there is Aegis [1] on F-Droid which seems to be an > > actively developed free replacement of Google Authenticator. > > > > [1] https://f-droid.org/en/packages/com.beemdevelopment.aegis/ > > Mentioning Google Authenticator was done by the django 2fa plugin we use. I > now overwrote the template > (https://invent.kde.org/websites/my-kde-org/-/blob/master/templates/two_fac > tor/core/setup.html) and mention andOTP (the 2fa tool I used on Android from > F-Droid) now too. > > I didn't want to do that at the beginning because it means more code to > maintain and I'm already hesitating of reverting overwriting the template :( > > I guess this needs a bit more discussion so I opened this invent task: > https://invent.kde.org/websites/my-kde-org/-/issues/17 to brainstorm this. > > Cheers, > Carl > > > 2020년 10월 3일 토요일 오전 11시 56분 21초 CEST에 Carl Schwan 님이 쓴 글: > > > Hello folks, > > > I'm happy to announce the successful deployment of the new identity > > > system > > > in KDE, codename MyKDE. The new identity system is now available in > > > https://my.kde.org. You should be able to login into the my.kde.org > > > website > > > with your normal KDE credential. > > > For the moment, only the wikis are using MyKDE but in the comming months > > > this should change with more and more services switching to MyKDE. I > > > will > > > let you all know of the progress of the migration. > > > > > > FAQ: > > > > > > = > > > > > > Why the move? > > > > > > -- > > > > > > identity.kde.org is using OpenLDAP for user management with a small PHP > > > frontend allowing the account creation. And we had the following > > > problems > > > with it: > > > > > > - Account removal is hard, requiring significant manual intervention > > > and > > > > > > effort (several hours work in some instances) > > > > > > - Account registration takes 30 seconds or more to complete, creating > > > a poor> > > > > user experience > > > > > > - Groups don't scale effectively > > > - Anti-spam measures are too crude > > > > > > More on that in https://phabricator.kde.org/T8449 > > > > > > Will my data be migrated? > > > > > > -- > > > > > > Yes, your data are migrated just by login into MyKDE once. This will > > > migrate all your group membership (KDE developer, Akademy Team, ...), > > > personal data and password. > > > For users who didn't log into MyKDE during the migration period. If you > > > are > > > a KDE developer or KDE e.V. member, your account will be imported as a > > > disabled account and you will need to ask sysadmins to enabled it. For > > > the > > > rest of the users of identity.kde.org who don't have a membership to > > > groups, your account will be removed. We think this is the best > > > solution because there is no need to store personal information that we > > > don't need from users who don't use the system anymore. If you want to > > > conserve your account (and username), please log at least once. We will > > > send periodic emails reminding you of migrating your account. > > > > > > How do I register a new account in MyKDE? > > > > > > -- > > > > > > For the moment the possibility of registering a new account is disabled > > > in > > > MyKDE and the only possibility is to create an identity.kde.org account > > > and > > > then migrate your account. This is due to the fact we don't want some > > > accounts existing only in MyKDE. This will naturally change when we > > > migrate > > > fully to MyKDE. > > > > > > How to I collect a badge? > > > > > > -- > > > > > > MyKDE has the possibility to grant badges to users. For the moment there > > > is > > > only one badge enabled: KDE developer. This badge is given to every KDE > > > developer and is displayed on their public profile (if enabled). When > > > the > > > new Season of KDE website will be deployed, it will be also possible to > > > have an SoK mentor and SoK mentee badge. > > > I'm interested in ideas of new badges (and badge designs), so please let > > > me > > > know if you have a genius idea that doesn't gamify KDE contribution (e.g > > > no > > > made 100/1000/10 000 commits badge). > > > Note that you are in control of that badge get displayed. > > > > > > What is the public profile functionality? > > > > > > -- > > > > > > One of the new features of MyKDE is the possibility to have a public > > > profile. This public profile is opt-in, so you need to
Re: Announcing MyKDE
Le samedi, octobre 3, 2020 12:10 PM, Shinjo Park a écrit : > Just my 2 cents, on the 2FA registration page I wish there should be tools > other than Google Authenticator listed. Not only tools for other platform > (e.g. Plasma Mobile - do we have one? Sailfish, iOS, ...) but also F/OSS in > Android. At least there is Aegis [1] on F-Droid which seems to be an actively > developed free replacement of Google Authenticator. > > [1] https://f-droid.org/en/packages/com.beemdevelopment.aegis/ Mentioning Google Authenticator was done by the django 2fa plugin we use. I now overwrote the template (https://invent.kde.org/websites/my-kde-org/-/blob/master/templates/two_factor/core/setup.html) and mention andOTP (the 2fa tool I used on Android from F-Droid) now too. I didn't want to do that at the beginning because it means more code to maintain and I'm already hesitating of reverting overwriting the template :( I guess this needs a bit more discussion so I opened this invent task: https://invent.kde.org/websites/my-kde-org/-/issues/17 to brainstorm this. Cheers, Carl > > 2020년 10월 3일 토요일 오전 11시 56분 21초 CEST에 Carl Schwan 님이 쓴 글: > > > Hello folks, > > I'm happy to announce the successful deployment of the new identity system > > in KDE, codename MyKDE. The new identity system is now available in > > https://my.kde.org. You should be able to login into the my.kde.org website > > with your normal KDE credential. > > For the moment, only the wikis are using MyKDE but in the comming months > > this should change with more and more services switching to MyKDE. I will > > let you all know of the progress of the migration. > > > > FAQ: > > > > = > > > > Why the move? > > > > -- > > > > identity.kde.org is using OpenLDAP for user management with a small PHP > > frontend allowing the account creation. And we had the following problems > > with it: > > > > - Account removal is hard, requiring significant manual intervention and > > effort (several hours work in some instances) > > > > - Account registration takes 30 seconds or more to complete, creating a > > poor > > user experience > > > > - Groups don't scale effectively > > - Anti-spam measures are too crude > > > > More on that in https://phabricator.kde.org/T8449 > > > > Will my data be migrated? > > > > -- > > > > Yes, your data are migrated just by login into MyKDE once. This will migrate > > all your group membership (KDE developer, Akademy Team, ...), personal data > > and password. > > For users who didn't log into MyKDE during the migration period. If you are > > a KDE developer or KDE e.V. member, your account will be imported as a > > disabled account and you will need to ask sysadmins to enabled it. For the > > rest of the users of identity.kde.org who don't have a membership to groups, > > your account will be removed. We think this is the best solution because > > there is no need to store personal information that we don't need from > > users who don't use the system anymore. If you want to conserve your > > account (and username), please log at least once. We will send periodic > > emails reminding you of migrating your account. > > > > How do I register a new account in MyKDE? > > > > -- > > > > For the moment the possibility of registering a new account is disabled in > > MyKDE and the only possibility is to create an identity.kde.org account and > > then migrate your account. This is due to the fact we don't want some > > accounts existing only in MyKDE. This will naturally change when we migrate > > fully to MyKDE. > > > > How to I collect a badge? > > > > -- > > > > MyKDE has the possibility to grant badges to users. For the moment there is > > only one badge enabled: KDE developer. This badge is given to every KDE > > developer and is displayed on their public profile (if enabled). When the > > new Season of KDE website will be deployed, it will be also possible to have > > an SoK mentor and SoK mentee badge. > > I'm interested in ideas of new badges (and badge designs), so please let me > > know if you have a genius idea that doesn't gamify KDE contribution (e.g no > > made 100/1000/10 000 commits badge). > > Note that you are in control of that badge get displayed. > > > > What is the public profile functionality? > > > > -- > > > > One of the new features of MyKDE is the possibility to have a public > > profile. This public profile is opt-in, so you need to explicitly enable it > > to make it work and it can display a small bio, your avatar, name, > > username, social network account, Liberapay account, and badges earned. > > This is for example how it looks for me: https://my.kde.org/user/carlschwan/ > > > > Can I contribute to MyKDE? > > > > --- > > > > Yes, the source code is hosted in https://invent.kde.org/websites/my-kde-org > > and all the deployment
Re: Announcing MyKDE
Am 03.10.2020 um 16:01 schrieb Elvis Angelaccio: Thanks Carl and everyone who was involved :) On 03/10/20 14:56, Raghavendra Kamath wrote: Hi Shinjo, On Saturday, 3 October, 2020 3:40:16 PM IST Shinjo Park wrote: Just my 2 cents, on the 2FA registration page I wish there should be tools other than Google Authenticator listed. Not only tools for other platform (e.g. Plasma Mobile - do we have one? Sailfish, iOS, ...) but also F/OSS in Android. At least there is Aegis [1] on F-Droid which seems to be an actively developed free replacement of Google Authenticator. I used Andotp [1] and it worked. It is Free software and is available in fdroid for android devices. FreeOTP works as well: https://freeotp.github.io/ ...and can be installed from google play or f-droid. Extra fun: install the pam module for 2fa, and a network manager dispatcher hook that can DISable it's use when you're in your "home" LAN (I use the MAC address of the default gateway for that). Or in other words: my laptop does 2FA for logins, but not when I'm home. Cheers Mathias -- Mathias Homann mathias.hom...@opensuse.org Jabber (XMPP): le...@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
Re: Announcing MyKDE
Thanks Carl and everyone who was involved :) On 03/10/20 14:56, Raghavendra Kamath wrote: > Hi Shinjo, > > On Saturday, 3 October, 2020 3:40:16 PM IST Shinjo Park wrote: >> Just my 2 cents, on the 2FA registration page I wish there should be tools >> other than Google Authenticator listed. Not only tools for other platform >> (e.g. Plasma Mobile - do we have one? Sailfish, iOS, ...) but also F/OSS in >> Android. At least there is Aegis [1] on F-Droid which seems to be an >> actively developed free replacement of Google Authenticator. > > I used Andotp [1] and it worked. It is Free software and is available in > fdroid for android devices. FreeOTP works as well: https://freeotp.github.io/ > > Thank you > > [1] https://f-droid.org/en/packages/org.shadowice.flocke.andotp/ > Cheers, Elvis
Re: Announcing MyKDE
Hey Carl. Great work!! Many thanks for that. Uli On 2020-10-03 11:56, Carl Schwan wrote: > Hello folks, > I'm happy to announce the successful deployment of the new identity system > in KDE, codename MyKDE. The new identity system is now available in > https://my.kde.org. You should be able to login into the my.kde.org website > with your normal KDE credential. > > For the moment, only the wikis are using MyKDE but in the comming months > this should change with more and more services switching to MyKDE. I will > let you all know of the progress of the migration. > > > FAQ: > > > Why the move? > - > > identity.kde.org is using OpenLDAP for user management with a small PHP > frontend allowing the account creation. And we had the following problems > with it: > > * Account removal is hard, requiring significant manual intervention and > effort (several hours work in some instances) > * Account registration takes 30 seconds or more to complete, creating a poor > user experience > * Groups don't scale effectively > * Anti-spam measures are too crude > > More on that in https://phabricator.kde.org/T8449 > > Will my data be migrated? > - > > Yes, your data are migrated just by login into MyKDE once. This will migrate > all your group membership (KDE developer, Akademy Team, ...), personal > data and password. > > For users who didn't log into MyKDE during the migration period. If you are > a KDE developer or KDE e.V. member, your account will be imported as a > disabled account and you will need to ask sysadmins to enabled it. For the > rest of the users of identity.kde.org who don't have a membership to groups, > your account will be removed. We think this is the best solution because there > is no need to store personal information that we don't need from users who > don't use the system anymore. If you want to conserve your account (and > username), please log at least once. We will send periodic emails reminding > you of migrating your account. > > How do I register a new account in MyKDE? > - > > For the moment the possibility of registering a new account is disabled in > MyKDE and the only possibility is to create an identity.kde.org account and > then migrate your account. This is due to the fact we don't want some > accounts existing only in MyKDE. This will naturally change when we migrate > fully to MyKDE. > > How to I collect a badge? > - > > MyKDE has the possibility to grant badges to users. For the moment there is > only one badge enabled: KDE developer. This badge is given to every KDE > developer and is displayed on their public profile (if enabled). When the > new Season of KDE website will be deployed, it will be also possible to have > an SoK mentor and SoK mentee badge. > > I'm interested in ideas of new badges (and badge designs), so please let me > know if you have a genius idea that doesn't gamify KDE contribution (e.g no > made > 100/1000/10 000 commits badge). > > Note that you are in control of that badge get displayed. > > What is the public profile functionality? > - > > One of the new features of MyKDE is the possibility to have a public profile. > This public profile is opt-in, so you need to explicitly enable it to make > it work and it can display a small bio, your avatar, name, username, social > network account, Liberapay account, and badges earned. > > This is for example how it looks for me: https://my.kde.org/user/carlschwan/ > > Can I contribute to MyKDE? > -- > > Yes, the source code is hosted in https://invent.kde.org/websites/my-kde-org > and all the deployment information can be found here: > https://sysadmin-docs.kde.org/services/mykde.html > > Cheers, > Carl Schwan > https://carlschwan.eu > >
Re: Announcing MyKDE
On Sat, Oct 3, 2020 at 11:56 AM Carl Schwan wrote: > > Hello folks, > I'm happy to announce the successful deployment of the new identity system > in KDE, codename MyKDE. The new identity system is now available in > https://my.kde.org. You should be able to login into the my.kde.org website > with your normal KDE credential. > Congratulations! It looks pretty slick. Regards, - Johan Ouwerkerk
Re: Announcing MyKDE
Just my 2 cents, on the 2FA registration page I wish there should be tools other than Google Authenticator listed. Not only tools for other platform (e.g. Plasma Mobile - do we have one? Sailfish, iOS, ...) but also F/OSS in Android. At least there is Aegis [1] on F-Droid which seems to be an actively developed free replacement of Google Authenticator. [1] https://f-droid.org/en/packages/com.beemdevelopment.aegis/ 2020년 10월 3일 토요일 오전 11시 56분 21초 CEST에 Carl Schwan 님이 쓴 글: > Hello folks, > I'm happy to announce the successful deployment of the new identity system > in KDE, codename MyKDE. The new identity system is now available in > https://my.kde.org. You should be able to login into the my.kde.org website > with your normal KDE credential. > > For the moment, only the wikis are using MyKDE but in the comming months > this should change with more and more services switching to MyKDE. I will > let you all know of the progress of the migration. > > > FAQ: > > > Why the move? > - > > identity.kde.org is using OpenLDAP for user management with a small PHP > frontend allowing the account creation. And we had the following problems > with it: > > * Account removal is hard, requiring significant manual intervention and > effort (several hours work in some instances) > * Account registration takes 30 seconds or more to complete, creating a poor > user experience > * Groups don't scale effectively > * Anti-spam measures are too crude > > More on that in https://phabricator.kde.org/T8449 > > Will my data be migrated? > - > > Yes, your data are migrated just by login into MyKDE once. This will migrate > all your group membership (KDE developer, Akademy Team, ...), personal data > and password. > > For users who didn't log into MyKDE during the migration period. If you are > a KDE developer or KDE e.V. member, your account will be imported as a > disabled account and you will need to ask sysadmins to enabled it. For the > rest of the users of identity.kde.org who don't have a membership to groups, > your account will be removed. We think this is the best solution because > there is no need to store personal information that we don't need from > users who don't use the system anymore. If you want to conserve your > account (and username), please log at least once. We will send periodic > emails reminding you of migrating your account. > > How do I register a new account in MyKDE? > - > > For the moment the possibility of registering a new account is disabled in > MyKDE and the only possibility is to create an identity.kde.org account and > then migrate your account. This is due to the fact we don't want some > accounts existing only in MyKDE. This will naturally change when we migrate > fully to MyKDE. > > How to I collect a badge? > - > > MyKDE has the possibility to grant badges to users. For the moment there is > only one badge enabled: KDE developer. This badge is given to every KDE > developer and is displayed on their public profile (if enabled). When the > new Season of KDE website will be deployed, it will be also possible to have > an SoK mentor and SoK mentee badge. > > I'm interested in ideas of new badges (and badge designs), so please let me > know if you have a genius idea that doesn't gamify KDE contribution (e.g no > made 100/1000/10 000 commits badge). > > Note that you are in control of that badge get displayed. > > What is the public profile functionality? > - > > One of the new features of MyKDE is the possibility to have a public > profile. This public profile is opt-in, so you need to explicitly enable it > to make it work and it can display a small bio, your avatar, name, > username, social network account, Liberapay account, and badges earned. > > This is for example how it looks for me: https://my.kde.org/user/carlschwan/ > > Can I contribute to MyKDE? > -- > > Yes, the source code is hosted in https://invent.kde.org/websites/my-kde-org > and all the deployment information can be found here: > https://sysadmin-docs.kde.org/services/mykde.html > > Cheers, > Carl Schwan > https://carlschwan.eu
Announcing MyKDE
Hello folks, I'm happy to announce the successful deployment of the new identity system in KDE, codename MyKDE. The new identity system is now available in https://my.kde.org. You should be able to login into the my.kde.org website with your normal KDE credential. For the moment, only the wikis are using MyKDE but in the comming months this should change with more and more services switching to MyKDE. I will let you all know of the progress of the migration. FAQ: Why the move? - identity.kde.org is using OpenLDAP for user management with a small PHP frontend allowing the account creation. And we had the following problems with it: * Account removal is hard, requiring significant manual intervention and effort (several hours work in some instances) * Account registration takes 30 seconds or more to complete, creating a poor user experience * Groups don't scale effectively * Anti-spam measures are too crude More on that in https://phabricator.kde.org/T8449 Will my data be migrated? - Yes, your data are migrated just by login into MyKDE once. This will migrate all your group membership (KDE developer, Akademy Team, ...), personal data and password. For users who didn't log into MyKDE during the migration period. If you are a KDE developer or KDE e.V. member, your account will be imported as a disabled account and you will need to ask sysadmins to enabled it. For the rest of the users of identity.kde.org who don't have a membership to groups, your account will be removed. We think this is the best solution because there is no need to store personal information that we don't need from users who don't use the system anymore. If you want to conserve your account (and username), please log at least once. We will send periodic emails reminding you of migrating your account. How do I register a new account in MyKDE? - For the moment the possibility of registering a new account is disabled in MyKDE and the only possibility is to create an identity.kde.org account and then migrate your account. This is due to the fact we don't want some accounts existing only in MyKDE. This will naturally change when we migrate fully to MyKDE. How to I collect a badge? - MyKDE has the possibility to grant badges to users. For the moment there is only one badge enabled: KDE developer. This badge is given to every KDE developer and is displayed on their public profile (if enabled). When the new Season of KDE website will be deployed, it will be also possible to have an SoK mentor and SoK mentee badge. I'm interested in ideas of new badges (and badge designs), so please let me know if you have a genius idea that doesn't gamify KDE contribution (e.g no made 100/1000/10 000 commits badge). Note that you are in control of that badge get displayed. What is the public profile functionality? - One of the new features of MyKDE is the possibility to have a public profile. This public profile is opt-in, so you need to explicitly enable it to make it work and it can display a small bio, your avatar, name, username, social network account, Liberapay account, and badges earned. This is for example how it looks for me: https://my.kde.org/user/carlschwan/ Can I contribute to MyKDE? -- Yes, the source code is hosted in https://invent.kde.org/websites/my-kde-org and all the deployment information can be found here: https://sysadmin-docs.kde.org/services/mykde.html Cheers, Carl Schwan https://carlschwan.eu
