Re: [Kicad-developers] Sponsoring KiCad development

[Wayne Stambaugh]

Hi Schaarschmidt,

I apologize for not replying sooner.  I was busy with FOSDEM and then
recovering from my trip.  Thank you for you interest in sponsoring
KiCad.  Many of your suggestions have already been implemented in the
upcoming 5.1 release or are schedule to be implemented during the
version 6 development period.  You could always donate to KiCad though
CERN.  Sponsoring a KiCad developer directly is pretty difficult as we
are pretty much an all volunteer effort.  Most of us have very little
free time to side projects.  Hopefully we can figure out a way to
accommodate you that would be beneficial to all parties concerned.  I
have commented on your wish list below.

On 2/1/2019 1:14 AM, Schaarschmidt Wolf wrote:
> Dear KiCad developers,
> 
> our company Dorabot is an enthusiastic KiCad user,
> so we would like to *sponsor *some improvements:
> 
> *1. Schematic design part*
> a. provide off-page connection for a parallel bus. 

I believe this is already to merger into the development branch as soon
as 5.1 is released.

> b. provide customized power ports that can be edited by netlabel in case
> there are several power rails.

I don't know precisely what this is but we could implement this as part
of our connectivity improvements planned for v6.

> c. provide a convenient way to duplicate circuitry partially from
> another project.

You can already append a schematic to the current sheet.

> d. provide a convenient way to combine two different schematic-libs.

You can already do this with hierarchical sheets.  If you are thinking
of another method, we could discuss that further.

> e. provide a way to import schematic designs from other popular EDA
> tools, such as Altium Designer or Orcad.

That's going to be a ways down the road.  We have some partial solutions
for Altium primarily for board import.  We do have pretty good support
for importing Eagle project files.

> 
> *2. PCB layout part*
> a. provide teardrop connection methods, including mass and individual way.

Planned for v6

> b. provide a method to mass align REF numbers. 

This has not been discussed but could something to consider.

> c. provide a method to mass edit the size of REF numbers.

This already exists and will be released with 5.1.

> d. provide a method to move multiple components in *PCB* when selected
> in the schematic.

We could do this during v6 when the new toolkit is implemented in the
schematic editor.

> e. provide a method to add arc traces.

This is on the version 6 roadmap so hopefully we will get to this.

> f.  provide a method to add polygons with arc corners.

Same as e.

> g. have a specified rule to constrain the clearance between the edge and
> polygons or traces locally (not only globally).

Constraint management is going to be completely rewritten for version 6.

> h. provide a way to import PCB designs from other popular EDA tools,
> such as Altium Designer or Allegro.

Same goes here as for the schematic import.

> i.  provide a convenient way to fanout BGA footprints with certain VIA
> size and Trace width.

Via pad stacks are part of version 6 development which should address
most of this.

> j.  provide region constraint for small pitch size BGA footprint.

This could be part of the new constraint management system.

> 
> Please let us know whether you see an opportunity for us
> to *sponsor* (i.e. financially support) 
> some or all of these improvements. We are looking forward to hearing
> from you!

I do see opportunities for you to sponsor KiCad and/or a developer
directly.  Please keep in mind that contributions to KiCad have to go
though the lead development team for review and approval so your best
bet is to sponsor one of the lead developers to ensure any sponsored
code gets accepted.  I wish I had the free time to help you out but
being the project leader doesn't leave a lot of spare time to take on
side projects.

Cheers,

Wayne

> 
> Best regards,
> 
> *Wolf Schaarschmidt*｜Robot Engineer
> 
> w...@dorabot.com 
> 
> 
> No. 2 Zuopaotai Rd, H6-2, Nanshan District｜Shenzhen, Guangdong 518000,
> China
> 
> 0755-21650236｜
> i...@dorabot.com
> ｜www.dorabot.com 
> 
> ---
> 
> CONFIDENTIALITY NOTICE: The contents of this email message and any
> attachments are intended solely for the addressee(s) and contain
> confidential and/or privileged information and are legally protected
> from disclosure unless otherwise indicated. If you are not the intended
> recipient of this message or their agent, or if this message has been
> addressed to you in error, please immediately alert the sender by reply
> email and then delete this message and any attachments. If you are not
> the intended recipient, you are hereby notified that any use,
> dissemination, copying, 

