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 new branch on BB repo #180

Open
TheRealNoob opened this issue Apr 11, 2017 · 0 comments
Open

Create new branch on BB repo #180

TheRealNoob opened this issue Apr 11, 2017 · 0 comments
Assignees

Comments

@TheRealNoob
Copy link
Contributor

These are some thoughts I have about how to better organize the BashBunny repository.

The problem: The issue is that people submit payloads (as they should) but the quality varies drastically. Some people put in serious time, others not so much. Some people have good ideas but don't have the knowledge or time to carry those ideas to completion. I won't mention any specific scripts but just the other day I was reviewing some exploits and I saw that they all pulled the main bit from someone else's github whose script is only partially working. This is really unfortunate; You don't want to go on there with your new bunny looking to try out some of the coolest scripts only to find that they don't work. Now just 30 minutes after you open your bunny you're already doing troubleshooting. That sucks.

The solution: I think creating a second branch (call it "dev" for example) could really help you to maintain a strict quality standard, while still allowing everyone to submit. The dev branch would be the place that all user-submitted scripts would go to and development would be had on. The Hak5 team could appoint a few trusty viewers to oversee PR's made to this branch. And periodically the Hak5 employees could check in here to see what's good and possibly bring it over to master branch. Or alternatively I could see that group of trusty people making the PRs to master for the Hak5 team to review.

Closing thoughts:
This would do a few things:

  • Lighten the workload on the Hak5 crew
  • Set a tighter quality assurance standard on the repo (at least the front face of it)
    While still allowing everyone to contribute !! This is very important
  • By passing some control over the public you are showing even more commitment to open-source and community driven collaboration
@foxtrot foxtrot self-assigned this Jun 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants