-
-
Notifications
You must be signed in to change notification settings - Fork 49
Guidelines for contributing #183
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
Comments
Thanks for your interest in contributing!
Indeed, the general GeoPandas contributing guidelines should apply here as well. I see that our CONTRIBUTING.md file still points to dask (https://github.com/geopandas/dask-geopandas/blob/main/CONTRIBUTING.md), we can maybe update that to point to geopandas.
Most of the easy ones are already done by now, I think, but I added an update to that issue. #76 might be another good first issue. Also #79 or #81 should be doable but require some more advanced dask experience. |
#76 looks interesting. Is this referring to the class on line 884 and |
I asked about dependencies and Running |
Can you open an issue for that? |
@martinfleis here's the issue I made for this #184 |
Hello,
I'm loving using this project, and would love to contribute to it. The feature parity post seems like a great place to start.
And it seems like the guide for contributing to GeoPandas largely applies here as well.
Are there any substantial changes to those docs, either the list of features or the contributing guidelines? Edit: Especially curious about dependencies and testing that only apply here.
Thanks in advance, excited to learn.
Best,
Alex
The text was updated successfully, but these errors were encountered: