| 18 | |
| 19 | * Consider utilizing the openvpn.org domain. This could be done to varying degrees: |
| 20 | * total company split. openvpn.org is organized as a subsidiary of the for-profit company, with dedicated resources. |
| 21 | * total website split. link from openvpn.net to openvpn.org instead of going to community.openvpn.net. The .org domain becomes the TLD of community resources. Crosslinks between .net to .org can brand-differentiate / refer to "the open-source code that powers our business," and vice-versa. |
| 22 | * create a minimal redirect: openvpn.org becomes a simple redirect to a landing page on community.openvpn.net instead of the mainline openvpn.net site. |
| 23 | * create many redirects: .net site can link to "openvpn.org/source-code", with each URI linking to somewhere in community.openvpn.net or forums.openvpn.net. This seems twisty, I know - .net links to a .org just to 307 back to .net. The idea here would be to make the links clearly show that "this link is about the community/open-source edition." That you end up back on .net is what happens today, but you could do something more in line with a .org layer later. |