On Sat, 2005-11-26 at 15:04 -0800, Michael Werner wrote:
> Hi Ken, Mark, et al.,
>
> I'm open to being gatekeeper for the SourceForge projet. In fact,
> not long ago, I created a SourceForge project for distributing
> PCP packages for various OSs (along with some other distributed
> computing tools). The first file release will happen in about a
> week, after I get the website polished up.
I appreciate your volunteering, my only concern is that the project
title is so broad that anyone looking for "PCP" or "Performance
Co-Pilot" or "performance monitoring tools" is unlikely to find the sf
project.
Things like pcpmon, pcpviewer (http://pcpview.sourceforge.net/) and
(soon) kmchart probably need to be either independent source forge
projects that share enough common keywords that they'll all be found, or
we need an umbrella project for PCP add-ons that points to all of the
know pieces outside oss.sgi.com.
>
> I've finished off the MacOS port, including the production of an
> installable package. Solaris packages will come shortly after the
> the website is done. Aix and HP packages will come a bit later.
Are you feeding these changes back to Mark? I'd hate for the core PCP
code to become forked.
> Also, I've recently spoken to Michal Kara, and he has granted me
> stewardship of the pcpmon sources, which will be made available
> from the sourceforge site. The port of pcpmon to the mac is
> complete, and will be included in the upcoming release.
Excellent, I was wondering where Michal had gone ... the copies of
pcpmon in the wild are quite old and I suspect a little feral.
> The sourceforge project name is "Multi-system ToolWorks"
> The sourceforge site is: http://sourceforge.net/projects/reliable
> The project web site is: http://reliable.sourceforge.net
>
> I'm currently working on a redesign of the project web site, to
> be completed for the first file release. I was planning to announce
> all this shortly, after it was ready for prime time, but the rest
> of you have already begun the conversation - so here you have it.
Thanks for the info, let's keep the discussion going.
|