linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Greg Gallagher <greg@embeddedgreg.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Any maintainers or developers looking for help?
Date: Thu, 16 Jan 2020 17:00:34 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.21.2001161659020.7528@planxty> (raw)
In-Reply-To: <CALLqZ8QK5kJqwxZ-zze-OcwFCAWY5gDOmy_UwqUm89HE3rZ_gQ@mail.gmail.com>



On Wed, 15 Jan 2020, 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.
> 
> Thanks everyone for their time and sorry to spam the list,
> 
> Greg
> 

This is almost always the wrong approach. If you are interested in 
real-time then start working with the kernel and supporting software, and 
then if you see things that don't work the way you would like, or you have 
ideas for improvements, then submit patches.

Cheers

John

      parent reply	other threads:[~2020-01-16 16:00 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
2020-01-16 16:00 ` John Kacur [this message]

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=alpine.LFD.2.21.2001161659020.7528@planxty \
    --to=jkacur@redhat.com \
    --cc=greg@embeddedgreg.com \
    --cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).