I'm more interested in the documentation than the tickets. Docs help current and future users for the product we already provide, no development necessary. Next would be improvements to enable incremental development. But even with zero future development, we can do better for our users.
And while it would certainly be nice to have the tickets, it's a lot of work, and isn't necessary to do things like "...getting an update out in step with Libpurple, removing (adding) accounts on any abandoned networks, and porting some new prpls to Adium". Is there any reason we shouldn't "simply" move development, tickets, and wiki to BitBucket? On Fri, Jan 18, 2019 at 5:19 PM Moses Lei <b...@moseslei.net> wrote: > > > > On Fri, Jan 18, 2019 at 3:16 PM erythronium23 <erythroniu...@gmail.com> wrote: >> >> I work at a fairly large company (>2000 engineers on Macs) and very time I >> introduce a Google Talk user to Adium, they adopt it. I think part of the >> adoption/growth problem is simply visibility. I think that a clear value >> proposition, and presence in the app store, would go a long way. I could be >> wrong, but I think it's not expensive to test that hypothesis. > > We've already had the discussion of whether we can be in the App Store years > ago. We can't because it violates the GPL and people are not willing to grant > exemptions for Adium or libpurple in order to fulfill the App Store's > distribution requirements. -- Matthew
