-
Notifications
You must be signed in to change notification settings - Fork 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
MAINTAINER NEEDED #404
Comments
Hi Juri, I've been looking for a project to contribute to and I think this one looks like a splendid one to start with. Please contact me and let me know how I can help. Regards, |
Hey @ThomasAlanParker! Well this project came to a "stop" basically. I'm no more using Open Layers, nor Angular.js (version 1.x) as I moved to Angular. But there apparently still people using this library ~400 downloads per week on NPM. So the things to do here are mainly giving support in the issues, closing old issues and if necessary releasing critical bug fixes. Other than that I doubt this project will be evolved as people mostly start to move over to Angular (version 2+). If you're interested, maybe @tombatossals which is the original creator of this library and still owner of the repo can transfer you the committer permissions. |
I see, thanks for giving me an update. I am working on an Angular app as well and was hoping this was a good, possible place to start. I’ll keep looking thanks.
I’m seeing strange machine specific issues with Angular 8.x and OpenLayers 6.1.1 and I’m suspicious I’m using untested integrations. What runs fine on one machine fails on a literally cloned OS environment. I’m not sure what to try next.
…Sent from my iPhone
On Dec 17, 2019, at 2:27 PM, Juri Strumpflohner ***@***.***> wrote:
Hey @ThomasAlanParker! Well this project came to a "stop" basically. I'm no more using Open Layers, nor Angular.js (version 1.x) as I moved to Angular.
But there apparently still people using this library ~400 downloads per week on NPM. So the things to do here are mainly giving support in the issues, closing old issues and if necessary releasing critical bug fixes. Other than that I doubt this project will be evolved as people mostly start to move over to Angular (version 2+).
If you're interested, maybe @tombatossals which is the original creator of this library and still owner of the repo can transfer you the committer permissions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@ThomasAlanParker ah I see. Watch out then, since this repo here is for AngularJS, basically version 1.x. 🙂 (and not for Angular => version 2+) |
Hi,
I took over the project from @tombatossals a couple of years ago and slightly extended it, provided bugfixes and did the daily maintenance work. Unfortunately I'm not using it actively any more (at the moment), but I kinda feel sad seeing issues come in which don't get treated or looked at.
That said, if you're curious and want to start contributing and actively maintaining this library, PLEASE COMMENT BELOW and we can arrange to give you the access rights to the repo.
thanks 😃
The text was updated successfully, but these errors were encountered: