headers
Julian Mehnle | 21 Feb 23:17

The next meeting after 2007-02-17


Hi all,

I don't think we urgently need to have a meeting this week, and as a matter 
of fact I won't be able to make a meeting on this Saturday in any case.  
However if you want to meet this week-end anyway, don't hesitate to go 
ahead.  Otherwise, I'd say we meet again on 2007-03-03.

For the record, these are discussion items I currently have on my list:

  * How public should the "draft-otis-spf-dos-exploit Analysis" page
    <http://www.openspf.org/draft-otis-spf-dos-exploit_Analysis> be?
    (Wayne/Julian)
  * Conclusions on the DDoS issue
  * Conclusions on the project's involvement in the BITS proceedings
  * Control over the openspf.* name service? (Wayne)
  * Compliance logo license terms?
  * Have a directory of commercial consulting services on the SPF website?
  * The contact form support effort
      * Report: status of the support team?
      * Change modus operandi of RT support team and/or the RT instal-
        lation?
      * Broaden scope of the contact form team/issue-tracker?
  * Ideas for getting better access to SPF deployment statistics in the
    future
Permalink | Reply |
headers
Alex van den Bogaerdt | 22 Feb 04:27

Re: The next meeting after 2007-02-17

On Wed, Feb 21, 2007 at 10:20:08PM +0000, Julian Mehnle wrote:

> I don't think we urgently need to have a meeting this week, and as a matter 
> of fact I won't be able to make a meeting on this Saturday in any case.  
> However if you want to meet this week-end anyway, don't hesitate to go 
> ahead.  Otherwise, I'd say we meet again on 2007-03-03.

IMHO 3/3 is fine.  Every other week is probably fine in general.

>   * The contact form support effort
>       * Report: status of the support team?
>       * Change modus operandi of RT support team and/or the RT instal-
>         lation?
>       * Broaden scope of the contact form team/issue-tracker?

I suggest that if we would invite Koen, these items would be put first
on the agenda. No need for him to sit the entire session and not get
to talk again.

cheers
Alex

-------------------------------------------
Powered by Listbox: http://www.listbox.com
Permalink | Reply |
headers
Alex van den Bogaerdt | 23 Feb 19:30

Re: The next meeting after 2007-02-17

On Thu, Feb 22, 2007 at 04:27:17AM +0100, Alex van den Bogaerdt wrote:
> On Wed, Feb 21, 2007 at 10:20:08PM +0000, Julian Mehnle wrote:
> 
> > [snip: not available, suggest 3/3 as next meeting]
> [me too]

I have not seen more replies to this. I'm going to assume
everybody is fine with skipping next Saturday.

regards
Alex

-------------------------------------------
Powered by Listbox: http://www.listbox.com
Permalink | Reply |
headers
Julian Mehnle | 2 Mar 01:00

Re: The next meeting after 2007-02-17


Hi all,

does anyone have a problem with meeting coming Saturday 2007-03-03 at 16:00 
UTC?

If not, I propose the following agenda:

 1. Conclusions on the DDoS issue

 2. How public should the "draft-otis-spf-dos-exploit Analysis" page
    <http://www.openspf.org/draft-otis-spf-dos-exploit_Analysis> be?
    (Wayne/Julian)

 3. Conclusions on the project's involvement in the BITS proceedings

 4. Have a directory of commercial consulting services on the SPF
    website?
Permalink | Reply |
headers
Scott Kitterman | 2 Mar 01:03

Re: Re: The next meeting after 2007-02-17

On Fri, 2 Mar 2007 00:00:24 +0000 Julian Mehnle <julian <at> mehnle.net> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi all,
>
>does anyone have a problem with meeting coming Saturday 2007-03-03 at 
16:00 
>UTC?
>
>If not, I propose the following agenda:
>
> 1. Conclusions on the DDoS issue
>
> 2. How public should the "draft-otis-spf-dos-exploit Analysis" page
>    <http://www.openspf.org/draft-otis-spf-dos-exploit_Analysis> be?
>    (Wayne/Julian)
>
> 3. Conclusions on the project's involvement in the BITS proceedings
>
> 4. Have a directory of commercial consulting services on the SPF
>    website?
>
Sounds good to me.

Scott K

-------------------------------------------
Powered by Listbox: http://www.listbox.com
(Continue reading)

Permalink | Reply |

Gmane