Re: [Kicad-developers] 5.1.5 released.

2019-11-27 Thread Tim Hawkins
Is there a roadmap and timeline for 6.0 publicaly available? On Thu, Nov 28, 2019, 9:30 AM Steven A. Falco, wrote: > Perfect timing. The Fedora 30 and 31 builds of 5.1.5 just made it into > the downstream stable repository. It will take some hours to sync out to > all the mirrors, but should

Re: [Kicad-developers] 5.1.5 released.

2019-11-27 Thread Steven A. Falco
Perfect timing. The Fedora 30 and 31 builds of 5.1.5 just made it into the downstream stable repository. It will take some hours to sync out to all the mirrors, but should be there soon. Steve On 11/27/19 6:46 PM, Wayne Stambaugh wrote: > KiCad 5.1.5 has officially been released[1].

Re: [Kicad-developers] New border/title blocks?

2019-11-27 Thread Ian McInerney
They appear to be packaged in the update to Fedora, but I don't have a Windows install handy to test on to verify what I see there: /usr/share/kicad/demos/interf_u/pagelayout_logo.kicad_wks /usr/share/kicad/template/A2_ISO5457-1999_ISO7200-2004-compact_ASMEY1435-2014_EN.kicad_wks

Re: [Kicad-developers] New border/title blocks?

2019-11-27 Thread Mark Roszko
> Nick, is packaging Windows your domain? Is there any way I could help to get them included in an updated 5.1.5 release or 5.1.6? I know the GitLab stuff is taking a lot of time from everybody but I don't want to let this wither away. He is the main mainter yes. If you want to help him.

Re: [Kicad-developers] New border/title blocks?

2019-11-27 Thread Evan Shultz
In 5.1.5_2, on Windows, I don't see these new page layouts. So at least in Windows this wasn't packaged. I don't know about other OSes. Perhaps there's a way to make this more obvious so that when new page layouts are available all packagers are aware? The discussion above reads to me like the

Re: [Kicad-developers] Packaging for GitLab migration

2019-11-27 Thread Nick Østergaard
I think all of the PPA build definitions are on Jean-Samuels account on launchpad. I think this repo is used for the nightlies: https://code.launchpad.net/~js-reynaud/+git/kicad-daily-pkg I think you can make a merge request on lp. On Wed, 27 Nov 2019 at 21:46, Seth Hillbrand wrote: > Hi All-

[Kicad-developers] 5.1.5 released.

2019-11-27 Thread Wayne Stambaugh
KiCad 5.1.5 has officially been released[1]. Thank you to everyone who contributed your time and talent to make this release possible. Cheers, Wayne [1]: https://www.kicad-pcb.org/blog/2019/11/KiCad-5.1.5-Release/ ___ Mailing list:

Re: [Kicad-developers] KiCad joins the Linux Foundation

2019-11-27 Thread Mark Roszko
Aye it's fine for me. I only mentioned the guidelines because they want "The" and unfortunately their name would honestly be easier without it haha. On Wed, Nov 27, 2019 at 6:29 PM Seth Hillbrand wrote: > Added a mobile-friendly version that complies with TLF trademark > guidelines. > > Thanks

Re: [Kicad-developers] Fix lp:1849376

2019-11-27 Thread Jeff Young
Didn’t someone do a couple of icons recently that looked nice? Ian or Michael maybe? (I was hoping to get a new icon for something or another too, although I can’t remember what now….) > On 27 Nov 2019, at 08:00, Franck Jullien wrote: > >> I took a look at the intersheet reference patch and

Re: [Kicad-developers] KiCad joins the Linux Foundation

2019-11-27 Thread Seth Hillbrand
Added a mobile-friendly version that complies with TLF trademark guidelines.Thanks Nick for the quick review.  Let me know if this works for everyone.-SOn Nov 27, 2019 11:07 AM, Wayne Stambaugh wrote:I see that now, at least when your phone is in portrait mode.  I'm guessing we don't support

Re: [Kicad-developers] windows 32-bit builds

2019-11-27 Thread Ian McInerney
Technically Windows 10 has a 32-bit edition, and we specify we support all of Windows 10. How long Microsoft keeps up a 32-bit release is anyone's guess though. So we can't really cut out 32-bit releases yet (and I think even JP still has a 32-bit machine he uses). -Ian On Wed, Nov 27, 2019 at

Re: [Kicad-developers] windows 32-bit builds

2019-11-27 Thread Eeli Kaikkonen
Based on this poll: https://forum.kicad.info/t/which-windows-version-you-are-using-kicad-v5-or-newer-on/15618 there really have been some 32bit KiCad users. What do the download statistics say? The situation will change considerably when Win7 support will end. Most of the 32bit installations have

[Kicad-developers] Packaging for GitLab migration

2019-11-27 Thread Seth Hillbrand
Hi All- We're looking at timelines now for GitLab migration.  One thing we'd like to ensure is that the nightlight builds are still available. Toward that end, I've submitted a couple PRs for updating the git repository to the new GitLab location in the Fedora and Mac builds. It looks like

Re: [Kicad-developers] GitLab migration

2019-11-27 Thread Seth Hillbrand
On 11/27/19 11:42 AM, Rene Pöschl wrote: On 26/11/2019 21:54, Seth Hillbrand wrote: On 2019-11-26 12:41, Jeff Young wrote: OK, I’ve enabled 2FA.  Do I need to do something to get added back to the project?  (When I go to members, all I see are the bot, Seth and Wayne.) Cheers, Jeff. Hi Jeff-

Re: [Kicad-developers] GitLab migration

2019-11-27 Thread Wayne Stambaugh
Hi Rene, On 11/27/19 2:42 PM, Rene Pöschl wrote: > On 26/11/2019 21:54, Seth Hillbrand wrote: >> On 2019-11-26 12:41, Jeff Young wrote: >>> OK, I’ve enabled 2FA.  Do I need to do something to get added back to >>> the project?  (When I go to members, all I see are the bot, Seth and >>> Wayne.)

Re: [Kicad-developers] GitLab migration

2019-11-27 Thread Rene Pöschl
On 26/11/2019 21:54, Seth Hillbrand wrote: On 2019-11-26 12:41, Jeff Young wrote: OK, I’ve enabled 2FA. Do I need to do something to get added back to the project? (When I go to members, all I see are the bot, Seth and Wayne.) Cheers, Jeff. Hi Jeff- Wayne and the bot have permissions for

Re: [Kicad-developers] ***UNCHECKED*** Re: GitLab migration

2019-11-27 Thread Wayne Stambaugh
Before we entertain the idea of pursuing this (I'm neither suggesting that we should or shouldn't), what would be the harm in seeing if our 55K of CI pipeline is an issue? If it is, then we can discuss using an Azure pipeline. On 11/27/19 1:18 PM, Mark Roszko wrote: > Honestly, it would be

Re: [Kicad-developers] KiCad joins the Linux Foundation

2019-11-27 Thread Wayne Stambaugh
I see that now, at least when your phone is in portrait mode. I'm guessing we don't support mobile platforms specifically so we should probably leave the buttons as is. I wonder how may users have actually donated using their phone. On 11/27/19 11:23 AM, Nick Østergaard wrote: > I am on a

[Kicad-developers] windows 32-bit builds

2019-11-27 Thread Mark Roszko
Just throwing it out there. Is there any point in continuing 32-bit builds for Windows? 64-bit has been the default arch for over a decade on Windows now. Linux distros are in the process of purging 32-bit. macOS threw 32-bit into a deep dark hole this year. Pros: 1. Don't need to package twice

Re: [Kicad-developers] KiCad joins the Linux Foundation

2019-11-27 Thread Mark Roszko
I was debating it. It's visually weird to repeat "CERN" and "The Linux Foundation" as a section header and then in the button though. Side note: Legally, we have to say "The Linux Foundation" per their policy. https://www.linuxfoundation.org/trademark-usage/ Even technically need the silly

Re: [Kicad-developers] ***UNCHECKED*** Re: GitLab migration

2019-11-27 Thread Mark Roszko
Honestly, it would be awesome if we leveraged Azure Pipelines. For OSS it provides *unlimited minutes of* *Windows, OSX,Linux builds with up to 10 parallel jobs at a time.* Though the integration may not be as nice as it is with GitHub. But it blows away just a single build box and the standard

Re: [Kicad-developers] Plugin/3rd party content manager

2019-11-27 Thread Seth Hillbrand
On 11/27/19 1:19 AM, Eeli Kaikkonen wrote: Feel free to contact me through email or otherwise. Although I'm not really a python developer any more than a C++ developer (I have done some of both), in this context I'm personally more interested in getting the python part of KiCad forward.

Re: [Kicad-developers] Plugin/3rd party content manager

2019-11-27 Thread Seth Hillbrand
On 11/27/19 12:15 AM, mitjan696-ubu...@yahoo.co.uk wrote: Hi Seth, This does sound like an invitation. I've written a number of action plugins [1] and would be glad to help with KiCad main code, but my C++ skills are nonexistent (I do know a bit of C though, so the basic syntax should not be

Re: [Kicad-developers] ***UNCHECKED*** Re: GitLab migration

2019-11-27 Thread Seth Hillbrand
On 11/27/19 6:14 AM, Wayne Stambaugh wrote: On 11/27/19 6:28 AM, Simon Richter wrote: Hi Seth, On Tue, Nov 26, 2019 at 12:54:31PM -0800, Seth Hillbrand wrote: Wayne and the bot have permissions for the entire project. I'm there while sorting out the transition work. Coding permissions are

Re: [Kicad-developers] KiCad joins the Linux Foundation

2019-11-27 Thread Nick Østergaard
I am on a mobile screen ons. 27. nov. 2019 17.01 skrev Wayne Stambaugh : > I don't know how the donate window renders on your combination of > browser and platform but given the width of the window that I'm seeing > using Chrome on Linux, abbreviating Linux Foundation wont reduce the > size of

Re: [Kicad-developers] 5.1.5 release tag

2019-11-27 Thread Wayne Stambaugh
Hi Nick, Thanks, I'm not planning on making any changes to the release announcement so feel free to undraft it as is. Are you going to be able to complete this today? I was also planning on making announcements on some other platforms (Launcpad, User Forum, Twitter, etc.) as well so please ping

Re: [Kicad-developers] KiCad joins the Linux Foundation

2019-11-27 Thread Nick Østergaard
Maybe to keep the button name short use the strings: Donate via TLF Donate via CERN ons. 27. nov. 2019 15.06 skrev Wayne Stambaugh : > Hi Mark, > > I noticed you made some changes to the latest donations window which are > definitely an improvement. I'm wondering if we should also change the >

Re: [Kicad-developers] ***UNCHECKED*** Re: Re: GitLab migration

2019-11-27 Thread Seth Hillbrand
On 2019-11-27 06:48, Simon Richter wrote: Hi Seth, On Wed, Nov 27, 2019 at 06:29:11AM -0800, Seth Hillbrand wrote: >Ah, so that's why my application was ignored. :) Sorry about that Simon. My inbox got flooding with permission applications for folks and I haven't been able to find time

Re: [Kicad-developers] KiCad joins the Linux Foundation

2019-11-27 Thread Wayne Stambaugh
I don't know how the donate window renders on your combination of browser and platform but given the width of the window that I'm seeing using Chrome on Linux, abbreviating Linux Foundation wont reduce the size of the window. If we need to abbreviate to prevent layout issues, that's fine. On

Re: [Kicad-developers] ***UNCHECKED*** Re: Re: GitLab migration

2019-11-27 Thread Simon Richter
Hi Seth, On Wed, Nov 27, 2019 at 06:29:11AM -0800, Seth Hillbrand wrote: > >Ah, so that's why my application was ignored. :) > Sorry about that Simon. My inbox got flooding with permission > applications for folks and I haven't been able to find time yet to > got through all and respond to

Re: [Kicad-developers] ***UNCHECKED*** Re: GitLab migration

2019-11-27 Thread Wayne Stambaugh
On 11/27/19 6:28 AM, Simon Richter wrote: > Hi Seth, > > On Tue, Nov 26, 2019 at 12:54:31PM -0800, Seth Hillbrand wrote: > >> Wayne and the bot have permissions for the entire project. I'm >> there while sorting out the transition work. Coding permissions are >> specific to

Re: [Kicad-developers] ***UNCHECKED*** Re: GitLab migration

2019-11-27 Thread Seth Hillbrand
On 2019-11-27 03:28, Simon Richter wrote: Hi Seth, On Tue, Nov 26, 2019 at 12:54:31PM -0800, Seth Hillbrand wrote: Wayne and the bot have permissions for the entire project. I'm there while sorting out the transition work. Coding permissions are specific to https://gitlab.com/kicad/code/ .

Re: [Kicad-developers] 5.1.5 release tag

2019-11-27 Thread Nick Østergaard
Yes, late tonight in my timezone, tonight not that late in your timezone :) ons. 27. nov. 2019 15.17 skrev Wayne Stambaugh : > Hi Nick, > > Thanks, I'm not planning on making any changes to the release > announcement so feel free to undraft it as is. Are you going to be able > to complete this

Re: [Kicad-developers] KiCad joins the Linux Foundation

2019-11-27 Thread Wayne Stambaugh
Hi Mark, I noticed you made some changes to the latest donations window which are definitely an improvement. I'm wondering if we should also change the donate buttons to "Donate via Linux Foundation" and "Donate via CERN" to distinguish them. I know that they are separated people tend to not

Re: [Kicad-developers] New Official Bug Tracker Tags

2019-11-27 Thread Nick Østergaard
Would it be to controversial to just call it fpedit and symedit? I am not sure I understand why you wanted the hyphen, but I didn't really follow the discussion to much in this thread. What are the other multiword tags in gitlab? On Wed, 27 Nov 2019 at 12:13, Ian McInerney wrote: > I was trying

Re: [Kicad-developers] ***UNCHECKED*** Re: GitLab migration

2019-11-27 Thread Simon Richter
Hi Seth, On Tue, Nov 26, 2019 at 12:54:31PM -0800, Seth Hillbrand wrote: > Wayne and the bot have permissions for the entire project. I'm > there while sorting out the transition work. Coding permissions are > specific to https://gitlab.com/kicad/code/ . Library permissions > are specific to

Re: [Kicad-developers] New Official Bug Tracker Tags

2019-11-27 Thread Ian McInerney
I was trying to avoid creating long tags, and since our current tags seem to be distributed more on the short side (and since in the new GitLab interface the tags are visible next to the issue name, the longer the tag the more UI space it takes up) I was trying to keep them short. (and these new

Re: [Kicad-developers] 5.1.5 release tag

2019-11-27 Thread Nick Østergaard
I just need to make sure they are mirrored to the github tags, so please make it a pr and not mere it before the ci is green if you intend to make the website change. But I will undraft it when everything is good, so if you feed the need to add more info to the announcement please do so as a

Re: [Kicad-developers] Contributing Python to KiCad

2019-11-27 Thread Ian McInerney
Mitja, Thanks for expressing interest, and I would just like to say that you do not have to be a C++ developer to contribute to KiCad. There is a healthy Python presence in both the core codebase (the footprint generators and BoM scripts) as well as the library management systems

Re: [Kicad-developers] Plugin/3rd party content manager

2019-11-27 Thread Eeli Kaikkonen
ke 27. marrask. 2019 klo 1.51 Seth Hillbrand (s...@kipro-pcb.com) kirjoitti: > After the initial > ideas and implementation are documented, it will go to the lead > developers first to ensure everyone agrees with the plan and course of > action. After that, it will be published on the list for

Re: [Kicad-developers] Back annotate references from PCB

2019-11-27 Thread mitjan696-ubu...@yahoo.co.uk
I'll offer my thoughts on the subject bear in mind that I have zero knowledge of KiCad code internals and I could not really follow parts of this discussion. With back-annotation you really have a locking issue. Before re-annotating the layout, you have to make sure that the layout is in sync

Re: [Kicad-developers] [PATCH] Selection appearance options

2019-11-27 Thread Jonatan Liljedahl
Thanks! I will revisit patch #2 and make the selection thickness configurable as well, with a default value that keeps the current appearance. Cheers On Wed, Nov 27, 2019 at 5:06 AM Seth Hillbrand wrote: > > On 2019-11-23 05:46, Jonatan Liljedahl wrote: > > > Thanks Seth, > > > > I'm on Mac

Re: [Kicad-developers] Plugin/3rd party content manager

2019-11-27 Thread mitjan696-ubu...@yahoo.co.uk
Hi Seth, This does sound like an invitation. I've written a number of action plugins [1] and would be glad to help with KiCad main code, but my C++ skills are nonexistent (I do know a bit of C though, so the basic syntax should not be an issue). I've never built KiCad from source and I am

Re: [Kicad-developers] Fix lp:1849376

2019-11-27 Thread Franck Jullien
> I took a look at the intersheet reference patch and it looks like a nice > addition. It will need to wait until after the schematic file format > has been updated as it does introduce new functionality to the format. > We won't be adding new functionality to the existing, legacy schematic >