perfparse-devel-int

[Perfparse-devel-int] header or footer for this list ?

[Yves M. <yme...@li...>]

Ben,

Could you edit the parameters for perfparse-devel-int and add some footer=
 or header
(what's the best ?)
That footer or header would say that this is our high traffic developer m=
ailing-list,
and that we put this list in CC when answering the users, in order to tel=
l the other
developers about a problem.
That footer or header would also say that users don't need to subscribe h=
ere if they
want to be informed and that we don't expect them to do so.

Besides this, we have perfparse-devel and we are not using it any more. I=
 suggest that
we use it in a similar way as perfparse-announce. An example is the best =
explanation of
my idea :

users : perfparse-users (high traffic) / perfparse-announce (low traffic)
devs  : perfparse-devel-int (high traffic) / perfparse-devel (low traffic=
)

No need to rename perfparse-devel as perfparse-devel-announce :)

What do you think ?

If you agree, my next mail to perfparse-devel will be that I will spend a=
 while on
reinstalling perparse here and then work on the CGI. Ben, when you start =
on the new
schema, post a mail too, with the place where you put your development re=
leases. If we
work the way we already talked about, the merge between the 2 branchs sho=
uld be very
easy :)


Yves

PS. CVS users : yes, I would love to use CVS too, but CVS is not an http =
protocol and
the firewall accepts only http :)
--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -

[Perfparse-devel-int] cvs access

[Flo G. <fl...@bi...>]

>
> PS. CVS users : yes, I would love to use CVS too, but CVS is not an http protocol and
> the firewall accepts only http :)

The https protocol is excellent to pierce firewalls. I found this:

http://wiki.tcl.tk/9411

It seems that sourceforge is running a ssh server SSH-1.99-OpenSSH_3.6.1p2 
on the https port. Just try http://cvs-ssh.sourceforge.net:443/ in your 
browser. If it works, there is a chance that you can pierce your firewall. 
But it may be possible that your firewall blocks the CONNECT 
somewhere HTTP/1.1 request. Note also that your network admin could get 
upset, and if you do something wrong there is a theoretical chance that 
someone that hacked cvs-ssh.sourceforge.net can see something in your 
internal net (If you accidently enable Port forwarding).

Stunnel (http://www.stunnel.org/) is also a excellent product to gain 
ssh-access to the cvs server via https.

Good luck :-)

Flo

Re: [Perfparse-devel-int] header or footer for this list ?

[Ben C. <BCl...@pe...>]

Yves Mettier wrote:

> Ben,
> 
> Could you edit the parameters for perfparse-devel-int and add some footer or header
> (what's the best ?)
> That footer or header would say that this is our high traffic developer mailing-list,
> and that we put this list in CC when answering the users, in order to tell the other
> developers about a problem.
> That footer or header would also say that users don't need to subscribe here if they
> want to be informed and that we don't expect them to do so.
> 
> Besides this, we have perfparse-devel and we are not using it any more. I suggest that
> we use it in a similar way as perfparse-announce. An example is the best explanation of
> my idea :
> 
> users : perfparse-users (high traffic) / perfparse-announce (low traffic)
> devs  : perfparse-devel-int (high traffic) / perfparse-devel (low traffic)
> 
> No need to rename perfparse-devel as perfparse-devel-announce :)

Can't do this.  Once created they are permanent.  I can 'hide' the old 
one and create another.  But rather not as this would loose the postings...

> 
> What do you think ?

The title and subscription options are easy to alter, I can have a look 
at this.  I have never changed the footer but am sure there must be a way.


> If you agree, my next mail to perfparse-devel will be that I will spend a while on
> reinstalling perparse here and then work on the CGI.

I agree, I'll change the title of the groups sometime today.

> Ben, when you start on the new
> schema, post a mail too, with the place where you put your development releases. If we
> work the way we already talked about, the merge between the 2 branchs should be very
> easy :)

This is for another email :)

Ben