Site News: OpenBSD Jobs

> Our OpenBSD sysadmin posting is about to be updated. We actually have two openings that are OpenBSD-related: Systems Architect and Senior
> Systems Administrator. The current job positing, admittedly, is kind of lame. We're doing away with the quiz questions in favor of hard-hitting
> technical interviews.

Chris

Hopefully you'll find somebody within the community to fill the OpenBSD positions you have open.

I will admit I was one of the one's who gave you a hard time about you're initial job posting on misc@. It's good to see undeadly stepping up to the plate to give employers a place to look for experienced OpenBSD administrators.

g.day

> OpenBSD jobs = good for OpenBSD.
> License concerns. BSD and GPL might have weird + - when adding proprietary changes to BSD code. Derivative work or not?
> Input from OpenBSD developers on best way to help OpenBSD, but not taint it, with proprietary legal games later. Submarine changes, if you will.
>
> I've read some groklaw, and other sources of BSD, GPL, etc, but it seems a lot is unsettled.
>
> How much can proprietary work end up like a NDA, to an employee, or even a project?

How much more off-topic can you get?

I'm not even sure your comments/questions make sense.

> OpenBSD jobs = good for OpenBSD.
> License concerns. BSD and GPL might have weird + - when adding proprietary changes to BSD code. Derivative work or not?
> Input from OpenBSD developers on best way to help OpenBSD, but not taint it, with proprietary legal games later. Submarine changes, if you will.
>
> I've read some groklaw, and other sources of BSD, GPL, etc, but it seems a lot is unsettled.
>
> How much can proprietary work end up like a NDA, to an employee, or even a project?

.vantronix is open and I contributed some code which I initially wrote for commercial projects or for our products. For example trunk(4), hoststated(8) layer 7 "relay", or spamd-synchronisation. And I needed "SSH-VPN" which is used by our OpenBSD and MacOS X users when IPsec is not available. ...

From a commercial perspective, it is a big benefit to contribute code back to the OpenBSD community, it will help to improve the quality provided to our customers. Even if you hire a group of OpenBSD developers, it will not give you the same quality as if you release your code to the public tree, discuss it with developers, hack on it during hackathons. It is a shame that most companies using code from OpenBSD are doing it very rarely or not at all.

Yes, we keep some unrelated code in private, like the appliance-specific management tools (CLI, user interfaces, ...) and parts of our preinspection technology. This definitely is proprietary work, part of the commercial reality.

We also have some local changes that do not fit into the tree, like other limits (we don't have to care about really old hardware), and a complete GPL-free base system (because of license concerns, GPL is a no-go for our products). But normally I even discuss these specific changes within the project.

Reyk

> Unfortunately there are not many jobs for OpenBSDer's down under.

tell me about it.

> [And if you still haven't noticed, the .vantronix job is sweet! -dwc]
>
> Sure it looks really, really sweet, except it's not in my country of origin.
>
> Unfortunately there are not many jobs for OpenBSDer's down under.
>

It's not in my country, either. Jobs like .vantronix are rare everywhere! This is the benefit of having these on undeadly in the first place. When an OpenBSD related job comes up it's good for both the company and the OpenBSD community to have it here.

You can bet that I will keep an eye out in case something comes up in my area.

> Unfortunately there are not many jobs for OpenBSDer's down under.

Send me your resume. Generally, we much prefer US applicants because hiring them is much simpler but we consider all international applicants. We have an Aussie on staff and his visa was fairly simple; apparently .us and .au have some sort of immigration agreement in place.

Chris Snell
Backcountry.com
csnell@ ""