People involved in Puppy, especially new version developers

[bigpup]

It is time to do some work to support Puppy Linux.

Everyone needs to get involved.

Especially if you are a person that develops and builds new Puppy versions.

If you are someone that understands coding software and wants to help in offering new programs to use.
Fixing program code bugs or adding features to any of the Puppy specific programs.
People with knowledge on coding are needed all over the development of Puppy Linux.

Anyone else can help anyway they want to. Even using a Puppy version and reporting how it works is a big help.
Everything really needs testing by people, to uncover code errors, bugs, or not fully correctly put together new Puppy versions.
Everyone can test stuff by simply trying to use it. Reporting about how it worked. Any bugs, any issues, or it works great!

This topic is really uncovering some of the big issues in Puppy Linux.
https://forum.puppylinux.com/viewtopic.php?t=9538

These two posts everyone should read:

Is the big issue people not using the latest Woof-CE to build with?

The issue I see is 3 issues:
1) People not using latest woof-CE, so some Puppy releases lag behind and have bugs already fixed in other releases
1.1) People using woof-CE but not adopting new features: for example, many Puppy releases are still built with some ancient ROX-Filer .pet package that contains known issues, instead of using woof-CE's ability to build ROX-Filer from source with the latest Puppy patches
2) People using some version of woof-CE, modifying it locally and never contributing back the changes, so one Puppy release has a unique feature or unique bug fix others don't have ... then, the Puppy version described as its "successor" is a step backwards because it was built without that modification
3) Too many people trying to build too many Puppy releases, so no release gets tested properly, the various releases are similar to each other (because a solo developer doesn't have the time to develop big features) and big problems that require collaboration (things like reviving PPM, porting ROX-Filer away from GTK+ 2 or cleaning up 20 years of legacy cruft in Puppy) don't get any attention

This one concerns 01micko, who is suppose to be the Puppy master and overall keeper of the Puppy name, registration, main web sites, and repository.
He has stated that will not be that involved anymore.

@01micko is going to have to hand over the GitHub rights. Simple as that. Crazy to have someone who's not involved and not intending to get more involved and is mostly absent and be the one who is making the code review and is the one with woof-CE commit merging control and "ownership" of the GitHub account containing woof-CE.

It has nothing to do with the "Do-acracy" concept but is based on reality. It is like riding off into the sunset and taking the house keys and the Deed along.

Probably a good time to remind people that the rent for the forum space has been increased

Please get involved and help anyway you can!!!!

[mikewalsh]

I will just add here that by "testing" it means using the Puppy as-is, as it comes, OOTB.

Please don't report results having already customized your Puppy. Testing Puppy in its original condition, as released, means that everyone is "singing from the same hymn-sheet", and bugs/issues should be reproducible by all.

Thanks.

Mike.