kicad-developers team mailing list archive

[Jeff Young <jeff@xxxxxxxxx>]

Hi Bernhard,

I’d be happy to help maintain it, but I’m not a Kicad committer so I don’t know if I can ask for write access.

Cheers,
Jeff.


> On 14 Jan 2018, at 20:42, Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx> wrote:
> 
> Hi all,
> 
> after the discussion [1] some while ago (sorry, have been busy since then) Nick created a fork of wxWidgets in KiCad GitHub.
> Before I start to create an (at least initial) branch, I’d like to get some agreements/opinions.
> 
> 1) Branch name
> wxWidgets has a lot of branches (I’ll see if we can delete what we don’t need).
> To be consistent to the usual development flow, I’d propose to add the patches new branches.
> I’d name them 
>   KiCad_<original branch name>
> If we want to emphasise that this is only for macOS, we could also use
>   KiCad_macOS_<original branch name>
> Opinions, decisions (@Wayne)?
> 
> 2) Commits
> The branch should always be rebased to wxWidgets changes, so all patches will stay at the top.
> I still find it somehow difficult to see where original branch ends and own changes start.
> Should we add some prefix “KiCad: …” to all commit messages?
> 
> 3) Patches to add
> I know what patches are mandatory, but didn’t follow 3.0.x for quite a while.
> Especially, I don’t know what patches Adam currently uses for the official builds.
> So, I need some feedback here (most important @Adam).
> 
> Last but not least… if someone else wants to help maintain it, please tell Nick to get write access…
> 
> 
> Regards,
> Bernhard
> 
> [1] https://www.mail-archive.com/kicad-developers@xxxxxxxxxxxxxxxxxxx/msg27348.html <https://www.mail-archive.com/kicad-developers@xxxxxxxxxxxxxxxxxxx/msg27348.html>
> 
> 
> _______________________________________________
> 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