kicad-developers team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

 @Amir, Currently, any help at getting this list sorted out is progress.

https://gitlab.com/kicad/code/kicad/-/issues?scope=all&utf8=%E2%9C%93&state=opened&milestone_title=6.0.0-rc1

But that list contains both big and small items, but items that do require
some real work.

On Tue, 29 Jun 2021 at 16:11, Mark Roszko <mark.roszko@xxxxxxxxx> wrote:

> >The number of issues is about 1170 on any day since a few months. My
> goal is to reduce the number of open issues to a bare minimum or eliminate
> them
>
>
> You realize we only have <100 real issues right? You cannot look at the
> silly total displayed and assume. You have to drill down by tags.
> A vast majority are wishlist items (849), not actual bugs.
>
> Some bugs also cannot be fixed by wishful thinking, they are platform
> issues or user specific with no reproduction cases but we leave open for
> documentation. Some bugs are also slated for later fixes in newer versions
> downstream.
>
> You came barging in assuming we are just randomly  committing code without
> plans. We absolutely do and have a workflow. Of course we are volunteers
> and work on what we want and when we want which is why we don't take kindly
> to someone coming in and accosting us that we need someone to manage us and
> spend months writing fizz buzz to work on KiCad which is already going slow.
>
>
> On Tue, Jun 29, 2021, 8:12 AM Amit M <wjl239423sdjl@xxxxxxxxx> wrote:
>
>> Hello all,
>>
>>
>>
>> I’m a beginner to Kicad source code. I’m looking to test some modules and
>> components. Is there a way to learn which module does what in the repo? I
>> have the source code with me.  The whole project seems a bit complex so I’m
>> trying to figure out one part , test it and then increase tests to other
>> parts to cover most or all of it.  I am sort of familiar with understanding
>> large code bases but am finding a starting point. I have been told to look
>> at the directory below and write tests there.
>>
>> https://gitlab.com/kicad/code/kicad/-/tree/master/qa
>>
>>
>>
>> The entire code is below:
>>
>> https://gitlab.com/kicad/code/kicad/-/tree/master
>>
>>
>>
>> If you can, can you please suggest any documentation or emails or
>> anything which can explain which module does what and how does each module
>> work ? Examples of some modules I’m wanting to learn to test are eeschema
>> <https://gitlab.com/kicad/code/kicad/-/tree/master/qa/eeschema>, pcbnew,
>> qa_utils, gerber and geometry just to name a few. I  also looked at UI and
>> other things such as 3d viewer modules. I figure there may be UI related
>> bugs because there were crashes as listed in the mailing list or in the
>> issue list here:
>>
>> https://gitlab.com/kicad/code/kicad/-/issues
>>
>>
>>
>> The number of issues is about 1170 on any day since a few months. My goal
>> is to reduce the number of open issues to a bare minimum or eliminate them.
>>
>> I had some discussions with the developers and they didn’t accept
>> suggestions that writing detailed software requirements and design
>> specifications to reduce bugs would work as most developers are volunteers.
>>
>>
>>
>> Thanks,
>>
>> Amit
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>