[14:01] <eagles0513875> pleia2: seems like there is resistance to a custom developed document management system
[16:01] <pleia2> eagles0513875: I only see the comment from bkerensa
[16:02] <pleia2> it certaainly is an ambitious plan :) I think defining the requirements at this stage so you can evaluate existing options is good
[16:45] <eagles0513875> pleia2: i am reevaluating my concept at this point
[16:45] <eagles0513875> if we can work with alfresco and get the issues ironed out with open jdk erroring under high load
[16:45] <eagles0513875> i think alfresco would be a very viable option
[16:46] <eagles0513875> mhall119: balloons either of you around
[16:46] <pleia2> ok
[16:47] <mhall119> eagles0513875: in a meeting atm
[16:48] <eagles0513875> no problem mhall119 i might be able to provide you with the documentation of alfresco that might help you get a charm created
[16:53] <balloons> eagles0513875, in meetin'
[16:57] <eagles0513875> balloons: ok sry
[16:57] <eagles0513875> pleia2: alfresco is very nice to work with
[16:57] <eagles0513875> pleia2:  it has great potential in this application. for alot of projects and versioning control of documents as well as images eliminating the need for bzr all together
[16:58] <eagles0513875> we need to put it under high load and debug what issues alfresco is having with open jdk
[17:00] <pleia2> I think sorting out requirements is an important first step, we do need to support things like translations
[17:00] <pleia2> and make srure the translations community is ok with a translations system outside of bzr
[17:01] <eagles0513875> let me ask something really quickly
[17:01] <eagles0513875> pleia2: what format do the current translation files take?
[17:01] <eagles0513875> if they are .po files i think we could setup a seperate system entierly
[17:01] <eagles0513875> using pootle
[17:01] <pleia2> I don't know anything about translations
[17:02]  * pleia2 only speaks english :)
[17:02] <eagles0513875> i have done a bit of translating of libreoffice
[17:02] <eagles0513875> pootle is vry easy to make sure no strings are missed and can be done either offline or online
[17:03] <eagles0513875> pleia2: http://pootle.translatehouse.org/
[17:03] <eagles0513875> have no experience with system setup of this stuff.
[17:03] <eagles0513875> http://pootle.translatehouse.org/discover.html pleia2
[17:04] <pleia2> eagles0513875: honestly I don't have time to learn about them either, you'll really want to engage with them directly
[17:04] <eagles0513875> ya i dont either
[17:04] <eagles0513875> tbh
[17:04] <eagles0513875> atm catchign up on stuff for a deadline of two days ago
[17:06] <pleia2> even if I understood, I can't speak for preferences or workflows :)
[17:07] <pleia2> overhauling documentation is a massive job and you will need to recruit a team to work with if you want to propose something
[17:07] <eagles0513875> there is you phillw belkinsa lol
[17:07] <eagles0513875> im sure hall and the baloon master would be willing to join us
[17:08] <eagles0513875> dont want to highlight them as they are in a meeting
[17:08] <pleia2> I can devote time to improving the existing docs, but not this whole new system
[17:09] <pleia2> I've never really liked the comment-style docs and I remain unconvinced that months of work this will take will actually lead to something better
[17:10] <pleia2> but if it's something you want to do, I fully support the attempt :)
[17:10] <pleia2> just can't work on it directly myself
[17:10] <eagles0513875> i would love to do it :)
[17:10] <eagles0513875> it will be way easier to manage the teams and documentation
[17:10] <eagles0513875> with alfresco you setup projects
[17:10] <eagles0513875> and each project has its own wiki etc
[17:10] <eagles0513875> and then you add people to each respective project etc
[17:46] <shaunm> eagles0513875: what's wrong with the current bzr-based workflow?
[17:58] <eagles0513875> shaunm: dont you think its a bit steep of a learning curve for someone who has no idea how to work with version control
[17:58] <eagles0513875> let alone using the commandline with it
[18:05] <shaunm> eagles0513875: in my experience, these things aren't terribly difficult to teach.
[18:06] <shaunm> I mean, there are always trade-offs between making systems easier for beginners and making them useful for efficiently producing great results
[18:25] <eagles0513875> pleia2: what the heck is the deal with ubuntu splitting off dovecot for instance into a million different packages
[19:04] <eagles0513875> hey belkinsa
[19:04] <belkinsa> Hey, need anything from me?
[19:04] <eagles0513875> no just saying hi
[19:04] <belkinsa> I see.
[19:04] <eagles0513875> and swearing as to why canonical has opted to fragment dovecot into even more packages then before
[19:05]  * belkinsa is completely clueless here
[20:36] <pleia2> eagles0513875: in the case of dovecot there are lots of different add-ons for it, not all of which everyone wants to use, different database backends, different protocol support, much much better to just be able to install what you want to use + run than a monster of a package that has everything
[20:41] <pleia2> (and it wasn't Ubuntu or Canonical, those packages come from Debian