[yocto-ab] YP Advisory Board: VOTE YP Participant, RTSoft

Philip Balister philip at balister.org
Thu Mar 2 11:04:26 PST 2017


On 03/02/2017 01:59 PM, Jeff Osier-Mixon wrote:
> Thanks, Kevin
> 
> The AB already approved Bronze (in December). However, my understanding is
> that Bronze is not meant to displace YP Participant. Bronze is a non-voting
> level of membership for people who donate money or resources to the
> project, but who can't afford Silver. Participant simply recognizes people
> who are active in the community and meet the conditions on the form.

I forget the exact details of RTSoft, but if they are in the group of
companies slightly over the size limit for participant (that we have
been approving anyway), maybe suggesting bronze as part of the
participant badge is a good path.

Philip

> 
> I wasn't at the AB meeting last week, so perhaps my understanding is out of
> date. In any case, though, the project still needs a method for recognizing
> active participants at no cost, so I hope this is still valid.
> 
> 
> On Thu, Mar 2, 2017 at 10:38 AM, McCombe, Kevin <Kevin_McCombe at mentor.com>
> wrote:
> 
>> Is there an option to give them YP Participant only until we have Bronze
>> approved and let them know they’ll be expected to sign-up for bronze at
>> that time ?
>>
>> From: <yocto-ab-bounces at yoctoproject.org> on behalf of Jeff Osier-Mixon <
>> jefro at jefro.net>
>> Date: Thursday, March 2, 2017 at 10:36 AM
>> To: "Osier-mixon, Jeffrey" <jeffrey.osier-mixon at intel.com>
>> Cc: "yocto-ab at yoctoproject.org" <yocto-ab at yoctoproject.org>
>> Subject: Re: [yocto-ab] YP Advisory Board: VOTE YP Participant, RTSoft
>>
>> I have heard from a few folks, but I'd like to get a quorum. If you
>> haven't voted on this yet, please take a look and do so, as these folks are
>> ready to use the branding.
>>
>> thanks
>>
>> On Mon, Feb 20, 2017 at 8:33 AM, Osier-mixon, Jeffrey <
>> jeffrey.osier-mixon at intel.com> wrote:
>>
>>> I thought RTSoft had already been inducted into the ranks of YP
>>> Participants, but evidently not. They have been around for a while as
>>> active consultants in Germany. They technically have a few more employees
>>> than our application specifies, but we have allowed other orgs with that
>>> many employees in before.
>>>
>>>
>>>
>>> Please vote yes/no on RTSoft as a YP Participant:
>>>
>>>
>>>
>>>  --Contact information--
>>>      Organization / project name: RTSoft SWDC
>>>      Contact name: hubert.hafner at rtsoft.de
>>>      Contact email address: hubert.hafner at rtsoft.de
>>>      URL to organization or product link: www.rtsoft.de
>>>      Registration date: 2017-02-20
>>>      Compliance Agreement revision: 1.0
>>>
>>>
>>> Criteria:
>>>   - Visibly participating in the Yocto Project community. Please
>>> describeyour
>>> participation in the comments section below.: Yes
>>>   - Working towards and supporting the aims and objectives of the Yocto
>>> Project. These include decreasing the fragmentation of embedded ecosystem
>>> and
>>> focusing around a common shared set of tools, formats and best practices.
>>> We
>>> want to avoid multiple groups of people repeating the same work and have
>>> one
>>> set of great tools rather than multiple tools with drawbacks.: Yes
>>>   - Committed to promoting the OpenEmbedded architecture, layer model,
>>> andBSP
>>> format.: Yes
>>>   - Are all your publicly accessible layers listed in the OpenEmbedded
>>> Layers
>>> index (http://layers.openembedded.org)?: No (explain below)
>>>   - Committed to sending to the open source community any patches to
>>> OpenEmbedded-Core, BitBake and other Yocto Project layers.: No (explain
>>> below)
>>>   - Aiming for compatibility and interoperability among different metadata
>>> layers.: Yes
>>>   - Are a non-profit, small business (up to 80 employees), or existing
>>> Yocto
>>> Project member organization, or if the project's parent organization is an
>>> open-source project.: No (explain below)
>>> Explanation:
>>> Hello,
>>>
>>> RTSoft is focussed on embedded Software development. In terms of yocto, we
>>> help our customers to port their BSPs to a proper Yocto approach. We are a
>>> profit-company with round-about 100 developers. We do not list all layers
>>> nor
>>> send all the patches back. The reason therefore is that we work on behalf
>>> of
>>> customrs, the drive the direction what to be published and sent back to
>>> community - of course all in allignment with copyright copyleft
>>> agreements.
>>>
>>>
>>>
>>> Jeffrey “Jefro” Osier-Mixon, Intel Corporation
>>>
>>> Open Source Community Engineer & Advocate
>>>
>>> Yocto Project Community Manager
>>>
>>>
>>>
>>> --
>>> _______________________________________________
>>> yocto-ab mailing list
>>> yocto-ab at yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto-ab
>>>
>>>
>>
>>
>> --
>> Jeff Osier-Mixon - Open Source Community Engineer, Intel Corporation
>>
> 
> 
> 
> 
> 


More information about the yocto-ab mailing list