From: Samuli S. <sa...@op...> - 2011-01-20 17:16:06
|
Hi, Here's the summary of the previous community meeting. --- COMMUNITY MEETING Place: #openvpn-devel on irc.freenode.net Date: Thursday, 13th Jan 2011 Time: 18:00 UTC Planned meeting topics for this meeting were on this page: <https://community.openvpn.net/openvpn/wiki/Topics-2011-01-13> 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 <http://www.timeanddate.com/world clock> or with $ date -u SUMMARY dazo, ecrist, jamesyonan, krzee, mattock, psha and trispace were present in this meeting. -- Discussed integration of "Coverity" code analysis tool into Buildbot. Mattock will take care of this now that he has the necessary credentials. -- Discussed the latest plugin V3 API patch: <http://thread.gmane.org/gmane.network.openvpn.devel/4255> Jamesyonan gave this patch an ACK, which means that the entire plugin v3 API patchset can be now be merged into Git. -- Discussed the "Use \r\n as newline in log files on Windows" patch: <http://thread.gmane.org/gmane.network.openvpn.devel/4274> Although it seems Notepad is the only text editor that does not support UNIX linefeeds, it is also the default editor on Windows: agreed that this patch makes sense. Jamesyonan gave this patch an ACK. -- Discussed the "Multicast over TAP w/ OpenVPN" issue: <https://forums.openvpn.net/post9180.html#p9180> <http://openvpn.net/archive/openvpn-devel/2004-04/msg00032.html> Mattock promised to create a new feature request to Trac, and did: <https://community.openvpn.net/openvpn/ticket/79> -- Discussed the "OpenVPN to filter DHCP requests in bridge mode" patch: <https://forums.openvpn.net/topic7479.html> Noted that the same effect can be achieved with tools such as ebtables. Also, the scope of the patch was too specific (DHCP only), so decided to give the patch a NACK. -- Discussed the "OpenVPN documentation (man page) review" project: <http://thread.gmane.org/gmane.network.openvpn.devel/4354> Agreed that whenever a patch changes functionality, it should be accompanied with update to documentation (e.g. man-page) to avoid undocumented features. So far this has not been mandatory. Participants of the meeting were divided on which tools to use for documentation writing. The (Trac) Wiki has a number of benefits, especially when trying to get contributions from non-developers: - built-in versioning - no need to learn developer tools or processes - relative ease of use The Wiki documentation will of course require editing to stay coherent. Also, to simplify things, content would have to be edited in Wiki only, and only moved to the Git repository periodically. Other approaches were suggested also: - man page in Git, the rest in Wiki (hybrid approach) - everything in Git repo As the goal of the man-page review project is to get more non-developers involved in the documentation effort it was decided to start using the Wiki as main documentation repository. If this does not result in more non-developer contributions, we can reconsider our approach. --- Full chatlog as an attachment -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock |