>always add custom backend system later to complement free infra.
We do have free infrastructure that can run backend code at CERN. Just
needs to package up in a docker container and run as non-root inside the
container. Assuming also it's not some resource hog of a system that eats
the entire
On 2019-11-25 13:28, Seth Hillbrand wrote:
> On 11/25/19 1:01 PM, Michael Geselbracht wrote:
>
>> That's me. Someone from Gitlab just contacted me. I totally missed this
>> mailing.
>>
>> I have replied that I was not aware that my private group names may affect
>> other users and that I am
Hi Seth,
Yes, I planned to write up my design in google doc and open it to comments.
I think that works best for public discussion, even though it requires
having a google account.
Design I'm thinking about requires 0 custom backend work. It will rely
entirely on publicly available infra such as
On 11/25/19 3:21 PM, Andrew Lutsenko wrote:
Hi all,
Is anyone currently working on some sort of plugin manager or 3rd
party library manager?
https://bugs.launchpad.net/kicad/+bug/1823733
I have some ideas that I want to write down in a form of high level
design document and share with the
That’s been a topic near to my heart for some time, but I’ve done nearly
nothing toward implementing it. I’d be very interested in being involved in
discussions of possible shapes it could take.
-Brian H
> On Nov 25, 2019, at 6:21 PM, Andrew Lutsenko wrote:
>
>
> Hi all,
>
> Is anyone
Hi all,
Is anyone currently working on some sort of plugin manager or 3rd party
library manager?
https://bugs.launchpad.net/kicad/+bug/1823733
I have some ideas that I want to write down in a form of high level design
document and share with the group for discussion. If there is already some
If providing the cheap U2F yubikeys to some folks on the dev team
would help this happen, please let me know.
Adam
On Mon, Nov 25, 2019 at 3:48 PM Jon Evans wrote:
>
> While there are many forms of 2FA in the world, GitLab does not support all
> of them.
> Currently, TOTP and U2F are the only
Does it sound like I can make this release? While the application may
not be perfect, I haven't heard anything that makes me think the
packaging change is causing issues.
Adam
On Mon, Nov 25, 2019 at 9:48 AM Wayne Stambaugh wrote:
>
> Hi Andy,
>
> On 11/22/19 2:21 PM, Andy Peters wrote:
> >
>
While there are many forms of 2FA in the world, GitLab does not support all
of them.
Currently, TOTP and U2F are the only supported methods [1]
This means that if we enabled it, everyone with commit access would need
either a device running a TOTP-compliant program, or a U2F device such as a
> On Nov 25, 2019, at 10:10 AM, jp charras wrote:
>
> Le 25/11/2019 à 17:53, Kevin Cozens a écrit :
>> On 2019-11-25 11:03 a.m., Seth Hillbrand wrote:
>>> 2FA would be using something like Google Authenticator on your phone,
>>> a YubiKey or SMS message code to verify your login on a computer
On 11/25/19 1:01 PM, Michael Geselbracht wrote:
That's me. Someone from Gitlab just contacted me. I totally missed
this mailing.
I have replied that I was not aware that my private group names may
affect other users and that I am willing to rename the group.
Is it sufficient to just rename
That's me. Someone from Gitlab just contacted me. I totally missed this
mailing.
I have replied that I was not aware that my private group names may affect
other users and that I am willing to rename the group.
Is it sufficient to just rename the group name? Or will this only change
the displayed
ma 25. marrask. 2019 klo 20.11 Mark Roszko (mark.ros...@gmail.com)
kirjoitti:
> > I don't have, or want, a cell phone (or any Google account).
> You do not need a cell phone. You can use a computer based TOTP supporting
> authentication app such as Authy or FOSS KeePassXC (
>
2FA can also use a normal land-line audio only telephone. The daemon at
the other end just reads a code and you write it down. As secure (or
more so) than a text message.
On 11/25/19 12:11 PM, Mark Roszko wrote:
> I don't have, or want, a cell phone (or any Google account).
You do not need a
> I don't have, or want, a cell phone (or any Google account).
You do not need a cell phone. You can use a computer based TOTP supporting
authentication app such as Authy or FOSS KeePassXC (
https://keepassxc.org/screenshots/)
> A simple password is not perfect, but at least it is easy to use and
On 11/25/19 12:10 PM, jp charras wrote:
> Le 25/11/2019 à 17:53, Kevin Cozens a écrit :
>> On 2019-11-25 11:03 a.m., Seth Hillbrand wrote:
>>> 2FA would be using something like Google Authenticator on your phone,
>>> a YubiKey or SMS message code to verify your login on a computer in
>>> addition
Le 25/11/2019 à 17:53, Kevin Cozens a écrit :
> On 2019-11-25 11:03 a.m., Seth Hillbrand wrote:
>> 2FA would be using something like Google Authenticator on your phone,
>> a YubiKey or SMS message code to verify your login on a computer in
>> addition to the password.
>
> It may not affect me as
On 2019-11-22 2:29 p.m., Brian wrote:
Can someone tell me an example use-case for a single schematic symbol
corresponding to multiple board entities within a single project?
Here is another example use case.
I drew up the schematic for an LED sign panel. It has 10 8x8 LED blocks in
two rows
On 2019-11-25 11:03 a.m., Seth Hillbrand wrote:
2FA would be using something like Google Authenticator on your phone, a
YubiKey or SMS message code to verify your login on a computer in addition
to the password.
It may not affect me as I'm a user of KiCad and occasional reporter of bugs.
GitLab does send emails when SSH keys are added by default, but it's not
enough.
It's about GitLab (and even GitHub) allowing you to edit code right in the
web interface without needing to touch git.
But yes, GitLab does support 2FA. It is optional per account by default BUT
it can be mandated on
On 11/25/19 11:03 AM, Seth Hillbrand wrote:
> On 2019-11-25 06:08, Wayne Stambaugh wrote:
>> Hi Mark,
>>
>> Do you mean using a GPG key? I see the gitlab supports signed commits
>> so would that be an adequate solution? I'm fine with this, it's
>> probably something we should be doing anyway.
On 2019-11-25 06:08, Wayne Stambaugh wrote:
Hi Mark,
Do you mean using a GPG key? I see the gitlab supports signed commits
so would that be an adequate solution? I'm fine with this, it's
probably something we should be doing anyway. Anyone else object to
this?
2FA would be using
Mm, no, just two factor auth, this is not about signed commits.
man. 25. nov. 2019 15.09 skrev Wayne Stambaugh :
> Hi Mark,
>
> Do you mean using a GPG key? I see the gitlab supports signed commits
> so would that be an adequate solution? I'm fine with this, it's
> probably something we should
Hi Simon,
I merged your patch.
Thanks,
Wayne
On 11/22/19 7:23 PM, Simon Richter wrote:
>
> This allows asking CTest for running the test suite under valgrind
> ---
> CMakeLists.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> ___
Hi Jonatan,
I merged your patch even though I really don't have any way to test it.
I did confirm that you fixed the zoom behavior on Linux. Thank you for
your contribution to KiCad.
Cheers,
Wayne
On 11/22/19 5:34 AM, Jonatan Liljedahl wrote:
> Hi,
>
> I found it. Here's an updated patch
Hi Mark,
Do you mean using a GPG key? I see the gitlab supports signed commits
so would that be an adequate solution? I'm fine with this, it's
probably something we should be doing anyway. Anyone else object to this?
Cheers,
Wayne
On 11/24/19 4:13 PM, Mark Roszko wrote:
> Can the use of 2FA
It looks good to me :)
søn. 24. nov. 2019 02.50 skrev Mark Roszko :
> The attempt I took on adding TLF is live.
>
> On Sat, Nov 23, 2019 at 8:45 AM Wayne Stambaugh
> wrote:
>
>> Hi Sujith,
>>
>> I got it. Thank you.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 11/22/19 10:09 PM, Sujith Anandan wrote:
>>
27 matches
Mail list logo
