Skip to content
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

To Dos after the move #1

Closed
5 tasks done
egekorkan opened this issue Feb 17, 2024 · 9 comments
Closed
5 tasks done

To Dos after the move #1

egekorkan opened this issue Feb 17, 2024 · 9 comments

Comments

@egekorkan
Copy link
Member

egekorkan commented Feb 17, 2024

The move has finished. The contributors look correct now.

  • Publishing to npm
  • Agreeing on the versioning
  • Deprecating older packages (including @hidetak packages)
  • Making old repo a public archive
  • Evaluating the existing issues if they are still issues
@hidetak
Copy link
Contributor

hidetak commented Feb 17, 2024

@egekorkan @JKRhb

Evaluating the existing issues if they are still issues

Along with the server-side node development, I have modified the following Issue to meet the request.
thingweb/node-red-contrib-web-of-things#17

@hidetak
Copy link
Contributor

hidetak commented Feb 17, 2024

Deprecating older packages (including @hidetak packages)

I will deprecate my package after a new package is released.

@egekorkan
Copy link
Member Author

egekorkan commented Feb 17, 2024

ok it seems I cannot comment when the repo is archived or close an issue. In the next meeting, we can evaluate which way to go. I am fine by leaving the issues open, it is unlikely that someone will trace back there. We should simply open the issues here if they are still present. Any thoughts @danielpeintner , @relu91, @JKRhb ?

@danielpeintner
Copy link
Member

danielpeintner commented Feb 20, 2024

I agree, we should

  • open the same issues here again (if still valid)
  • add a pointer to its new location (I did not find it)

Maybe we can temporarily un-archive the old repo to close all old issues and add a BIG Header were the new content went...

@egekorkan
Copy link
Member Author

egekorkan commented Feb 20, 2024

I have unarchived it and closed all the non-relevant issues. There is only thingweb/node-red-contrib-web-of-things#12 left that I think we can move here since we were discussing it in the last meeting.

I have also added a warning banner on the top of the readme.

@egekorkan
Copy link
Member Author

In today's call, we have fixed the versioning and then will publish to npm after integrating prettier and eslint workflow.

egekorkan pushed a commit that referenced this issue Feb 29, 2024
@egekorkan
Copy link
Member Author

egekorkan commented Mar 4, 2024

@hidetak the packages are published to npm https://www.npmjs.com/package/@thingweb/node-red-node-wot and also available in flows library at https://flows.nodered.org/node/@thingweb/node-red-node-wot .

Still some small todos:

@hidetak
Copy link
Contributor

hidetak commented Mar 4, 2024

@egekorkan

Thank you for making the package available to the public.

  • @hidetak can you deprecate your packages?

I have changed to deprecated.
https://www.npmjs.com/package/@hidetak/node-red-contrib-web-of-things

@egekorkan
Copy link
Member Author

Thank you @hidetak. I have deprecated the old ones as well after getting access to the organization. The todos are completed, closing issue :)

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

No branches or pull requests

3 participants