zalando / zalando-howto-open-source Goto Github PK

I just wanted to ask / start the discussion if we should also add a part regarding having a Pull-Request Template in your projects.

Most of the time OSS maintainers are doing PR's for specific Issues and from time to time new contributors might miss to add a related Issue.

For such cases I find it really cool to have a PR Template like here or here.

If yes, I would like to create a PR for this + provide maybe a simple PR Template.

If the LICENSE file starts with

MIT License (MIT)

instead of 'The MIT License (MIT)', Github is able to parse the License (and putting a fancy badge on the tabs - see 'MIT' tab next to contributors on https://github.com/zalando-incubator/lib-oauth-tooling).

I think we should make it clearer that the purpose of our "Open Source" efforts is not just purely about "releasing source code" and raising "brand awareness", but also to contribute to society and promote freedom (which is in line with Radical Agility).

That's why we should consider shifting away from the term "Open Source" to a more appropriate "Free and open-source software (FOSS)" or FLOSS.

See also:

• The important four freedoms: https://fsfe.org/about/basics/freesoftware.en.html
• FOSS/FLOSS: https://en.wikipedia.org/wiki/Free_and_open-source_software
• Richard M. Stallmann on the topic (obviously always with strong opinions): https://www.gnu.org/philosophy/floss-and-foss.en.html

These guys decided to use the term "FOSS" everywhere in their policy: https://github.com/18F/open-source-policy/blob/master/policy.md

https://github.com/zalando/zalando-howto-open-source/blob/master/READMEtemplate.md

endorsements:

• http://softwareleadweekly.com/issues/205
  https://cronweekly.com/issue-51/

codes of conduct

• https://www.openssl.org/community/conduct.html
  How to become a core contributor
• https://www.wordfugue.com/tips-becoming-core-contributor/
• http://glasnt.com/blog/2016/06/08/on-becoming-a-core-contributor.html

Basic open source info sources
https://www.openhub.net/
open source orgs https://github.com/showcases/open-source-organizations

https://www.instagram.com/about/legal/libraries/
https://libraries.io/
maintenance https://fordfoundcontent.blob.core.windows.net/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf

External projects we're contributing to (Hibernate)

We should make sure that the "How to Open Source" page is also properly licensed (Creative Commons maybe?) and has a proper MAINTAINERS file (mentioning @LappleApple?).