From: Curtis Hall <curt@bluecherry.net>
To: linux-media@vger.kernel.org
Subject: [Job posting] Linux software developer with experience with the Video4Linux2 API / ALSA
Date: Wed, 17 Nov 2010 11:50:33 -0600 [thread overview]
Message-ID: <4CE415E9.10008@bluecherry.net> (raw)
Note, before posting this I asked in the #v4l channel on freenode if a
(single) announcement for a job posting would be acceptable. I was told
that it should be okay, so if it's against the policy let me know (I do
apologize if it is).
We are looking for a Linux software developer for our Linux based
surveillance application (www.bluecherrydvr.com). This reason I'm
posting this on the linux-media mailing list is because our application
uses the Video4Linux and ALSA APIs for accessing video / audio. We
recently released a open source MPEG-4 / H.264 driver (see links below),
and since our application uses this driver we are in need of developers
with extensive knowledge with Video4Linux and ALSA to extend our
application. This position would also handle IP camera integration,
which is not directly related to the V4L.
The complete job posting with more specific requirements is here:
http://jobview.monster.com/Linux-video-surveillance-software-developer-Video4Linux-ALSA-Job-Fulton-MO-US-91967697.aspx?fwr=true
If you have any questions please email me off-list (email address is
below) as not to crowd up the mailing list.
Telecommuting is an option for this position.
Thanks!
Links:
http://git.kernel.org/?p=linux/kernel/git/bcollins/solo6x10-staging.git;a=summary
http://linux.slashdot.org/story/10/06/17/1929230/Bluecherry-Releases-GPLd-MPEG-4-Driver
http://support.bluecherrydvr.com/entries/235174-using-the-bluecherry-hardware-compression-open-source-linux-drivers-mpeg-4-h-264
--
--
Curtis Hall (curt@bluecherry.net)
Bluecherry - www.bluecherrydvr.com
(877) 418-3391 x 283 / (573) 642-6161
reply other threads:[~2010-11-17 17:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CE415E9.10008@bluecherry.net \
--to=curt@bluecherry.net \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox