From: Greg Gallagher <greg@embeddedgreg.com>
To: Daniel Wagner <wagi@monom.org>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Any maintainers or developers looking for help?
Date: Thu, 16 Jan 2020 10:12:39 -0500 [thread overview]
Message-ID: <CALLqZ8RW10upgssYB7q486JqRuZOJw+uYwyZnROFQvUZP0M-pA@mail.gmail.com> (raw)
In-Reply-To: <559de2dd-c9fa-d5d0-af05-3537be9a9a79@monom.org>
Hi Daniel,
On Thu, Jan 16, 2020 at 4:24 AM Daniel Wagner <wagi@monom.org> wrote:
>
> Hi Greg,
>
> On Wed, Jan 15, 2020 at 01:06:30PM -0500, Greg Gallagher wrote:
> > Hi RT users and developers,
> > I was wondering if any RT maintainers or developers that are on
> > this list need any help with tasks that they haven't had a chance to
> > do (documentation, small fixes, testing etc)? I've been working with
> > RTOS's, Linux and C for the past ten years, I've contribute to smaller
> > open source projects in the past. I'm still a novice when it comes to
> > working with the open source community and I'm reaching out to the
> > list since if possible I'd like to work with someone to start. I know
> > that not everyone has time to help but I thought I would reach out and
> > see if I could help someone clear out some old tasks that need to be
> > completed in exchange for some help getting started contributing to
> > the RT project.
>
> One thing which could be a good starting point is testing the various
> devel-rt and stable-rt releases. There are a bunch of tests tools in
> rt-tests (which could also some love). I am sure you will find things
> which are not working in either the kernel or in the rt-tests.
>
> Another related thing is automate the testing. For example I'm using
> LAVA[1] to orchistrate my small lab with Linaro's test-definitions[2]
> as test harness. Everthing is duck taped together but works pretty
> awesome for me. I've created a small (but horrible) python script
> which allows me to configure, build and submit the binaries for
> testing to LAVA in one go.
>
> Thanks,
> Daniel
>
> [1] https://github.com/igaw/lava-docker-compose/tree/lithium-setup
> [2] https://github.com/igaw/test-definitions/tree/preempt-rt
I will start looking at what you mentioned above. Thanks for replying,
I’ll post back once I’ve made some progress.
Thanks
Greg
next prev parent reply other threads:[~2020-01-16 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 18:06 Any maintainers or developers looking for help? Greg Gallagher
2020-01-16 9:24 ` Daniel Wagner
2020-01-16 15:12 ` Greg Gallagher [this message]
2020-01-16 16:00 ` John Kacur
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=CALLqZ8RW10upgssYB7q486JqRuZOJw+uYwyZnROFQvUZP0M-pA@mail.gmail.com \
--to=greg@embeddedgreg.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=wagi@monom.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;
as well as URLs for NNTP newsgroup(s).