BlazorLeaflet
BlazorLeaflet copied to clipboard
Mehigh17
Status of this project; maintainers and future efforts?
BlazorLeaflet is a great project and has saved me a lot of time. @Mehigh17 , I greatly appreciate your efforts. You've created a great library with good documentation. Thank you.
I'm wondering what the future holds for BlazorLeaflet? I see a healthy community behind this project with good outside engagement. However, I see that six pull requests have remained unresolved. I've also noticed the Nuget package and some documentation is out of date. I'm wondering what, if anything, might spark this project back to life? Maybe additional maintainers (@chucker ?).
I'm more than happy to contribute where I can. If possible, I'd like a better sense of a roadmap before I do though.
See also https://github.com/Mehigh17/BlazorLeaflet/issues/51#issuecomment-727096795
As for me, thanks for asking, but I don't currently have an ongoing Blazor project. I hope someone will step up, though!
Ah, thanks for the response. I should have checked closed issues before opening a new one. Also, I didn't mean to put you on the spot, just thought you'd do a good job :) Will wait patiently for @Mehigh17 's announcement for maintainers.
I'm planning on using this component again and want to incorporate the wonderful PRs that have been contributed. @Mehigh17 mentioned in #51 that he plans to post an announcement to seek contributors. Anyone know if there has been an updates on this (that I missed)?
Without maintainers I think my only option is to incorporate the PRs into a fork. I want to support this repo though, so any advice on best practices/how to play nice are appreciated.
@bryanrcarlson I'd like to use this library but it's a little scary without a clear path forward.
Might be alright to create a new repo with a new name and same license. See here:
https://dev.to/ben/whats-the-proper-etiquette-for-forking-an-abandoned-repo-d5h
@Tailslide , unfortunately, I've moved on. I ended up creating my own, slimmed down, component. I only needed to display geojson on a slippy map so I just created a streamlined version using javascript interop.
I'm still interested in contributing to this library but no longer have the motivation to maintain it (or a fork).
@Tailslide I don't think it's a question of etiquette so much as… would there be enough interest?
I recently started a new Blazor project, and found that this is still a good choice for a map component. I'm unsure how to proceed, though — there are a number of open pull requests, and there isn't really a roadmap or an idea if those fit the vision of the original maintainer.
@chucker I think Blazor will just continue to get more popular.. if this dies then someone will make something similar at some point... if you publish a repo then at least you won't be maintaining your copy on your own. I wound up needing offline map ability so instead of reviving this and adding offline support I wound up making my own wrapper for leaflet.offline
I have the same questions.
In a few weeks, I need to create a small WebGIS and I would like to use Blazor and this library. But it seems no one is actively maintaining this library.
I could fork this one and add the functionality I'm missing myself, but I would rather join a well-maintained and active library.
I also found this library https://github.com/darnton/LeafletBlazor, but it seems it is not actively maintained as well.
Anybody knows a well-maintained and active library to add maps with custom geo-data to a Blazor application? Using OpenLayers instead of Leaflet is also fine.
I'm also working on a project that will be using this repo as a starting point for a map centric web application. Looks like a few people have forks and are contributing important pull requests.
@Mehigh17 if you're unable to maintain this at present, it'd be very much appreciated if a few additional people could be deputized to help with pull requests and nugets. I saw you mentioned planning to do that in another issue response. This would be especially important with releasing updated public nugets. I'm willing and able, and it sounds like several others here would as well. Thanks!
Another vote here for some clarity - I really want to add Maps into my OSS app but I don't want to invest in integrating a dead component. :(
