[yocto] newcomers

[Randy MacLeod]

On 10/3/19 12:38 PM, Maciej Pijanowski wrote:
> 
> On 03.10.2019 18:33, Steve Scott wrote:
>>
>> How would a newcomer get started?

Welcome to the Yocto Project Steve!

Ideally, everything should be linked from:
    https://www.yoctoproject.org/
and there is, in fact a 'Get started here' link there:
    https://www.yoctoproject.org/software-overview/
which ends with a numbered list of documents for new devs/users
in the "New to the Yocto Project" section.


>>
>> Is there an FAQ or Wiki that gives a developer overview of the 
>> project, 

The first link used to be called 'Getting Started' but now it's
called quick build:

https://www.yoctoproject.org/docs/2.7.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html


Oh and the Wikipedia page links to Yoctoproject.org too so that's good.

Do you think we need to simplify the landing page?

>> patch submission process, etc.?
>>
> This one is pretty accurate when it comes to patch submission process:
> https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
>>
>> It’s hard to jump on to the moving train…

Yes, there's lots to learn.

When I start new developers, I get them to clone poky and build
core-image-minimal which is prety much what:
 
https://www.yoctoproject.org/docs/current/brief-yoctoprojectqs/brief-yoctoprojectqs.html
does except it uses core-image-sato.

The docs are quite verbose and some people prefer to learn by doing.
Do you think the, "Yocto Project Quick Build" is suitable for that
path?

../Randy

>>
>> *From:*yocto-bounces at yoctoproject.org 
>> [mailto:yocto-bounces at yoctoproject.org] *On Behalf Of *Stephen K Jolley
>> *Sent:* Monday, September 30, 2019 8:50 AM
>> *To:* openembedded-core at lists.openembedded.org; yocto at yoctoproject.org
>> *Subject:* [yocto] (no subject)
>>
>> All,
>>
>> The triage team is starting to try and collect up and classify bugs 
>> which a newcomer to the project would be able to work on in a way 
>> which means people can find them. They're being listed on the triage 
>> page under the appropriate heading:
>>
>> https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
>>
>> The idea is these bugs should be straight forward for a person to help 
>> work on who doesn't have deep experience with the project.  If anyone 
>> can help, please take ownership of the bug and send patches!  If 
>> anyone needs help/advice there are people on irc who can likely do so, 
>> or some of the more experienced contributors will likely be happy to 
>> help too.
>>
>> Also, the triage team meets weekly and does its best to handle the 
>> bugs reported into the Bugzilla. The number of people attending that 
>> meeting has fallen, as have the number of people available to help fix 
>> bugs. One of the things we hear users report is they don't know how to 
>> help. We (the triage team) are therefore going to start reporting out 
>> the currently 309 unassigned or newcomer bugs.
>>
>> We're hoping people may be able to spare some time now and again to 
>> help out with these.  Bugs are split into two types, "true bugs" where 
>> things don't work as they should and "enhancements" which are features 
>> we'd want to add to the system.  There are also roughly four different 
>> "priority" classes right now, “2.8”, “2.9’, "2.99" and "Future", the 
>> more pressing/urgent issues being in "2.8" and then “2.9”.
>>
>> Please review this link and if a bug is something you would be able to 
>> help with either take ownership of the bug, or send me 
>> (sjolley.yp.pm at gmail.com <mailto:sjolley.yp.pm at gmail.com>) an e-mail 
>> with the bug number you would like and I will assign it to you (please 
>> make sure you have a Bugzilla account).  The list is at: 
>> https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs
>>
>> -- 
>>
>> Thanks,
>>
>> */Stephen K. Jolley/*
>>
>> *Yocto Project Program Manager*
>>
>> *7867 SW Bayberry Dr., Beaverton, OR 97007*
>>
>> (*Cell*: (208) 244-4460
>>
>> * *Email*:_s <mailto:stephen.k.jolley at intel.com>jolley.yp.pm at gmail.com 
>> <mailto:jolley.yp.pm at gmail.com>_
>>
>>
> -- 
> Maciej Pijanowski
> Embedded Systems Engineer
> https://3mdeb.com  | @3mdeb_com
> 
> 


-- 
# Randy MacLeod
# Wind River Linux