[Perfparse-devel] Re: Working on PerfParse stuff...

[Ben C. <Be...@cl...>]

Garry, Yves,

At the moment, if we submit patches against a common version to my self, 
I'll keep them, add them and forward them on through the perfparse-devel 
news group.  Taking Yves lead on this, making a patch from the 
previously released version against your version, rather than against 
any increment.  And using the same news group to ensure we are not 
editing exactly the same code.  Lets see if it can work...

I like RCS, but not Internet friendly.  CVS might have to come one day 
when we have hundreds of developers, but since 66.6% of the developers 
currently have problems accessing CVS, it might have to wait :)

I am planning to install a Linux box on my home DMZ, as soon as I have 
built my home DMZ :)  Which we could use for direct ftp in combination 
with RCS, but that feels like that might be a bit complex....

Garry, did you have any luck with the JavaScript version of perfgraph, 
and prototyping using other CGI controls?

Whilst I am talking to you both,

In the previous version we had a name change of the installed programs. 
  'perfgraph.cgi' -> 'perfgraph' and 'perfchart.png' -> 'perfchart'. 
Which was probably a mistake on my part for not noticing it, and has 
annoyed several users who couldn't find the new files :)

In the next version I think we should go back to the original format, 
and I'll put a very clear comment (and apology from me) in the README :)

Yves, I've not yet had time to put groups in, but have planned the work. 
  I should think I'll have time tomorrow.

Right now there is an England soccer game I just can't miss :)

Regards to you both, Ben



Cook, Garry wrote:

>  >> I think that we should all join the pp-dev mailing list, if we haven't
>  >> done so already, and start posting there in case anyone else would
>  >> decide to lend a hand. I think that with the PP questions being posted
>  >> to the Nagios list, you'll probably see interest in the project start to
>  >> rise really quickly in the next few days/weeks, which should lead to
>  >> more offers for assistance. Therefore, CVS implentation might be a good
>  >> idea as well.
>  >
>  >I already talked with Ben about CVS: he does not have access to CVS. 
> Nether do I. How
>  >and who would do it frequently ?
>  >
>  >Yves
> Well, I don't really know that much about CVS, I've used an ?RCS? 
> repository on my box, with emacs, when working on some plugins. I do 
> this just to make sure that I don't have 10 different versions of a 
> single file, each with a different name that tries to be descriptive. I 
> figured that you guys would know more about CVS than I.
>  
> There is CVS access setup on the perfparse area of sourceforge.net. If 
> we were to use this, it would allow us to work on code simutaneously, 
> while not having to worry about diverging copies of files. Also, 
> it would allow users to test the code before the next release, and 
> provide us feedback before releasing.
>  
> Just a thought. If you guys don't want to use CVS, then we don't have 
> to. But if anyone else wishes to help with development, it may become 
> messy without it, especially if more than 1 or 2 people were to volunteer.
>  
> -g 
>