Re: [Kicad-developers] 5.1.0-rc1

[Wayne Stambaugh]

On 2/7/2019 2:28 PM, Steven A. Falco wrote:
> On 2/7/19 2:11 PM, Wayne Stambaugh wrote:
>> On 2/7/2019 1:38 PM, Vesa Solonen wrote:
>>> Steven A. Falco kirjoitti 7.2.2019 klo 18.04:
>>>
 However, because of the eeschema line-width issues that I mentioned 
 yesterday, I'm not convinced that users will be happy with gtk3.

 In the attached screenshot, compare the line width at pin 2 and pin 3 of 
 the op-amp.
>>>
>>> Hi Steve,
>>>
>>> This is not gtk3 specific, but comes from the rounding issues in
>>> Eeschema new drawing code (both OpenGL and Cairo). Unfortunately proper
>>> solutions are not trivial. One can mask it bearably by using Cairo
>>> drawing with anti-aliasing turned on (at least on 4k resolutions).
>>>
>>> -Vesa
>>>
>>
>> This problem will get fixed during v6 development.  The other option is
>> to build with wxWidgets with gtk2 and disable wxPython support.  There
>> is no ideal solution at the moment.  This is the reason that we even
>> created a 5.1 release.  I think users would rather have the slightly
>> distorted graphics (which Vesa's suggest improves) than no wxPython support.
> 
> Well, based on my test of the nighlies (built with gtk2), I don't think gtk2 
> will help.  I attached three screen shots - the titles should be 
> self-explanatory.  You can see the distortion even in the gtk2 nightlies.
> 
>   Steve

The legacy canvas is still available with gtk2 builds so you don't have
to use the modern canvas should you choose not to do so.  The legacy
canvas is disabled in gtk3 builds because it is completely broken.

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] still graphical issues in Eeschema also in GTK+3 builds (Re: 5.1.0-rc1)

[Carsten Schoenert]

This thread is getting offtopic ... better open up a new one.

Am 07.02.19 um 20:24 schrieb Steven A. Falco:> I'm concerned that people
will post bug reports (or just downgrade)
> if they see the display artifacts.  Would it make sense to put up a
> dialog the first time the new version is run, advising users to
> switch their settings if they don't like the appearance?  Or perhaps
> force the settings to "fallback+AA" one time on an upgrade?
I personally find such "suggesting windows" more annoying than helpful.
This whole topic is nothing more than the issues that can probably
happen because of the various know problem with graphic cards and
drivers, and mostly only hit people on Linux based systems. So why
bothering people that are affected by this like Windows users?

Better is a place where users can be pointed to in general. We have such
a place on the main website for KiCad. It might need a bit of update.

http://kicad-pcb.org/help/known-system-related-issues/

For more specific hints, especially in context to the used Linux
distribution this needs to be handled by their maintainers. If really
needed a dedicated information can go to the Help menu in KiCad which
I'd more prefer than pop up windows.

-- 
Regards
Carsten Schoenert

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0-rc1

[Steven A. Falco]

