Do you need help maintaining this repository?

josegonzalez commented 9 years ago

I'd be happy to pitch in and clean up some of the issues/pull requests, as well as implement them in a way that doesn't break CI in cases where they currently do.

josegonzalez commented 9 years ago

Bump :)

ghost commented 9 years ago

Why you can't create a featue-branch and send pull-request. If author is not responding you can fork cookbook. And send to all users, who has starred this repo, info about it!

josegonzalez commented 9 years ago

@cvl-skubriev The cookbook is listed as the official openvpn cookbook on chef supermarket, and opscode moved the cookbook here in the hopes that it would be better maintained. There are a few PRs without response or update from the current maintainers, so if they need someone to triage the PRs, I'm willing to help.

There's also been no activity on the repository for quite a few months, so clarifying it's status would be nice.

ghost commented 9 years ago

I'd be happy if this cookbook will develop in future.

jtimberman commented 9 years ago

To be clear the only such thing as "official" cookbook is one written / maintained by the author of the software that it automates, IMO. Just because someone makes a cookbook named "armchair" doesn't make it an "official" cookbook for managing "armchair." For example, CHEF maintains a "chef-client" cookbook, for managing a "chef-client" configuration and/or service, thus CHEF"s official cookbook for "chef-client" is that cookbook.

This is a side effect of first-come first-serve on the old community site, and the current supermarket site, whereby I squatted all the good cookbook names years ago :smile:. While I know chef very well, I'm not a subject matter expert in every single piece of software I've automated with it. This is why we (CHEF) started diversifying maintainership of cookbooks. We did retain collaboration on supermarket for the cookbooks we're interested in assisting maintenance.

That said, I'm a collaborator of the cookbook on supermarket, and I do have a vested interest in it (I use it for maintaining my home VPN server).

@flaccid Would you please grant me push access to this repository so I can assist in maintenance?

Cheers, Joshua

flaccid commented 9 years ago

Sorry guys. The pull requests on this cookbook have been on my backlog for some time now. I'd like to keep the write access limited to myself and @jtimberman for now (your access is still there) just until the pull requests are processed; I just want some control on the new direction before we look at more direct contributors.

Some of the recent changes that did get implemented and merges are already non backward compatible with the last release, thus we are in a flux state preparing for the next major release.

Some elements to ensure we maintain, but not limited to:

enable configuration of servers and clients including specifying arbitrary config directives via node attributes (mostly done)
work with both chef server and chef solo (chef server can take advantage of node search etc.)
provide flexibility in how PKI is managed for user/client access - generating keys for users, revocation etc. (and think about persistence of user access if the node is wiped out and needs to be reconfigured)
support as many platforms as possible and maintain tests for those platforms
keep documentation up to date, add in documentation for changes

Now, I'll try to find some time to put in some hours to do the backlog; @jtimberman you are welcome to get started.

eherot commented 9 years ago

Just to be clear (since we are now over a year since the last release of any kind), are you hoping to fix the backwards compatibility issues before making the next release or is there something else that we are waiting for (something that I or someone else could potentially help with)?

josegonzalez commented 9 years ago

Closing this issue. My PR wasn't merged (and tests are just fundamentally broken because berk berk berk :P) and I was not directly responded to. I've since moved to using pritunl (which is nice) though it would still be nice to get movement on this repo, even if for the benefit of the chef community at large.

Good luck to those using this in production!

flaccid commented 9 years ago

@josegonzalez you may be pleased to see that we have made quite a bit of progress since your last comment. Its in a much better state for contributions, testing has been updated and we're ready for more pulls and issues :)

josegonzalez commented 9 years ago

Thats nice, hopefully that stays the case for future users of this cookbook. As I mentioned before, I have since moved to Pritunl, which works quite nicely for my use case.

Thanks for your hard work though!

ascendantlogic commented 8 years ago

There have (as of this writing) been 181 commits to master since the last release. Is there a reason new releases have not been made? I'm just curious because I'd really rather not have to fork and freeze as a method of capturing the more recent changes.

flaccid commented 8 years ago

@ascendantlogic we just need to complete https://github.com/xhost-cookbooks/openvpn/milestones/v3 before we tag a new major release, v3.0.0.

lock[bot] commented 5 years ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

sous-chefs / openvpn

Do you need help maintaining this repository? #39