10:57:12 < kevinUofA> Good morning everyone!
10:59:12 -!- Shpoon [n=Miranda@c-67-190-184-217.hsd1.co.comcast.net] has joined #horde-board
10:59:31 < yunosh> hey kevin, liam, michael
10:59:39 < yunosh> and jan
10:59:43 < bklang_> Greetings all
10:59:46 -!- You're now known as bklang
11:00:17 < kevinUofA> How's everyone today?  Anybody been "fooled" yet?
11:00:40 < bklang> No, but I'm considering a change of profession to a monastic pursuit, does that count?
11:01:16 -!- MrVi [n=nuno@194.65.5.235] has joined #horde-board
11:01:32 < yunosh> not personally yet
11:01:34 < yunosh> hi nuno
11:01:38 < MrVi> is today's meeting a 1st of april joke?
11:01:43 < MrVi> or is it for real?
11:01:47 < yunosh> hehe, for real
11:01:54 < MrVi> hi all
11:01:55 < kevinUofA> uh... sure?  Hehe.  I'll take your stuff if you're purging, bk ;)
11:01:56 < liamr> i think we should impliment this in the new versions of ?IMP
11:01:57 < liamr> http://mail.google.com/mail/help/customtime/index.html
11:02:02 < bklang> kevinUofA: :)
11:02:37 < bklang> haha, nice feature
11:02:58 < yunosh> yeah, great indeed
11:03:07 < bklang> I guess we'll wait another minute or two before getting started
11:03:08 -!- duckslo [n=chatzill@84-255-207-254.static.t-2.net] has joined #horde-board
11:03:08 < kevinUofA> hehe e-flux capacitor.  Funny
11:03:11 < bklang> or use the CUstom Time feature
11:03:19 < kevinUofA> :{
11:03:23 < kevinUofA> er I mean :P
11:03:29 < kevinUofA> stupid fingers...
11:03:37 < yunosh> the formular is nice too
11:03:51 < bklang> I wonder what P works out to
11:04:04 < kevinUofA> 17
11:04:24 < yunosh> hi jakob
11:04:40 < kevinUofA> which, conicidentally, is the amount of wood a woodchuck could chuck if said woodchuck could chuck wood....
11:04:59 < yunosh> apropos chuck, he will be missing today
11:05:02 < bklang> Chuck has not pontificated on woodchuck capacity to my knowledge
11:05:47 < kevinUofA> Ah... well you must not have paid for your woodchucking awareness course through the church of Chuckology
11:06:19 < bklang> alright my clock shows 5 after so we should get started
11:06:30 < yunosh> alright, enough of april fun :)
11:06:35 < kevinUofA> :)
11:06:36 < yunosh> welcome everybody again
11:06:44 < yunosh> looks like we get smaller each time
11:06:51 < yunosh> i hope it doesn't stay like that
11:07:07 < yunosh> bklang will lead through the agenda, so lets start
11:07:14 < liamr> unfortunately, we have a local meeting at this time to discuss our Horde 3.2 / IMP 4.2 deployment.
11:07:16 < liamr> fate.
11:07:23 < bklang> Alright the first item is Horde 3.2 release status
11:07:45 < bklang> Yunosh if you'll give an overview of where we are.  Also Chuck wanted to mention our showstoppers and see if there are any volunteers for assistance
11:07:52 < yunosh> yeah
11:08:03 < yunosh> well, we're still progressing
11:08:07 < yunosh> slow but steady
11:08:17 < yunosh> it's overtime for another set of RCs
11:08:31 < yunosh> many bugs have been fixed and few niceties added since the last
11:08:46 < yunosh> i *hope* to get the finals out before my vacation
11:08:52 < yunosh> that will be in two weeks
11:08:59 < yunosh> but i'm afraid that won't work out
11:09:08 < liamr> We
11:09:17 < liamr> (oops, sorry)
11:09:24 < yunosh> it would help if people could take a look at the showstopper list: http://wiki.horde.org/ShowStoppersThreeTwo?referrer=ReleaseManagement#
11:09:43 < yunosh> see if there are patches or tests, or analyzing necessary
11:09:54 < yunosh> so that we get them closed as soon as possible
11:10:04 < Shpoon> i jan - that's not right
11:10:07 < MrVi> jan: all the tasks there say DONE at the end
11:10:08 < Shpoon> its a different link
11:10:15 < Shpoon> you want the whups link
11:10:16 < MrVi> so i guess we're ready :)
11:10:22 < yunosh> eh, yes, wrog copy and paste
11:10:41 < Shpoon> http://bugs.horde.org/runquery.php?query=329
11:10:42 < MrVi> miranda: no skiing today?
11:10:58 < yunosh> thanks
11:11:52 -!- cjh [n=chuck@horde/chuck] has joined #horde-board
11:12:04 < yunosh> ah, hi chuck
11:12:10 < yunosh> meeting over already?
11:12:19 < cjh> yeah, interview was cancelled
11:12:30 < yunosh> good for us, i guess
11:12:38 < Shpoon> one note - we have 6179 as a showstopper, but it depends on ticket 6132 (a non-showstopper)
11:12:39 < yunosh> any comments, questions to the show stopper list?
11:12:46 < Shpoon> excuse me 6312
11:13:02 < yunosh> that is the redirecting bug right?
11:13:09 < yunosh> should be a showstopper too then
11:13:34 < yunosh> added
11:14:23 < bklang> Unless anyone has any other feedback on the bug list, I'll say please feel free to jump in on those to help us speed the 3.2 release
11:14:29 < bklang> and we can move on to the next item
11:14:55 < Shpoon> i was going to ask jan about the dimp preview bug, but i can do that privately
11:14:56 < MrVi> do you believe that 3.2 is released before the next meeting?
11:15:06 < bklang> before the next Board meeting?
11:15:12 < yunosh> that would be great
11:15:22 < yunosh> and we should have that as a goal
11:16:03 < MrVi> hehe
11:16:26 < bklang> Alright the next item is discussion of the applications being released with or after Horde  3.2
11:16:39 < MrVi> being great is one thing, believing it will be released is a different thing :)
11:16:48 < yunosh> http://wiki.horde.org/ReleaseManagement is the correct link for that
11:17:00 < yunosh> MrVi: i know :)
11:17:22 < yunosh> basically we release all groupware apps with horde 3.2
11:17:32 < bklang> This item is mostly information and dovetails nicely into the next item which is all the new apps going 1.0
11:17:34 < yunosh> wo we can also release the groupware 1.1 bundles
11:18:00 < yunosh> yeah, after the 3.2 release we realease the remaining stable apps, plus a set of new ones
11:18:22 < yunosh> does anybody not know all the applications listed there?
11:18:29 < yunosh> i.e. what they do?
11:18:38 < kevinUofA> Are there descriptions of what the new apps released after 4.2 are somewhere?
11:18:52 < kevinUofA> I've heard of a few but not all
11:18:57 < bklang> I will add that information to teh wiki page, but you can see the information on the CVS page
11:19:17 < bklang> http://www.horde.org/source/modules.php
11:19:17 < yunosh> we are going to add application pages on the horde websites for those of course
11:19:33 < kevinUofA> cool.  thanks
11:19:43 < bklang> that page has a one-line description of ALL the "beta" and "stable" apps in CVS
11:19:55 < bklang> not including the "incubator" apps, which are alpha or less
11:20:03 < yunosh> ansel: gallery, hermes: time tracking, jonah, feed reader/agregator/etc, trean: bookmarks, whups: tickets, wicked: wiki
11:20:40 < bklang> I think it's significant to note that this is a large improvement in the "stable" base of applications within Horde
11:20:46 < kevinUofA> awesome... someone was asking me if we could do something like Trean just the other day.  Very handy :)
11:20:48 < bklang> dramatically expanding its scope beyond just groupware
11:21:07 < yunosh> yeah
11:21:09 < bklang> kevinUofA: and that's why I'm personally so excited to see these apps released
11:21:25 < bklang> they were in some ways Horde's best kept secret
11:22:10 < yunosh> well, at least they are listed on the home page ;)
11:22:14 < kevinUofA> I think I'm gonna have fun this summer playing with these and seeing what I can get into production :)
11:22:21 < bklang> Alright unless there are questions on the apps for 3.2 or the new 1.0 apps we can move on
11:22:58 < bklang> Oh, one thing Chuck asked me to mention is the first Dashboard widget design for Horde
11:23:18 < kevinUofA> oh yeah!  what's that about?
11:23:21 < bklang> it is a part of Hermes (one of the new 1.0 apps) and allows users to enter time directly from the OS X Dashboard using XML-RPC
11:23:28 < bklang> the name of the app is "Sandals"
11:23:31 < bklang> or widget rather
11:23:58 < bklang> there are a few ToDos left on it but it does work now.  I'm using it personally at work to track my time
11:24:09 < kevinUofA> neat!
11:24:17 < yunosh> btw, might not belong here, but is there a way to provide it for download?
11:24:27 < yunosh> the current installation is a bit awkward
11:24:46 < yunosh> that is, download in a single file
11:24:49 < bklang> well we could zip it as part of the release tarball
11:24:52 < bklang> that's common for Apple widgets
11:25:13 < yunosh> ok, so that's how other widgets are distributed too?
11:25:17 < bklang> but I didn't think it was big enough for its own project (feel free to say otherwise)
11:25:30 < bklang> yeah, the .wdgt on OSX is actually a directory
11:25:35 < bklang> though Finder presents it as a single unit
11:25:39 < bklang> it's a common thing on OS X
11:25:44 < yunosh> yeah, i know, like the .app dirs
11:25:47 < bklang> exactly
11:25:54 < bklang> I'd suggest we zip it up for distribution
11:25:59 < yunosh> well, we can create a zip on the fly then
11:26:14 < yunosh> that would even have the paths right then
11:26:20 < yunosh> and server name etc
11:26:22 < bklang> There may be other Widgets released in the future, partially depending on the feedback we get froM Sandals
11:26:31 < bklang> yunosh: that would be fantastic
11:26:45 < bklang> I also want to expand it to include Horde theme support, which could also be preconfigured based on Pref
11:27:10 < bklang> right now I have different Horde installs and the only wait Ikeep them straight is that each one has its own color set :)
11:27:12 < yunosh> true, or even fetched from the server?
11:27:34 < bklang> that might work, though would be more work for the client...not sure how feasible it is to have Widgets self-modify
11:27:45 < bklang> anyway we can have this discussion in #horde-dev later :)
11:28:02 < yunosh> true
11:28:19 < bklang> I only have one other item, and that is the announcement of the first app to emerge from the Incubator
11:28:31 < bklang> there was an announcement to dev@lists.horde.org earlier  as well
11:28:44 < bklang> The module is named Beatnik and allows the management of DNS records via the Horde user interface
11:28:54 < bklang> it currently has two backends: ldap2dns and sql
11:29:03 < kevinUofA> cool!
11:29:07 < bklang> ldap2dns is a separate project (which I maintain incidentally) that can prepare zone files for BIND or TinyDNS
11:29:26 < bklang> the sql backend was written by Duck and includes a script to create zone files (all in PHP)
11:29:52 < bklang> this module is Beta at the moment 
11:30:01 < bklang> it works for me but is not quite feature complete
11:30:38 < bklang> Well I guess that's about it
11:30:40 < bklang> are there any questions?
11:30:43 < duckslo> works for me. but we are using it internally.
11:31:13 < kevinUofA> I have one.  My boss has been bugging me to ask about Kronolith and whether anyone was working on an AJAX version
11:31:23 < kevinUofA> that's the only way he'll ok implementation...
11:31:38 < yunosh> yes :)
11:31:45 < kevinUofA> *JOY*
11:32:05 < kevinUofA> what stage ca I tell him that project is at?
11:32:11 < kevinUofA> (can)
11:32:29 < yunosh> pre-contract
11:32:36 < yunosh> not a single line of code yet, sorry
11:33:08 < yunosh> but maybe this is not a bad forum here to ask for comments on a name for that new module
11:33:21 < yunosh> it will work like DIMP as an ajax frontend to kronolith
11:33:24 < bklang> I guess DKronolith doesn't have the same appeal as DIMP
11:33:28 < yunosh> lol
11:33:35 < kevinUofA> hehe
11:33:38 < yunosh> i have some ideas already
11:33:53 < bklang> Akrono?
11:33:57 < yunosh> Kronular, Perenna, Gregor, Kalki, Dekad
11:33:57 < bklang> A for asynchronous
11:34:06 < yunosh> not bad either
11:34:40 < bklang> I like keeping the name close to Kronolith so people familiar with Horde can sense the connection at sight
11:34:43 < kevinUofA> how bout akronos (seems to roll off the tongue better)?
11:34:56 < bklang> works for me
11:35:20 < yunosh> yeah, better than Akrono
11:35:30 < Shpoon> do we need a name?
11:35:38 < yunosh> sure?
11:35:42 < Shpoon> i.e. dimp and mimp are going to be going away as of IMP 5
11:35:51 < Shpoon> since they will all be integrated
11:35:54 < yunosh> well, yeah
11:35:59 < yunosh> good point
11:36:06 < kevinUofA> if it's a separate application you'd want a way to distinguish the project at least
11:36:22 < cjh> seems like doing it as part of krono from the start would be better to me
11:36:44 < bklang> If that's practical I tend to agree.  
11:36:49 < MrVi> a name started with a "D" would be cool.. you could name all the ajax apps as the "D" family apps
11:36:54 < kevinUofA> agreed.  If it's an upgrade to krono then that makes more sense.
11:37:38 < yunosh> i guess we'll have to discuss the pros and cons of separate vs. single app
11:37:46 < yunosh> but that's not the place here for that
11:37:53 < yunosh> thanks for the suggestions though :)
11:37:58 < kevinUofA> :)
11:38:04 < bklang> Alright, any other questions on anything Horde related?
11:39:01 < bklang> Well hearing nothing, I want to thank everyone for turning out again.  Our next meeting will be Tuesday, May 6.
11:39:17 < kevinUofA> Sounds good!
11:39:22 < MrVi> hopefully with 3.2 released :D
11:39:27 < bklang> Anything in the meantime can of course go to board@lists.horde.org
11:39:49 < yunosh> i'll be in italy by then :)
11:39:55 < liamr> here's hoping.  we're planning on deploying Horde 3.2 at the beginning of May.
11:40:24 < bklang> We'll do what we can. Again anyone who can help with a showstopper bug would be very helpful.
11:40:48 < bklang> http://bugs.horde.org/runquery.php?query=329 just in case :)
11:41:08 < bklang> Alright thanks again everyone.  Talk to you all again in May
11:41:19 < duckslo> back to work. bye bye
11:41:21 -!- duckslo [n=chatzill@84-255-207-254.static.t-2.net] has quit ["ChatZilla 0.9.81 [Firefox 2.0.0.13/2008031114]"]
11:41:23 < yunosh> see you, everyone
11:41:32 < cjh> thanks!
11:44:45 < kevinUofA> Hey regarding the new 1.0 apps... are they "in the can" and ready to go and just waiting for 3.2?
11:45:32 < yunosh> like the other apps: there are few bugs to close yet, and a few features to add
11:45:38 < yunosh> but they're usable as-is
11:45:49 < yunosh> and pretty stable
11:45:58 < kevinUofA> cool.