Hi,
W dniu 12.03.2024 o 15:15, Jon Evans pisze:
For what it's worth, I'm guessing that if you are trying phone numbers
from around the world, you are getting these phone numbers from VOIP
services and they aren't actually linked to a physical phone that you
control, which is kind of exactly what GitLab is trying to block...
The numbers from that site look like being able to receive activation
codes for verity of services (including google). The receive box is
publicly visible, so I could browse the history and see many such codes
there. So, even if they are VoIP, they get the SMS from senders.
But there is a limited count of those numbers, so they are easy to
enumerate on blacklists, and that's what gitlab probably did.
I don't claim that GitLab's system is perfect or ideal, but the point is
that they are giving anyone who signs up free resources, and they have a
lot of trouble with abuse of their resources. In order to get access to
those resources, you need to be willing to disclose enough information
to them for them to feel like you are a low risk (because, if you
started abusing their system, you'd be "burning" the good will of your
identity).
I have a different opinion:
1. I haven't started accessing their resources (unless you count putting
a phrase into an input-text field as such "access")
2. They've started abusing my patience.
BTW: the only problem they could have with abusing their resources is
through their free CI/CD - and this can be prevented easily by allowing
only "thoroughly verified" users to commit code to the builds. Or they
could disabled CI/CD for the "free" projects and be 100% on the safe
side. The didn't. They have overdone their "security".
So I'm very sorry, but that's a nogo for me.
-R
PS: this is out off the topic here, but since I'm probably be signing
off the list in near future, I'd like to ask a question regarding KiCAD
design. After years of doing the ordinary sequence of: draw-sch,
numerate, footprint assign, export to pcb ... I've looked up the files
and to my surprise found out, that the footprints are actually stored in
the PCB, not in the SCH. So my question is: is the footprint assignment
BEFORE netlist export to PCB a "design feature", or is it implemented
this way because of some legacy code from the past? (the question
originates from pondering of multiboard/multi-pcb-variant design options)
-Jon
On Tue, Mar 12, 2024 at 7:24 AM 'Rafał Pietrak' via KiCad Developers
<devlist@kicad.org <mailto:devlist@kicad.org>> wrote:
Ho Oliver,
Yes, I've tried, and with numbers from US, from swiss and even from
pakistan - all that to no avail. gitlab declined verification almost
immediately, so I won't be able join the work there. Sorry.
bye.
-R
W dniu 12.03.2024 o 09:17, 'White Fox' via KiCad Developers pisze:
> Hi Rafal, did you managed to join gitlab?
>
> Is there somethign new on this front side?
>
> greetings
> Oliver Lenz
>
>
>
> Am 29.02.2024 um 21:38 schrieb 'Rafał Pietrak' via KiCad Developers:
>> Oliver,
>>
>> Thenx. If it works, it's fine by me. I'll give it a try in three
days
>> (my username is used/reserved at gitlab for that duration).
>>
>> -R
>>
>> W dniu 29.02.2024 o 20:38, 'White Fox' via KiCad Developers pisze:
>>> Hi guys
>>>
>>> That's sad that the topic goes this way.
>>> @Rafal: I have never tried it and do not want to advertise this
service,
>>> but maybe this (or something similiar) is an option for you?
>>> https://quackr.io/ <https://quackr.io/>
>>>
>>> best regards
>>> Oliver
>>>
>>>
>>> Am 29.02.2024 um 19:14 schrieb 'Rafał Pietrak' via KiCad
Developers:
>>>> Seth,
>>>>
>>>> I really do regard my phone number as private information and
even if
>>>> I share it with my physician without hesitation, giving it out
to a
>>>> global corpo is out of the question for me. I do understand,
that they
>>>> may have some internal policies based on some reasoning, and
I'm not
>>>> going to argue with that. Let them have it. Only I'm not going to
>>>> accept that.
>>>>
>>>> Then again. I do UNDERSTAND, that I won't be able to
contribute to the
>>>> project. I really do get it. My intention in writing the
massage was
>>>> only that:
>>>> 1. the core developers may not be aware, that this sort of
"additional
>>>> confirmation" could be unfriendly to people. (no matter
argumentation).
>>>> 2. and I wanted to tell Oliver that at this point I won't be
>>>> contributing to this "multiboard docs" project. I'm sorry.
>>>>
>>>> Anyway, thenx everybody for wonderful KiCAD and see you
somewhere else.
>>>>
>>>> bye.
>>>>
>>>> -R
>>>>
>>>> W dniu 29.02.2024 o 18:24, Seth Hillbrand pisze:
>>>>> GitLab is where all development happens. If their
requirements are
>>>>> too onerous then, while we are sorry to lose you, there are
extremely
>>>>> limited ways that you'll be able to be involved in KiCad at all.
>>>>>
>>>>> You can still offer translations at
>>>>> https://hosted.weblate.org/projects/kicad/
<https://hosted.weblate.org/projects/kicad/>
>>>>> <https://hosted.weblate.org/projects/kicad/
<https://hosted.weblate.org/projects/kicad/>> but that is all.
>>>>> Everything else happens on GitLab. We do not accept patches
through
>>>>> the mailing list.
>>>>>
>>>>> It is interesting to me that you would consider phone numbers
to be
>>>>> private information. We used to print huge books with everyone's
>>>>> name, address and phone number in them. Then everyone got a
copy of
>>>>> the book. Of course, I put my phone number in my e-mail
signature,
>>>>> so maybe I'm missing something. Regardless, GitLab isn't
using your
>>>>> phone number for nefarious purposes, they offer a free
service with
>>>>> free CI time on their shared machines. Before they asked for
>>>>> verification information, cryptobros would abuse this for bitcoin
>>>>> mining and everyone suffered. Now, projects like KiCad are
able to
>>>>> use the CI machines for testing builds and finding bugs.
>>>>>
>>>>> Seth
>>>>>
>>>>> KiCad Services Corporation Logo
>>>>> Seth Hillbrand
>>>>> *Lead Developer*
>>>>> +1-530-302-5483
>>>>> Long Beach, CA
>>>>> www.kipro-pcb.com <http://www.kipro-pcb.com>
<https://www.kipro-pcb.com/ <https://www.kipro-pcb.com/>>
i...@kipro-pcb.com <mailto:i...@kipro-pcb.com>
>>>>> <mailto:i...@kipro-pcb.com <mailto:i...@kipro-pcb.com>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 29, 2024 at 4:08 AM 'Rafał Pietrak' via KiCad
Developers
>>>>> <devlist@kicad.org <mailto:devlist@kicad.org>
<mailto:devlist@kicad.org <mailto:devlist@kicad.org>>> wrote:
>>>>>
>>>>> Hmmm... I just tried to setup an account there (on
gitlab), and it
>>>>> asked
>>>>> me for a phone number "for confirmation" - that's
unacceptable
>>>>> invasion
>>>>> of privacy. So, (regrettably) I'm not be able to join you
there.
>>>>>
>>>>> BR.
>>>>>
>>>>> Rafał
>>>>>
>>>>> W dniu 29.02.2024 o 09:06, Kliment (Future Bits) pisze:
>>>>> > Hello Rafał,
>>>>> >
>>>>> > KiCad development was never on GitHub - it was
originally on
>>>>> Launchpad
>>>>> > and later moved to GitLab. The issue (and therefore
feature
>>>>> request)
>>>>> > tracker is at
https://gitlab.com/kicad/code/kicad/-/issues/
<https://gitlab.com/kicad/code/kicad/-/issues/>
>>>>> <https://gitlab.com/kicad/code/kicad/-/issues/
<https://gitlab.com/kicad/code/kicad/-/issues/>> - you can
>>>>> > search for related issues there, or start a new one.
>>>>> >
>>>>> > Hope this helps
>>>>> >
>>>>> > -Kliment
>>>>> >
>>>>> > On 29.02.24 08:56, 'Rafał Pietrak' via KiCad
Developers wrote:
>>>>> >> Hi Oliver,
>>>>> >>
>>>>> >> The subject somehow died out, but I'd like to followup:
>>>>> >> 1. I've looked up current kicad github for guidance,
and it
>>>>> looks
>>>>> >> pretty "overpopulated" - lots of small repositories
without
>>>>> any
>>>>> sort
>>>>> >> of "oversight". Many marked as "legacy", but still
visible ...
>>>>> and in
>>>>> >> consequence creating "information noise".
>>>>> >> 2. so i might have missed a place where such discussion
>>>>> (documentation
>>>>> >> gathering) currently takes place - pls advice.
>>>>> >> 3. if there is none and I create one, how do I invite
kicad
>>>>> (and
>>>>> other
>>>>> >> tools) users to join the discussion?
>>>>> >> 4. is there a naming convention to use for a project, or
>>>>> "multiboard"
>>>>> >> would be just fine?
>>>>> >>
>>>>> >> -R
>>>>> >>
>>>>> >> W dniu 26.02.2024 o 19:22, 'White Fox' via KiCad
Developers
>>>>> pisze:
>>>>> >>> Hi Rafal
>>>>> >>>
>>>>> >>> Well, this seems to me exactly like what I would
start with,
>>>>> thank you.
>>>>> >>> Where is this snippet from? I can't remember such an
email
>>>>> thread here.
>>>>> >>>
>>>>> >>> greetings
>>>>> >>> Oliver
>>>>> >>>
>>>>> >>> Am 26.02.2024 um 19:12 schrieb 'Rafał Pietrak' via KiCad
>>>>> Developers:
>>>>> >>>> Dear everybody,
>>>>> >>>>
>>>>> >>>> W dniu 26.02.2024 o 15:47, Jon Evans pisze:
>>>>> >>>> [----------------]
>>>>> >>>>>
>>>>> >>>>> For "multiboard projects" I think if you ask 5
people, you
>>>>> will
>>>>> >>>>> possibly get 5 different answers about what this
feature
>>>>> means, and
>>>>> >>>>> what they want to do with it.
>>>>> >>>>> So, figuring this out (and getting it documented)
is a good
>>>>> first
>>>>> >>>>> step.
>>>>> >>>>
>>>>> >>>> If that could be of any help, and should anybody have
>>>>> already
>>>>> ideas
>>>>> >>>> and/or experience regarding multiboard design in
form of
>>>>> loose
>>>>> >>>> comments or discussion, I can gather those into an
initial
>>>>> >>>> documentation and put it on a github somewhere.
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> -R
>>>>>
>
> --
> Das Nötige ist einfach und das Komplizierte unnötig
> -Michail Kalaschnikow
>
>
> As a german, please let me tell you: Germans are not rude.
> If you invite a german to have lunch with you and he says simply
'No',
> be assured that he means:
> «I'm so glad that you ask me to spend lunch time with you, I'm
sure it
> would be a great time,
> but unfortunately, I'm deeply sorry for that, I have a meeting
with my
> boss and a few minutes later,
> I promised our most important customer a call.
> And moreover, I'm a little embarassed for that, I feel a bit sick
today,
> maybe I'm not a good lunch companion today.
> But I really hope so that we can share this great time another time.»
>
> The reason for this kind of highly efficient conversation, which is
> typical for germans, is quite simple:
> He knows that you are probably very busy with highly important
business,
> and it is a special kind of German courtesy not to want to waste
your
> precious time.
> So please, don't misunderstand short and precise communication as
> rowdyness.
>
--
You received this message because you are subscribed to the Google
Groups "KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to devlist+unsubscr...@kicad.org
<mailto:devlist%2bunsubscr...@kicad.org>.
To view this discussion on the web visit
https://groups.google.com/a/kicad.org/d/msgid/devlist/3aa37107-fe4b-473e-9e69-a58b1b7e143e%40electric-sheep.eu
<https://groups.google.com/a/kicad.org/d/msgid/devlist/3aa37107-fe4b-473e-9e69-a58b1b7e143e%40electric-sheep.eu>.
--
You received this message because you are subscribed to the Google
Groups "KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to devlist+unsubscr...@kicad.org
<mailto:devlist+unsubscr...@kicad.org>.
To view this discussion on the web visit
https://groups.google.com/a/kicad.org/d/msgid/devlist/CA%2BqGbCA-%3DAsZk2x0qyZnPT%3DajyREsW%2B98fGqH5rQC%3D00C71Qkw%40mail.gmail.com <https://groups.google.com/a/kicad.org/d/msgid/devlist/CA%2BqGbCA-%3DAsZk2x0qyZnPT%3DajyREsW%2B98fGqH5rQC%3D00C71Qkw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "KiCad
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to devlist+unsubscr...@kicad.org.
To view this discussion on the web visit
https://groups.google.com/a/kicad.org/d/msgid/devlist/eaa99e2e-869a-4fdb-9e00-e571c74a78c3%40electric-sheep.eu.
