Skip to content

enh: Reorg license sections as recommended in #189 #415

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
willingc opened this issue Oct 7, 2024 · 2 comments
Open

enh: Reorg license sections as recommended in #189 #415

willingc opened this issue Oct 7, 2024 · 2 comments
Labels
documentation Improvements or additions to documentation help wanted We welcome a contributor to work on this issue! thank you in advance! sprintable

Comments

@willingc
Copy link
Collaborator

willingc commented Oct 7, 2024

Reorg the license sections page as discussed in #189.

 i feel like some of this would be useful above. what is we thought about re-organizing this page jonny? 

at the top we have 

## Where to store your license

### Use open permissive licenses when possible

what is instead we do something like this
## Where to store your license
keep text as is 

##Types of licenses: permissive vs copyleft 

explain inbound vs outbound restrictions here to frame the text below

### Overview of permissive licenses

### Overview of copyleft licenses (make your breakout into this section)

 ## How to chose a license 

* we suggest mit or bsd-3 for compatibilty with the scientific Python ecosystem
* scipy text as a reference 

## Following license guidelines

more about how to follow and how that impacts permissive vs copyleft (which by now it's clear how these are different). and yo've already explain inbound vs outbound permisions above so you can just have a little table even and demonstrate how the licenses are different.

_Originally posted by @lwasser in https://github.com/pyOpenSci/python-package-guide/pull/189#discussion_r1534304132_
            
@willingc willingc added the documentation Improvements or additions to documentation label Oct 7, 2024
@Lincoln-developer
Copy link

Hey @willingc , I would love to work on this if on one is working on it yet. Thanks

@lwasser
Copy link
Member

lwasser commented May 19, 2025

Hi Friends! i'm checking in on this issue!! I'm going to add a help wanted to it. Pull requests are welcome!!

@lwasser lwasser added help wanted We welcome a contributor to work on this issue! thank you in advance! sprintable labels May 19, 2025
@lwasser lwasser moved this to python programming in pyOpenSci Help Wanted Project Board May 19, 2025
@lwasser lwasser moved this from python programming to Python Package Guide in pyOpenSci Help Wanted Project Board May 19, 2025
@lwasser lwasser changed the title Reorg license sections as recommended in #189 enh: Reorg license sections as recommended in #189 May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted We welcome a contributor to work on this issue! thank you in advance! sprintable
Projects
Status: Python Package Guide
Development

No branches or pull requests

3 participants