BusPirate / Bus_Pirate

Community driven firmware and hardware for Bus Pirate version 3 and 4
625 stars 131 forks source link

Add members to the project #171

Open matsievskiysv opened 1 year ago

matsievskiysv commented 1 year ago

This project has not seen any updates in a while. Maybe some active contributors could be given write access so development could move on?

DerekGn commented 1 year ago

@matsievskiysv

Another, less than ideal, idea maybe to fork the project and continue the development on the fork. Create the fork under an organization and add a number of admins to that org/fork.

You can create a forked repo and then add the BusPirate/Bus_pirate repo as an upstream repo

git remote add upstream https://github.com/BusPirate/Bus_Pirate.git

You can then pull all the open PRs to the forked repo

git fetch [NAME REMOTE PROJECT] pull/[PR NUMBER]/head:[PR BRANCH NAME]

For example pull PR 170 changes to a branch called pr_name

git fetch upstream pull/170/head:pr_name

That way all of the contributions can be merged into the fork.

matsievskiysv commented 1 year ago

I know how to create PRs. The problem is that this project has a lot of very old PRs with no reviews. Clearly, the maintainer of the project could use some help with those. I didn't mean that project members should push their code directly to master. They could help with currently opened PRs.

DerekGn commented 1 year ago

I think you missed the point, never said you didn't know how to create PRs, that fact is self evident you have an open PR #170 :)

These are not instructions to create PRs. These are instructions on how to copy existing PR changes from this repo into a new repo. Basically a whole sale fork of this repo in it current state. The copied PR changes are moved to their own branch on the fork.

At this point there has not been significant code changes made to this repo for a number of years, hence suggestion to do a wholesale fork of the repo.

Maybe the owner of this repo will open it up only time will tell.

matsievskiysv commented 1 year ago

@DerekGn Oh, I've misread your comment. Sorry.

DerekGn commented 1 year ago

@matsievskiysv Hey no problem

psolyca commented 1 year ago

Done https://gist.github.com/psolyca/6423302561f4cc6be46716c201758abb Everyting is compiling but currently I did not test it on the board.

ojg78 commented 1 year ago

Is the gist going to become a full supported fork? I'm trying to work out if this project is dead\dying or if getting the v4 hardware would be a good idea.

psolyca commented 1 year ago

Sorry I have built a bin and used it but forgot to update the gist 😅 I'm just using the UART mode.

matsievskiysv commented 1 year ago

I'm trying to work out if this project is dead\dying or if getting the v4 hardware would be a good idea.

IMHO this firmware is good enough for many applications. It's my go-to device for getting acquainted with the new chips.

ojg78 commented 1 year ago

Is there a consensus on choosing v4 vs V3. X? Thanks for the responses.

matsievskiysv commented 1 year ago

Is there a consensus on choosing v4 vs V3. X? Thanks for the responses.

I'm a simple man, I just go with higher number. I don't remember having any v4 specific issues.