Skip to contentSkip to conversation

v2, add PR template in order to simplify new developers cooperate properly if they open PR. discussed here: https://sourceforge.net/p/openvpn/mailman/message/35601310/

PATCH In review Ilya Shipitsin 5 participants 12 messages Feb 6, 2017 – Feb 7, 2017

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 v2, add PR template in order to simplify new developers cooperate properly if they open PR. discussed here: https://sourceforge.net/p/openvpn/mailman/message/35601310/

v2: @mattock has changed links and provided an example of "git send-email"

---
 .github/PULL_REQUEST_TEMPLATE.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 .github/PULL_REQUEST_TEMPLATE.md
.github/PULL_REQUEST_TEMPLATE.md new file +15 -0
new file mode 100644
index 0000000..a8653d8
@@ -0,0 +1,15 @@
+# Thank you for your contribution
+
+You are welcome to open PR, but they are used for discussion only. All
+patches must eventually go to the openvpn-devel mailing list for review:
+
+* https://lists.sourceforge.net/lists/listinfo/openvpn-devel
+
+Please send your patch using [git-send-email](https://git-scm.com/docs/git-send-email). For example to send your latest commit to the list:
+
+    $ git send-email [email protected] HEAD~1
+
+For details, see these Wiki articles:
+
+* https://community.openvpn.net/openvpn/wiki/Contributing
+* https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation
Signature · 1 line
2.5.5
#1 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have ACKed and applied this, just to get this one resolved. But I am very disappointed that you have yet again completely ignored the guidelines described in the URL[1] already provided to you - which describes how a patch and commit message should look like.

In fact - your SUBJECT line was 167 characters long, _including_ a URL. It did not even have a proper body message. *sigh*

You really need to stop wasting our [2] time and really read and truly learn what you read in a far better ways. If you do not change your behaviour here, the result will be that we will not put much efforts into your contributions in the future - unless we have a lot of time available, which, honestly, is not very happening often.

Just ask yourself: If you care so little to play by our guidelines, why should we care about your patches?

[1] <http://chris.beams.io/posts/git-commit/>
[2] our ==> primarily developers and reviewers

Regardless, your patch has been applied to the master branch

commit 9e849c1e00a88abed65760ac7bee3df4aed2b754

Author: Ilya Shipitsin
Date:   Mon Feb 6 11:55:15 2017 +0500
     github: Add PR template with contributor related information

     Acked-by: David Sommerseth <[email protected]...>
     Message-Id: <[email protected]...>
     URL: https://www.mail-archive.com/[email protected]/msg14010.html
     Signed-off-by: David Sommerseth <[email protected]...>

- --
kind regards,

David Sommerseth

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJYmFN/AAoJEIbPlEyWcf3yQoUP+wSNXtlDXyXgsGQpwoaPkuic u9wrjwtAxdizLXgtfNV0hY5ouoV9gEEA0L0UY+UmCi1Dk4cgGQq1uDyxDTytyW3q k6ilwzf8dCsa2KnWnJgF7ZTVmq8xn/XKj8FYJcNVI3sT9fWE+xUsJUHzINQmRVKc q9SrKC3BrCDJX6+pgQqMXwXE/i5iwBy+wAYILVQnQ936nOap0EsJFiI7pOqADNrf 6JlTzRJm1N+0sF54dX9eek27s4CuUDR+XMwO3DLp+qA3oCQfldFhwWz99aUR0DM4 wloW0B3IRvcQAUWgIU3dDrMt78AzMZxd+BbPpCvKq6V6Msbk0AoUiQ+PduYEJ1bn 270iGhfL8mcMscGo7H/W2tHeZOpCzODlvflCEa83oFEiVYYltaIfxLpnoDiZ0gWy J4jCD4fqE5gcC3J7GkcpTtuSv+eYpjvNT8vsNSVaMHjrPESgfDWx1RYc2sqwbmCP uBcHWjBqJb8Fkq8r9cGc36+kAdfo3ljfPKSM+dtQxse/8U8xSMoMTjDpSAnJ8w2p s8gWU2rvB06gijBHxC4Bt9G3BXEPhRU4GKwP0Vnf8IGCVgXMyKf8nZZzWWs7/BAk ZzgXTfggHZLcuV9CxxpCLLDSe2NXk5Vapz+Y1AVh/bE+oRDooevxLzrLhnrdbFwQ FIXn7HqzCwJoxW7xP08c
=IYjw
-----END PGP SIGNATURE-----

#2 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

2017-02-06 15:44 GMT+05:00 David Sommerseth <[email protected]...>:

Quoted 10 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have ACKed and applied this, just to get this one resolved. But I am very
disappointed that you have yet again completely ignored the guidelines described in the URL[1] already provided to you - which describes how a patch
and commit message should look like.

what I have learned is --annotate switch and, as you can see, now subject contains "v2", so it is easy to distingush this patch and earlier edition.

Quoted 4 lines

In fact - your SUBJECT line was 167 characters long, _including_ a URL. It did not even have a proper body message. *sigh*

it is the same as previous version of this patch, which I sent before your guidelines, and you did not complain earlier.
it is not clear, how 167 chars long might be bad or good. for me it is just 167 chars.

if it is really bad, we might involve some automatic to submission process, which will check how long is string.
@mattock ?

it is not trivial to be sure that it will fit your expectation. as an example, there are automatic tests. and you are ok with that. you do not being tedious "guys, I told you many times, write code without bugs... why you are ignoring me..."

we should not assign machine job to a man, just involve some automation which will tell "your commit message is too long" without involving your time.

Quoted 55 lines

You really need to stop wasting our [2] time and really read and truly learn
what you read in a far better ways. If you do not change your behaviour here,
the result will be that we will not put much efforts into your contributions
in the future - unless we have a lot of time available, which, honestly, is not very happening often.

Just ask yourself: If you care so little to play by our guidelines, why should we care about your patches?

[1] <http://chris.beams.io/posts/git-commit/>
[2] our ==> primarily developers and reviewers

Regardless, your patch has been applied to the master branch

commit 9e849c1e00a88abed65760ac7bee3df4aed2b754

Author: Ilya Shipitsin
Date:   Mon Feb 6 11:55:15 2017 +0500
     github: Add PR template with contributor related information

     Acked-by: David Sommerseth <[email protected]...>
     Message-Id: <[email protected]...>
     URL: https://www.mail-archive.com/[email protected]...
sourceforge.net/msg14010.html
     Signed-off-by: David Sommerseth <[email protected]...>

- --
kind regards,

David Sommerseth

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJYmFN/AAoJEIbPlEyWcf3yQoUP+wSNXtlDXyXgsGQpwoaPkuic u9wrjwtAxdizLXgtfNV0hY5ouoV9gEEA0L0UY+UmCi1Dk4cgGQq1uDyxDTytyW3q k6ilwzf8dCsa2KnWnJgF7ZTVmq8xn/XKj8FYJcNVI3sT9fWE+xUsJUHzINQmRVKc q9SrKC3BrCDJX6+pgQqMXwXE/i5iwBy+wAYILVQnQ936nOap0EsJFiI7pOqADNrf 6JlTzRJm1N+0sF54dX9eek27s4CuUDR+XMwO3DLp+qA3oCQfldFhwWz99aUR0DM4 wloW0B3IRvcQAUWgIU3dDrMt78AzMZxd+BbPpCvKq6V6Msbk0AoUiQ+PduYEJ1bn 270iGhfL8mcMscGo7H/W2tHeZOpCzODlvflCEa83oFEiVYYltaIfxLpnoDiZ0gWy J4jCD4fqE5gcC3J7GkcpTtuSv+eYpjvNT8vsNSVaMHjrPESgfDWx1RYc2sqwbmCP uBcHWjBqJb8Fkq8r9cGc36+kAdfo3ljfPKSM+dtQxse/8U8xSMoMTjDpSAnJ8w2p s8gWU2rvB06gijBHxC4Bt9G3BXEPhRU4GKwP0Vnf8IGCVgXMyKf8nZZzWWs7/BAk ZzgXTfggHZLcuV9CxxpCLLDSe2NXk5Vapz+Y1AVh/bE+oRDooevxLzrLhnrdbFwQ FIXn7HqzCwJoxW7xP08c
=IYjw
-----END PGP SIGNATURE-----

#3 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

Quoted 5 lines · Илья Шипицин

it is the same as previous version of this patch, which I sent before your guidelines, and you did not complain earlier.
it is not clear, how 167 chars long might be bad or good. for me it is just 167 chars.

You do understand and realize you just prove my earlier points and make them really obvious? ... you seem not to read and learn ... from the same URL [1] already provided several times now:

The seven rules of a great Git commit message
---------------------------------------------

1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line
6. Wrap the body at 72 characters
7. Use the body to explain what and why vs. how

[1] <http://chris.beams.io/posts/git-commit/#seven-rules>

As a clever person once said: "I can only provide the information, I cannot make you understand it".

Quoted 2 lines

it is not trivial to be sure that it will fit your expectation. as an example, there are automatic tests. and you are ok with that.

First ... *read* URL[1], *read* the 7 guidelines above.

Code itself can be automated tested. But the syntax of the code needs to be correct to be possible to test it. From my point of view, making an analogy: You break the syntax. It doesn't compile. Which means the result isn't testable.

Quoted 3 lines

we should not assign machine job to a man, just involve some automation which will tell "your commit message is too long" without involving your time.

Those seven rules are not that far away from the coding style guidelines we all are being picked at from time to time (*including* myself).

It is first and foremost the submitters responsibility to ensure that everything is in order before doing the submission. And we have both on-list, off-list and IRC requests from time to time, where people ask what kind of guidelines we use, where to find them and so on. This is a pretty common behaviour by most community contributors, not even remotely unique to OpenVPN. What you want is a way to not take proper ownership of your contribution, moving the responsibility out of your area.

Sorry, this is not going to happen.

And I don't think I will even have much to say for the future in this regards.

Signature · 4 lines
kind regards,

David Sommerseth
OpenVPN Technologies, Inc
#4 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

In reply to David Sommerseth
Quoted 10 lines · David Sommerseth

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have ACKed and applied this, just to get this one resolved. But I am very disappointed that you have yet again completely ignored the guidelines described in the URL[1] already provided to you - which describes how a patch and commit message should look like.

In fact - your SUBJECT line was 167 characters long, _including_ a URL. It did not even have a proper body message. *sigh*

The 80 character limit is only documented here:

<https://community.openvpn.net/openvpn/wiki/CodeStyle>

This is a fairly new page and not linked to from anywhere. On top of that the page says that "This coding style is not final and not yet in effect."

Moreover, our developer documentation is quite a mess right now:

<https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation>
<https://community.openvpn.net/openvpn/wiki/Contributing>

For example, the DeveloperDocumentation page links to here:

<https://community.openvpn.net/openvpn/wiki/CodingConventions>

That page is a stub with very little and possibly outdated/false information. Then we have

<https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation#Formatting>

which says we use "GNU coding style". And then we have the actual 2.4 code style instructions here:

<https://community.openvpn.net/openvpn/wiki/CodeStyle>

There is a fairly well-hidden link on the DeveloperDocumentation page to these Git commit message instructions:

<http://who-t.blogspot.com/2009/12/on-commit-messages.html>

I think that blog posting is too verbose. The essential information, such as the "seven rules" you linked to should be directly on the DeveloperDocumentation page, with links to the original documents.

I don't want to argue whether Ilya should know the 80 character limit or not. But how can we expect _new_ developers to get our rules if they are not documented properly or if documentation is contradictory? Or if the documentation is hidden as well as the CodeStyle page?

I will create a copy of the DeveloperDocumentation page and clean that one up. Then I will send a link so that others can have a look.

Signature · 5 lines
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock
#5 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

Quoted 9 lines · Samuli Seppänen
Quoted 8 lines · David Sommerseth

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have ACKed and applied this, just to get this one resolved. But I am very disappointed that you have yet again completely ignored the guidelines described in the URL[1] already provided to you - which describes how a patch and commit message should look like.

Quoted 7 lines
Quoted 2 lines

In fact - your SUBJECT line was 167 characters long, _including_ a URL. It did not even have a proper body message. *sigh*

The 80 character limit is only documented here:

<https://community.openvpn.net/openvpn/wiki/CodeStyle>

Actually, that was just the line length for _code_, not for commit messages. So the only indirect guideline for Git commit message line length was

"The maximum length of the line differs between projects, it's usually somewhere between 50 and 78 characters"

which was on this page:

<http://who-t.blogspot.fi/2009/12/on-commit-messages.html>

The "seven rules" URL David linked to says the following:

* Limit the subject line to 50 characters
* Wrap the body at 72 characters

I can't recall us ever agreeing to such limits.

Let's agree on what we want and then document it properly.

Signature · 5 lines
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock
Quoted 40 lines

This is a fairly new page and not linked to from anywhere. On top of that the page says that "This coding style is not final and not yet in effect."

Moreover, our developer documentation is quite a mess right now:

<https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation>
<https://community.openvpn.net/openvpn/wiki/Contributing>

For example, the DeveloperDocumentation page links to here:

<https://community.openvpn.net/openvpn/wiki/CodingConventions>

That page is a stub with very little and possibly outdated/false information. Then we have

<https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation#Formatting>

which says we use "GNU coding style". And then we have the actual 2.4 code style instructions here:

<https://community.openvpn.net/openvpn/wiki/CodeStyle>

There is a fairly well-hidden link on the DeveloperDocumentation page to these Git commit message instructions:

<http://who-t.blogspot.com/2009/12/on-commit-messages.html>

I think that blog posting is too verbose. The essential information, such as the "seven rules" you linked to should be directly on the DeveloperDocumentation page, with links to the original documents.

I don't want to argue whether Ilya should know the 80 character limit or not. But how can we expect _new_ developers to get our rules if they are not documented properly or if documentation is contradictory? Or if the documentation is hidden as well as the CodeStyle page?

I will create a copy of the DeveloperDocumentation page and clean that one up. Then I will send a link so that others can have a look.

#6 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

2017-02-07 15:09 GMT+05:00 Samuli Seppänen <[email protected]...>:

Quoted 31 lines · Samuli Seppänen
Quoted 13 lines · David Sommerseth
Quoted 11 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have ACKed and applied this, just to get this one resolved. But I am very
disappointed that you have yet again completely ignored the guidelines described in the URL[1] already provided to you - which describes how a patch
and commit message should look like.

Quoted 10 lines
Quoted 4 lines

In fact - your SUBJECT line was 167 characters long, _including_ a URL. It
did not even have a proper body message. *sigh*

The 80 character limit is only documented here:

<https://community.openvpn.net/openvpn/wiki/CodeStyle>

Actually, that was just the line length for _code_, not for commit messages. So the only indirect guideline for Git commit message line length was

"The maximum length of the line differs between projects, it's usually somewhere between 50 and 78 characters"

Quoted 9 lines

which was on this page:

<http://who-t.blogspot.fi/2009/12/on-commit-messages.html>

The "seven rules" URL David linked to says the following:

* Limit the subject line to 50 characters
* Wrap the body at 72 characters

as I am somehow related to this topic...
well, I did not mean to annoy David in purpose, it happened accidently (as I already said).

as for compliance check, it will always annoy people if it is something written somewhere. people will forget to have a look at it. can we involve something like that

https://github.com/openresty/lua-nginx-module/blob/master/.travis.yml#L61-L62
?

and other checks we agreed upon

Quoted 57 lines

I can't recall us ever agreeing to such limits.

Let's agree on what we want and then document it properly.

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

irc freenode net: mattock

This is a fairly new page and not linked to from anywhere. On top of

Quoted 41 lines

that the page says that "This coding style is not final and not yet in effect."

Moreover, our developer documentation is quite a mess right now:

<https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation>
<https://community.openvpn.net/openvpn/wiki/Contributing>

For example, the DeveloperDocumentation page links to here:

<https://community.openvpn.net/openvpn/wiki/CodingConventions>

That page is a stub with very little and possibly outdated/false information. Then we have

<https://community.openvpn.net/openvpn/wiki/DeveloperDocumen
tation#Formatting>

which says we use "GNU coding style". And then we have the actual 2.4 code style instructions here:

<https://community.openvpn.net/openvpn/wiki/CodeStyle>

There is a fairly well-hidden link on the DeveloperDocumentation page to these Git commit message instructions:

<http://who-t.blogspot.com/2009/12/on-commit-messages.html>

I think that blog posting is too verbose. The essential information, such as the "seven rules" you linked to should be directly on the DeveloperDocumentation page, with links to the original documents.

I don't want to argue whether Ilya should know the 80 character limit or not. But how can we expect _new_ developers to get our rules if they are not documented properly or if documentation is contradictory? Or if the documentation is hidden as well as the CodeStyle page?

I will create a copy of the DeveloperDocumentation page and clean that one up. Then I will send a link so that others can have a look.

#7 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

Quoted 6 lines · Илья Шипицин

as for compliance check, it will always annoy people if it is something written somewhere. people will forget to have a look at it. can we involve something like that

https://github.com/openresty/lua-nginx-module/blob/master/.travis.yml#L61-L62
?

That check is to test the *code*. It does not apply to this discussion at all, as we are here primarily discussing commit messages. And such a checks makes no sense on commit messages. Some times it is needed to exceed 80 characters, as log lines are quoted to explain what happened and give reasons for why the patch is needed.

For quality checks, for both code and commit messages, good developers usually tries to ensure everything is set and in order *before* submitting a patch. Heck, most I know even tries to ensure that things are proper before doing the local commit. Many calls this process the "personal hygiene step". It's a fairly good description of the importance of doing so.

Signature · 4 lines
kind regards,

David Sommerseth
OpenVPN Technologies, Inc
#8 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

2017-02-07 18:11 GMT+05:00 David Sommerseth <
[email protected]...>:

Quoted 11 lines · Илья Шипицин
Quoted 5 lines

as for compliance check, it will always annoy people if it is something written somewhere. people will forget to have a look at it. can we involve something like that

https://github.com/openresty/lua-nginx-module/blob/master/.

travis.yml#L61-L62

Quoted 1 line

?

That check is to test the *code*. It does not apply to this discussion

I know, it is an example.

similar check might be applied to "git log" output.

Quoted 21 lines

at all, as we are here primarily discussing commit messages. And such a checks makes no sense on commit messages. Some times it is needed to exceed 80 characters, as log lines are quoted to explain what happened and give reasons for why the patch is needed.

For quality checks, for both code and commit messages, good developers usually tries to ensure everything is set and in order *before* submitting a patch. Heck, most I know even tries to ensure that things are proper before doing the local commit. Many calls this process the "personal hygiene step". It's a fairly good description of the importance of doing so.

--
kind regards,

David Sommerseth
OpenVPN Technologies, Inc

#9 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

In reply to Samuli Seppänen

Hi,

Quoted 8 lines · Samuli Seppänen

The "seven rules" URL David linked to says the following:

* Limit the subject line to 50 characters
* Wrap the body at 72 characters

I can't recall us ever agreeing to such limits.

Let's agree on what we want and then document it properly.

Those are good guidelines, but we should not set them in stone (read:
if a subject line is clear and concise and needs 63 characters, that is more welcome than something cryptic in 49 characters).

To find the actual "aim for this" number for the Subject: line, I'd go through our recent commits, look at Subject: lines that look reasonable and just measure what we've been using. Yes, "reasonable" is very subjective.

gert

Signature · 4 lines
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             [email protected]...
fax: +49-89-35655025                        [email protected]...
#10 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

In reply to Samuli Seppänen
Quoted 3 lines · Samuli Seppänen

Actually, that was just the line length for _code_, not for commit messages. So the only indirect guideline for Git commit message line length was

Correct.

Quoted 5 lines

"The maximum length of the line differs between projects, it's usually somewhere between 50 and 78 characters"

which was on this page:

Quoted 8 lines

<http://who-t.blogspot.fi/2009/12/on-commit-messages.html>

The "seven rules" URL David linked to says the following:

* Limit the subject line to 50 characters
* Wrap the body at 72 characters

I can't recall us ever agreeing to such limits.

That is actually a pretty much a de-facto standard among all git users. The subject line at 50 chars is because it makes git shortlog, git log --oneline and similar tools produce reasonable outputs which keeps the total line length, including indenting, within 78 characters.

In addition github, gitlab, gerrit, etc will also truncate subject lines which are longer than 50 characters.

Similarly the body wrapping at 72, is to account for a similar indenting which git does when presenting the body message text.

And it just takes a quick look at our git log to see that we try to stay beyond that limit. We do sometimes exceed 50 characters, and we let that pass silently. But more than 3 times longer, then something must be done.

Signature · 4 lines
kind regards,

David Sommerseth
OpenVPN Technologies, Inc
#11 lore raw

Re: [Openvpn-devel] [PATCH applied] github: Add PR template with contributor related information

Quoted 29 lines · David Sommerseth
Quoted 3 lines · Samuli Seppänen

Actually, that was just the line length for _code_, not for commit messages. So the only indirect guideline for Git commit message line length was

Correct.

Quoted 5 lines

"The maximum length of the line differs between projects, it's usually somewhere between 50 and 78 characters"

which was on this page:

Quoted 8 lines

<http://who-t.blogspot.fi/2009/12/on-commit-messages.html>

The "seven rules" URL David linked to says the following:

* Limit the subject line to 50 characters
* Wrap the body at 72 characters

I can't recall us ever agreeing to such limits.

That is actually a pretty much a de-facto standard among all git users. The subject line at 50 chars is because it makes git shortlog, git log --oneline and similar tools produce reasonable outputs which keeps the total line length, including indenting, within 78 characters.

In addition github, gitlab, gerrit, etc will also truncate subject lines which are longer than 50 characters.

Quoted 9 lines

Similarly the body wrapping at 72, is to account for a similar indenting which git does when presenting the body message text.

And it just takes a quick look at our git log to see that we try to stay beyond that limit. We do sometimes exceed 50 characters, and we let that pass silently. But more than 3 times longer, then something must be done.

I rewrote the DevelopDocumentation page:

<https://community.openvpn.net/openvpn/wiki/DeveloperDocumentationNew>

Changes in a nutshell:

- Most of the verbose but useful stuff was moved to separate page
- Some totally outdated content was removed (FRP, release process, etc)
- Redundant content was removed

Does the new page look like a reasonable starting point for _new_ developers?

Signature · 5 lines
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock