Re: [Kicad-developers] Revisiting the Git decision - document git-bzr bridge!

2014-02-06 Thread Jake
On Thu, 6 Feb 2014, Blair Bonnett wrote: Hi Jake, I think Brian was referring to the GitHub mirror workflow that has been discussed in this thread in the last 24 hours. The following messages are the key ones in this workflow discussion: 1: https://lists.launchpad.net/kicad-developers/msg1214

Re: [Kicad-developers] Revisiting the Git decision - document git-bzr bridge!

2014-02-06 Thread Brian Sidebotham
On 5 February 2014 22:35, Blair Bonnett wrote: > On 6 February 2014 10:31, Jake wrote: >> >> On Wed, 5 Feb 2014, Brian Sidebotham wrote: >> >>> On 5 February 2014 10:11, Jake wrote: I just want to say the same thing that a lot of other people have been saying for a long time. Baz

Re: [Kicad-developers] Revisiting the Git decision

2014-02-05 Thread Povilas Kanapickas
On 02/05/2014 08:25 AM, Miguel Angel wrote: > Well, two interesting things here: > > 1) the git-bzr-ng looks great, we can add some documentation to the > website based on what inkscape provides. > This should make people more used to git happier, and we have an > easy migration path if somet

Re: [Kicad-developers] Revisiting the Git decision - document git-bzr bridge!

2014-02-05 Thread Blair Bonnett
On 6 February 2014 10:31, Jake wrote: > On Wed, 5 Feb 2014, Brian Sidebotham wrote: > > On 5 February 2014 10:11, Jake wrote: >> >>> I just want to say the same thing that a lot of other people have been >>> saying for a long time. Bazaar is holding kicad back. I am yet another >>> developer

Re: [Kicad-developers] Revisiting the Git decision - document git-bzr bridge!

2014-02-05 Thread Jake
On Wed, 5 Feb 2014, Brian Sidebotham wrote: On 5 February 2014 10:11, Jake wrote: I just want to say the same thing that a lot of other people have been saying for a long time. Bazaar is holding kicad back. I am yet another developer who would be contributing to improving the project if it w

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-05 Thread Cirilo Bernardo
> > From: Fabrizio Tappero >To: Cirilo Bernardo >Cc: James Hagerman ; >"kicad-developers@lists.launchpad.net" >Sent: Wednesday, February 5, 2014 8:51 PM >Subject: Re: [Kicad-developers] Revisiting the Git decision (I come in peac

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-05 Thread Brian Sidebotham
On 5 February 2014 10:11, Jake wrote: > I just want to say the same thing that a lot of other people have been > saying for a long time. Bazaar is holding kicad back. I am yet another > developer who would be contributing to improving the project if it weren't > kept in an arcane and frustrating

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-05 Thread Jake
I just want to say the same thing that a lot of other people have been saying for a long time. Bazaar is holding kicad back. I am yet another developer who would be contributing to improving the project if it weren't kept in an arcane and frustrating VCS. So, if you're putting letters like t

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-05 Thread Fabrizio Tappero
es Hagerman > >Cc: "kicad-developers@lists.launchpad.net" < > kicad-developers@lists.launchpad.net> > >Sent: Tuesday, February 4, 2014 8:32 PM > >Subject: Re: [Kicad-developers] Revisiting the Git decision (I come in > peace! - with a patch) > > > >

Re: [Kicad-developers] Revisiting the Git decision

2014-02-05 Thread Lorenzo Marcantonio
On Tue, Feb 04, 2014 at 01:27:12PM -0800, Cirilo Bernardo wrote: > I doubt it, but for the moment it works and Canonical don't seem so > concerned either. Some of the software I use has barely changed in 30 > years, some haven't changed at all for almost 40 years now, but that > means nothing other

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Miguel Angel
+34 636 52 25 69 skype: ajoajoajo 2014-02-05 Cirilo Bernardo : > - Original Message - > > > From: Wayne Stambaugh > > To: kicad-developers@lists.launchpad.net > > Cc: > > Sent: Wednesday, February 5, 2014 11:04 AM > > Subject: Re: [Kicad-developers] Revi

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Cirilo Bernardo
- Original Message - > From: Wayne Stambaugh > To: kicad-developers@lists.launchpad.net > Cc: > Sent: Wednesday, February 5, 2014 11:04 AM > Subject: Re: [Kicad-developers] Revisiting the Git decision > > On 2/4/2014 9:57 AM, Tomasz Wlostowski wrote: >> On

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Henner Zeller
On 4 February 2014 18:36, Blair Bonnett wrote: > > On 5 February 2014 15:03, Henner Zeller wrote: >> >> ...snip... >> >> This sounds excellent. I think I am going to base my pending work on >> your mirror until the official kicad-source-mirror is fixed to be >> up-to-date. >> >> We need to make s

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Blair Bonnett
On 5 February 2014 15:03, Henner Zeller wrote: > ...snip... > > This sounds excellent. I think I am going to base my pending work on > your mirror until the official kicad-source-mirror is fixed to be > up-to-date. > > We need to make sure though that the reverse path back into the KiCad > source

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Henner Zeller
On 4 February 2014 10:07, Blair Bonnett wrote: > On 5 February 2014 03:07, Brian Sidebotham > wrote: >> >> >> ...snip... >> >> >> I sent the other link very much on purpose, as on that page, a few >> paragraphs in is a link to this page: >> http://www.inkscape.org/en/develop/using-git-repositorie

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Wayne Stambaugh
On 2/4/2014 9:57 AM, Tomasz Wlostowski wrote: > On 02/04/2014 12:57 PM, Brian Sidebotham wrote: >> I suspect it's all just a documentation issue too as someone else >> suggested because it's so easy to branch the code and generate a patch >> using Bazaar. >> >> Perhaps the best place for anyone who

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Cirilo Bernardo
- Original Message - > From: Joel Holdsworth > To: kicad-developers@lists.launchpad.net > Cc: > Sent: Wednesday, February 5, 2014 12:04 AM > Subject: Re: [Kicad-developers] Revisiting the Git decision > > Hi All, > > Thank you all for taking the time

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-04 Thread Cirilo Bernardo
> > From: Fabrizio Tappero >To: James Hagerman >Cc: "kicad-developers@lists.launchpad.net" > >Sent: Tuesday, February 4, 2014 8:32 PM >Subject: Re: [Kicad-developers] Revisiting the Git decision (I come in peace! >- with a pa

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Fabrizio Tappero
Dear Joel, thank you for your messages, "The KiCad website and KiCad Launchpad page are full of broken or misleading links to old, outdated, or conflicting information. Binaries (and libraries) for all platforms are not readily available on either site." Could you please point out those many bro

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Chris Morgan
> There is another option for people who want to use Git: a mirror. There is a > mirror under the KiCad user account (the one with all the libraries) on > GitHub: > > https://github.com/KiCad/kicad-source-mirror > > However, it usually seems to be out of date, and very sporadically updated. > For s

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Blair Bonnett
On 5 February 2014 03:07, Brian Sidebotham wrote: > > ...snip... > > I sent the other link very much on purpose, as on that page, a few > paragraphs in is a link to this page: > http://www.inkscape.org/en/develop/using-git-repositories/ > > in other words, fill your boots, work with Git on the KiC

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Travis Ayres
> After reading Adam's last email, I think that a complete binary archive/installer for all platforms would make sense (including our own boost/wx libs, just like LibreOffice/Mozilla). Just unpack or run the installer and enjoy! Also, being able to update from inside the program itself is a really

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Lorenzo Marcantonio
On Tue, Feb 04, 2014 at 03:57:40PM +0100, Tomasz Wlostowski wrote: > $du -h ./kicad-feat1 > 203M Wait until you compile :P 3,1Gkicad-bzr Also unstripped binaries are a little scary: -rwxr-xr-x 1 lomarcan lomarcan 114433370 feb 3 19:39 pcbnew (yes, ld time is painful). No i7 here, just a D

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Tomasz Wlostowski
On 02/04/2014 12:57 PM, Brian Sidebotham wrote: I suspect it's all just a documentation issue too as someone else suggested because it's so easy to branch the code and generate a patch using Bazaar. Perhaps the best place for anyone who has decided Bazaar is dead (it works for me by the way!) an

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Joel Holdsworth
On 04/02/14 14:21, Adam Wolf wrote: > I'd like to make a quick point: producing a package for Kicad > that works on all the Ubuntu flavors, works in both Python > integration modes, *and* follows Ubuntu packaging policy is not a > simple task. I'm about 100 hours into it, maybe more, and while >

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Travis Ayres
This should be a wiki page, and the more time consuming steps should be a wiki pave as well. How amazing (and helpful) would that be? On Feb 4, 2014 3:57 AM, "Brian Sidebotham" wrote: > I suspect it's all just a documentation issue too as someone else > suggested because it's so easy to branch th

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Adam Wolf
I'd like to make a quick point: producing a package for Kicad that works on all the Ubuntu flavors, works in both Python integration modes, *and* follows Ubuntu packaging policy is not a simple task. I'm about 100 hours into it, maybe more, and while I'm just about finished, there is still plenty

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Brian Sidebotham
On 4 February 2014 13:04, Joel Holdsworth wrote: > Hi All, > > Thank you all for taking the time to respond to my original e-mail. It > seems to me that whatever the outcome this discussion it is well worth > having. > > > On 04/02/14 11:57, Brian Sidebotham wrote: >> I suspect it's all just a doc

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Joel Holdsworth
Hi All, Thank you all for taking the time to respond to my original e-mail. It seems to me that whatever the outcome this discussion it is well worth having. On 04/02/14 11:57, Brian Sidebotham wrote: > I suspect it's all just a documentation issue too as someone else > suggested because it's s

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Brian Sidebotham
I suspect it's all just a documentation issue too as someone else suggested because it's so easy to branch the code and generate a patch using Bazaar. Perhaps the best place for anyone who has decided Bazaar is dead (it works for me by the way!) and therefore cannot contribute (and particularly gi

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Lorenzo Marcantonio
On Tue, Feb 04, 2014 at 03:08:49AM -0800, Rick Walker wrote: > Then, just use the magic of merge to sync the work between both systems > from time to time. > > So, just fork it and stay in touch. Isn't painful to keep in sync the merge infos between git and bzr... or is there an automated 'bridg

Re: [Kicad-developers] Revisiting the Git decision

2014-02-04 Thread Rick Walker
Hey Guys, The answer seems simple. The point of both VCSs is to make merges easy. So just break into two different teams. A friendly code-fork. One group works in git and another in Bazaar. New people would have to choose the group to join based on 1) what things they wanted to work on an

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-04 Thread Fabrizio Tappero
Hi James, thanks for your message. Could you please point me to the (say 5) most serious problems that the official kicad website has. I might have some time/ability to fix it. thanks Fab. On Tue, Feb 4, 2014 at 3:00 AM, James Hagerman wrote: > Hi there, > > I've been lurking and haven't gotte

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-03 Thread Miguel Angel
aunchpad+bzr), and it works well. --- irc: ajo / mangelajo Miguel Angel Ajo Pelayo +34 636 52 25 69 skype: ajoajoajo 2014-02-04 Cirilo Bernardo : > > > > From: Henner Zeller > >To: Joel Holdsworth > >Cc: kicad-developers@lists.launchpad

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-03 Thread Cirilo Bernardo
> > From: Henner Zeller >To: Joel Holdsworth >Cc: kicad-developers@lists.launchpad.net >Sent: Tuesday, February 4, 2014 3:43 PM >Subject: Re: [Kicad-developers] Revisiting the Git decision (I come in peace! >- with a patch) > > &g

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-03 Thread Henner Zeller
Thank you for this mail. I fullheartedly agree. I myself am usually very active with contributing to projects I am using - many projects from KDE to LyX, gimp, kphotoalbum, OpenScad ... (many more to name) have patches from me. Mostly because whenever I use a program, and I see things to change/fi

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-03 Thread Cirilo Bernardo
> > From: James Hagerman >To: Chris Morgan >Cc: "kicad-developers@lists.launchpad.net" > >Sent: Tuesday, February 4, 2014 1:00 PM >Subject: Re: [Kicad-developers] Revisiting the Git decision (I come in peace! >- with a pat

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-03 Thread James Hagerman
Hi there, I've been lurking and haven't gotten into the KiCad source code yet. I joined the dev list to get help with building under OS X. This bzr/git debate is something I've been wondering about as well. I initially had issues installing bzr and bzr-tools under OS X. I tried using the KiCad Ho

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-03 Thread Chris Morgan
On Mon, Feb 3, 2014 at 2:37 PM, Wayne Stambaugh wrote: > On 2/2/2014 9:16 AM, Mitch Davis wrote: >> On Sat, Feb 1, 2014 at 10:40 PM, Joel Holdsworth >> wrote: >>> discouraged by the friction. >> >> Amen. >> >> Mitch. >> > > Is using Bazaar really enough "friction" (your word not mine) to prevent

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-03 Thread Wayne Stambaugh
On 2/2/2014 9:16 AM, Mitch Davis wrote: > On Sat, Feb 1, 2014 at 10:40 PM, Joel Holdsworth > wrote: >> discouraged by the friction. > > Amen. > > Mitch. > Is using Bazaar really enough "friction" (your word not mine) to prevent developers from contributing to KiCad? I hope not. That would be

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-02 Thread Mitch Davis
On Sat, Feb 1, 2014 at 10:40 PM, Joel Holdsworth wrote: > discouraged by the friction. Amen. Mitch. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad

Re: [Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-01 Thread Fabrizio Tappero
Hi Joel, Great e-mail. I personally would support the git move. Regards Fabrizio On 01/02/2014 1:48 PM, "Joel Holdsworth" wrote: > Hi Guys, > > I'm new to this project - though not to open source in general. I'm the > author of PulseView - a GUI for logic analyzers and oscilloscopes; part > of

[Kicad-developers] Revisiting the Git decision (I come in peace! - with a patch)

2014-02-01 Thread Joel Holdsworth
Hi Guys, I'm new to this project - though not to open source in general. I'm the author of PulseView - a GUI for logic analyzers and oscilloscopes; part of the sigrok project. I've been trying to get started making contributions to your project, building from source, fixing problems etc. and I fe