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

Calling for new contributors #352

Open
adrien-berchet opened this issue Feb 10, 2022 · 25 comments
Open

Calling for new contributors #352

adrien-berchet opened this issue Feb 10, 2022 · 25 comments

Comments

@adrien-berchet
Copy link
Member

Dear GeoAlchemy2 community,
The main developers of this library no longer work into the GIS world, so it's hard for them to find the time to contribute to this library. But there are still some improvements that would be nice to have. That's why I am looking for new contributors to help answer issues, fix bugs and add new features.
If anyone is interested, please answer here :-)

@krisHans3n
Copy link

@adrien-berchet I'd be happy to help where I can with feature developments, in particular the MySQL (#318 ) support issue. As far as I can tell only PostgreSQL/PositGIS is supported. I know the original version of Geoalchemy has support for it and the version of SQLAlchemy (8.0) has MySQL support. I just think it would be handy to have since MySQL has good spatial capability. Do you or anybody else know if there is a particular reason why MySQL was excluded from Geoalchemy2 and why PostgreSQL was the main focus?

@adrien-berchet
Copy link
Member Author

Hi @krisHans3n !
Thank you for your answer, it would be super nice to have you working on MySQL support!
For now GeoAlchemy2 supports two spatial DB: PostgreSQL / PostGIS and SQLite / SpatiaLite. I don't know the historical reasons why the initial development focused on PostGIS, maybe because the initial authors needed only this and could not take time to support all DB. But I don't think there is any technical reason.
If you want to work on this we can speak about it in #318 and you can try to start from my old attempt in #330 (I could not take more time on this and the branch is quite old now so you will have to rebase it).
See you soon and welcome aboard ;-)

@NoharaMasato
Copy link

Hello, @adrien-berchet
I'd like to contribute here if possible. Do you have any help-wanted or good-first issues?
Thank you for maintaining geoalchemy.

@adrien-berchet
Copy link
Member Author

Hi @NoharaMasato
Thank you very much for proposing your help!
I have several improvements in mind:

  1. I just created 2 new issues that I have in mind for some time: Rorganize dialect-specific code #395 and Associate spatial functions to each type #396. If you want to try one of them it would be nice.
  2. You can also give a try to Support for MySQL spatial queries #318 since I haven't heard from @krisHans3n anymore (though it would be better to work on Rorganize dialect-specific code #395 first).
  3. You can work on inserting raster directly from an array instead of using the external raster2pgsql binary (see details in How to insert raster data from an array? #87).
  4. If you have any other improvement in mind we can discuss it of course.

Please let me know what you prefer so we don't work on the same things.
And don't hesitate to ask me if you need any help to start :-)

@NoharaMasato
Copy link

@adrien-berchet Thank you listing the new features and issues.
Then, I'll start from #395 .

@adrien-berchet
Copy link
Member Author

Cool, thank you very much @NoharaMasato !

@papacodebear
Copy link

@adrien-berchet I'm interested in contributing if I can. Let me know if there's anywhere in particular you're looking for support.

@adrien-berchet
Copy link
Member Author

Hi @papacodebear , thanks for offering to help!
I think a good first contribution would be to solve #396. Would that be ok for you?

@papacodebear
Copy link

That works great for me. I'll dig into it @adrien-berchet

@adrien-berchet
Copy link
Member Author

Great, thanks! Don't hesitate to ask for help if you need.

@jjgarrett0
Copy link

I'd like to contribute if possible.

@adrien-berchet
Copy link
Member Author

Hi @jjgarrett0
Thanks for offering to help! I think it would be nice to work on #401 and #436 if you can. If you are not familiar with SQLAlchemy the second one might be hard...
Please keep me informed on what you want to work to avoid duplicate work. And don't hesitate to call for help.
Thanks again!

@jjgarrett0
Copy link

@adrien-berchet I can take a crack at #401.

@adrien-berchet
Copy link
Member Author

@adrien-berchet I can take a crack at #401.

Ok, nice, thanks!

@adrien-berchet adrien-berchet pinned this issue Jul 5, 2023
@krishnaglodha
Copy link

Hi, I'll be available for contributing to the library

@adrien-berchet
Copy link
Member Author

Hi @krishnaglodha !
Sorry for the delay, I was on holiday. And thanks for proposing to help us!
I think the main pending issues are #401 , #436 and #467. Would you be ok to check one of them?

@sdp5
Copy link
Contributor

sdp5 commented Apr 9, 2024

Hi @adrien-berchet

I'm starting with geospatial, and would like to contribute.
Please help me with some good-first-issues and the roadmap in general.

thanks!

@adrien-berchet
Copy link
Member Author

Hi @sdp5
Thanks for offering your time to this project!
I think that #401 could be a good first one since it should be more focused on Python things than spatial issues, which is probably simpler if you are starting with geospatial. If you want to go deeper in the SQLAlchemy guts, you can try #467, but I think this one is quite hard, though it would be super nice to solve it.
On a more general aspect, the roadmap consists only in solving the different issues, but there is no major change forecasted.
Let me know on which issue you want to work (it can also be another one if you prefer).

@sdp5
Copy link
Contributor

sdp5 commented Apr 12, 2024

Let me know on which issue you want to work

thank you for responding @adrien-berchet
happy to start with #401

cheers!

@adrien-berchet
Copy link
Member Author

Ok, thanks!
Don't hesitate to call for help if you need anything, I will try to take some time for this.

@adrien-berchet
Copy link
Member Author

@sdp5 if you have some time in the next few days you can try to work on #505 if you wish. I think it's a good one to start. Otherwise I will try to fix it next week.

@sdp5
Copy link
Contributor

sdp5 commented Apr 13, 2024

@sdp5 if you have some time in the next few days you can try to work on #505 if you wish. I think it's a good one to start. Otherwise I will try to fix it next week.

cool, looks interesting. let me take a quick look, thanks @adrien-berchet !

@sdp5
Copy link
Contributor

sdp5 commented Apr 24, 2024

thanks for the release @adrien-berchet , will start with #401 next shortly.

@adrien-berchet
Copy link
Member Author

thanks for the release @adrien-berchet , will start with #401 next shortly.

Thanks @sdp5 !
You can also take a look at #508 if you wish, it seems interesting.

@sdp5
Copy link
Contributor

sdp5 commented Apr 26, 2024

You can also take a look at #508 if you wish, it seems interesting.

thank you for the example 👍🏻 - following through sqlalchemy.sql.type_api.

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

No branches or pull requests

7 participants