Change Details

"As a Developer, I want to release my API client software under a Free and Open Source software license, so that [I can empower users, follow my personal principles, and garner support from other software developers]." (There are probably another hundred reasons someone wants to release software as FLOSS; I don't think that it's important to describe those. I'm happy to change the justification to "because I want to" if we get too hung up on the reasons.) Our use of OAuth 2.0 client IDs needs to support FLOSS clients. They can't easily keep a single API key secret because the source code is available (although there are options, like providing the key at build time), so we need to have other mechanisms or flows that work. This isn't a user story on https://www.mediawiki.org/wiki/Core_Platform_Team/Initiatives/OAuth2 , but an open question. I decided to make it a user story here so we can think of it as a problem to solve.

"As a Developer, I want to release my API client software under a Free and Open Source software license, so that [I can empower users, follow my personal principles, and garner support from other software developers]." (There are probably another hundred reasons someone wants to release software as FLOSS; I don't think that it's important to describe those. I'm happy to change the justification to "because I want to" if we get too hung up on the reasons.) Our use of OAuth 2.0 client IDs needs to support FLOSS clients. They can't easily keep a client ID/client secret pair secret because the source code is available (although there are options, like providing the key at build time), so we need to have other mechanisms or flows that work. This isn't a user story on https://www.mediawiki.org/wiki/Core_Platform_Team/Initiatives/OAuth2 , but an open question. I decided to make it a user story here so we can think of it as a problem to solve.

"As a Developer, I want to release my API client software under a Free and Open Source software license, so that [I can empower users, follow my personal principles, and garner support from other software developers]." (There are probably another hundred reasons someone wants to release software as FLOSS; I don't think that it's important to describe those. I'm happy to change the justification to "because I want to" if we get too hung up on the reasons.) Our use of OAuth 2.0 client IDs needs to support FLOSS clients. They can't easily keep a single API keyclient ID/client secret pair secret because the source code is available (although there are options, like providing the key at build time), so we need to have other mechanisms or flows that work. This isn't a user story on https://www.mediawiki.org/wiki/Core_Platform_Team/Initiatives/OAuth2 , but an open question. I decided to make it a user story here so we can think of it as a problem to solve.