Hi Frank,
----- Original Message -----
> > ...
> I'll stew on this over the weekend, and attempt to come up with some
> possible directions forward for us here, seeking compromise. It feels
> a bit like we're going in circles by email here now, and we need a new
> tack as we're stale-mated on each others needs/concerns.
As discussed on IRC earlier this week, I'm uncomfortable continuing to
release this as-is, as part of a default install. I'm also not going
to (would never) simply jump in and start taking a big red pen to the
configuration/code in an area you're passionate about like this.
So, I think the best way forward will be to create a new pcp-manager
sub-package within PCP, optionally installed, with the defaults as you
like 'em for now. This'll give us more time to continue to assess and
evolve, hopefully toward the safer, more efficient and environmentally
friendly solution that I prefer. ;)
After a few more releases, if the three of us still cannot find common
ground, we have an option then of making a separate project out of the
pcp-manager code and having two source trees respectfully go on their
separate ways. Maybe not holding hands, walking into the sunset - but
at least they might still be pen-pals.
This also provides scope to flag this package as containing a much more
aggressive schedule for enabling new/experimental features (different
to the cast-in-stone must-be-100%-backward-compatible mantra we attempt
to carry off for the rest of PCP).
Appreciate the doc updates in the fche/dev branch too - naturally, they
don't quite give the punter as much warning as I feel they should, but
its a good start - thanks!
cheers.
--
Nathan
|