Git-secret: Additional maintainer(s) wanted

[sobolevn]

Call for maintainers

Right now I don't have much time to support this project. Sorry.

But I do not want to leave it unmaintained, since it is working fine, but still needs some major improvements. And I love using it already.

I would love to contribute to this project in the future, but right now it requires someone to care for it. I would post some advertising around the web, so feel free to contact me!

Required experience

• Solid bash
• Solid git
• Some gpg (it is pretty easy to use, actually)
• Some docker (we are running tests inside docker containers)
• Some general DevOps (since we use a lot of automation: deb and rpm generation, etc)
• Some testing (tests are still in bash)

Time

I expect that 6 hours a week would be sufficient.

[Prathamesh404]

So I have experience in some -
Bash
git
Will I be able to help?

[sobolevn]

@Gitcat711 of course! Feel free to contribute.

You can ask @joshrabinowitz about what can you help him with.

[joshrabinowitz]

~~Hello @Gitcat711 ! The most pressing issues are

120, regarding the deploy process, and

135 , regarding spaces in pathnames

There are pretty extensive notes on each issue. Your input is welcome and appreciated! Feel free to ask any follow-up questions in the issues themselves.~~
(edit: these have been fixed)

[joshrabinowitz]

@Gitcat711 also let me know if you need help getting your dev environment set up, or if you want to take on an easier issue than the ones above.

[joshrabinowitz]

It looks like PR https://github.com/sobolevn/git-secret/pull/184 fixes issue #120 'Deploy step is ignored'
It would be great if someone would fix issue #179 'travis-ci can't find man pages'
(edit: this has been fixed.)

[simbo1905]

I have got a fix for #179 that I am testing locally (the test ci suite takes a loooooong time locally).

@sobolevn @joshrabinowitz Do you mind making me a collaborator so that I can label issues that are blocking the 0.2.4 release so that we can focus on that?

[sobolevn]

I totally do not mind!
Welcome!

[Prathamesh404]

Hello Josh,
I was burned up due to some other work. So how I can start from scratch and
contribute. I am sorry to let you down, but I ain't no ninja coder. Let's
see how I can create impact. Any roadmap for environment setup?

On Tue, Jun 5, 2018 at 4:04 PM, Josh Rabinowitz [e-mail]
wrote:

@Gitcat711 https://github.com/Gitcat711 also let me know if you need
help getting your dev environment set up, or if you want to take on an
easier issue than the ones above.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sobolevn/git-secret/issues/100#issuecomment-394661966,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYrkJNC6XIBbg8TtbHfRyXTgWfy5J3qAks5t5l6dgaJpZM4OZTn6
.

[simbo1905]

@Gitcat711 the ci build and release is now fixed so its easier to contribute bug fixes. there are also some documentation issues. take a look at the open issues and see if there are any you would like to spend some time on. take a read of contributing.md, fork, fix, send a PR, and watch the travis build to see if it passes and fix as needed 👍🏻

[joshrabinowitz]

It would also be great if someone would implement https://github.com/sobolevn/git-secret/blob/master/RFC/RFC001.md which would fix interoperation issues between versions of GPG

[apallennz]

Hi there, i found this as a result of looking for open source projects to contribute to, i'm new
I'm really keen on Linux, have recently been studying bash via LinuxAcademy, and have a little bash experience
Please let me know if this is a project I could help with, if you're still wanting help
Cheers

[sobolevn]

@apallennz welcome!

I am pretty sure there are some things you can help us with.
I would suggest to start from the documentation updates:

• just read through the existing docs and point out parts that are not easily understandable for you
• create new issues with "documentation" badge
• together we will try to fix the bad parts

You can start from CONTRIBUTING.md and README.md moving to the man files later on.
This way you will get familiar with the project and help us to improve the docs.
How does it sound to you?

[apallennz]

Sounds good, thanks for responding

On 3/09/2018 11:33 PM, "Nikita Sobolev" [e-mail] wrote:

@apallennz https://github.com/apallennz welcome!

I am pretty sure there are some things you can help us with.
I would suggest to start from the documentation updates:

• just read through the existing docs and point out parts that are not
  easily understandable for you
• create new issues with "documentation" badge
• together we will try to fix the bad parts

You can start from CONTRIBUTING.md and README.md moving to the man files
later on.
This way you will get familiar with the project and help us to improve the
docs.
How does it sound to you?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sobolevn/git-secret/issues/100#issuecomment-418088243,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmhECQGFyDKqQ-rH1KFpcq0vJ50N-wslks5uXROBgaJpZM4OZTn6
.

[apallennz]

so, question
what private data would you be wanting to store inside a git repo?

[joshrabinowitz]

@apallennz some examples of secrets you might want to store in a git-secret repo include "SSH keys, SSL private keys, API keys, passwords, and client secrets." https://embeddedartistry.com/blog/2018/3/15/safely-storing-secrets-in-git

[joshrabinowitz]

We could also use maintainers to help us submit packages to EPEL/Fedora and Debian and FreeBSD Ports:
See #312, #315, #316 .