(old)Puppy Linux Discussion Forum

nice piece of hacking there! It works thats what counts. Perhaps

http://www.phpbbhacks.com/download/7842

I there a volunteer who would be willing to summarize these problems and make a list, and check which ones still exist in 3.02 when it comes out? All reported bugs in 3.02 should be ironed out in 3.03ce.

Thanks

alienjeff wrote:Please resize screenshots. Sheesh.

Good idea. What is the tool/command

nic2109 wrote:

alienjeff wrote:Please resize screenshots. Sheesh.

Good idea. What is the tool/command

mtPaint and image>scale canvas. I find 800x600 is plenty for the forum, and if you use http://www.tinypic.com they don't take up space either.

Hope that helps

ecomoney wrote:Is there a volunteer who would be willing to summarize these problems and make a list, and check which ones still exist in 3.02 when it comes out? All reported bugs in 3.02 should be ironed out in 3.03ce.

There was one such volunteer. And a "bug reporting thingy."

http://www.murga-linux.com/puppy/viewto ... 831#129831

Then came a developer's statement - an amicable divorce between official and CE versions.

Now a volunteer is needed to weed through the forum for bugs instead of one of those troublesome bug reporting thingies ...

In the immortal words of Peter Boehnert, "Ready. Fire. Aim."

Pass the beer nuts.

Yes, I recall being shown that, it was a shame. Bug reporting/handling is really important and its one of the things that has been pointed out many times as needing improvement in the development of puppy. Since this is the community edition then the community can help with this one. Ive started a request for a bug "SWAT" team here, to compile a thorough list of the things that will need fixing before the community edition in a more methodical way than just reporting via the forum (although this is simple and easy for newbies to do, and bugs do need an easy way of being reported.)

Barry is doing his bit by making the 3.01, and 3.02 version bug fix releases to make an already quite stable core for the next CE edition. "We can use this to iron out the final creases" as well as providing new features that the wider community have asked for.

The request for SWAT members can be found here

How about using Bugzilla for issue reporting/tracking? See http://www.bugzilla.org

nic2109 wrote:How about using Bugzilla for issue reporting/tracking? See http://www.bugzilla.org

It's been Barry's preference to have a more informal bug reporting mechanism such as this thread.

http://www.puppylinux.com/development/p ... tement.htm

rarsa wrote:

nic2109 wrote:How about using Bugzilla for issue reporting/tracking? See http://www.bugzilla.org

It's been Barry's preference to have a more informal bug reporting mechanism such as this thread.

http://www.puppylinux.com/development/p ... tement.htm

Thanks. I've been told that several times since this posting- including by Barry himself. So; OK guys I get the message.

However........ ecomoney does want to report and track bugs for the next CE (which he has volunteered to co-ordinate) and is looking for a suitable tool...................

nic2109 wrote:However........ ecomoney does want to report and track bugs for the next CE (which he has volunteered to co-ordinate) and is looking for a suitable tool...................

Well, there are several options.

1. We used a bugtracker for 1.09CE. It may still be alive. I don't remember who provided it, but if you ask Nathan he may remember.

2. I have an account for Puppy on cvsdude. It includes a bug tracker but we haven't used it. As far as I remember being a free account it had a limitation on the number of people that can enter bugs.