Separate out all the puppy apps into their own reps then, and you will defo get more PRs in future...mavrothal wrote:Pull requests are always welcome and mostly granted.Most Puppy users and even devs refuse to get involved in anything Git or GitHub
There are not many coming though....
Having them all in a mono repo blob, makes it so much harder to contribute.
Let's say I do a fix to the puppy installer... I don't have th option of pulling down the installers repo, making a feature branch, and doing a pull request on just that program... I cant even pull down the installer repo, build the program on its own... basic!
Instead, I have to pull down all of Woof-CE, make some changes in the installer program, manually copy them into some other place to test them, copy them back, and THEN do a PR of the whole woof-ce thing - making merge conflicts way more likely, changes MUCH harder to find, (let alone revert) and leaving the installer changes to be lost in the massive git history of the mono repo ...
Creating feature branches is essential to getting multiple devs working on a single code base, but the way woof is organised, that becomes almost impossible..
It's also imossible to create forks of individual puppy programs, cos they live in the mono woof-ce repo .. this slows down development as well..
I've literally never known any serious software project bundle all kinds of DIFFERENT changes (bugfix, new feature, breaking change, minor change) into a single blob of a "testing" branch, instead of doing new features and bugfixes all in separate branches..
TBH, its a mess of a repo. That is why more people don't contribute to it - duplicated effort, hard track changes, terrible docs about the changes made, awful cryptic commit messages... No documentation attached to PRs... No reason given when PRs are closed not merged... etc.. etc..
Almost impossible for a new user to get involved..
The reason Alpine and others have gone from zero to hero so quickly is simply cos they have good dev practices - which encourage (rather than discourage) new & skillful devs to want to contribute and get involved.. Alpine, SLAX and others make/made it very easy for devs to get involved, Puppy doesn't.
....And as I have pointed out before, one we have a "good build" setup, which produces a very good puppy, that should be saved out into a separate, versioned branch...
Then ppl can simply do:
git pull
git checkout <some-known-puppy-version-or-build>
Example:
git checkout puppy-precise-5.5
or
git checkout puppy-precise-5.5-lxde
And then they are all setup to produce a specific puppy version/setup, and juts run 0setup etc as nomal...