ENH: Create script to set up a development environment using docker
This script will help the contributors with the process of setting up a docker container. So instead of manually passing the Github username in the Dockerfile and then running a couple of commands, you can run only this:

```
./docker.sh
```

...and enter the Github username when prompted.

I think this can be good, right? Especially for the new users.

I suppose this is ok, we don't normally recommend using docker at all, but to the extent people use it, having a script is good.

cc @simonjayhawkins @WillAyd  will look soon, can docker build args not be used? or username passed to docker run? Given that the Dockerfile exists, this seems like a good idea to me - though perhaps this would be better placed in `scripts/`? > can docker build args not be used?

Yeah I guess so. That would avoid the `sed` part.

> though perhaps this would be better placed in scripts/?

Sure, but I have to make some changes to make it work there because the `docker run` command will mount the **current working directory** into the container, in that case would be the `scripts/` dir but we want to mount the root of the project. And the Dockerfile would be one dir up, so the `docker build` command should be updated. > the docker run command will mount the current working directory into the container, in that case would be the scripts/ dir but we want to mount the root of the project

Actually there's no need to change this, you can just run from the root of the project. I modified the `docker build` command to pass the Github username as the build argument, and I moved the script to the `scripts/` directory (and updated the doc instruction). This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this. @gcmaciel There has been some changes to the documentation. Can you merge master and resolve conflicts. >Can you merge master and resolve conflicts

@simonjayhawkins Done. @simonjayhawkins @MarcoGorelli Can you guys take a look? Thanks. > @simonjayhawkins @MarcoGorelli Can you guys take a look? Thanks.

Hey - sorry for the delay, and thanks for the ping! I'll try running this next week and'll let you know

EDIT: sorry, haven't had a chance to do this yet Personally I don't see how this is making things easier. To me it makes them more complicated. Running two docker commands seem reasonable, at least the user knows what is doing, and what's going on. Replacing this by a script, and losing visibility of what's going on, doesn't seem an improvement, even if instead of having to copy two commands from the doc, only one is needed. @datapythonista I understand your point. For someone who's already used to docker, *manually* running those commands doesn't seem a big deal, but I've seen people here struggling to set up the docker environment and the trickiest part is the one you have to pass your username in the Dockerfile, that's not so intuitive and someone can easily forget to revert the change and/or commit the Dockerfile with his name on it. This script avoids that and makes it easier (in my opinion) to run the container because it replaces a long command that can be hard to remember (the script can be used not only to set up the environment but also to run the container every time you want to work on the project). 

Of course I'm suspicious to say because this was my idea but I still think this is good. I've been using this since then and I'll keep using it because I found it better this way. 

I don't know if I was clear enough but I hope the best decision to be made (even if the best decision would be not approving this). > and someone can easily forget to revert the change and/or commit the Dockerfile with his name on it

That's not correct. The `ARG` directive is not meant to be edited in the dockerfile, but as a parameter, for example: `--build-arg gh_username=datapythonista`

Users who don't know what they are doing they'll simply copy whatever we say in the docs they need to run. This is just a shortcut, so instead of two commands, they need to copy one. To me, not worth having to maintain an extra script in a project already too complex like pandas. Having to support users who will start using a new script...

I think pandas main challenge is to keep things simple, not make it trivial to contribute (with this or without this script, contributing to pandas is not a trivial thing). So, personally, we're looking for trouble with shortcuts like this, trying to solve a problem in my opinion we don't have. Not even sure if it's a good idea to have a dockerfile to contribute to pandas to be honest. >The ARG directive is not meant to be edited in the dockerfile, but as a parameter, for example: --build-arg gh_username=datapythonista

@datapythonista Yes, that's what the script does:
https://github.com/pandas-dev/pandas/blob/09d75f936c308a103f2bdf0f71164fe15fc4d89b/scripts/docker.sh#L19-L21

>contributing to pandas is not a trivial thing

I agree, maybe the best advice for someone who is starting would be "spend the day reading the docs".

>Not even sure if it's a good idea to have a dockerfile to contribute to pandas to be honest.

Yeah I've heard this before. For me it was good because I was already used to docker, but I'm not sure if this is the best way or not.

Anyway, if you think this will add even more complexity to the project, all I have to do is agree with you. You know this project much more than me so I'm sure you know what you are saying. I'm here to learn more than anything. Thanks again for the contribution. Since there hasn't been a strong champion for this enhancement from the team (IMO I think running the Docker commands explicitly is better as well) and the discussions have stalled, going to close this PR. Can reopen if another team member feels strongly about this enhancement.  > Can reopen if another team member feels strongly about this enhancement.

I'm not sure that our current DockerFile is appropriate anyway if we use GitHub codespaces going forward.

(I have changed this locally (and tested with [Visual Studio Code Remote - Containers](https://code.visualstudio.com/docs/remote/containers)  but can't test with [GitHub Codespaces](https://code.visualstudio.com/docs/remote/codespaces) as I am on the waitlist for codespaces. I believe pandas does have codespaces access since I see this message... "conda-forge and pandas-dev have Codespaces access but have not enabled it for your account. Contact your organization admin to enable access."

I could maybe try this on a PR if I had access but have been waiting for codespaces on my fork to experiment) 

