From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE/Yocto developer survey
Date: Mon, 26 Oct 2015 13:38:07 -0600 [thread overview]
Message-ID: <562E811F.8010907@mlbassoc.com> (raw)
In-Reply-To: <CAOd_LFwgMqDUBKzxjs50G+=F0TgFg8ZuoCBX6jqs6p8fLFQibg@mail.gmail.com>
On 2015-10-26 13:18, Cliff Brake wrote:
> Hi,
>
> I'd like to get some feedback on the following questions -- feel free
> to respond to list, or directly to me, and I'll withhold your
> name/company from any results.
>
> I would like to collect feedback until 2015-11-02, and will summarize
> the results after that.
>
> My goal with this survey is to get a sense for best practices and what
> is most commonly used among Yocto/OE developers so I can better advise
> clients using Yocto/OE. Hopefully this will also generate some
> interesting discussions.
>
> How long have you been using OE? __5+ years___
>
> How do you use OE/Yocto?
> [ X ] product development
> [ X ] hobby/research/education/yocto core developer, etc
>
> What distro do you use?
> [ ] Poky
> [ ] Angstrom
> [ X ] nodistro or custom
>
> How do you organize multiple git repos?
> [ ] Git submodules
> [ X ] Repo
> [ ] Other
>
> What packaging system?
> [ X ] OPKG
> [ ] RPM
> [ ] Other
>
> What GUI toolkits?
> [ X ] Qt
> [ X ] Gtk
> [ ] EFL
> [ ] HTML5/JS
> [ ] Other
>
> What init system?
> [ ] systemd
> [ X ] sysvinit
> [ ] busybox init
> [ ] Other
>
> What libc?
> [ X ] glibc
> [ ] uclibc
> [ ] musl
> [ ] Other
>
> How do you develop custom applications?
> [ ] application-SDK
> [ X ] devshell
> [ X ] develop on PC, test on target
> [ ] Other
>
> What language do you primarily use for custom applications?
> [ ] C
> [ ] C++
> [ X ] Python
> [ ] Javascript
> [ ] Lua
> [ ] Other
>
> What do you use for Continuous Integration?
> [ ] Buildbot
> [ ] Jenkins
> [ ] Other
>
> Do you use any any of the tooling projects
> (https://www.yoctoproject.org/tools-resources/projects) such as ADT,
> Hob, Toaster, etc?
>
> ___None at this time ____________________
>
> Reasons or explanations are appreciated, and please feel free to
> include additional choices/information you think are relevant.
>
> Thanks,
> Cliff
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-10-26 19:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 19:18 OE/Yocto developer survey Cliff Brake
2015-10-26 19:38 ` Gary Thomas [this message]
2015-10-26 20:08 ` Martin Jansa
2015-10-26 20:17 ` Brian Hutchinson
2015-10-26 23:04 ` Andreas Müller
2015-10-27 8:08 ` Marc Reilly
2015-10-27 8:12 ` Christian Ege
2015-10-27 8:40 ` [yocto] " Alex J Lennon
2015-10-27 9:12 ` Andrei Gherzan
2015-10-27 16:35 ` Stephano Cetola
2015-10-28 7:32 ` Chris Morgan
2015-10-29 5:09 ` Sven Ebenfeld
2015-10-29 6:01 ` 彥瑾
2015-10-29 11:59 ` Anders Darander
2015-10-29 14:36 ` Changhyeok Bae
2015-10-29 17:09 ` Nicolas Aguirre
2015-11-07 0:06 ` Phil Blundell
2015-11-12 12:06 ` Cliff Brake
2015-11-12 16:15 ` Cliff Brake
2015-11-12 16:10 ` Alejandro del Castillo
2015-11-13 10:19 ` Steffen Sledz
2015-11-18 15:26 ` Cliff Brake
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=562E811F.8010907@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.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