Hello, Asher.

Don't read much into the lack of activity here; I think all of us that have
been active over the last year have used other channels for communication.
At least after a few pings to see who was actually interested in continuing
the effort... At this point, 99% of our efforts have been towards the
infrastructure, so that we can actually use the resources we already have
(tickets, documentation, code, xtras, etc).

Matthew


On Tue, Dec 10, 2019 at 6:59 PM Asher Haig <as...@strong.ai> wrote:

> Hey Everyone!
>
> *Looks Around* … Echoes?
>
> Somehow, after two decades and plenty of bit rot, Adium still manages to
> be not only functional but IMO still the best chat option around (kudos to
> Evan and others for doing such an outstanding job writing sustainable
> code).
>
> That said, it seems there has been quite a bit of inevitable creep,
> particularly in repository organization. I’m going to work on cleaning that
> up as well as updating the code base. While doing so, I’d like to avoid
> stepping on any toes as much as possible— but given how much needs to be
> moved around, that may be inevitable.
>
> So in the interest of coordination, could anyone that is still active or
> would like to participate in this process (even if only by way of dialogue)
> please sound off?
>
> If I can get a sense of who is still interested in participating in Adium
> it will help figure out the best way to approach things.
>
> Thanks!
>
> Asher
>
> > On Dec 10, 2019, at 7:52 PM, Evan Schoenberg <e...@adium.im> wrote:
> >
> > I’d like to introduce to you all my cousin Asher Haig.  He is one of
> Adium’s longest-term and heaviest users.  I’ll never forget redesigning the
> Events system with his help while visiting him in Berlin over Spring Break
> circa 2004.  He has a PhD in artificial intelligence, and is a skilled
> programmer, with a primary background in C and C++.
> >
> > He uses Adium daily and is interested in helping maintain and improve
> it.  I’ve added him directly to the GitHub team and to the committers
> list.  There’s nobody active enough right now to provide useful and timely
> code review if we were to follow the “traditional” patch process.  I’ve
> been working with him to get him acclimated to the code, though that often
> takes the form of “Hm, I do remember when we wrote that hack 14 years ago…”
> or “Yeah, that was a workaround for a bug in Mac OS X 10.2.”  Good times.
> >
> > Best,
> > Evan
>
>

-- 

Matthew

Reply via email to