On Fri, Jan 18, 2019 at 9:39 PM Matthew <mathuaerkne...@gmail.com> wrote:
> 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. > Funny you mention documentation. Pidgin is currently in the process of converting pidgin.im and developer.pidgin.im into a static site generated by hugo. You can see an early version of it at http://nest.pidgin.im. All the docs are being converted from the genshi template format that trac uses to markdown which hugo then renders. Hugo has a huge theme database and it's pretty straight forward to get going with. > > 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". > The other thing about the old tickets is... If they're really bad.. they'll reappear :) > Is there any reason we shouldn't "simply" move development, tickets, > and wiki to BitBucket? > Pidgin only moved the code to bitbucket primarily for pull requests. The wiki isn't bad, but it's not great either. See my earlier comments about moving to hugo and https://nest.pidgin.im for the way Pidgin went. Issues are problematic too as Bitbucket's issues are super nerfed as Atlassian wants you to use Jira... That said, Atlassian does offer open source licenses for all of their products. That's how Pidgin is using Bamboo. Thanks, -- Gary Kramlich <g...@reaperworld.com>