On 2/7/19 2:11 PM, Wayne Stambaugh wrote:
> On 2/7/2019 1:38 PM, Vesa Solonen wrote:
>> Steven A. Falco kirjoitti 7.2.2019 klo 18.04:
>>
>>> However, because of the eeschema line-width issues that I mentioned 
>>> yesterday, I'm not convinced that users will be happy with gtk3.
>>>
>>> In the attached screenshot, compare the line width at pin 2 and pin 3 of 
>>> the op-amp.
>>
>> Hi Steve,
>>
>> This is not gtk3 specific, but comes from the rounding issues in
>> Eeschema new drawing code (both OpenGL and Cairo). Unfortunately proper
>> solutions are not trivial. One can mask it bearably by using Cairo
>> drawing with anti-aliasing turned on (at least on 4k resolutions).
>>
>> -Vesa
>>
> 
> This problem will get fixed during v6 development.  The other option is
> to build with wxWidgets with gtk2 and disable wxPython support.  There
> is no ideal solution at the moment.  This is the reason that we even
> created a 5.1 release.  I think users would rather have the slightly
> distorted graphics (which Vesa's suggest improves) than no wxPython support.

Well, based on my test of the nighlies (built with gtk2), I don't think gtk2 
will help.  I attached three screen shots - the titles should be 
self-explanatory.  You can see the distortion even in the gtk2 nightlies.

Steve

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0-rc1

[Steven A. Falco]

On 2/7/19 1:38 PM, Vesa Solonen wrote:
> Steven A. Falco kirjoitti 7.2.2019 klo 18.04:
> 
>> However, because of the eeschema line-width issues that I mentioned 
>> yesterday, I'm not convinced that users will be happy with gtk3.
>>
>> In the attached screenshot, compare the line width at pin 2 and pin 3 of the 
>> op-amp.
> 
> Hi Steve,
> 
> This is not gtk3 specific, but comes from the rounding issues in
> Eeschema new drawing code (both OpenGL and Cairo). Unfortunately proper
> solutions are not trivial. One can mask it bearably by using Cairo
> drawing with anti-aliasing turned on (at least on 4k resolutions).

You are right.

I tried an older 5.0.2 build and it looks perfect at any zoom level.  However, 
both the latest nightly build (gtk2) and my gtk3 build show the problem.  So it 
is not specific to gtk3.

Based on your suggestion I played around with the preferences: With my gtk3 
build, I can make it look good by switching to "Modern Toolset fallback + high 
antialiasing".

For "Modern Toolset accelerated", I find that "supersampling 2x" makes it look 
decent, but still not quite as good as "Modern Toolset fallback + high 
antialiasing" or the older 5.0.2 code.

I'm concerned that people will post bug reports (or just downgrade) if they see 
the display artifacts.  Would it make sense to put up a dialog the first time 
the new version is run, advising users to switch their settings if they don't 
like the appearance?  Or perhaps force the settings to "fallback+AA" one time 
on an upgrade?

Steve


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0-rc1

[Wayne Stambaugh]

On 2/7/2019 1:38 PM, Vesa Solonen wrote:
> Steven A. Falco kirjoitti 7.2.2019 klo 18.04:
> 
>> However, because of the eeschema line-width issues that I mentioned 
>> yesterday, I'm not convinced that users will be happy with gtk3.
>>
>> In the attached screenshot, compare the line width at pin 2 and pin 3 of the 
>> op-amp.
> 
> Hi Steve,
> 
> This is not gtk3 specific, but comes from the rounding issues in
> Eeschema new drawing code (both OpenGL and Cairo). Unfortunately proper
> solutions are not trivial. One can mask it bearably by using Cairo
> drawing with anti-aliasing turned on (at least on 4k resolutions).
> 
> -Vesa
> 

This problem will get fixed during v6 development.  The other option is
to build with wxWidgets with gtk2 and disable wxPython support.  There
is no ideal solution at the moment.  This is the reason that we even
created a 5.1 release.  I think users would rather have the slightly
distorted graphics (which Vesa's suggest improves) than no wxPython support.

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0-rc1

[Vesa Solonen]

Steven A. Falco kirjoitti 7.2.2019 klo 18.04:

> However, because of the eeschema line-width issues that I mentioned 
> yesterday, I'm not convinced that users will be happy with gtk3.
> 
> In the attached screenshot, compare the line width at pin 2 and pin 3 of the 
> op-amp.

Hi Steve,

This is not gtk3 specific, but comes from the rounding issues in
Eeschema new drawing code (both OpenGL and Cairo). Unfortunately proper
solutions are not trivial. One can mask it bearably by using Cairo
drawing with anti-aliasing turned on (at least on 4k resolutions).

-Vesa

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] 5.1 bug triage

[Wayne Stambaugh]

For final preparation of the 5.1 release, I just did a quick search of
bug reports[1] that have not been closed or assigned to a milestone.
There are a few reports with critical and high priority which I believe
have been fixed.  If you are aware that any of these bug reports have
been fixed, please update the status of the bug reports.  I just want to
make sure we didn't miss anything.

Cheers,

Wayne

[1]
https://bugs.launchpad.net/kicad/+bugs?field.searchtext==-importance%3Alist=NEW%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE_option=any=_reporter=_commenter==_subscriber==_combinator=ANY_cve.used=_dupes.used=_dupes=on_me.used=_patch.used=_branches.used=_branches=on_no_branches.used=_no_branches=on_blueprints.used=_no_blueprints.used=_no_blueprints=on=Search

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0-rc1

[Seth Hillbrand]

Am 2019-02-07 11:04, schrieb Steven A. Falco:

I've posted a patch for the Fedora nightlies to enable
gtk3/wxpython4/python3 and to turn on scripting:

https://github.com/KiCad/fedora-packaging/pull/26

However, because of the eeschema line-width issues that I mentioned
yesterday, I'm not convinced that users will be happy with gtk3.

In the attached screenshot, compare the line width at pin 2 and pin 3
of the op-amp.

Steve



Steve-

I don't think that the line width issue is gtk3-specific.  Do you not 
observe the issue with gtk2?


-Seth

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0-rc1

[Steven A. Falco]

I've posted a patch for the Fedora nightlies to enable gtk3/wxpython4/python3 
and to turn on scripting:

https://github.com/KiCad/fedora-packaging/pull/26

However, because of the eeschema line-width issues that I mentioned yesterday, 
I'm not convinced that users will be happy with gtk3.

In the attached screenshot, compare the line width at pin 2 and pin 3 of the 
op-amp.

Steve

On 2/6/19 7:10 PM, Wayne Stambaugh wrote:
> Nick,
> 
> Thanks for the heads up.  It seems there are more gtk3/wxpython4/python3
> builds than I was aware of.
> 
> Cheers,
> 
> Wayne
> 
> On 2/6/2019 5:34 PM, Nick Østergaard wrote:
>> @Wayne
>> It is enabled with phoenix and gtk3 as default for Archlinux AUR
>>
>> @Steven
>> You may find inspiration here:
>> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=kicad-git
>>
>> Make sure to use the correct wxWidgets_CONFIG_EXECUTABLE, I don't
>> remember what they are called on fedora, but I think there are two
>> wx-config binaries on fedora if you have wxgtk with both gtk2 and gtk3.
>>
>> Nick
>>
>> On Wed, 6 Feb 2019 at 22:59, Steven A. Falco > > wrote:
>>
>> On 2/6/19 2:38 PM, Carsten Schoenert wrote:
>> > Am 06.02.19 um 20:00 schrieb Wayne Stambaugh:
>> >> Any idea the number of unique downloads?  I'm guessing not many users
>> >> install from experimental.
>> >
>> > Yes, people need to know that they want to use a version from
>> > experimental, so the base is rather small. But I can't say anything
>> > about the user base that is using the version from testing/unstable
>> > and/or experimental.
>> > Looking at the pocon chart for kicad and kiacd-libraries in detail
>> there
>> > are about 900 installations of the package kicad-libraries that is
>> only
>> > available since version 5.0.0. Given that there are about 3000 kicad
>> > installations recorded than that means that over 60% are using older
>> > versions.
>> >
>> > https://qa.debian.org/popcon.php?package=kicad
>> >
>> > But popcon only is a bad indicator as it's up to the user to
>> contribute,
>> > we wont see data from people that don't can submit data because of
>> > firewalls etc.
>> > The popcon chart has made some bump after the packages of version 5.0
>> > hit the archive and are currently quite near the all time high.
>> >
>> > You would need also to have a look into all the downstreams of Debian,
>> > the biggest is of course Ubuntu. So it's difficult to say how big the
>> > user base on Kicad 5.x on Debian and downstreams really is.
>> >
>> > ...
>> >> I'm not sure what the issue is with glm and gcc but it has been
>> rather
>> >> annoying.  Hopefully clang wont make any changes that breaks the
>> build.
>> >
>> > I can build the current head with clang and also can use the output as
>> > usual. So far I've understand the problem it's "just" because of
>> the C++
>> > standard. I've seen some more warnings (than build with gcc) while
>> build
>> > was running.
>> >
>>
>> I tried running a Fedora build with wxGTK3 and that seemed to go
>> ok.  I then tried enabling KICAD_SCRIPTING_WXPYTHON_PHOENIX, but I'm
>> not sure what library KiCad is looking for.  I get this:
>>
>> ModuleNotFoundError: No module named 'wx'
>> CMake Error at CMakeModules/FindwxPython.cmake:52 (message):
>>   wxPython/Phoenix does not appear to be installed on the system
>>
>> I'll try to figure it out, but if anyone has a suggestion of what
>> the library package might be called, that would help.
>>
>>         Steve
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@lists.launchpad.net
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New lead developer announcement.

[John Beard]

Hi Wayne and Team,

I'm really happy to have been extended this honour. I look forward to
being part of the great things coming!

Cheers,

John

On Thu, Feb 7, 2019 at 1:32 PM Wayne Stambaugh  wrote:
>
> I am happy to announce that John Beard has accepted the offer to join
> the KiCad lead development team.  John's contributions have proven that
> he will be a valuable asset to the project.  Congratulations John and
> welcome to the lead development team.  We look forward to your continued
> contributions to KiCad.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New lead developer announcement.

[Seth Hillbrand]

Congratulations John!  This is well deserved and I'm looking forward to working with you.-S___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New lead developer announcement.

[Adam Wolf]

Congrats John!

On Thu, Feb 7, 2019 at 7:32 AM Wayne Stambaugh  wrote:

> I am happy to announce that John Beard has accepted the offer to join
> the KiCad lead development team.  John's contributions have proven that
> he will be a valuable asset to the project.  Congratulations John and
> welcome to the lead development team.  We look forward to your continued
> contributions to KiCad.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New lead developer announcement.

[Maciej Suminski]

Excellent! I have been looking forward to John's promotion for some time
already, congratulations!

Cheers,
Orson

On 2/7/19 2:30 PM, Wayne Stambaugh wrote:
> I am happy to announce that John Beard has accepted the offer to join
> the KiCad lead development team.  John's contributions have proven that
> he will be a valuable asset to the project.  Congratulations John and
> welcome to the lead development team.  We look forward to your continued
> contributions to KiCad.
> 
> Cheers,
> 
> Wayne
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New lead developer announcement.

[Jeff Young]

Welcome, John!  Glad to have you on board.

Cheers,
Jeff.


> On 7 Feb 2019, at 13:52, Javier Serrano  
> wrote:
> 
> Congratulations John! And thanks for all the great work so far.
> 
> Javier
> 
> PS. I don't know if somebody already posted this. The video of Wayne's talk 
> in FOSDEM is already online:
> https://video.fosdem.org/2019/AW1.125/kicad.mp4 
> 
> https://video.fosdem.org/2019/AW1.125/kicad.webm 
> 
> On Thu, Feb 7, 2019 at 2:32 PM Wayne Stambaugh  > wrote:
> I am happy to announce that John Beard has accepted the offer to join
> the KiCad lead development team.  John's contributions have proven that
> he will be a valuable asset to the project.  Congratulations John and
> welcome to the lead development team.  We look forward to your continued
> contributions to KiCad.
> 
> Cheers,
> 
> Wayne
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers 
> 
> Post to : kicad-developers@lists.launchpad.net 
> 
> Unsubscribe : https://launchpad.net/~kicad-developers 
> 
> More help   : https://help.launchpad.net/ListHelp 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New lead developer announcement.

[Javier Serrano]

Congratulations John! And thanks for all the great work so far.

Javier

PS. I don't know if somebody already posted this. The video of Wayne's talk
in FOSDEM is already online:
https://video.fosdem.org/2019/AW1.125/kicad.mp4
https://video.fosdem.org/2019/AW1.125/kicad.webm

On Thu, Feb 7, 2019 at 2:32 PM Wayne Stambaugh  wrote:

> I am happy to announce that John Beard has accepted the offer to join
> the KiCad lead development team.  John's contributions have proven that
> he will be a valuable asset to the project.  Congratulations John and
> welcome to the lead development team.  We look forward to your continued
> contributions to KiCad.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] New lead developer announcement.

[Wayne Stambaugh]

I am happy to announce that John Beard has accepted the offer to join
the KiCad lead development team.  John's contributions have proven that
he will be a valuable asset to the project.  Congratulations John and
welcome to the lead development team.  We look forward to your continued
contributions to KiCad.

Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp