On Fri, Jan 18, 2019 at 5:06 PM Moses Lei <b...@moseslei.net> wrote: > Colin/Matthew: do we have enough development resources to continue on with > the project, in your opinion? > > If we don't have people to maintain infrastructure, perhaps we should look > at some more creative solutions? For example, how about exporting our trac > data and importing it into Pidgin's trac as a component? That saves us from > having to manage trac, and gives us direct linking to the pidgin/libpurple > community's bugs and issues. >
Pidgin's trac will be dying at somepoint... When exactly, I don't know as other options kind of suck... But trac is a pig on resources and slow to boot. It needs to be replaced. > On a similar note, could Adium rebrand and become Pidgin for MacOS? @Gary, > I'm curious as to what you think of that. > I mean.. that's possible sure.. but Pidgin3 uses Gtk3 and Gtk3 has a native Quartz backend, so Pidgin3 will literally just work natively (read no XQuartz) on OSX. Thanks, -- Gary Kramlich <g...@reaperworld.com>
