Skip to content

Conversation

@Neeratyoy
Copy link
Contributor

What does this PR implement/fix? Explain your changes.

This is w.r.t. the JMLR guidelines requiring the license to be mentioned in each and every source file of the package.

Any other comments?

The sklearn repo was used as a reference. Random examples below:

If I understood the Submission Checklist correctly, they do not expect the package zip to contain other auxiliary files such as the rst files for documentation, testing files, examples, etc.

@Neeratyoy Neeratyoy requested a review from mfeurer November 5, 2019 14:52
@Neeratyoy
Copy link
Contributor Author

Currently, have added license to only the source files under openml.datasets and an example (which I checked by rendering the docs).

@codecov-io
Copy link

codecov-io commented Nov 5, 2019

Codecov Report

Merging #862 into develop will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #862   +/-   ##
========================================
  Coverage    88.38%   88.38%           
========================================
  Files           37       37           
  Lines         4298     4298           
========================================
  Hits          3799     3799           
  Misses         499      499
Impacted Files Coverage Δ
openml/datasets/data_feature.py 68% <ø> (ø) ⬆️
openml/datasets/__init__.py 100% <ø> (ø) ⬆️
openml/datasets/functions.py 94.11% <ø> (ø) ⬆️
openml/datasets/dataset.py 87.03% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 34d54d9...e945564. Read the comment docs.

Copy link
Collaborator

@mfeurer mfeurer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks alright. Great that you already checked the example. I think you can then annotate the whole package.

Could you please update the contribution guides, the changelog and the PR template with this information, too?

@Neeratyoy
Copy link
Contributor Author

Neeratyoy commented Nov 6, 2019

@mfeurer I shall make the changes and create a PR.
Just to confirm, were my assumptions correct? That is, should I not touch other directories and edit just the openml and examples directories (along with the files you mentioned)?

@mfeurer
Copy link
Collaborator

mfeurer commented Nov 6, 2019

I guess it would be great if for consistency we just annotate all files where possible. What do you think about that?

@Neeratyoy
Copy link
Contributor Author

Makes sense. I'll see where it is not possible. Especially in the rst files.

@Neeratyoy Neeratyoy marked this pull request as ready for review November 6, 2019 13:30
@Neeratyoy Neeratyoy requested a review from mfeurer November 6, 2019 13:30
@mfeurer mfeurer merged commit e489f41 into develop Nov 6, 2019
@mfeurer mfeurer deleted the add_license branch November 6, 2019 16:03
PGijsbers pushed a commit that referenced this pull request Nov 7, 2019
* Fixing broken links (#864)

* Adding license to each source file (#862)

* Preliminary addition of license to source files

* Adding license to almost every source file

* add task_type to list_runs (#857)

* add task_type to list_runs

* length of run change

* changelog

* changes in progress rst

* Prepare new release (#868)
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 this pull request may close these issues.

4 participants