Re: [Openvpn-devel] Summary of the IRC meeting (9th June 2011)

2011-06-14 Thread Jan Just Keijser 
Hi *,


> Discussed the possibility of arranging a "real" face-to-face meeting
> between the company and community people, for example in New York. Costs
> are an issue, but this might happen eventually.
JM2CW: I think this would be a *very* good thing , for both the openvpn
community developers as well as for the people working for 'openvpn
inc'.  Let me know if I can help.

cheers,

JJK



Samuli Seppänen wrote:
> Hi,
>
> Here's the summary of the previous community meeting.
>
> ---
>
> COMMUNITY MEETING
>
> Place: #openvpn-devel on irc.freenode.net
> Date: Thursday, 9th June 2011
> Time: 18:00 UTC
>
> Planned meeting topics for this meeting were on this page:
>
> 
>
> Next meeting will be announced in advance, but will 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 were present in this meeting.
>
> --
>
> Discussed branching out beta/2.3. There are a few patches that are
> required first:
>
> * PolarSSL and Doxygen patches from andj
> * Visual Studio 2008 build fixes now in "winbuildtmp" branch
> * Cron2 needs to make "tap" work with "push route-ipv6"
> * https://community.openvpn.net/openvpn/ticket/128 (if reproducible)
> * https://community.openvpn.net/openvpn/ticket/140
> * https://community.openvpn.net/openvpn/ticket/125
> * Some open tickets from 2.2.0
>
> --
>
> Discussed 2.2.0 release. Will try to get it out in two weeks. There's at
> least a few patches missing:
>
> * James segfault fix from SVN (left out from 2.2.0)
> * https://community.openvpn.net/openvpn/ticket/125
>
> --
>
> Discussed the possibility of placing non-invasive ads to OpenVPN Windows
> installers, e.g. links to commercials product in Start menu or to the
> README file. Idea met with lukewarm response, because the community has
> effectively ran the project for the last ~18 months. The fact that
> OpenVPN (OSS) is hard to find from all commercial content in openvpn.net
> also raised critique.
>
> For the above reasons agreed that splitting openvpn.net (commercial
> site) and openvpn.org (community site) would make sense. Both sites
> would be linked together tightly. Agreed that having a joint community /
> company meeting focusing on this issue makes sense. At least Samuli,
> Francis and James would need to attend (from the company) along with
> most active  community members.
>
> Also agreed that the company needs to mentally "let openvpn go" and
> focus on working with the project and build products on top of it
> like everyone else. If a fork ever happened, getting distributors (*NIX
> distros) and later users to migrate to it should not pose a big problem.
> OpenOffice.org/LibreOffice is a good analogy: most/all major *NIX
> distros migrated to LibreOffice in their first post-fork release.
>
> --
>
> Discussed the possibility of arranging a "real" face-to-face meeting
> between the company and community people, for example in New York. Costs
> are an issue, but this might happen eventually.
>
> --
>
> Discussed the problem with Access Server's OpenVPN version, which is
> effectively a fork (based on 2,1 release). This means AS is atm lacking
> features which OpenVPN has. This divergence has already caused some
> nasty merge conflicts.
>
> --
>
> Discussed Russell's questions posted to the mailinglist:
>
> 
>
> Management interface does come up before connection, but it's only used
> for passing the username and password to OpenVPN daemon.
>
> Adding more granular exit codes to OpenVPN would be possible, but it
> would not be trivial without a (needed) overhaul of err.[ch].
>
> ---
>
> Full chatlog as an attachment
>
>   
> 
>
> --
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> 
>
> ___
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel

[Openvpn-devel] Summary of the IRC meeting (9th June 2011)

2011-06-10 Thread Samuli Seppänen 
Hi,

Here's the summary of the previous community meeting.

---

COMMUNITY MEETING

Place: #openvpn-devel on irc.freenode.net
List-Post: openvpn-devel@lists.sourceforge.net
Date: Thursday, 9th June 2011
Time: 18:00 UTC

Planned meeting topics for this meeting were on this page:



Next meeting will be announced in advance, but will 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 were present in this meeting.

--

