Re: [Kicad-developers] DRC rules

[mdoesbur]

I've just tested this on a design and the drc-rules is read, which I
know because if I don't add "(version 1)" at the first line I get an
error message. Other than that I doesn't seem to do anything.

I tried to add "(priority 100)" to the rules, but that is refused when
reading the drc file. It's also not clear to me what the clearance
dimension is, so I assumed nanometers.

I've been using a hack to get clearance rules working for some time, so
the design is already pretty large and uses 209 different netclasses. I
did a clean built of 0658d297e528616e233b4074c27f1bdcb870dede,created
drc-rules and edited the pcb file to create all the netclasses. I then
loaded the board and rebuilt the planes, but all the rules seem to
be ignored. I've attached the drc-rules file for reference.

regards,

Mark
(version 1)
(selector (match_netclass "+12V_ui") (match_netclass "+16P") (rule "5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "+800V") (rule "5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "+SOLAR") (rule "5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "/battery/B+") (rule 
"5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "/battery/B-") (rule 
"5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass 
"/battery/Flyback_control/DISABLE") (rule "5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass 
"/battery/Flyback_control/sw") (rule "5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "/battery/M+") (rule 
"5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "/battery/M-") (rule 
"5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "/control/CAN1_N") (rule 
"1mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(J45-Pad1)") (rule 
"5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(J46-Pad1)") (rule 
"5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(J47-Pad1)") (rule 
"5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(J48-Pad1)") (rule 
"5.5mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R15-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R25-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R269-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R270-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R28-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R306-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R426-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R429-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R432-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R435-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R438-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R440-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R45-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R78-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+12V_ui") (match_netclass "Net-(R79-Pad2)") (rule 
"1.3mm"))
(selector (match_netclass "+16P") (match_netclass "+800V") (rule "2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/NEUTRAL_out") (rule 
"1.3mm"))
(selector (match_netclass "+16P") (match_netclass "/Vin-") (rule "5.5mm"))
(selector (match_netclass "+16P") (match_netclass "/balancer/GH+") (rule 
"2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/battery/B-") (rule "5.5mm"))
(selector (match_netclass "+16P") (match_netclass "/battery/Flyback/sw") (rule 
"5.5mm"))
(selector (match_netclass "+16P") (match_netclass "/battery/M+") (rule "5.5mm"))
(selector (match_netclass "+16P") (match_netclass "/battery/M-") (rule "2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/flyback_mains/sw") (rule 
"5.5mm"))
(selector (match_netclass "+16P") (match_netclass "/half-bridge1/-5V_hs") (rule 
"2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/half-bridge2/-5V_hs") (rule 
"2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/half-bridge3/-5V_hs") (rule 
"2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/solar0/hv") (rule "2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/solar0/pf1") (rule "2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/solar0/pf2") (rule "2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/solar0/sw1") (rule "2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/solar0/sw2") (rule "2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/solar1/hv") (rule "2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/solar1/pf1") (rule "2.4mm"))
(selector (match_netclass "+16P") (match_netclass "/sol

Re: [Kicad-developers] DRC rules

[Jeff Young]

Hi Mark,

Clearances are in mm, so your clearances are *really* big.  At a guess I’d say 
all the clearances are overflow when we multiply them by mm-to-nm, but I’d 
think that would give random results not no results.

You shouldn’t need to set a priority unless you’re authoring a “relaxed” 
constraint (for instance, spacing can be decreased near a BGA).  But in any 
case (priority x) goes in the selector, not the rule.

I see some lines of the form: (match_netclass "Net-(R79-Pad2)”).  Did you 
create netclass to match the net names, or are you trying to match against a 
specific net?  (The later isn’t implemented, although maybe it needs to be.)

Let me know how it goes with smaller clearances.  If it still doesn’t work I 
may need a copy of your project to debug.

Cheers,
Jeff.


> On 18 May 2020, at 10:18, mdoes...@xs4all.nl wrote:
> 
> I've just tested this on a design and the drc-rules is read, which I
> know because if I don't add "(version 1)" at the first line I get an
> error message. Other than that I doesn't seem to do anything.
> 
> I tried to add "(priority 100)" to the rules, but that is refused when
> reading the drc file. It's also not clear to me what the clearance
> dimension is, so I assumed nanometers.
> 
> I've been using a hack to get clearance rules working for some time, so
> the design is already pretty large and uses 209 different netclasses. I
> did a clean built of 0658d297e528616e233b4074c27f1bdcb870dede,created
> drc-rules and edited the pcb file to create all the netclasses. I then
> loaded the board and rebuilt the planes, but all the rules seem to
> be ignored. I've attached the drc-rules file for reference.
> 
> regards,
> 
> Mark
> 


___
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] DRC rules

[mdoesbur]

Hello Jeff,

Seems easy to reproduce, so here is a test project.  There are just two
netclasses and three nets. I expected the cutout in the zone to create
a 1.3mm clearance for Net-(R1-Pad2).

regards,

Mark.

___
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] DRC rules

[mdoesbur]

Sorry, forgot to attach the project.


<>
___
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] Build Server for MacOS

[S.Weber]

Hello KiCad team,

I am new to kicad and was thinking about helping with the MacOS CI.

Ian McInerney was mentioning on https://gitlab.com/kicad/code/kicad/-/merge_requests/218 
that "currently there are no reliable macOS CI solutions for KiCad".


We don't currently have a reliable macOS CI solution. GitLab doesn't provide 
one out of the box, and the nightly build server sometimes has issues that 
aren't related to the code, but instead to packaging.


I am wondering if someone is working on a "new" macOS CI or do have some 
experience there?

I found two CIs provider which are free for MacOS open-source Projects:

https://travis-ci.com/plans

https://www.appveyor.com/pricing/

=> appveyor seems to directly support gitlab
=> travis only supports github => build needs to go over github mirror of kicad 
repo..

So I think appveyor might be worth a try.

What do you think?


Stefan

___
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] Build Server for MacOS

[Nick Østergaard]

Hi Stefan

Do you have a macos yourself? If yes, you are probably better off
starting with resolving issues at
https://gitlab.com/kicad/packaging/kicad-mac-builder/-/issues

Adam Wolf got some new hardware for building for macos, the plan is to
add it as a gitlab runner. This has not been done yet.

Nick

On Mon, 18 May 2020 at 19:17, S.Weber  wrote:
>
> Hello KiCad team,
>
> I am new to kicad and was thinking about helping with the MacOS CI.
>
> Ian McInerney was mentioning on 
> https://gitlab.com/kicad/code/kicad/-/merge_requests/218 that "currently 
> there are no reliable macOS CI solutions for KiCad".
>
> >We don't currently have a reliable macOS CI solution. GitLab doesn't provide 
> >one out of the box, and the nightly build server sometimes has issues that 
> >aren't related to the code, but instead to packaging.
>
> I am wondering if someone is working on a "new" macOS CI or do have some 
> experience there?
>
> I found two CIs provider which are free for MacOS open-source Projects:
>
> https://travis-ci.com/plans
>
> https://www.appveyor.com/pricing/
>
> => appveyor seems to directly support gitlab
> => travis only supports github => build needs to go over github mirror of 
> kicad repo..
>
> So I think appveyor might be worth a try.
>
> What do you think?
>
>
> Stefan
>
> ___
> 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] Requesting maintainership for KiCad manifest on flathub.org

[Nick Østergaard]

Yeah, hence there are probably no one here that can give you
maintainer ship, unfortunately. :/

On Sat, 16 May 2020 at 16:10, Johannes Maibaum  wrote:
>
> Hi Nick,
>
> Am Samstag, den 16.05.2020, 15:50 +0200 schrieb Nick Østergaard:
>
> I am not aware of who the maintainer of the flatpak is, nor do I think he may 
> follow this list closely.
>
>
> From what I can say, so far the flatpak has been maintained by whoever sent 
> in a PR, and it was updated whenever one of the main flathub maintainers 
> found time to review the PR.
>
> Johannes
>
>
> But it would certanly be good to get the package updated to be on part with 
> other packages.
>
> Nick
>
> lør. 16. maj 2020 12.27 skrev Johannes Maibaum :
>
> Hello KiCad team,
>
> during the past months, I have been updating the KiCad flatpak on
> flathub.org from time to time, via PRs to
> https://github.com/flathub/org.kicad_pcb.KiCad (I am preparing the
> update to KiCad 5.1.6 right now as well).
>
> There are a few pending issues with the current flatpak build manifest
> for KiCad which I'd like to address: Activating Python scripting
> support, adding the docs, and generally updating various dependencies
> would be my next steps.
>
> I was recently being asked by another user if I would like to request
> the maintainership of the KiCad manifest on flathub, and I am now
> contemplating to do so. But, since I did only contribute a few tiny-tiny
> things to KiCad in the past, I wanted to ask the core
> packagers/developers first, if anyone else would take over the
> maintainership instead?
>
>
> Cheers,
> Johannes
> ___
> 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] DRC rules

[Jeff Young]

Congrats on the first bug!

Actually 4 separate ones: the caching mechanism was causing the rules to not be 
loaded when the board was read, the zone cutout stuff wasn’t fully hooked up to 
the new rules engine, there’s no "Net-(C1-Pad2)" netclass in the document (only 
"Net-(C1-Pad1)”), and the code responded poorly to failing to find a net 
(putting subsequent nets off-by-one).

The third one is yours. ;)

Fixes for the other three are now in master (if you build your own); otherwise 
you can get them from tonight’s nightly.

Cheers,
Jeff.

> On 18 May 2020, at 12:01, mdoes...@xs4all.nl wrote:
> 
> Sorry, forgot to attach the project.
> 
> 
> 


___
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] DRC rules

[mdoesbur]

Excellent, now it works :-)

I'll test the big board tomorrow. For me this was the most important
feature missing from kicad, thanks for making it work.

regards,

Mark.

Jeff Young  wrote:

Congrats on the first bug!

Actually 4 separate ones: the caching mechanism was causing the rules 
to not be loaded when the board was read, the zone cutout stuff wasn???t fully 
hooked up to the new rules engine, there???s no "Net-(C1-Pad2)" netclass in the 
document (only "Net-(C1-Pad1)???), and the code responded poorly to failing to 
find a net (putting subsequent nets off-by-one).

The third one is yours. ;)

Fixes for the other three are now in master (if you build your own); 
otherwise you can get them from tonight???s nightly.

Cheers,
Jeff.

> On 18 May 2020, at 12:01, mdoes...@xs4all.nl wrote:
> 
> Sorry, forgot to attach the project.
> 
> 
> 

___
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] Build Server for MacOS

[Mark Roszko]

90% chance AppVeyor won't work because its build time restricted to 60
minutes. And KiCad builds quite slowly on the free services taht only
provide 1 or 2 cores.


An alternative, there's also the Azure Pipelines KiCad account where I run
Coverity. It has unlimited minutes for open source project and provides
macOS/Linux/Windows VMs with up to 10 parallel jobs at a time.


On Mon, May 18, 2020 at 1:23 PM Nick Østergaard  wrote:

> Hi Stefan
>
> Do you have a macos yourself? If yes, you are probably better off
> starting with resolving issues at
> https://gitlab.com/kicad/packaging/kicad-mac-builder/-/issues
>
> Adam Wolf got some new hardware for building for macos, the plan is to
> add it as a gitlab runner. This has not been done yet.
>
> Nick
>
> On Mon, 18 May 2020 at 19:17, S.Weber  wrote:
> >
> > Hello KiCad team,
> >
> > I am new to kicad and was thinking about helping with the MacOS CI.
> >
> > Ian McInerney was mentioning on
> https://gitlab.com/kicad/code/kicad/-/merge_requests/218 that "currently
> there are no reliable macOS CI solutions for KiCad".
> >
> > >We don't currently have a reliable macOS CI solution. GitLab doesn't
> provide one out of the box, and the nightly build server sometimes has
> issues that aren't related to the code, but instead to packaging.
> >
> > I am wondering if someone is working on a "new" macOS CI or do have some
> experience there?
> >
> > I found two CIs provider which are free for MacOS open-source Projects:
> >
> > https://travis-ci.com/plans
> >
> > https://www.appveyor.com/pricing/
> >
> > => appveyor seems to directly support gitlab
> > => travis only supports github => build needs to go over github mirror
> of kicad repo..
> >
> > So I think appveyor might be worth a try.
> >
> > What do you think?
> >
> >
> > Stefan
> >
> > ___
> > 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
>


-- 
Mark
___
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] Build Server for MacOS

[Adam Wolf]

I provide the release builder and nightlies builder for macOS for
KiCad.  I would love to have the macOS build cluster also provide CI
checks for branches and builds!

A few months ago, the second machine in the cluster broke.  The first
machine is able to keep up with nightlies, but cannot do any builds
beyond that.  I have purchased another (expensive...) system for the
cluster.  I'll be adding it into the cluster soon, but I am located in
the United States and my business, where some of these machines are
located, is not easily accessible due to the lockdown.  Additionally,
I have two young children who no longer have school or childcare, and
my KiCad time has approached zero.  I was able to get the 5.1.6
release out last week on time, which, to non-parents right now, may
seem like a regular accomplishment, but to me, this was a Herculean
effort.

kicad-mac-builder is primarily used for making release builds on
macOS.  These needs are similar but also much more extensive than the
needs for development or "does this build/test fine".  I've been doing
this for quite a few years now, and I am continually impressed by the
new and different ways that release builds of something of KiCad's
magnitude can break on macOS.  (Because of that, the nightly and
release macOS builds are performed in their own VM, each time, with
all the dependencies built each time.  This sounds like dramatic
overkill to everyone except for people who package and distribute
macOS software outside of Xcode.)

If you're interested in helping out, I would love some extra help.  If
you want to try some third-party services, awesome.  It will be much
easier to get kicad to build in a third-party CI service than to get
kicad packaged, so I would suggest starting there.

If you want to work on kicad-mac-builder so that I have more time for
doing things like "setting up the build cluster", that's awesome too.
There's a good balance of small and big issues on the issue tracker,
and I can usually respond within a day, Monday through Thursday.
nickoe has been helping out lately too, and he seems to be available
at all hours within a few seconds ;)

Adam Wolf

On Mon, May 18, 2020 at 2:31 PM Mark Roszko  wrote:
>
> 90% chance AppVeyor won't work because its build time restricted to 60 
> minutes. And KiCad builds quite slowly on the free services taht only provide 
> 1 or 2 cores.
>
>
> An alternative, there's also the Azure Pipelines KiCad account where I run 
> Coverity. It has unlimited minutes for open source project and provides 
> macOS/Linux/Windows VMs with up to 10 parallel jobs at a time.
>
>
> On Mon, May 18, 2020 at 1:23 PM Nick Østergaard  wrote:
>>
>> Hi Stefan
>>
>> Do you have a macos yourself? If yes, you are probably better off
>> starting with resolving issues at
>> https://gitlab.com/kicad/packaging/kicad-mac-builder/-/issues
>>
>> Adam Wolf got some new hardware for building for macos, the plan is to
>> add it as a gitlab runner. This has not been done yet.
>>
>> Nick
>>
>> On Mon, 18 May 2020 at 19:17, S.Weber  wrote:
>> >
>> > Hello KiCad team,
>> >
>> > I am new to kicad and was thinking about helping with the MacOS CI.
>> >
>> > Ian McInerney was mentioning on 
>> > https://gitlab.com/kicad/code/kicad/-/merge_requests/218 that "currently 
>> > there are no reliable macOS CI solutions for KiCad".
>> >
>> > >We don't currently have a reliable macOS CI solution. GitLab doesn't 
>> > >provide one out of the box, and the nightly build server sometimes has 
>> > >issues that aren't related to the code, but instead to packaging.
>> >
>> > I am wondering if someone is working on a "new" macOS CI or do have some 
>> > experience there?
>> >
>> > I found two CIs provider which are free for MacOS open-source Projects:
>> >
>> > https://travis-ci.com/plans
>> >
>> > https://www.appveyor.com/pricing/
>> >
>> > => appveyor seems to directly support gitlab
>> > => travis only supports github => build needs to go over github mirror of 
>> > kicad repo..
>> >
>> > So I think appveyor might be worth a try.
>> >
>> > What do you think?
>> >
>> >
>> > Stefan
>> >
>> > ___
>> > 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
>
>
>
> --
> Mark
> ___
> 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

___
Mail

Re: [Kicad-developers] Requesting maintainership for KiCad manifest on flathub.org

[Johannes Maibaum]

Am Montag, den 18.05.2020, 19:35 +0200 schrieb Nick Østergaard:
> Yeah, hence there are probably no one here that can give you
> maintainer ship, unfortunately. :/

My original intent for asking here was not asking someone on this list
to give me maintainer rights, but rather if somebody from the core
packagers/devs would be wanting to take over the flathub maintainership
themselves.

Anyhow, I have just asked over on flathub [1] if they would be giving me
maintainership rights. Let's see what comes out of this.

Johannes

[1]: https://github.com/flathub/flathub/issues/1527

> 
> On Sat, 16 May 2020 at 16:10, Johannes Maibaum 
> wrote:
> > Hi Nick,
> > 
> > Am Samstag, den 16.05.2020, 15:50 +0200 schrieb Nick Østergaard:
> > 
> > I am not aware of who the maintainer of the flatpak is, nor do I
> > think he may follow this list closely.
> > 
> > 
> > From what I can say, so far the flatpak has been maintained by
> > whoever sent in a PR, and it was updated whenever one of the main
> > flathub maintainers found time to review the PR.
> > 
> > Johannes
> > 
> > 
> > But it would certanly be good to get the package updated to be on
> > part with other packages.
> > 
> > Nick
> > 
> > lør. 16. maj 2020 12.27 skrev Johannes Maibaum :
> > 
> > Hello KiCad team,
> > 
> > during the past months, I have been updating the KiCad flatpak on
> > flathub.org from time to time, via PRs to
> > https://github.com/flathub/org.kicad_pcb.KiCad (I am preparing the
> > update to KiCad 5.1.6 right now as well).
> > 
> > There are a few pending issues with the current flatpak build
> > manifest
> > for KiCad which I'd like to address: Activating Python scripting
> > support, adding the docs, and generally updating various
> > dependencies
> > would be my next steps.
> > 
> > I was recently being asked by another user if I would like to
> > request
> > the maintainership of the KiCad manifest on flathub, and I am now
> > contemplating to do so. But, since I did only contribute a few tiny-
> > tiny
> > things to KiCad in the past, I wanted to ask the core
> > packagers/developers first, if anyone else would take over the
> > maintainership instead?
> > 
> > 
> > Cheers,
> > Johannes
> > ___
> > 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] Requesting maintainership for KiCad manifest on flathub.org

[Johannes Maibaum]

Wow, that was quick. I got added as a collaborator.

And I have just merged the update to v5.1.6 on flathub. This should hit
flatpak users as soon as some build machine does the job. It will still
lack all of the open issues, like no Python scripting support, no docs,
among a few other things), but I will start tackling them during the
next few days.

Let me just repeat in case I wasn't getting through my point before: If
anyone from the core team wants to maintain 
https://github.com/flathub/org.kicad_pcb.KiCad please let me know.

Apart from that I will try doing my best as flatpak packager from now
on.

Johannes

Am Montag, den 18.05.2020, 22:16 +0200 schrieb Johannes Maibaum:
> Am Montag, den 18.05.2020, 19:35 +0200 schrieb Nick Østergaard:
> > Yeah, hence there are probably no one here that can give you
> > maintainer ship, unfortunately. :/
> 
> My original intent for asking here was not asking someone on this list
> to give me maintainer rights, but rather if somebody from the core
> packagers/devs would be wanting to take over the flathub
> maintainership
> themselves.
> 
> Anyhow, I have just asked over on flathub [1] if they would be giving
> me
> maintainership rights. Let's see what comes out of this.
> 
> Johannes
> 
> [1]: https://github.com/flathub/flathub/issues/1527
> 
> > On Sat, 16 May 2020 at 16:10, Johannes Maibaum 
> > wrote:
> > > Hi Nick,
> > > 
> > > Am Samstag, den 16.05.2020, 15:50 +0200 schrieb Nick Østergaard:
> > > 
> > > I am not aware of who the maintainer of the flatpak is, nor do I
> > > think he may follow this list closely.
> > > 
> > > 
> > > From what I can say, so far the flatpak has been maintained by
> > > whoever sent in a PR, and it was updated whenever one of the main
> > > flathub maintainers found time to review the PR.
> > > 
> > > Johannes
> > > 
> > > 
> > > But it would certanly be good to get the package updated to be on
> > > part with other packages.
> > > 
> > > Nick
> > > 
> > > lør. 16. maj 2020 12.27 skrev Johannes Maibaum  > > >:
> > > 
> > > Hello KiCad team,
> > > 
> > > during the past months, I have been updating the KiCad flatpak on
> > > flathub.org from time to time, via PRs to
> > > https://github.com/flathub/org.kicad_pcb.KiCad (I am preparing the
> > > update to KiCad 5.1.6 right now as well).
> > > 
> > > There are a few pending issues with the current flatpak build
> > > manifest
> > > for KiCad which I'd like to address: Activating Python scripting
> > > support, adding the docs, and generally updating various
> > > dependencies
> > > would be my next steps.
> > > 
> > > I was recently being asked by another user if I would like to
> > > request
> > > the maintainership of the KiCad manifest on flathub, and I am now
> > > contemplating to do so. But, since I did only contribute a few
> > > tiny-
> > > tiny
> > > things to KiCad in the past, I wanted to ask the core
> > > packagers/developers first, if anyone else would take over the
> > > maintainership instead?
> > > 
> > > 
> > > Cheers,
> > > Johannes
> > > ___
> > > 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] Requesting maintainership for KiCad manifest on flathub.org

[Jon Evans]

Hi Johannes,

Thank you for offering to take on maintenance of the flathub package.
We are happy to have your help with this, and as far as I know none of
the other lead developers was planning on taking it on.

Please feel free to reach out here if you run into any challenges with
fixing the packaging issues.  I'm not sure how much experience any
of us have with flatpak, but we can do our best to help figure them out.

Best,
Jon

On Mon, May 18, 2020 at 4:33 PM Johannes Maibaum  wrote:

> Wow, that was quick. I got added as a collaborator.
>
> And I have just merged the update to v5.1.6 on flathub. This should hit
> flatpak users as soon as some build machine does the job. It will still
> lack all of the open issues, like no Python scripting support, no docs,
> among a few other things), but I will start tackling them during the
> next few days.
>
> Let me just repeat in case I wasn't getting through my point before: If
> anyone from the core team wants to maintain
> https://github.com/flathub/org.kicad_pcb.KiCad please let me know.
>
> Apart from that I will try doing my best as flatpak packager from now
> on.
>
> Johannes
>
> Am Montag, den 18.05.2020, 22:16 +0200 schrieb Johannes Maibaum:
> > Am Montag, den 18.05.2020, 19:35 +0200 schrieb Nick Østergaard:
> > > Yeah, hence there are probably no one here that can give you
> > > maintainer ship, unfortunately. :/
> >
> > My original intent for asking here was not asking someone on this list
> > to give me maintainer rights, but rather if somebody from the core
> > packagers/devs would be wanting to take over the flathub
> > maintainership
> > themselves.
> >
> > Anyhow, I have just asked over on flathub [1] if they would be giving
> > me
> > maintainership rights. Let's see what comes out of this.
> >
> > Johannes
> >
> > [1]: https://github.com/flathub/flathub/issues/1527
> >
> > > On Sat, 16 May 2020 at 16:10, Johannes Maibaum 
> > > wrote:
> > > > Hi Nick,
> > > >
> > > > Am Samstag, den 16.05.2020, 15:50 +0200 schrieb Nick Østergaard:
> > > >
> > > > I am not aware of who the maintainer of the flatpak is, nor do I
> > > > think he may follow this list closely.
> > > >
> > > >
> > > > From what I can say, so far the flatpak has been maintained by
> > > > whoever sent in a PR, and it was updated whenever one of the main
> > > > flathub maintainers found time to review the PR.
> > > >
> > > > Johannes
> > > >
> > > >
> > > > But it would certanly be good to get the package updated to be on
> > > > part with other packages.
> > > >
> > > > Nick
> > > >
> > > > lør. 16. maj 2020 12.27 skrev Johannes Maibaum  > > > >:
> > > >
> > > > Hello KiCad team,
> > > >
> > > > during the past months, I have been updating the KiCad flatpak on
> > > > flathub.org from time to time, via PRs to
> > > > https://github.com/flathub/org.kicad_pcb.KiCad (I am preparing the
> > > > update to KiCad 5.1.6 right now as well).
> > > >
> > > > There are a few pending issues with the current flatpak build
> > > > manifest
> > > > for KiCad which I'd like to address: Activating Python scripting
> > > > support, adding the docs, and generally updating various
> > > > dependencies
> > > > would be my next steps.
> > > >
> > > > I was recently being asked by another user if I would like to
> > > > request
> > > > the maintainership of the KiCad manifest on flathub, and I am now
> > > > contemplating to do so. But, since I did only contribute a few
> > > > tiny-
> > > > tiny
> > > > things to KiCad in the past, I wanted to ask the core
> > > > packagers/developers first, if anyone else would take over the
> > > > maintainership instead?
> > > >
> > > >
> > > > Cheers,
> > > > Johannes
> > > > ___
> > > > 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] Requesting maintainership for KiCad manifest on flathub.org

[Jeff Young]

Awesome!  Welcome on board, Johannes.

> On 18 May 2020, at 21:42, Jon Evans  wrote:
> 
> Hi Johannes,
> 
> Thank you for offering to take on maintenance of the flathub package.
> We are happy to have your help with this, and as far as I know none of
> the other lead developers was planning on taking it on.
> 
> Please feel free to reach out here if you run into any challenges with
> fixing the packaging issues.  I'm not sure how much experience any
> of us have with flatpak, but we can do our best to help figure them out.
> 
> Best,
> Jon
> 
> On Mon, May 18, 2020 at 4:33 PM Johannes Maibaum  > wrote:
> Wow, that was quick. I got added as a collaborator.
> 
> And I have just merged the update to v5.1.6 on flathub. This should hit
> flatpak users as soon as some build machine does the job. It will still
> lack all of the open issues, like no Python scripting support, no docs,
> among a few other things), but I will start tackling them during the
> next few days.
> 
> Let me just repeat in case I wasn't getting through my point before: If
> anyone from the core team wants to maintain 
> https://github.com/flathub/org.kicad_pcb.KiCad 
>  please let me know.
> 
> Apart from that I will try doing my best as flatpak packager from now
> on.
> 
> Johannes
> 
> Am Montag, den 18.05.2020, 22:16 +0200 schrieb Johannes Maibaum:
> > Am Montag, den 18.05.2020, 19:35 +0200 schrieb Nick Østergaard:
> > > Yeah, hence there are probably no one here that can give you
> > > maintainer ship, unfortunately. :/
> > 
> > My original intent for asking here was not asking someone on this list
> > to give me maintainer rights, but rather if somebody from the core
> > packagers/devs would be wanting to take over the flathub
> > maintainership
> > themselves.
> > 
> > Anyhow, I have just asked over on flathub [1] if they would be giving
> > me
> > maintainership rights. Let's see what comes out of this.
> > 
> > Johannes
> > 
> > [1]: https://github.com/flathub/flathub/issues/1527 
> > 
> > 
> > > On Sat, 16 May 2020 at 16:10, Johannes Maibaum  > > >
> > > wrote:
> > > > Hi Nick,
> > > > 
> > > > Am Samstag, den 16.05.2020, 15:50 +0200 schrieb Nick Østergaard:
> > > > 
> > > > I am not aware of who the maintainer of the flatpak is, nor do I
> > > > think he may follow this list closely.
> > > > 
> > > > 
> > > > From what I can say, so far the flatpak has been maintained by
> > > > whoever sent in a PR, and it was updated whenever one of the main
> > > > flathub maintainers found time to review the PR.
> > > > 
> > > > Johannes
> > > > 
> > > > 
> > > > But it would certanly be good to get the package updated to be on
> > > > part with other packages.
> > > > 
> > > > Nick
> > > > 
> > > > lør. 16. maj 2020 12.27 skrev Johannes Maibaum  > > > 
> > > > >:
> > > > 
> > > > Hello KiCad team,
> > > > 
> > > > during the past months, I have been updating the KiCad flatpak on
> > > > flathub.org  from time to time, via PRs to
> > > > https://github.com/flathub/org.kicad_pcb.KiCad 
> > > >  (I am preparing the
> > > > update to KiCad 5.1.6 right now as well).
> > > > 
> > > > There are a few pending issues with the current flatpak build
> > > > manifest
> > > > for KiCad which I'd like to address: Activating Python scripting
> > > > support, adding the docs, and generally updating various
> > > > dependencies
> > > > would be my next steps.
> > > > 
> > > > I was recently being asked by another user if I would like to
> > > > request
> > > > the maintainership of the KiCad manifest on flathub, and I am now
> > > > contemplating to do so. But, since I did only contribute a few
> > > > tiny-
> > > > tiny
> > > > things to KiCad in the past, I wanted to ask the core
> > > > packagers/developers first, if anyone else would take over the
> > > > maintainership instead?
> > > > 
> > > > 
> > > > Cheers,
> > > > Johannes
> > > > ___
> > > > 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.ne