[Printing-architecture] OpenPrinting News

Kurt Pfeifle kurt.pfeifle at googlemail.com
Thu Feb 14 23:43:56 UTC 2019

On Thu, Feb 14, 2019 at 9:58 PM Till Kamppeter <till.kamppeter at 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.

In any case, starting at the last link I provided, this leads, within 5
minutes to...

* ...his info that he works for Canonical,
* ...an email address registered by Trent with GitHub,
* ...a website run by him showing his Twitter handle,
* ...confirming his Canonical association info,
* ...showing his frequent Twitter activity.

In the same time span spent at https://github.com/lathiat/avahi/issues I
could not identify...

* ...any bug reports related to problems created by Avahi shortcomings
   for CUPS printing as mentioned before,
* ...any pull requests submitted at GitHub to solve these problems.

But maybe I was not aware of what I should search for....

However I noted the following Avahi statistics on GitHub:

* 81 open vs. 43 closed Issues.
* 39 open vs. 55 closed Pull Requests.

So indeed, the activities on Avahi have slowed down in recent years.
But it is not the case that Trent is missing from planet earth or turned
un-interested regarding computer-related topics.

So my advice would be the following:

* Create the relevant bug reports ("issues") for Avahi on GitHub.
* Create the most wanted feature requests for Avahi on GitHub.
* For each bug and feature supply a pull request on GitHub.
* Upvote/comment/like/discuss these new activities on Avahi's GitHub.
* Contact Trent via Twitter (where he seems most responsive) about
   the Github issues and ask for his comments.
* If he does not show any willingness to integrate well done pull
   requests, then only seriously consider a fork on the project. Y'all
   will have an easier way to convince people about the need for
   such a drastic step, if your PRs are sitting there for too long. Also
   a fork will have a headstart, if the code to add/improve is already
   waiting there, well-tested.

Don't just jump into such an adventure based on rumours, un-prepared and
without your troops well-equipped.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/printing-architecture/attachments/20190215/a7d120ae/attachment.html>

More information about the Printing-architecture mailing list