-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Noyes wrote:
| On Wed, 2005-05-18 at 12:28, Cristian Rodriguez wrote:
|> 2005/5/18, Tom Eastep <[EMAIL PROTECTED]>:
|> > I've attached the simple scripts that I use to publish to Sourceforge
|> > and to my own server (shorewall.net AKA lists.shorew
Paul Gear wrote:
> Cristian Rodriguez wrote:
>>...
>>My ideas are the following:
>>
>>1. Declare Shorewall "alive but feature frozen",only bug fixes, until
>>we can organize and get the needed coders,especially some good bash
>>coders and an iptables geek (¿anyone?)
>>
>>2.I can take care of a mir
On Wed, 2005-05-18 at 12:28, Cristian Rodriguez wrote:
> 2005/5/18, Tom Eastep <[EMAIL PROTECTED]>:
> > I've attached the simple scripts that I use to publish to Sourceforge
> > and to my own server (shorewall.net AKA lists.shorewall.net AKA
> > cvs.shorewall.net AKA rsync.shorewall.net).
> >
> ht
Mike Noyes wrote:
> Do you pull or push with rsync? SF doesn't offer public rsync hosting.
> Only project members with shell access can rsync to/from the shell.
Currently, all of the mirrors pull from rsync.shorewall.net.
>
> I use a script on SF to xslt docbook xml to html. It's not great, but
On Wed, 2005-05-18 at 11:57, Tom Eastep wrote:
> Cristian Rodriguez wrote:
> Possibly Mike Noyes can help you with coming up with a new arrangement;
> he has offered to help with things at the Sourceforge end. I'm uncertain
> how to set up a publishing scheme based at Sourceforge that can keep the
Cristian Rodriguez wrote:
> 2005/5/18, Tom Eastep <[EMAIL PROTECTED]>:
>
>
>>>- We need to look at the big issues and make sure we've got a good
>>>handle on them. For me, these include (in rough order of priority from
>>>my perspective):
>>>* Multiple ISPs & load balancing
>>>* Features to enab
