All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: kurt.pfeifle@gmail.com,
	"printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>
Cc: Aveek Basu <aveek.basu@lexmark.com>
Subject: Re: [Printing-architecture] OpenPrinting News
Date: Thu, 14 Feb 2019 21:57:59 +0100	[thread overview]
Message-ID: <74fba676-bbc2-e318-724f-131f30b5ec07@gmail.com> (raw)
In-Reply-To: <CAK+62whQu7X+PwS3RsZk__vY7q1deG-HwejpTTkqWV-4He-pow@mail.gmail.com>

On 14/02/2019 18:49, Kurt Pfeifle wrote:
> This is not correct.
> 
> Avahi was initially created by Trend Lloyd in early 2004. He was 
> certainly inspired by Apple's Bonjour, which unfortunately was not Open 
> Source initially, so there as a strong motivation to implement a FOSS 
> ZeroConf stack, since all of the relevant specs (mDNS + DNS-SD) were 
> already there at IETF, and open.
> 
> Later that same year Lennart Poettering started a similar project to 
> implement mDNS/DNS-SD functionality called "FlexMDNS".
> 
> Both projects united and merged their code bases sometime in 2005. 
> Though I have no idea which of the two guys wrote more lines of code 
> that still exists in today's code base, Poettering surely had a heavy 
> impact on today's Avahi.
> 
> Apple released Bonjour as Open Source software under the Apache License 
> only in 2006.
> 
> Avahi's name certainly was Trend's decision, and he started his 
> implementation half a year before Poettering.
> 
> Poettering's last commit into Avahi's GitHub code was in Sept  2012. 
> Trend's last commit was 10 days ago. The last time Trend merged a major 
> pull request was in August 2018. See 
> https://github.com/lathiat/avahi/commits?author=lathiat.
> 
>   According to https://github.com/lathiat Trend works for Canonical.
> 

That is interesting to know. Now I understand why Trent does not like 
that someone will take the project away from him.

The best would be if Trent would allow some additional persons to 
directly upload and perhaps even to do releases, so that he does not 
have the full workload but still be part of his project.

He needs to admit that he is not able to carry the load and 
responsibility of leading a project which is an integral part of the OS.

For me it looks like that we have to prepare a fork to have a version 
where the distros can work with and rely on.

    Till



  reply	other threads:[~2019-02-14 20:57 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 18:14 [Printing-architecture] OpenPrinting News Till Kamppeter
2019-02-13 20:34 ` Michael Sweet
2019-02-13 21:26   ` Till Kamppeter
2019-02-13 21:43     ` Michael Sweet
2019-02-13 23:56     ` Solomon Peachy
2019-02-14  8:34       ` Zdenek Dohnal
2019-02-14 17:49       ` Kurt Pfeifle
2019-02-14 20:57         ` Till Kamppeter [this message]
2019-02-14 23:43           ` Kurt Pfeifle
2019-02-14 13:21 ` Zdenek Dohnal
2019-02-14 14:39   ` Zdenek Dohnal
2019-02-14 15:31     ` Till Kamppeter
2019-02-14 16:12       ` Zdenek Dohnal
2019-02-14 14:52   ` Till Kamppeter
2019-03-06 14:55 Till Kamppeter
2019-04-05 15:10 Till Kamppeter
2019-04-05 19:20 ` Till Kamppeter
2019-04-07 15:21   ` Till Kamppeter
2019-04-07 15:28     ` Ira McDonald
2019-04-07 15:38 ` Till Kamppeter
2019-05-12 16:03 Till Kamppeter
2019-05-12 18:15 ` Matthias Apitz
2019-05-12 18:48   ` Till Kamppeter
2019-06-04 10:41 Till Kamppeter
2019-06-04 11:24 ` Zdenek Dohnal
2019-08-07 12:44 Till Kamppeter
2019-09-03 21:16 Till Kamppeter
2019-11-06 23:06 Till Kamppeter
2019-12-14  0:44 Till Kamppeter
2020-01-17 21:24 Till Kamppeter
2020-02-17 11:19 Till Kamppeter
2020-03-20 22:18 Till Kamppeter
2020-03-23  6:03 ` Zdenek Dohnal
2020-04-11  8:32 Till Kamppeter
2020-05-18 21:27 Till Kamppeter
2020-06-05 22:58 Till Kamppeter
2020-07-10 18:57 Till Kamppeter
2020-08-14  6:29 Till Kamppeter
2020-08-14 11:42 ` Till Kamppeter
2020-08-17  6:00   ` Zdenek Dohnal
2020-09-11 18:53 Till Kamppeter
2020-10-26 19:54 Till Kamppeter
2020-11-12 22:59 Till Kamppeter
2020-12-13 20:10 Till Kamppeter
2021-01-15 20:05 Till Kamppeter
2021-02-08 23:13 Till Kamppeter
2021-02-10  6:01 ` Zdenek Dohnal
2021-03-06  0:14 Till Kamppeter
2021-04-11 12:53 Till Kamppeter
2021-05-21 16:30 Till Kamppeter
2021-06-15 11:21 Till Kamppeter
2021-07-17  0:10 Till Kamppeter
2021-07-18 10:50 ` Andreas Radke
2021-08-13 22:17 Till Kamppeter
2021-09-16 19:18 Till Kamppeter
2021-10-12 22:09 Till Kamppeter
2021-10-13 10:28 ` Zdenek Dohnal
2021-10-13 11:57   ` Till Kamppeter
2021-10-13 12:32     ` Zdenek Dohnal
2021-11-13 23:49 Till Kamppeter
2021-12-10 19:25 Till Kamppeter
     [not found] ` <20211210212022.7818a35d@laptop64>
2021-12-10 22:54   ` Till Kamppeter
2022-01-17 18:16 Till Kamppeter
2022-02-14 18:38 Till Kamppeter
2022-03-18 15:00 Till Kamppeter
2022-04-13 20:08 Till Kamppeter
2022-05-11 22:12 Till Kamppeter
2022-06-14 18:51 Till Kamppeter
2022-08-19 22:13 Till Kamppeter
2022-09-22 17:43 Till Kamppeter
2022-10-21  0:38 Till Kamppeter
2022-11-21 13:43 Till Kamppeter
2022-12-19  0:26 Till Kamppeter
2023-01-20 22:29 Till Kamppeter
2023-02-27 23:35 Till Kamppeter
2023-03-28 20:56 Till Kamppeter
2023-04-16 21:06 Till Kamppeter
2023-05-25  9:07 Till Kamppeter
2023-07-04 16:51 Till Kamppeter
2023-09-05 22:06 Till Kamppeter
2023-10-04 23:48 Till Kamppeter
2023-11-03  9:00 Till Kamppeter
2023-11-28  1:30 Till Kamppeter
2023-12-21  4:05 Till Kamppeter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=74fba676-bbc2-e318-724f-131f30b5ec07@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=aveek.basu@lexmark.com \
    --cc=kurt.pfeifle@gmail.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.