Discussed branching out beta/2.3. There are a few patches that are
required first:

* PolarSSL and Doxygen patches from andj
* Visual Studio 2008 build fixes now in "winbuildtmp" branch
* Cron2 needs to make "tap" work with "push route-ipv6"
* https://community.openvpn.net/openvpn/ticket/128 (if reproducible)
* https://community.openvpn.net/openvpn/ticket/140
* https://community.openvpn.net/openvpn/ticket/125
* Some open tickets from 2.2.0

--

Discussed 2.2.0 release. Will try to get it out in two weeks. There's at
least a few patches missing:

* James segfault fix from SVN (left out from 2.2.0)
* https://community.openvpn.net/openvpn/ticket/125

--

Discussed the possibility of placing non-invasive ads to OpenVPN Windows
installers, e.g. links to commercials product in Start menu or to the
README file. Idea met with lukewarm response, because the community has
effectively ran the project for the last ~18 months. The fact that
OpenVPN (OSS) is hard to find from all commercial content in openvpn.net
also raised critique.

For the above reasons agreed that splitting openvpn.net (commercial
site) and openvpn.org (community site) would make sense. Both sites
would be linked together tightly. Agreed that having a joint community /
company meeting focusing on this issue makes sense. At least Samuli,
Francis and James would need to attend (from the company) along with
most active  community members.

Also agreed that the company needs to mentally "let openvpn go" and
focus on working with the project and build products on top of it
like everyone else. If a fork ever happened, getting distributors (*NIX
distros) and later users to migrate to it should not pose a big problem.
OpenOffice.org/LibreOffice is a good analogy: most/all major *NIX
distros migrated to LibreOffice in their first post-fork release.

--

Discussed the possibility of arranging a "real" face-to-face meeting
between the company and community people, for example in New York. Costs
are an issue, but this might happen eventually.

--

Discussed the problem with Access Server's OpenVPN version, which is
effectively a fork (based on 2,1 release). This means AS is atm lacking
features which OpenVPN has. This divergence has already caused some
nasty merge conflicts.

--

Discussed Russell's questions posted to the mailinglist:



Management interface does come up before connection, but it's only used
for passing the username and password to OpenVPN daemon.

Adding more granular exit codes to OpenVPN would be possible, but it
would not be trivial without a (needed) overhaul of err.[ch].

---

Full chatlog as an attachment

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock
cron2 21:01:19
meeting
let's go about it and be quick, I'm up since 04:30 and it's now 20:00 over here 
- and I'm tired 21:01:34
 
dazo 21:03:54

agreed 21:04:01
 
mattock 21:04:22
meeting time
https://community.openvpn.net/openvpn/wiki/Topics-2011-06-09 21:05:23
 
vpnHelper 21:05:24
Title: Topics-2011-06-09 – OpenVPN Community (at community.openvpn.net)   

mattock 21:05:32
2.2.1 patch queue?
what's missing? 21:05:34
dazo? 21:06:06
 
dazo 21:06:08
tbh, I don't know   

cron2 21:06:09
dazo?   

mattock 21:06:37
are the VS2008 build fixes already in "master"? 

dazo 21:06:38
I remember having merged in quite some patches ...
most of them, yes ... I think there was some more cleanup from jjo which I'm 
not sure of 21:06:56
 
mattock 21:07:10
we can take a look later
I think we should set a release date today 21:07:29
 
dazo 21:07:36
sure can do!

cron2 21:08:30
dazo: did you merge to master? I thought it's all in the winbuild-test branch?  

mattock 21:08:34
it's been nearly 6 weeks since 2.2.0... is next Friday (not tomorrow) doable?   

cron2 21:08:38
haven't seen any mails otherwise

dazo 21:08:40
but lets also agree on what we want to have cleaned up ... in the moment we 
branch out the beta/2.3 branch, I'd say we should have agreed on all new 
additional features
I'm waiting for andj to come up with the PolarSSL and doxygen patches, which we 
want into 2.3 21:09:14
that's the only "missing" pieces 21:09:24
 
mattock 21:09:39
have we seen any pieces yet?

dazo 21:09:40
there are also quite a few Trac tickets to look at as well