Closed rodolfo-viana closed 5 years ago
We can safely remove .pyup.yml
. As for .travis.yml
it is supposed to run a test we've written to assure every contribution has the .html
and .py
version — very useful for code reviewing. So I'd keep it (and enable Travis CI).
I agree with Cuducos on this one. removal of .pyup.yml
and keep the .travis.yml
@cuducos could activate the travis for this repo? I'm not sure I can do it.
What I think we should do:
.pyup.yml
filesrc
folder (since the same content is available in the okfn-brasil/serenata-de-amor repo)notebooks/deliver
and notebooks/develop
to notebooks
(and delete the empty folders) Dockerfile
, the requirements.txt
and the jupyter_notebook_config.py
to the project root
~- create the missing setup
file~Dockerfile
to the new structure+1
Would you do that, @jtemporal?
Already on it @rodolfo-viana :+1:
I'll leave the setup
to a new issue, will open it up later :wink:
What is the problem?
As this repo is designed to people who wants to learn and develop data science skills, I believe some files are not necessary and may confuse newcomers. For example
deliver
andtest
folders, as well as.travis.yml
and.pyup.yml
. Or are they necessary for this repo? If not, how about deleting them?How can this be addressed?
If @jtemporal and @cuducos agree, I suggest we keep only notebooks and necessary codes to assist users, and delete everything else.
Who could help with this issue?
JT and Cuducos.