next-theme fork and theme next future

[noraj]

Issue Checklist

• [x] I am using NexT version 8.0 or later.
• [x] I have already read the relevant documents of Hexo and NexT.
• [x] I have already searched for current issues, which does not help me.

Other Information

Can someone explain me that https://github.com/theme-next/hexo-theme-next/issues/1663?

[noraj]

It seems there are some answer here https://github.com/next-theme/hexo-theme-next/issues/4 but it's all in Chinese so I can't read it.

[noraj]

Translation

https://github.com/next-theme/hexo-theme-next/issues/4#issuecomment-626187669

Team theme-next and next-theme what is the relationship?

https://github.com/next-theme/hexo-theme-next/issues/4#issuecomment-626205848

Simply put, the problem is that the owner of the theme-next team always refuses to provide sufficient permissions to any other team members, and the owner himself has been offline for six months since October 2019, causing other active team members to be unable to manage the warehouse. Unable to invite new members. Since I do not have expectations for the future of the theme-next team, as the main contributor of theme-next, I have stopped contributing code to the old warehouse from April 2020 and created a new organization to ensure the normal maintenance work

[noraj]

None of the original https://github.com/orgs/theme-next/people came to https://github.com/orgs/next-theme/people?

[ljcbaby]

NexT has a total of three different repo:

Version | Year | Repo -- | -- | -- v5.1.4 or below | 2014 ~ 2017 | https://github.com/iissnan/hexo-theme-next v6.0.0 ~ v7.8.0 | 2018 ~ 2019 | https://github.com/theme-next/hexo-theme-next v8.0.0 or higher | 2020 | https://github.com/next-theme/hexo-theme-next

---

next-theme is a new team re-established by the active contributors of theme-next.

[noraj]

@ljcbaby Thank you for the enlightenment!

[noraj]

Since someone with write access on theme-next (onurkat) pushed a commit 9 days ago, is that possible to ask him to archive the theme-next repositories? If he only have dev access and not maintainer/owner, then a push to the README stating the project now live at next-theme org to avoid future confusion?

[njzjz]

Since someone with write access on theme-next (onurkat) pushed a commit 9 days ago, is that possible to ask him to archive the theme-next repositories? If he only have dev access and not maintainer/owner, then a push to the README stating the project now live at next-theme org to avoid future confusion?

The one who merged this PR is actually @jiangtj ...

[jiangtj]

😂 I currently only do maintenance for some bugs. Make sure that 7.8 version's users can use the NexT theme as well.

In theme-next repositories, only ivan-nginx has owner permission. You can see the difference between member and owner.

https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization

[jiangtj]

If he only have dev access and not maintainer/owner, then a push to the README stating the project now live at next-theme org to avoid future confusion?

After all, I am not the owner, maybe I have permission to archive it and update the readme, but I won’t do that

Let’s make a hypothesis. If you may have left GitHub for some reason, but after a period of time, you come back and see that your own project is marked as archived by others, how would you feel?

[njzjz]

@jiangtj 👍🏼

[github-actions[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. It is possible issue was solved or at least outdated. Feel free to open new for related bugs.