On Fri, Jan 18, 2019 at 11:02 AM Luke Hiesterman <gravis...@gmail.com> wrote:
> Maybe start with your ideas? > 1. move the bitbucket.org/adium account from a single use account to a team account, provide access to everyone that needs it 2. move primary repo from hg.adium.im to bitbucket.org/adium. We did the same with pidgin about 2 years ago now and it's been working well. 3. Either fix up buildbot or integrate adium into https://bamboo.pidgin.im. I have a mac mini running high sierra i think, i'd have to check to be sure, and get that setup to do CI which has been planned to get added to the pidgin bamboo already. 4. if we're going to stick with the existing cpanel instance, we can leave it where it is, or we can migrate it to a hosting provider where a pidgin dev works. 5. Get trac back up and running, either on the existing cpanel instance or pull it into the kubernetes cluster I've been migrating pidgin services to. I had more, but that should be a good start? > Luke > Thanks, -- Gary Kramlich <g...@reaperworld.com>
