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

Create you move this repository into the openfortivpn organization? #1260

Open
Neustradamus opened this issue Jan 2, 2025 · 11 comments
Open

Comments

@Neustradamus
Copy link

Neustradamus commented Jan 2, 2025

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.

@Neustradamus Neustradamus changed the title Create an organization and transfer openfortivpn repository into? Create you move this repository into the openfortivpn organization? Jan 2, 2025
@DimitriPapadopoulos
Copy link
Collaborator

I am not the maintainer. Actually, I don't have much time any more to devote to openfortivpn.

@adrienverge
Copy link
Owner

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.

@Neustradamus
Copy link
Author

Neustradamus commented Jan 2, 2025

@adrienverge: Only you can do it.
Example, you leave GitHub, the project is always blocked because of you.

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.

@DimitriPapadopoulos
Copy link
Collaborator

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.

@Neustradamus
Copy link
Author

@DimitriPapadopoulos: Changes have been integrated in upstream?

@DimitriPapadopoulos
Copy link
Collaborator

You're mistaken, there's no "upstream".

@Neustradamus
Copy link
Author

@adrienverge
Copy link
Owner

@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.

@Neustradamus
Copy link
Author

@adrienverge: Good, you confirm that it still alive because @DimitriPapadopoulos is here :)
So it will be very logic to transfer in the organization managed by all of you two.

After this repository transfer, redirections will be here, no lost, example of previous transfers:

@DimitriPapadopoulos
Copy link
Collaborator

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:

  • Use systemd-resolved when available, or better yet switch to vpnc-scripts to set routing and DNS parameters.
  • Support IPv6 - switching to vpnc-scripts would help considerably.
  • Address 2FA.
  • Work on compatibility with the FortiClient Endpoint Management Server (EMS).

@Neustradamus
Copy link
Author

@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.

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