From: matthias.tafelmeier@gmx.net (Matthias Tafelmeier)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP endeavor decision
Date: Sun, 26 Jun 2016 10:17:02 +0200 [thread overview]
Message-ID: <576F8F7E.7010700@gmx.net> (raw)
Hello
who I am: I work as a operartions engineer at a data centre in Europe
and formerly I worked for several years as a development engineer in SDN
networking area.
Your project has caught my attention for its corageous mission. I am
strongly interested in bringing forward civic from a computing
technicial perspective and I see me fit to do so.
I haven't had any experience in working in linux collab projects yet and
there are quite many projects in linux collab. So to help me decide if
participating in your project is the right endeavor for me: please,
answer me a few questions, although those can seem a little blunt.
>
Is it at all imperative for you gathering together individuals to solve
technicial intricacies or is it rather a tightly financial sponsor
interests guided project, and therefore for the members of the sponsors?
Are extraneous forces really welcome?
To what level in software terms do you want to bring about innovations?
You are speaking abstractly about a platform and glue mechanisms. To
what extend? Down to the driver level?
Are there opportunities for individuals or is it rather meant to cheaply
tap into ressources? Can one ascend therein?
<
--
BR
Matthias Tafelmeier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x8ADF343B.asc
Type: application/pgp-keys
Size: 4746 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20160626/6fe392ef/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20160626/6fe392ef/attachment.sig>
reply other threads:[~2016-06-26 8:17 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=576F8F7E.7010700@gmx.net \
--to=matthias.tafelmeier@gmx.net \
--cc=cip-dev@lists.cip-project.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