Skip to content
This repository has been archived by the owner on Feb 15, 2023. It is now read-only.

Remove node red node cf cloudant #77

Closed
wants to merge 2 commits into from

Conversation

nfstein
Copy link
Member

@nfstein nfstein commented Jun 8, 2021

No description provided.

@knolleary
Copy link
Contributor

Why is this being removed? Lots of users rely on this node to make use of cloudant. Has there been any discussion over the impact this will have?

@nfstein
Copy link
Member Author

nfstein commented Jun 8, 2021

Nothing rash is going on. This is part of this issue: https://github.ibm.com/arf/planning-force/issues/4227

@knolleary
Copy link
Contributor

Unfortunately I'm no longer an IBMer so don't have access to that internal repo.

@nfstein
Copy link
Member Author

nfstein commented Jun 8, 2021

Description:

There is an old Node-RED palette library included in the dependencies of the Node-RED starter kit that is out of date and receives little-to-no developer support.

We should make a PR to remove the library to development and tag Nick O'Leary to see Developer Advocate implications of removing the library (users would still be able to add back via Palette UI / manual install).

If Nick gives 👍 or doesn't respond in a reasonable amount of time, we should remove the library from the starter kit as it's not being supported adequately.

If Nick gives us a replacement library, we can use that instead.


Acceptance Criteria:

  • Open up PR to remove library from package.json and tag Nick O'Leary
  • After 1 week (if no response) merge and promote the PR to remove the library

@knolleary
Copy link
Contributor

Okay, well consider this a big 👎🏻

There were some efforts underway to get the cloudant nodes updated which have stalled in part due to my leaving IBM. We should still be able to revive that work.

node-red-contrib-ibm-cloud/community#1

@nfstein
Copy link
Member Author

nfstein commented Jun 8, 2021

So you don't consider node-red-contrib-cloudantplus to be a suitable replacement at this time either?

@johnwalicki
Copy link
Contributor

While it maybe useful to force the issue here, the right answer is to decide how we want to handle node-red-node-cf-cloudant upstream. Discussion in the issue linked by Nick above.

@github-actions
Copy link

👋 Hi! This pull request has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.

@github-actions github-actions bot added the stale label Jul 23, 2021
@github-actions github-actions bot closed this Jul 30, 2021
@jmeis jmeis deleted the remove-node-red-node-cf-cloudant branch July 30, 2021 14:15
@jmeis jmeis restored the remove-node-red-node-cf-cloudant branch July 30, 2021 14:15
@jmeis jmeis reopened this Jul 30, 2021
@jmeis jmeis removed the stale label Jul 30, 2021
@github-actions
Copy link

👋 Hi! This pull request has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.

@github-actions github-actions bot added the stale label Aug 30, 2021
@github-actions github-actions bot closed this Sep 6, 2021
@jmeis jmeis deleted the remove-node-red-node-cf-cloudant branch November 15, 2022 21:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants