Team awareness required: Future project state about angular-translate HOT 7 CLOSED

Thank you all for your input.

@0x-r4bbit Yeah, I have already stumbled across this some days ago. Got the proof by your history. ;)

@joeeames I have prepared the readme text in a branch. I have add a link to you site, but please feel to update me when things can be more detailed. https://github.com/angular-translate/angular-translate/blob/6fb2f1a4dad714f0666ad9f520a97c29ccb61a57/README.md

from angular-translate.

Well, while I'm writing these lines, the background processes of some servers currently deploying all the notices.

• new releases built and tagged in the git repositories
• pushed into the bower (😱) repositories as well as to the npm registry
• nearly all git repositories are now archived being now read-only
• all library projects on the npm registry are flagged as deprecated
• the docs index file also contain a prominent notice

The (un)funny part of this was however, these tasks were not so easily to accomplish. It's a very old environment technically incompatible with a modern arm64/Mac M1/2 hardware...

I'll close this repository next week also.

❤️ So again, thank you all: all project members, but also all contributors of this project. But also big thanks to all the users.

from angular-translate.

Hey, @knalli - to make my comment short: Good idea and I support your approach / concept.

from angular-translate.

One thing I'd like to add to this, is that the README.md include a link to the ongoing support that HeroDevs would offer.

As mentioned although we're happy to get access to the repositories, it's fine if that isn't done. HeroDevs is now the official provider of long term support for AngularJS (among several other projects such as Drupal) so we do have a long history and the trust of the Angular team.

from angular-translate.

One thing I'd like to add to this, is that the README.md include a link to the ongoing support that HeroDevs would offer.

Sure, as already said that I'm fine with this. I'll propose the texts the next days and you can give more details than.

from angular-translate.

Hey everyone,

Pascal here (yes it's me, I can sign a message for proof - or go check the contributions/commits).

First of all, I want to say thank you @knalli for all the work you've done here and keeping the ball rolling. I've removed myself from this project a long time ago and I think angular-translate is a perfect example that shows that open source can work and sustain itself with a healthy community.

Now, what you're bringing up is something i agree with.
I haven't been doing anything Angular related in a long time, so I don't have a good picture of what's the usage of AngularJS in this space. However I'm not surprised when people tell me that enterprise companies are still using it and can't simply upgrade to something else.

angular-translate has always been open source, we've never charged for anything so we're also not owning anyone anything. With that said, I think it's perfectly fine to settle the project, at least from the core team's perspective in the sense that we'll no longer maintain it.

I think archiving the repositories and putting them in read-only is the way to go.
The problem with trust assumptions you're bringing up is a very valid concern.

If teams like HeroDevs and/or @joeeames want to take over the work or maintain it, I think it's best if it's done via a fork. Anyone is free to do so and I wouldn't be surprised if people have done it anyways.

Green light from me doing the steps you've described.
Also, if you have the time and energy, feel free to work anything out with Joe. I know him personally and the people behind HeroDevs as well.

Thanks again for all the work and patience with this project!

from angular-translate.

So long, and thanks for all the fish.

from angular-translate.