[09:02] <davidcalle> Morning o/
[16:53] <jose> jcastro, mhall119: ping, is there any way I can get ahold of elmo? sent him an email weeks ago and no response back
[16:53] <mhall119> jose: do you need elmo specifically, or just someone in IS?
[16:54] <jose> mhall119: elmo. I basically asked if there was any knowledge or previous effort/discussion to migrate the wiki so we didn't step on anyone's toes, but I already asked a couple individuals in IS and all of them end pointing me to elmo
[16:55] <jcastro> I think many have talked about it but no one has tried tried
[16:55] <mhall119> jose: in that case you may have to wait until Tuesday, lots of people are on holiday already
[16:55] <jose> that's fine
[16:55] <jose> jcastro: I'd like to know if they found anything in their discussions (fwiw, I know elmo wanted to move at some point)
[16:55] <jose> if there's any blockers they found it may be a good time to address them
[16:57] <jcastro> I don't think it's been thought of any time soon
[16:57] <jcastro> so like, probably whatever issues he talked about are at least 3-4 years old
[16:57] <jose> ah ok
[16:59] <mhall119> jose: https://github.com/django-wiki/django-wiki :)
[17:00] <jose> looks really nice, but it's a beta - I'd prefer to have something stable for such vital wikis
[17:00] <mhall119> we lived with moin for all these years, would we even know what to do with a stable wiki?
[17:03] <wxl> mhall119: YES
[17:03] <mhall119> back in the day newz2000 and I built a prototype branch-based-editing CMS on Django...that would have been fun to use
[17:03]  * mhall119 misses newz
[17:04] <svij> we have a django-based Wiki in our german community. Works pretty good.
[17:05] <svij> no, not open source (yet), and also a "all in one" self-written solution with forums, news, planet and wiki…
[17:05] <mhall119> svij: that's the danger or making a new django project, you never know when to stop :)
[17:06] <svij> well back in 2008 we were running moinmoin + wordpress + phpBB bundled together that got replaced
[17:06] <svij> now we don't have enough contributors to open source it (many hardcoded stuff and maybe some security issues)
[17:10] <mhall119> svij: yeah, ours wasn't open sourced either, mostly because it was hacked together over a few evenings during UDS-P while we were sprinting
[17:10] <svij> ah okay
[17:11] <mhall119> still, the idea behind it was pretty cool I thought, having "branches" of content in your CMS that you can selectively merge into trunk
[17:11] <svij> we hope to open source it this year, might be intersting for other LoCos who needs such a "all in one" solution
[17:11] <mhall119> svij: awesome, put out a call for help and you can recruit some trustworthy folks to help you clean up any security issues
[17:12] <svij> I actually never thought about doing a wider call, we just had a few german guys
[17:12] <svij> but yes, I'll note that idea and talk to the other guys. :)
[17:13] <mhall119> svij: having a ready to deploy "loco team website" project would be great
[17:13] <svij> yeah
[17:13] <mhall119> jcastro could help us charm it up and have a single-command deployment
[17:14] <svij> it's running on https://ubuntuusers.de/ btw
[17:16] <jcastro> afaik I think that's how a loco team website would be done
[17:16] <jcastro> it'd just be a branch on top of django like how IS does wordpress
[17:17] <jcastro> https://insights.ubuntu.com/2015/04/22/rewriting-wordpress-juju-charms-for-security-and-ha-on-openstack/
[17:18] <jcastro> I think when people start to talk about it though
[17:18] <jcastro> really it's either mediawiki, which is known and understood
[17:18] <jcastro> or some variation of boutique wiki on weird stacks no one will want to use
[17:18] <jcastro> or "a front end onto git"
[18:19] <mhall119> s/git/bzr/ and I'm sold
[18:20] <mhall119> the bitbucket wikis that were mercurial branches were awesome to work on