gmvault icon indicating copy to clipboard operation
gmvault copied to clipboard

The future of GMvault?

Open mrjcleaver opened this issue 7 years ago • 13 comments
trafficstars

Hi @gaubert ,

I can see from Github that 95% of commits came from you, and from Linked In that you got a new job in Jan 2017 - I can imagine this is all absorbing.

So, can we assume that any piece of software is done? I'd bet it will work on Windows 10, for instance, but that's not listed.

There are some 14 pull requests - perhaps one of those authors is willing to take over?

Thanks, MArtin.

mrjcleaver avatar May 13 '18 10:05 mrjcleaver

Hi, just to inform that I'm using without problems on Windows 10.

TowerBR avatar May 14 '18 20:05 TowerBR

There will be issues when Python 2.6 is completely deprecated.

ghost avatar Jun 23 '18 10:06 ghost

I'd be happy to help, I'm looking for an open source project to volunteer in

ochronus avatar Jul 20 '18 12:07 ochronus

Is this project dead? A lot of forks, no activity in a while.

nicholashead avatar Nov 01 '18 16:11 nicholashead

Pinging @guillaumeaubert.

jpellman avatar Dec 05 '18 21:12 jpellman

Pinging @guillaumeaubert.

Wrong Guillaume Aubert. You're looking for @gaubert.

guillaumeaubert avatar Dec 07 '18 06:12 guillaumeaubert

@guillaumeaubert - Ah, my apologies. I thought @gaubert might have gotten a new Github account.

Honestly, I thought that your gmvault-docker project + your shared name was a clear indication that you two were the same person.

jpellman avatar Dec 07 '18 15:12 jpellman

Honestly, I thought that your gmvault-docker project + your shared name was a clear indication that you two were the same person.

No worries, it's indeed a bit confusing. My contributions were limited to packaging GMVault into a docker container in a repo that is independent of the main GMVault project, and we're two different people :)

guillaumeaubert avatar Dec 08 '18 22:12 guillaumeaubert

@gaubert Any way to set someone else as maintainer?

lkraider avatar Jan 07 '19 21:01 lkraider

Some sort of shared governance of the project would indeed be prudent (even if @gaubert still intends to work on this and is just temporarily side-tracked). Ideally a CentOS-like situation should be avoided.

jpellman avatar Jan 08 '19 16:01 jpellman

Next steps for the project could be:

  • release 1.9.2, with these commits from 2017: https://github.com/gaubert/gmvault/compare/master...gmv-1.9.2, and with any other small change to keep it working under Python2
  • make it work under Python3: see https://github.com/gaubert/gmvault/pull/284, there are already a few proposed code changes

@gaubert If you're busy, maybe you can open a new GitHub issue to request a new maintainer, and when it's decided you grant rights to the new maintainer.

clemente avatar May 20 '23 18:05 clemente

If you end up here, because your distro no longer has Python2 and gmvault is still not Python3-ready, I recommend using the containerized Python2 approach: https://github.com/luckylittle/gmvault

luckylittle avatar Jul 25 '23 03:07 luckylittle

Seems like @gaubert is still active, making a few contributions a year on Github. but I think he's busy with other things.

I think we should fork the project under a new repo and modernize it. It's been about 10 years since the last commit.

zeidoo avatar Sep 30 '23 02:09 zeidoo