I would grump less, if that counts for anything ;) On Mon, Jan 11, 2016 at 12:12:45AM +0100, Piotr Esden-Tempski wrote: > Hi everyone, > > Here also my 1ct. I am another of those potential developers that would much > more likely contribute to the project if done through GitHub. > > So +1 for GitHub transition from me. :) > > Cheers, > Esden > > On 01/10/2016 01:19 AM, Duane Johnson wrote: > >As a software developer on the sidelines thinking of getting involved, > >this would significantly lower the barrier to entry (cognitive or > >otherwise) since git/github is so familiar to me. > > > >Duane > > > >On Jan 9, 2016 3:50 PM, "Nick Østergaard" <[email protected] > ><mailto:[email protected]>> wrote: > > > > 2016-01-06 0:50 GMT+01:00 Wayne Stambaugh <[email protected] > > <mailto:[email protected]>>: > > > On 1/5/2016 4:00 AM, Maciej Sumiński wrote: > > >> On 12/11/2015 05:58 PM, Wayne Stambaugh wrote: > > >>> On 12/11/2015 3:25 AM, Maciej Sumiński wrote: > > >>>> On 12/08/2015 09:57 PM, Wayne Stambaugh wrote: > > >>>> [snip] > > >>>>> I'm not the biggest github fan either. I think its OK but it was > > >>>>> expecting a lot more given all of the fan fair. I do like > > working with > > >>>>> git. I've been using it exclusively for my Eeschema refactor > > work. Has > > >>>>> anyone tried using the git support on launchpad yet? I > > haven't had time > > >>>>> to mess around with it. I know it's still a beta version but > > it might > > >>>>> be worth a look. It could be a low pain option as long as > > the launchpad > > >>>>> devs get all the bug tracker and merge request support > > working with git. > > >>>>> It may be worth trying to get an idea of when the LP devs > > plan to have > > >>>>> this done. If it's within the next year, it may be worth > > waiting rather > > >>>>> than jumping ship. > > >>>> > > >>>> There is basic support for git in Launchpad, and it seems to work. > > >>>> Following a short manual [1], I was able to push a branch to > > my git > > >>>> repository on LP [2]. It has taken me less than 5 minutes, > > thanks to our > > >>>> code is already stored in a git repo on github. > > >>>> If our main goal is to switch to git, then this must be the > > cheapest & > > >>>> quickest way. > > >>>> > > >>>> Regards, > > >>>> Orson > > >>>> > > >>>> 1. https://help.launchpad.net/Code/Git > > >>>> 2. https://code.launchpad.net/~orsonmmz/kicad/+git/kicad > > >>>> > > >>> > > >>> Did you try to link a fake LP bug report and/or merge request > > to this > > >>> repo. If those two things work at least as well as they do > > with bzr, it > > >>> might just be the way to go. > > >> > > >> For the moment there is no possibility to fill a bug report > > against a > > >> specific commit, though it seems to me that it is a rarely used > > option. > > >> Majority of bug reports contain the version information in the > > >> description field. Unfortunately, it may also mean there is no > > way to > > >> mark a specific commit as a bug fix. > > >> > > >> It is possible to propose a branch to be merged, though the > > interface is > > >> not well polished yet. It was not clear to me what should be put in > > >> "Target repository" (e.g. ~orsonmmz/kicad/+git/kicad) and > > "Target path" > > >> (branch name in the repository) fields, but perhaps they are > > >> automatically filled out when requesting merge against the main > > >> repository. It is also possible to add reviews, as in the > > Launchpad version. > > >> > > >> Regards, > > >> Orson > > >> > > > > > > It looks like git support in launchpad is a work in progress. I will > > > contact the launchpad devs to see what their time frame is for > > getting > > > full launchpad support up and running. I don't want to loose the > > link > > > between bug reports and the repo version if I can help it. I'll hold > > > off any final decision until I hear back from the launchpad devs. > > > > > > Wayne > > > > I my humble opinion, I think we could just start using git and not > > nessesarely change the kicad source code bugtracker yet, that is keep > > using it on launchpad. We never used the few features that the > > launchpad bug tracker had to refer to the source code anyway. > > > > So basically, all we need to switch completely to git is: > > 1. rename the kicad-source-mirror to kicad on github. > > 2. disable write access on the bzr repo on launchpad. > > 3. delete your bzr workspace (if you use that) and clone the new git > > repo. > > > > Effort for the above is very low. > > > > The issue tracker for the git repo on github can be disabled and we > > can link the launchpad bug tracker from the repo description on > > github. > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : [email protected] > > <mailto:[email protected]> > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > > > > > > >_______________________________________________ > >Mailing list: https://launchpad.net/~kicad-developers > >Post to : [email protected] > >Unsubscribe : https://launchpad.net/~kicad-developers > >More help : https://help.launchpad.net/ListHelp > > > > -- > -- > Piotr Esden-Tempski > Founder, Embedded Systems Engineer > 1 Bit Squared 'Professional Nano UAV Systems' > http://1bitsquared.com > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
