kicad-lib-committers team mailing list archive

[Fabrizio Tappero <fabrizio.tappero@xxxxxxxxx>]

you mean anybody who wants to contribute to the kicad lib needs a
github account?

thanks for the many info.



On Fri, Mar 21, 2014 at 2:26 PM, Carl Poirier <carl.poirier.2@xxxxxxxxx> wrote:
> You have to replace "yourUsername" in the URL by your actual Github
> username. So that it leads to your forked repo. Sorry if I was not clear.
>
> I linked a Github tutorial in the other thread that talks about syncing your
> local repo. Anyway, here it is again:
>
>> # Changes the active directory in the prompt to the newly cloned
>> "Spoon-Knife" directory
>> git remote add upstream https://github.com/octocat/Spoon-Knife.git
>> # Assigns the original repository to a remote called "upstream"
>> git fetch upstream
>> # Pulls in changes not present in your local repository, without modifying
>> your files
>
> I have seen the other thread you started, so let's continue there.
>
>
> On Fri, Mar 21, 2014 at 3:52 AM, Fabrizio Tappero
> <fabrizio.tappero@xxxxxxxxx> wrote:
>>
>> Hi Carl,
>> hum, it sounds quite easy actually. I just tried but:
>>
>> $ git clone https://github.com/yourUsername/kicad-library
>> Cloning into 'kicad-library'...
>> Username for 'https://github.com':
>> Password for 'https://github.com':
>> fatal: Authentication failed
>>
>> isn't anonymous cloning not possible?
>>
>>
>> Also, the problem I have with the bullet points you mention is similar
>> to the problem many people might have with any git-based contribution.
>> Ill try to explain. When you get a repo because you want to contribute
>> (either is kicad it self or the kicad lib repo) u clone it you do your
>> modifications, you create and send to developers your patch. Few days
>> after your patch gets applied and ideally your would like to re-synch
>> your repo with the newest repo but it is not possible because your
>> current repo is out of synch since you did your modifications locally.
>>
>> Create a branch and go back to the original branch is one possible
>> solution. Well all this procedure seems to me quite complicated
>> especially when the contribute is some kicad users who is trying to
>> update a lib component.
>>
>> Do you agree? Once again, in my opinion, git is made for developers
>> not for pcb designers who we are trying to take advantage of for
>> improving kicad lib quality.
>>
>> So, is a solution to ease this lib contrib process needed needed?
>>
>> If you do not mind I'd like to pose this question on the kicad dev mailing
>> list.
>>
>> Regards
>> Fabrizio
>>
>>
>>
>>
>>
>> On Thu, Mar 20, 2014 at 11:59 PM, Carl Poirier <carl.poirier.2@xxxxxxxxx>
>> wrote:
>> >> Unfortunately i do not understand how to actually contribiute to any
>> >> lib
>> >> component since the lib component editing is not done with a txt editor
>> >> but
>> >> instead with kicad lib comp editor.
>> >> So this is what users will want to know:
>> >> - how to download or get the lib comp to midify (do i already have it
>> >> in
>> >> kicad?) or how to generate a new lib component file to send to you
>> >> - how to turn this new component into a patch
>> >> - how to send it to you
>> >> - how to get newest lib components in my kicad distro
>> >
>> >> Best way is a 1 min video where u do it and i can describe it by txt
>> >> using
>> >> google docs. Once done i ask for quick contribiutions from any
>> >> developers.
>> >> Git anf github is for coders and i have the impression we are trying to
>> >> get kicad users to use it to make kicad lib better. Is it doable? How?
>> >> What do u think?
>> >
>> >
>> > Hi Fabrizio,
>> >
>> > Contributing to the library components is done the same way. I do think
>> > git
>> > is simple enough (compared to bzr) for contributors to use. If not, they
>> > can
>> > still email us their changes directly.
>> >
>> > 0. fork a git repo though Github
>> > 1. git clone https://github.com/yourUsername/kicad-library
>> > 2. in eeschema, change library folder to that dir
>> > 3. Make modifications
>> > 4. git commit
>> > 5. git push
>> > 6. Create pull request.
>> >
>> > To update the libraries on your computer, if you use this method, then
>> > it
>> > would be a simple matter of doing "git pull".
>> >
>> > A video is a good idea. I'll look into that.
>> >
>> > Regards,
>> >
>> > Carl
>> >
>> >
>> > On Wed, Mar 19, 2014 at 6:03 AM, Fabrizio Tappero
>> > <fabrizio.tappero@xxxxxxxxx> wrote:
>> >>
>> >> Ciao Carl.
>> >> Yes i did read it. Unfortunately i do not understand how to actually
>> >> contribiute to any lib component since the lib component editing is not
>> >> done
>> >> with a txt editor but instead with kicad lib comp editor.
>> >> So this is what users will want to know:
>> >> - how to download or get the lib comp to midify (do i already have it
>> >> in
>> >> kicad?) or how to generate a new lib component file to send to you
>> >> - how to turn this new component into a patch
>> >> - how to send it to you
>> >> - how to get newest lib components in my kicad distro
>> >>
>> >> Best way is a 1 min video where u do it and i can describe it by txt
>> >> using
>> >> google docs. Once done i ask for quick contribiutions from any
>> >> developers.
>> >> Git anf github is for coders and i have the impression we are trying to
>> >> get kicad users to use it to make kicad lib better. Is it doable? How?
>> >> What do u think?
>> >> Fabrizio
>> >>
>> >> On 18/03/2014 1:32 PM, "Carl Poirier" <carl.poirier.2@xxxxxxxxx> wrote:
>> >>>
>> >>> Hi Fabrizio,
>> >>>
>> >>> does this answer your questions?
>> >>>
>> >>> Carl
>> >>>
>> >>>
>> >>> On Tue, Mar 18, 2014 at 7:03 AM, Fabrizio Tappero
>> >>> <fabrizio.tappero@xxxxxxxxx> wrote:
>> >>>>
>> >>>> no worries
>> >>>>
>> >>>> On Mon, Mar 17, 2014 at 11:18 PM, Carl Poirier
>> >>>> <carl.poirier.2@xxxxxxxxx> wrote:
>> >>>> > Hi Fabrizio,
>> >>>> >
>> >>>> > Please hold on a few moments, I'm writing an email that explains
>> >>>> > some
>> >>>> > of it
>> >>>> > on the lib-committer mailing list.
>> >>>> >
>> >>>> > I was actually wondering if the information could be added where it
>> >>>> > needs
>> >>>> > to. :)
>> >>>> >
>> >>>> > Carl
>> >>>> >
>> >>>> >
>> >>>> > On Mon, Mar 17, 2014 at 5:56 PM, Fabrizio Tappero
>> >>>> > <fabrizio.tappero@xxxxxxxxx> wrote:
>> >>>> >>
>> >>>> >> Hi Carl,
>> >>>> >> I am updating the getting started with kicad tutorial pdf liked to
>> >>>> >> all
>> >>>> >> kicad programs. I'd like to add a section on lib on github but I
>> >>>> >> first
>> >>>> >> need to know what is going on. Could u please direct me to
>> >>>> >> something
>> >>>> >> i
>> >>>> >> can read or see.
>> >>>> >>
>> >>>> >> thanks
>> >>>> >> Fabrizio
>> >>>> >>
>> >>>> >> On Mon, Mar 17, 2014 at 9:10 PM, Carl Poirier
>> >>>> >> <carl.poirier.2@xxxxxxxxx>
>> >>>> >> wrote:
>> >>>> >> >
>> >>>> >> >> Is anyone working on doing some sort of collaborative library
>> >>>> >> >> where
>> >>>> >> >> people
>> >>>> >> >> could create components and by users votes have the components
>> >>>> >> >> validate
>> >>>> >> >> them-selves?
>> >>>> >> >> I know a little about the github "official" library for KiCad
>> >>>> >> >
>> >>>> >> > Few of us (like me) work on libraries on a voluntary basis. So
>> >>>> >> > much
>> >>>> >> > as
>> >>>> >> > those
>> >>>> >> > who volunteer for any other good cause.
>> >>>> >> >
>> >>>> >> > Basically, contributors started to open merge requests to one or
>> >>>> >> > more
>> >>>> >> > GitHub
>> >>>> >> > libraries. We then validate as much as we can and pull the merge
>> >>>> >> > request.
>> >>>> >> > That's how you would do to contribute some corrections to a
>> >>>> >> > library
>> >>>> >> > and/or
>> >>>> >> > commit a new one.
>> >>>> >> >
>> >>>> >> > For now, the merge requests can be handled by one person but I
>> >>>> >> > suspect
>> >>>> >> > this
>> >>>> >> > will change soon, once the GitHub plugin gets more users. We
>> >>>> >> > will
>> >>>> >> > then
>> >>>> >> > need
>> >>>> >> > more people to validate the footprints and libraries.
>> >>>> >> >
>> >>>> >> > Carl
>> >>>> >> >
>> >>>> >> >
>> >>>> >> > On Mon, Mar 17, 2014 at 3:45 PM, Dick Hollenbeck
>> >>>> >> > <dick@xxxxxxxxxxx>
>> >>>> >> > wrote:
>> >>>> >> >>
>> >>>> >> >> On 03/17/2014 01:35 PM, Alejandro Méndez A. wrote:
>> >>>> >> >> > Ok,
>> >>>> >> >> >
>> >>>> >> >> > I will do that in a new post with another title so it is easy
>> >>>> >> >> > to
>> >>>> >> >> > find.
>> >>>> >> >> >
>> >>>> >> >> > I could make a video since I already have a youtube channel
>> >>>> >> >> > with
>> >>>> >> >> > plenty
>> >>>> >> >> > of visits but I'm
>> >>>> >> >> > not a native English speaker so I think it might be better
>> >>>> >> >> > just
>> >>>> >> >> > to
>> >>>> >> >> > keep
>> >>>> >> >> > the written version :)
>> >>>> >> >> >
>> >>>> >> >> > In fact I've been doing a tutorial for Kicad in Spanish but I
>> >>>> >> >> > haven't
>> >>>> >> >> > finished since the
>> >>>> >> >> > last changes for KiCad have changed a lot in PCBNew and
>> >>>> >> >> > Library
>> >>>> >> >> > and
>> >>>> >> >> > I'm
>> >>>> >> >> > thinking of
>> >>>> >> >> > redoing the first ones with a newer version of KiCad
>> >>>> >> >> > including
>> >>>> >> >> > the
>> >>>> >> >> > new
>> >>>> >> >> > features of PCBNew.
>> >>>> >> >> > Should I keep waiting a little longer for more big changes?
>> >>>> >> >> >
>> >>>> >> >> > I'll try to make a useful post for the environment variables
>> >>>> >> >> > and
>> >>>> >> >> > how
>> >>>> >> >> > to
>> >>>> >> >> > use them to be
>> >>>> >> >> > able to work with Kicad seamlessly in different platforms.
>> >>>> >> >> >
>> >>>> >> >> > Last but not least. I think there is already work being done
>> >>>> >> >> > with the
>> >>>> >> >> > libraries but I
>> >>>> >> >> > think that it would be really good for KiCad to have a very
>> >>>> >> >> > large
>> >>>> >> >> > contributive components
>> >>>> >> >> > library since most "hobbiest" users don't wan't to make their
>> >>>> >> >> > own
>> >>>> >> >> > parts
>> >>>> >> >> > and people like me
>> >>>> >> >> > that are freelance or work for small companies will use
>> >>>> >> >> > already
>> >>>> >> >> > created
>> >>>> >> >> > components when
>> >>>> >> >> > they come from a "respectable" source. I spend a lot of time
>> >>>> >> >> > creating
>> >>>> >> >> > my
>> >>>> >> >> > own footprints
>> >>>> >> >> > and I've found that the best library out there in my opinion
>> >>>> >> >> > is
>> >>>> >> >> > this
>> >>>> >> >> > one:
>> >>>> >> >> > http://smisioto.no-ip.org/elettronica/kicad/kicad-en.htm . Is
>> >>>> >> >> > anyone
>> >>>> >> >> > working on doing some
>> >>>> >> >> > sort of collaborative library where people could create
>> >>>> >> >> > components
>> >>>> >> >> > and
>> >>>> >> >> > by users votes have
>> >>>> >> >> > the components validate them-selves?
>> >>>> >> >> > I know a little about the github "official" library for KiCad
>> >>>> >> >> > and
>> >>>> >> >> > also I
>> >>>> >> >> > know of a web
>> >>>> >> >> > that is doing that for three differents packages (KiCad
>> >>>> >> >> > included), it
>> >>>> >> >> > is
>> >>>> >> >> > called
>> >>>> >> >> > CircuitHub. It is a great idea but they try to cover too
>> >>>> >> >> > much,
>> >>>> >> >> > at
>> >>>> >> >> > least
>> >>>> >> >> > for now, in my
>> >>>> >> >> > opinion. You can create the components in their web, et
>> >>>> >> >> > cetera.
>> >>>> >> >> > I've
>> >>>> >> >> > tried it and I've
>> >>>> >> >> > even talked to one of the founders for support, since there
>> >>>> >> >> > are
>> >>>> >> >> > many
>> >>>> >> >> > things that don't
>> >>>> >> >> > work right yet and they make it basically unusable at the
>> >>>> >> >> > end.
>> >>>> >> >> > They've
>> >>>> >> >> > told me they are
>> >>>> >> >> > working on it, but it have passed at least 6 months and they
>> >>>> >> >> > have
>> >>>> >> >> > added
>> >>>> >> >> > other things but
>> >>>> >> >> > the component creation part is still not working right. To
>> >>>> >> >> > the
>> >>>> >> >> > point
>> >>>> >> >> > of
>> >>>> >> >> > not even been able
>> >>>> >> >> > to create new schematic symbols.
>> >>>> >> >> >
>> >>>> >> >> > Anyway, I just want to know if there is somebody working in
>> >>>> >> >> > an
>> >>>> >> >> > idea
>> >>>> >> >> > like
>> >>>> >> >> > that but just to
>> >>>> >> >> > keep the components, not creating them in the web since I
>> >>>> >> >> > could
>> >>>> >> >> > help
>> >>>> >> >> > creating components
>> >>>> >> >> > and a system to let people create components to share,
>> >>>> >> >> > following
>> >>>> >> >> > a
>> >>>> >> >> > common criteria which
>> >>>> >> >> > could give some security to the people wanting to use them.
>> >>>> >> >> >
>> >>>> >> >> > BTW, sorry for the long boring reply.
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >> >> For any task requiring large man-hours to succeed, there
>> >>>> >> >> typically
>> >>>> >> >> needs
>> >>>> >> >> to be incentive
>> >>>> >> >> or economic sustenance.  Simply voting does not cut it.  You
>> >>>> >> >> could
>> >>>> >> >> ask
>> >>>> >> >> 50
>> >>>> >> >> people to dig
>> >>>> >> >> ditches, and tell them you will vote on who does the best job,
>> >>>> >> >> and
>> >>>> >> >> they
>> >>>> >> >> will walk away
>> >>>> >> >> with a curious look on their faces.
>> >>>> >> >>
>> >>>> >> >> The guys maintaining the github repo are picking up steam and
>> >>>> >> >> are
>> >>>> >> >> changing
>> >>>> >> >> and adding
>> >>>> >> >> footprints and parts fairly regularly now.  This is an economic
>> >>>> >> >> miracle.
>> >>>> >> >> There is no
>> >>>> >> >> economic explanation for it.  I vote "yeah" for Carl and the
>> >>>> >> >> gang!
>> >>>> >> >>
>> >>>> >> >> You get what you pay for, or you get what you do, anything
>> >>>> >> >> after
>> >>>> >> >> that
>> >>>> >> >> is
>> >>>> >> >> an economic
>> >>>> >> >> miracle (or a free lunch, but they don't exist, because in
>> >>>> >> >> English
>> >>>> >> >> it
>> >>>> >> >> is
>> >>>> >> >> well known that
>> >>>> >> >> "there is no free lunch").
>> >>>> >> >>
>> >>>> >> >> If you want to learn more, join the ~kicad-library-committers
>> >>>> >> >> team, but
>> >>>> >> >> what you want is
>> >>>> >> >> not happening here on this mailing list and I'll have nothing
>> >>>> >> >> additional
>> >>>> >> >> to do with it
>> >>>> >> >> (other than having previously recruited Carl and having written
>> >>>> >> >> the
>> >>>> >> >> github
>> >>>> >> >> plugin.)
>> >>>> >> >>
>> >>>> >> >> Now Carl and company are the engine of improvement.  Name
>> >>>> >> >> names,
>> >>>> >> >> and
>> >>>> >> >> give
>> >>>> >> >> thanks.
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >> >> _______________________________________________
>> >>>> >> >> 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
>> >>>> >> >
>> >>>> >> >
>> >>>> >> >
>> >>>> >> > _______________________________________________
>> >>>> >> > 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
>> >>>> >> >
>> >>>> >
>> >>>> >
>> >>>
>> >>>
>> >
>
>