Skip to content
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

Update COPYING.txt #5425

Closed
jdfreder opened this issue Mar 25, 2014 · 4 comments · Fixed by #5428
Closed

Update COPYING.txt #5425

jdfreder opened this issue Mar 25, 2014 · 4 comments · Fixed by #5428
Milestone

Comments

@jdfreder
Copy link
Member

From the dev meeting, March 20, 2014

We should use this header or something similar for source files:

# Copyright (c) IPython Development Team.
# Distributed under the terms of the Modified BSD License.
@jdfreder jdfreder added this to the 2.0 milestone Mar 25, 2014
@jdfreder
Copy link
Member Author

Related question: If we use a copyright string like the one mentioned above, should we still use the horizontal breaks made of dashes to separate code regions, i.e.

#-----------------------------------------------------------------------------
# Classes
#-----------------------------------------------------------------------------

@ellisonbg
Copy link
Member

I think that kind of formatting is completely optional. These days I find
myself writing shorter files and not dividing code using banners like that,
but occasionally, it is nice to add formatting to code to help readability.
I don't think any action is needed on this front.

On Tue, Mar 25, 2014 at 11:11 AM, Jonathan Frederic <
notifications@github.com> wrote:

Related question: If we use a copyright string like the one mentioned
above, should we still use the horizontal breaks made of dashes to separate
code regions, i.e.

#-----------------------------------------------------------------------------# Classes#-----------------------------------------------------------------------------

Reply to this email directly or view it on GitHubhttps://github.com//issues/5425#issuecomment-38600298
.

Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger@calpoly.edu and ellisonbg@gmail.com

@jdfreder
Copy link
Member Author

I don't think any action is needed on this front.

But the date & names in COPYING.txt should still be updated, right?

@ellisonbg
Copy link
Member

Yes

On Tue, Mar 25, 2014 at 11:22 AM, Jonathan Frederic <
notifications@github.com> wrote:

I don't think any action is needed on this front.

But the date & names in COPYING.txt should still be updated, right?

Reply to this email directly or view it on GitHubhttps://github.com//issues/5425#issuecomment-38601673
.

Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger@calpoly.edu and ellisonbg@gmail.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants