Skip to content
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.

PSA: Deprecation notice 2018-09-30 #160

Open
nordnet-deprecation-bot opened this issue Sep 19, 2018 · 9 comments
Open

PSA: Deprecation notice 2018-09-30 #160

nordnet-deprecation-bot opened this issue Sep 19, 2018 · 9 comments

Comments

@nordnet-deprecation-bot
Copy link
Contributor

ℹ️ We are not using this repo anymore, and we lack the manpower and the experience needed to maintain it. We are aware of the inconveniece that this may cause you. Feel free to use it as is, or create your own fork.

⚠️ This repo will be deprecated and archived (become read-only) on 2018-09-30.

🙏 You can use this issue to link to your fork and/or alternatives to this repo.

This was referenced Sep 19, 2018
@NiklasMerz
Copy link

NiklasMerz commented Sep 19, 2018

That´s unfortunate, but thank you for clarifying the status of this project. Do you know what will happen with the npm package?

We based our own fork on flipflopapp which has a necessary fix for cordova 7.

@iamstarkov
Copy link
Member

as far as I concerned npm package will remain in the registry

@ccorcos
Copy link

ccorcos commented Sep 19, 2018

Hey there, I understand this is deprecated, but please do not lock the conversations. If someone comes up with a fix in a new fork, that fixes an issue, it would be nice if we could communicate that in the old issue or PR

@iamstarkov
Copy link
Member

iamstarkov commented Sep 19, 2018

I may be wrong but it seems to be perfectly valid to continue conversation in a fork's pr or issue linked to previous one in this repo

@ccorcos
Copy link

ccorcos commented Sep 19, 2018

I do I communicate to the people discussing an issue in this repo that I have a relevant fork in another repo?

@ccorcos
Copy link

ccorcos commented Sep 19, 2018

For example, how do I let these people know that I've created a fork that solved their problem? #122

@iamstarkov
Copy link
Member

post a link to your repo in here and tag relevant people in

@iamstarkov
Copy link
Member

we aim to archive repo in less two weeks anyway. #122 has been mostly quite for last year

@ccorcos
Copy link

ccorcos commented Sep 19, 2018

Alright. I just don't see a reason why you'd need to lock conversation. It doesn't cost you anything does it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants