On dinsdag 16 april 2019 15:15:48 CEST Nate Graham wrote:
> On Tue, 16 Apr 2019 02:14:31 -0600 Boudewijn Rempt wrote
>
> >
> > There's another, related thing. We've got a "full name" checking git hook
> which tries to force commits to have "real names".
> >
> > This hook is,
On Tue, 16 Apr 2019 02:14:31 -0600 Boudewijn Rempt wrote
>
> There's another, related thing. We've got a "full name" checking git hook
> which tries to force commits to have "real names".
>
> This hook is, of course, broken: no software developer can ever make a check
>
Am Dienstag, 16. April 2019, 22:00:24 CEST schrieb Nate Graham:
> On Tue, 16 Apr 2019 13:38:04 -0600 Ben Cooksley
> wrote
> > This hook was implemented in the first place to ensure that people had
> > correctly setup Git on their local machine. On some versions of Git
> > (maybe
On dinsdag 16 april 2019 22:10:54 CEST Friedrich W. H. Kossebau wrote:
>
> I wonder if the commit push hook could not actually compare against
> identity.kde.org to check for validness of name & email address, at least for
> the committer. The schema there already has name & email-address,
Am Dienstag, 16. April 2019, 21:38:04 CEST schrieb Ben Cooksley:
> This hook was implemented in the first place to ensure that people had
> correctly setup Git on their local machine.
>
> On some versions of Git (maybe all?) it will automatically use the local
> user account name as the name.
>
Am Dienstag, 16. April 2019, 22:59:52 CEST schrieb Boudewijn Rempt:
> I completely fail to understand what you're trying to say. This has nothing
> to do with a commit hook that makes a misguided attempt at parsing strings
> and validating them as real names.
? It has. For the start, it simply
On dinsdag 16 april 2019 21:38:04 CEST Ben Cooksley wrote:
> This hook was implemented in the first place to ensure that people had
> correctly setup Git on their local machine.
>
> On some versions of Git (maybe all?) it will automatically use the local
> user account name as the name.
>
>
Am Dienstag, 16. April 2019, 22:16:40 CEST schrieb Boudewijn Rempt:
> On dinsdag 16 april 2019 22:10:54 CEST Friedrich W. H. Kossebau wrote:
> > I wonder if the commit push hook could not actually compare against
> > identity.kde.org to check for validness of name & email address, at least
> > for
On Tue, 16 Apr 2019 14:58:26 -0600 Boudewijn Rempt
wrote
> On dinsdag 16 april 2019 22:31:38 CEST Nicolás Alvarez wrote:
>
> > It seems easier to whitelist legitimate mononyms on request...
>
> No, no, no! You cannot do that, unless you have an exhaustive list of "valid
>
On dinsdag 16 april 2019 23:04:02 CEST Friedrich W. H. Kossebau wrote:
> So this would actually implement what you ask for: no guess work about valid
> names.
What I want is an absolute cessation of any attempt at validating names. We
should not do that. Whether or not we can be sure that a
On Tue, 16 Apr 2019 13:38:04 -0600 Ben Cooksley wrote
> This hook was implemented in the first place to ensure that people had
> correctly setup Git on their local machine.
> On some versions of Git (maybe all?) it will automatically use the local
> user account name as the
> On 16 Apr 2019, at 16:45, Boudewijn Rempt wrote:
>
>> On dinsdag 16 april 2019 21:38:04 CEST Ben Cooksley wrote:
>>
>> This hook was implemented in the first place to ensure that people had
>> correctly setup Git on their local machine.
>>
>> On some versions of Git (maybe all?) it will
I completely fail to understand what you're trying to say. This has nothing to
do with a commit hook that makes a misguided attempt at parsing strings and
validating them as real names. We should not have that hook; such a hook cannot
be implemented.
On dinsdag 16 april 2019 22:42:50 CEST
El dimarts, 16 d’abril de 2019, a les 23:25:47 CEST, Boudewijn Rempt va
escriure:
> On dinsdag 16 april 2019 23:04:02 CEST Friedrich W. H. Kossebau wrote:
> > So this would actually implement what you ask for: no guess work about
> > valid
> > names.
>
> Whether or not we can be sure that a
There's another, related thing. We've got a "full name" checking git hook which
tries to force commits to have "real names".
This hook is, of course, broken: no software developer can ever make a check
for names that's not brokenm because there _are no rules for names_. This check
thinks that
On Tue, 16 Apr 2019 14:16:40 -0600 Boudewijn Rempt
wrote
> On dinsdag 16 april 2019 22:10:54 CEST Friedrich W. H. Kossebau wrote:
>
>
> >
> > I wonder if the commit push hook could not actually compare against
> > identity.kde.org to check for validness of name & email
On Wed, Apr 17, 2019 at 9:08 AM Friedrich W. H. Kossebau
wrote:
>
> Am Dienstag, 16. April 2019, 22:59:52 CEST schrieb Boudewijn Rempt:
> > I completely fail to understand what you're trying to say. This has nothing
> > to do with a commit hook that makes a misguided attempt at parsing strings
>
On Wed, 17 Apr 2019, 03:03 Boudewijn Rempt, wrote:
> On dinsdag 16 april 2019 15:15:48 CEST Nate Graham wrote:
> > On Tue, 16 Apr 2019 02:14:31 -0600 Boudewijn Rempt
> wrote
> > >
> > > There's another, related thing. We've got a "full name" checking git
> hook which tries to force
On Tue, 16 Apr 2019 14:16:40 -0600 Boudewijn Rempt
wrote
> On dinsdag 16 april 2019 22:10:54 CEST Friedrich W. H. Kossebau wrote:
>
>
> >
> > I wonder if the commit push hook could not actually compare against
> > identity.kde.org to check for validness of name & email
On dinsdag 16 april 2019 22:31:38 CEST Nicolás Alvarez wrote:
> It seems easier to whitelist legitimate mononyms on request...
No, no, no! You cannot do that, unless you have an exhaustive list of "valid
mononyms" -- and you're still deluding yourself into the assumption that you
can code
On Wed, Apr 10, 2019 at 9:39 AM Martin Klapetek
wrote:
>
> Nope, still says it cannot resolve that to a valid user. I think it has to be
> an actual user with actual email address.
Only real people can own apps or pages. One solution is to create a
business named KDE and then put all assets
On dinsdag 16 april 2019 22:00:24 CEST Nate Graham wrote:
> The only people who have commit access have been specifically granted this
> privilege.
Not quite: there are also the people who have submitted patches, but haven't
got access yet, and then we have to push their first couple of
Am Dienstag, 16. April 2019, 22:29:49 CEST schrieb Friedrich W. H. Kossebau:
> Am Dienstag, 16. April 2019, 22:16:40 CEST schrieb Boudewijn Rempt:
> > On dinsdag 16 april 2019 22:10:54 CEST Friedrich W. H. Kossebau wrote:
> > > I wonder if the commit push hook could not actually compare against
>
Hi,
Whether or not we can be sure that a string is a name should not be
relevant to us.
Just answering to say that this is actually what we're actually
discussing in this thread.
Can/Should we accept anonymous contributions (and thus we should not
care about a string being a name) or not?
I
[[ Since my blog is down, this is the all the report we'll see about FOSS-
North; do read Augustin's notes as well, though, https://toscalix.com/
2019/04/14/scale-summit-foss-north-and-some-routine-changes/ ]]
# Background
The KDE community was invited to the FOSS-North [1] conference again this
25 matches
Mail list logo
