-
Notifications
You must be signed in to change notification settings - Fork 327
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
Create you move this repository into the openfortivpn organization? #1260
Comments
I am not the maintainer. Actually, I don't have much time any more to devote to openfortivpn. |
Hello @Neustradamus, I understand that you would find it "really better", but I don't see the benefit of doing so. For info we already discussed this question with "the current team" some time ago. |
@adrienverge: Only you can do it. The history, "Issues" and "PRs" are only here. Your latest participation is old (2023-02-25): If you do not transfer this repository, @DimitriPapadopoulos will need to fork this repository to have in @openfortivpn organization (the good place), and after he will need to contact GitHub to detach the fork from upstream but all forks are linked to this repository. So all people need to remove this personal fork and to create a new one, and need to create new issues too, etc.. Note: After a very long battle with GitHub and the new maintainer of one project, not easy, several years, I have realized the transfer of an important project from a died person (RIP) because the dead was announcement at several places in the past. |
I do not intend to fork this repository and I don't have time to help much with openfortivpn any more. With that said, I hear your concern. However, we have been looking for volunteers to help maintain the project, without success so far. That's the real problem. |
@DimitriPapadopoulos: Changes have been integrated in upstream? |
You're mistaken, there's no "upstream". |
@DimitriPapadopoulos: https://github.com/openfortivpn/snap is a fork, upstream is currently https://github.com/adrienverge/openfortivpn ;) |
@Neustradamus my latest participation is not old, I periodically create new releases and follow everything that's happening here. With the huge help of @DimitriPapadopoulos, this repository is still alive. But as Dimitri says: the real problem is the lack of volunteers to help maintaining the project. It's not about changing the repository URL, in my opinion. |
@adrienverge: Good, you confirm that it still alive because @DimitriPapadopoulos is here :) After this repository transfer, redirections will be here, no lost, example of previous transfers:
|
To clarify, I don't have much time to devote to openfortivpn any more. The real issue is finding an experienced volunteer to maintain openfortivpn and help with the necessary changes:
|
@DimitriPapadopoulos: For the future of openfortivpn, it is better to move it into the @openfortivpn organization. It is easy to manage a project in the @openfortivpn existing organization by @adrienverge and you. If @adrienverge is not member, you must to add him here: Do not forget to add you in public too. In more, you can add new team members (volunteers) easily. It is a needed step. Thanks in advance. |
Dear @adrienverge,
Thanks for your openfortivpn work!
Can you transfer this repository into the @openfortivpn organization?
GitHub adds redirections after transfer, no lost.
It will be really better for the current team to manage, etc.
Thanks in advance.
The text was updated successfully, but these errors were encountered: