> Hi Luca, Hi Ayan,
>> >> In the last MISRA meeting Stefano told me about the Rule 10.3 and that we >> have a lot of violations, >> but GCC has a way to list them as written in rules.rst. >> >> So the issue was just that we have a lot of violations, most of them coming >> from headers and the >> Developer might feel a bit lost since the number is very high, so I’ve >> developed this script to take >> the GCC build log and create a list of unique occurrences of the violations >> sorted in descending >> order, so that who has a bit of time can try to fix some of those and maybe >> can start from the top >> of the list to fix as many as possible occurrences. >> >> I attach the script as patch file. > > This is an excellent script to see the violations in a neat way. For eg, I > see this > > arch/arm/domain_build.c:3883:28 (1) > arch/arm/domain_build.c:3910:36 (1) > ./include/xen/pfn.h:6:23 (1) > ./include/xen/macros.h:4:40 (1) > arch/arm/setup.c:221:10 (1) > arch/arm/setup.c:227:59 (1) > > I think once in a while, we have been approached by newbies wanting to > contribute to Xen project. > > For eg "Beginner looking to contribute to project in archived list" > > Sometimes people reach out individually as well. > > Do you have such similar tasks (like this) within or beyond the scope of > MISRA which will require some basic programming skills and is a great first > step to learn and contribute to Xen project ? > > This can be things which students/folks can contribute on an ad-hoc basis. Yes indeed, these are the kind of fixes that could be handled by beginners contributors, given the amount of them we need some help for sure! > > I can work with Kelly to see if we can put them in a wiki page. > > I could see https://wiki.xenproject.org/wiki/Outreach_Program_Projects , but > don't know if it is up to date. Sure we can sync with Kelly to see what we can do! Cheers, Luca
