Re: [Openvpn-devel] Summary of the IRC meeting (19th Jan 2012)

2012-01-30 Thread Adriaan de Jong
> 
> PS I'm intending to go to FOSDEM on sunday; which room will you guys
> meet in?
> 

Good question... I'm heading to Brussels on Friday evening, and will head over 
to the beer event in Delerium Tremens as soon as I've settled in to my hotel 
room. Anyone else heading there?

Adriaan


Re: [Openvpn-devel] Summary of the IRC meeting (19th Jan 2012)

2012-01-25 Thread Jan Just Keijser

Hi all,


Samuli Seppänen wrote:

Hi,

Here's the summary of the previous IRC meeting / sprint.

  
I've been offline for a while but am slowly getting back online ; as for 
the chatlog attachment: Gert did ask me about bug #97 (dhcpnak storm) ; 
I have not been able to reproduce the DHCP NAK storm with the openvpn 
2.2.2. tap-win32 adapter , so I'm inclined to consider this bug solved. 
I hope someone else can also verify this (i.e. install 2.2.1, produce 
the DHCP NAK storm, then upgrade to 2.2.2. etc).


cheers,

JJK

PS I'm intending to go to FOSDEM on sunday; which room will you guys 
meet in?




---

COMMUNITY MEETING

Place: #openvpn-devel on irc.freenode.net
Date: Thursday 19th Jan 2012
Time: 18:00 UTC

Planned meeting topics for this meeting were on this page:



Next meeting will be announced in advance, but will probably be on the same
weekday and at the same time. Your local meeting time is easy to check
from services such as



or with

$ date -u


SUMMARY

cron2, dazo, ecrist and mattock participated in this meeting.

--

Discussed Bruessels/FOSDEM hackfests. Agreed that arranging them on
Sat-Sun (4.-5. Feb) makes most sense for all. The goal is to complete
three related mini-projects:

1) The "squash/close as many bugs as possible"
2) Complete all tasks holding back 2.3 alpha and make the release
3) Review d12fk's Windows patches that got stuck to the patch queue

All of these should be doable within the given timeframe.

--

Discussed vBulletin's OpenVPN theme. According to raidz, the theme
should be ready next Monday.

---

Full chatlog as an attachment