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

donation project to the nebula-contrib tent/org #1

Closed
wey-gu opened this issue Sep 6, 2023 · 7 comments · Fixed by #2
Closed

donation project to the nebula-contrib tent/org #1

wey-gu opened this issue Sep 6, 2023 · 7 comments · Fixed by #2

Comments

@wey-gu
Copy link
Member

wey-gu commented Sep 6, 2023

Dear @jxnu-liguobin /HJ Fruit

ZIO-Nebula is a Great/Decent project, thanks a lot for the creation!

If it's possible to move this project to Nebula-Contrib Tent, as discussed here, our org admin @Shinji-IkariG could help with that!

Thanks!

@wey-gu
Copy link
Member Author

wey-gu commented Sep 6, 2023

I think the first move is to transfer the repo to @Shinji-IkariG and in parallel, @QingZ11 will reach out to you via mail(the outlook dot com one in your profile)!

Thanks!

@wey-gu
Copy link
Member Author

wey-gu commented Sep 7, 2023

Dear @jxnu-liguobin , could we transfer this repo to @Shinji-IkariG first, then he will put the repo to the Org afterward.

Thanks!

@jxnu-liguobin
Copy link
Collaborator

Waiting for acceptance

@jxnu-liguobin
Copy link
Collaborator

There is some work to be done.

This project uses the popular tool sbt-ci-release to automatically publish artifacts, so it needs to rely on these variables. (If we change the publishing organization).

If there is no need to change the organization of the artifact, are there variables present after the repository transfer?
image

@wey-gu
Copy link
Member Author

wey-gu commented Sep 7, 2023

There is some work to be done.

This project uses the popular tool sbt-ci-release to automatically publish artifacts, so it needs to rely on these variables. (If we change the publishing organization).

If there is no need to change the organization of the artifact, are there variables present after the repository transfer? image

What is your preference? I think we could keep the existing Sonatype publishing repo, but change the variables with a prefix: i.e. LGB_PGP_KEY ..., and you hand over the credentials to @Shinji-IkariG so he could configure them as secrets.

Or we could apply for its new Sonatype under .org.nebula-contrib

I think to keep io.github.jxnu-liguobin makes sense :)

@wey-gu
Copy link
Member Author

wey-gu commented Sep 7, 2023

Wow it's already under new org! 🎉

Also, @Shinji-IkariG could we consider granting @jxnu-liguobin permissions so that he could put those secrets on his own, so that no one else could get the record of his credentials?

@jxnu-liguobin jxnu-liguobin linked a pull request Sep 8, 2023 that will close this issue
@wey-gu
Copy link
Member Author

wey-gu commented Sep 8, 2023

confirmed with @jxnu-liguobin offline to know that the publishing with sbt is verified to be done smoothly already within the current configuration.

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

Successfully merging a pull request may close this issue.

2 participants