Puppy 6

[mavrothal]

Some people are architects and some are field engineers. The world needs both

Puppy needs both!

But what if the field engineers are actually designing without a blueprint, and the architects are designing as a goal and not as means to a high quality "product"?
What about if the two do not communicate or at least have common end goals?

The outcome will be (at best) an "one time good thing" that will stay within "a very little pond".
More often than not, not even that.

[greengeek]

Puppy needs both!

What i love about this forum is that all points of view have an opportunity to contribute and shape new directions.

The forum is like a backbone - it provides a strong central core but enabling offshoots. There are many offshoots of puppy and only time will tell which of those has the best overall structure and longevity. Or even which offshoots will not even be puppies at all. There is room for everything.

At least the debates here offer a kind of "trial by fire" that subjects each version to wideranging scrutiny.

I'm just thankful that the devs snd troubleshooters have vision and energy.

[ICPUG]

Iguleder is destined to be disappointed with Puppy!

The Puppy development method does not allow for infrastructure and gradual progression from one version/port to the next.

The Puppy development method is to:

- find a developer that wants to do a specific version.

- the developer then produces something while having as much fun as possible

Any suggestion about putting order into the development process is usually shouted down as not being fun (which is probably true).

I admire Iguleder's confidence in woof being the one true way and not looking at non-woof based puppies. He misses out on a lot of good ideas in my opinion.

If you want infrastructure then you need to be with a distro like Debian, Red Hat or SUSE.

Puppy development is chaotic. When a developer decides to build an ARM based Puppy it will be built. It probably will have tenuous links to any x86 Puppy but it will happen.

[jemimah]

Some people are architects and some are field engineers. The world needs both

Puppy needs both!

But what if the field engineers are actually designing without a blueprint, and the architects are designing as a goal and not as means to a high quality "product"?
What about if the two do not communicate or at least have common end goals?

The outcome will be (at best) an "one time good thing" that will stay within "a very little pond".
More often than not, not even that.

Yes it's absolutely true. There's nothing for it but to wait until the right people are at the same place at the same time.