Hi
> I don't know whether it would help but I thought I might like to
> contribute to the project by documenting the whole process for
> cloning the code, submitting revisions and reviewing code so that
> first time contributors would know what to do. I have recently
> obtained some access to th
Dear list,
I have been watching the conversation about reviewing submitted code
with interest and it seems to me that the problem is fundamentally one
of communication, or, rather, perhaps the lack of it. The developers
naturally want to focus on their core objectives of maintaining and
devel
I think the HACKING file in the different sigrok projects could be updated and
unified. Here is one step in that direction :
(also submitted as https://github.com/sigrokproject/libsigrok/pull/199 )
In there, I add two non-binding recommendations :
1- avoid bundling an assignment in a conditional
3 matches
Mail list logo
