2012-06-02T12:04:29  <willkg> ok. should be logging now.
2012-06-02T12:04:36  <willkg> sorry it took a while.
2012-06-02T12:04:40  <paroneayea> np :)
2012-06-02T12:04:41  <paroneayea> okay!
2012-06-02T12:04:49  <paroneayea> so, agenda http://wiki.mediagoblin.org/Meeting#Next_Meeting
2012-06-02T12:04:59  <paroneayea> we usually start off reflecting on how the last month has been
2012-06-02T12:05:30  <paroneayea> it seems like there have been some exciting things in development (a bit of work on kuneco, the api, plugins!)
2012-06-02T12:05:36  <paroneayea> but it also kind of feels like we're in a bit of a lull
2012-06-02T12:05:40  <paroneayea> I'm not sure if that's accurate or not
2012-06-02T12:05:55  <willkg> the work to move to sql was pretty intense.
2012-06-02T12:06:06  <paroneayea> yeah
2012-06-02T12:06:33  <paroneayea> it could just be that people need to recooperate, which is totally normal
2012-06-02T12:06:49  <paroneayea> as long as we can avoid the lull extending into loss of momentum :)
2012-06-02T12:07:00  <paroneayea> I've been distracted personally by a bunch of things, but those things will be resolving in about a week, I think.
2012-06-02T12:07:21  <paroneayea> so anyway
2012-06-02T12:07:33  <paroneayea> I'm not sure if anyone is here other than willkg, freedeb and I :)
2012-06-02T12:07:33  <willkg> anyone else at this meeting?
2012-06-02T12:07:39  <willkg> haha!
2012-06-02T12:08:07  <freedeb> hmm
2012-06-02T12:08:22  <freedeb> it's a pretty good day for an IRC mtg in Massachusetts
2012-06-02T12:08:24  <willkg> if it's just the three of us, we can work through things pretty quick.
2012-06-02T12:08:38  <paroneayea> maybe we really are in a lull ;)
2012-06-02T12:08:39  <willkg> freedeb: +1. rainy and dreary outside.
2012-06-02T12:08:51  <paroneayea> yeah, let's plow through the agenda then :)
2012-06-02T12:08:54  <willkg> did the meeting notification email go out?
2012-06-02T12:08:54  <freedeb> ok
2012-06-02T12:08:57  <freedeb> yes
2012-06-02T12:09:04  <willkg> ok. hrm... puzzling.
2012-06-02T12:09:07  <paroneayea> willkg: it did, but I failed to do a bit more drum up the day before
2012-06-02T12:09:09  <paroneayea> which I usually do.
2012-06-02T12:09:10  <freedeb> I pulled the agenda off it
2012-06-02T12:09:24  <willkg> maybe we need to do more to notify people. i know some folks aren't on the mailing list.
2012-06-02T12:09:35  <willkg> maybe gmgbot should remind people when they log in.
2012-06-02T12:09:45  <willkg> or something.
2012-06-02T12:09:52  <paroneayea> I think people also don't pay attention to a saturday morning notification
2012-06-02T12:09:58  <paroneayea> which is all I did this time
2012-06-02T12:10:07  <paroneayea> I guess next time I'll be more careful to do proper drum-up :)
2012-06-02T12:10:19  <willkg> it'd be nice to automate things, too.
2012-06-02T12:10:21  <freedeb> I saw bcs yesterday and forgot to mention it
2012-06-02T12:10:31  <freedeb> although I had intended to
2012-06-02T12:10:32  <paroneayea> joar put an item on the agenda
2012-06-02T12:10:39  <freedeb> it was a newsy week for floss
2012-06-02T12:10:46  <willkg> joar: you on?
2012-06-02T12:10:52  <paroneayea> I was a bit distracted by liberated pixel cup launch :)
2012-06-02T12:11:05  <freedeb> also jpope was on identi.ca a  half hour ago
2012-06-02T12:11:20  *** ErkanYilmaz2 has joined #mediagoblin
2012-06-02T12:11:24  <paroneayea> and elrond said he couldn't make it :)
2012-06-02T12:11:26  <paroneayea> ah well... so anyway, going through the agenda, first item is docs changes
2012-06-02T12:11:32  <paroneayea> willkg: that's all you!
2012-06-02T12:12:03  <willkg> sweet. so i want to add a "contributor's guide" section to the docs/.
2012-06-02T12:12:22  <paroneayea> willkg: what would that do relative to the HackingHowto?
2012-06-02T12:12:28  <willkg> what's in docs/ also goes out with release tarballs. it's versioned, so when we update hacker installs, that's specific to a version.
2012-06-02T12:12:48  <paroneayea> willkg: ah okay... what's the motivation?
2012-06-02T12:13:03  <willkg> so i was thinking i'd add a light contributor's guide to the docs/ which points to the wiki for "the latest". and i'd update it before every release.
2012-06-02T12:13:25  *** ErkanYilmaz2 has quit IRC
2012-06-02T12:13:41  <willkg> the motivation is like i said--stuff in docs/ goes out with release tarballs. plus it's versioned alongside the software. install guides apply to a specific version of the software, so it's good to have.
2012-06-02T12:13:57  <paroneayea> willkg: just a thought though: if the idea is to version the contribution guide, won't most contributors be working with git master anyway?
2012-06-02T12:14:00  <willkg> plus if someone comes to the project through docs.mediagoblin.org, there's no indication that we have a contributor base and all that.
2012-06-02T12:14:02  <paroneayea> not with a specific branch?
2012-06-02T12:14:08  <paroneayea> yeah I agree on that bit
2012-06-02T12:14:16  *** ErkanYilmaz2 has joined #mediagoblin
2012-06-02T12:14:20  <paroneayea> although maybe linking more clearly back and forth can help with that?
2012-06-02T12:15:00  <willkg> possibly. depends on what that entails specifically.
2012-06-02T12:15:00  <paroneayea> I'm not against the idea, but it maybe is an extra thing to maintain, which is why I bring up that most contributors will be working through git anyway?
2012-06-02T12:15:39  <willkg> i don't know.
2012-06-02T12:16:13  *** ErkanYilmaz2 has quit IRC
2012-06-02T12:16:13  <willkg> you have a better idea of our existing contributor base.
2012-06-02T12:16:51  <paroneayea> well I'm not against the idea, though I think the hackinghowto is working well enough for contributors presently.. the big risk is the lack of knowledge that the hackinghowto exists when you hit the docs
2012-06-02T12:16:53  <freedeb> would this help us potentially bring in new contributors?
2012-06-02T12:17:12  *** ErkanYilmaz2 has joined #mediagoblin
2012-06-02T12:17:30  <willkg> i have no stats on how often people look at our documentation, so i don't know for sure. i do know that it's an entry point for people. and if we lose them at that entry point, then we lose them.
2012-06-02T12:17:59  <willkg> so, if i'm someone and i look at http://docs.mediagoblin.org/ there's nothing that suggests we have a contributor base.
2012-06-02T12:18:04  <willkg> or that i can contribute.
2012-06-02T12:18:11  <paroneayea> willkg: I say for now we should add the links back and forth.
2012-06-02T12:18:17  <paroneayea> and that's a lot less difficult to maintain?
2012-06-02T12:18:22  <willkg> there's some bits in About GNU MediaGoblin.
2012-06-02T12:18:35  <freedeb> links all around
2012-06-02T12:18:35  <willkg> paroneayea: ok. i don't know what that entails, so is that something you can do?
2012-06-02T12:18:39  <paroneayea> since I'm not sure versioning the hackinghowto with code really helps much
2012-06-02T12:18:47  <paroneayea> willkg: wouldn't it just be maybe adding notes to the deployment guide
2012-06-02T12:18:52  <freedeb> we want to make sure we snag people wherever they click first
2012-06-02T12:18:56  <paroneayea> saying "If you're interested in contributing go here"
2012-06-02T12:18:59  <paroneayea> ?
2012-06-02T12:19:04  *** Marcel|HSD` has quit IRC
2012-06-02T12:19:32  <willkg> seems like you're asking me questions about your idea. i'm not sure i can answer them.
2012-06-02T12:20:52  <paroneayea> willkg: okay, if you want to do it, go for it; I'm slightly concerned it's one more thing to maintain and that just linking from the deployment guide might be easier.  But one way or another you are right that we shouldn't be losing contributors from the sphinx docs
2012-06-02T12:20:54  <paroneayea> and at the very least
2012-06-02T12:21:12  <paroneayea> that people sometimes think that the deployment guide is a contribution guide, which it isn't.
2012-06-02T12:21:26  <willkg> no... that's not what i'm getting at. i'm saying that you're asking me questions about your idea--and i can't answer those. i'm not resisting your linking option.
2012-06-02T12:21:38  <willkg> it's not a deployment guide anymore.
2012-06-02T12:21:52  <willkg> it's documentation that has a Site Administrator's Guide and a Plugin Writer's Guide.
2012-06-02T12:22:00  <paroneayea> willkg: okay, fair enough :)
2012-06-02T12:22:17  <paroneayea> willkg: I'm good with going that route.
2012-06-02T12:22:25  <willkg> it does have deployment stuff in it.
2012-06-02T12:22:29  <willkg> which route?
2012-06-02T12:22:32  <paroneayea> you are right that the sphinx docs are increasing in scope, and that that's probably a good thing
2012-06-02T12:22:56  <paroneayea> willkg: your suggestion of adding things to the docs.
2012-06-02T12:23:13  <paroneayea> anyway, I don't want to spend forever on this item.  I say, go for it
2012-06-02T12:23:16  <willkg> so, to clarify, i'm not resisting the linking option. i just don't know what it entails.
2012-06-02T12:23:44  <willkg> i'm on the fence about what to do until i know more about that and whether it solves the concerns i have.
2012-06-02T12:23:54  <willkg> but i'm game for moving on.
2012-06-02T12:23:57  <paroneayea> willkg: all I thought was adding a link like If you're interested in contributing, see our `HackingHowto on our wiki <http://wiki.mediagoblin.org/HackingHowto>`_
2012-06-02T12:24:02  <willkg> if we move on, i'll just table this until later.
2012-06-02T12:24:04  <paroneayea> and add it both to the index
2012-06-02T12:24:09  <paroneayea> and the deployment guide.
2012-06-02T12:24:12  <paroneayea> that's all I was suggesting.
2012-06-02T12:24:16  <willkg> ok.
2012-06-02T12:24:48  <paroneayea> willkg: what I'm really interested in talking about is the plugin writers guide and plugins stuff
2012-06-02T12:24:48  * Elrond is lurking partly.
2012-06-02T12:24:55  <willkg> i'll create a bug for this and we can figure out what to do later.
2012-06-02T12:25:00  <paroneayea> willkg: sounds great :)
2012-06-02T12:25:07  <paroneayea> heya Elrond
2012-06-02T12:25:08  *** ErkanYilmaz2 has quit IRC
2012-06-02T12:26:52  <freedeb> hi Elrond!
2012-06-02T12:27:59  <Elrond> Hi freedeb!
2012-06-02T12:28:12  <paroneayea> so
2012-06-02T12:28:17  <freedeb> so the plugins
2012-06-02T12:28:20  <paroneayea> yes
2012-06-02T12:28:34  <freedeb> if this is a thing other projects have done
2012-06-02T12:28:46  <freedeb> is there soem kind of well-known best practices?
2012-06-02T12:28:54  <freedeb> or do we just go with common sense?
2012-06-02T12:28:58  <paroneayea> well it's pretty well on its way now
2012-06-02T12:29:06  <freedeb> oh, sweet
2012-06-02T12:29:20  <paroneayea> willkg has written the core infrastructure, and I think has a lot of inspiration from having worked on miro and pyblosxom
2012-06-02T12:29:23  *** nightsh has quit IRC
2012-06-02T12:29:52  <freedeb> so yes
2012-06-02T12:30:01  <freedeb> and yes
2012-06-02T12:30:06  <paroneayea> yeah
2012-06-02T12:30:13  <willkg> so... here's where we're at:
2012-06-02T12:30:20  <freedeb> willkg being a bastion of experience and common sense
2012-06-02T12:30:24  <willkg> 1. i finished up and landed the infrastructure for loading, configuring, building plugins.
2012-06-02T12:30:30  <willkg> 2. i wrote up a quick start guide: http://docs.mediagoblin.org/pluginwriter/quickstart.html
2012-06-02T12:30:36  <willkg> that's it.
2012-06-02T12:31:25  <willkg> the next step is to flesh out the plugin API. this is the API that plugins will use to hook into GNU MediaGoblin. it allows us a level of indirection so that it's more likely we can change how the core works without breaking plugins.
2012-06-02T12:31:47  <willkg> there are a couple of ways to flesh out the plugin API.
2012-06-02T12:32:03  <willkg> 1. design by committee. we get a bunch of people together and flesh it all out committee-style.
2012-06-02T12:32:56  <willkg> 2. design by evolution. bunch of people have specific problems they want to solve with plugins and for each problem we figure out what needs to be implemented, whether we can generalize it, and thus the plugin API evolves over time.
2012-06-02T12:33:19  <willkg> i think number 2 sounds more fun. i was going to tackle a flatpages plugin.
2012-06-02T12:33:31  <willkg> that's where we're at.
2012-06-02T12:33:46  <willkg> i think i intended to send an email to the mailing list and update the wiki page, but haven't done either, yet.
2012-06-02T12:33:52  <Elrond> I'll vote for option 2.
2012-06-02T12:33:55  <gmgbot> *NEWS* issues: Ticket #457 (need to be more obvious regarding contributor-ship in docs/) created
2012-06-02T12:34:02  <paroneayea> I think having a flatpages plugin in by our next release would be a pretty neat release feature
2012-06-02T12:34:05  <willkg> Elrond: are there plugins you'd want to work through?
2012-06-02T12:34:12  <paroneayea> and proof that plugins are actulaly working
2012-06-02T12:34:25  <paroneayea> willkg: I think I'd like to have the openstreetmaps thing refactored into a plugin.
2012-06-02T12:34:31  <paroneayea> that's the big one I want plugin'ified.
2012-06-02T12:34:38  * willkg nods.
2012-06-02T12:34:57  <Elrond> willkg - I *was* considering to write a gallery2-upload frontend.  But that ended up in Elrond-went-to-RL and Elrond-needs-to-work-on-his-phd.
2012-06-02T12:34:57  <paroneayea> willkg: if you could get first steps working on plugins for flatpages
2012-06-02T12:35:00  <willkg> maybe it makes sense to make a list of a few plugins we want to implement for the next release, then find at least one person to work on each plugin?
2012-06-02T12:35:19  <paroneayea> I could start working on a openstreetmap thing (or pass it off if someone really wants it)
2012-06-02T12:35:24  <willkg> ok. i like this.
2012-06-02T12:35:25  <paroneayea> willkg: I think that's reasonable
2012-06-02T12:35:30  <willkg> so, for the next release, let's target:
2012-06-02T12:35:36  <willkg> 1. a flatpages plugin (i'll work on this)
2012-06-02T12:35:51  <willkg> 2. an openstreetmap plugin (chris or someone)
2012-06-02T12:36:02  <willkg> i'm not sure what a gallery2-upload plugin is.
2012-06-02T12:36:12  <willkg> Elrond: if you can define what that is, i'm game for adding it to the list.
2012-06-02T12:36:22  <Elrond> willkg - It makes GMG feel like it were Gallery2 to upload tools.
2012-06-02T12:36:40  <willkg> also, we have a list of plugins we've been thinking about here: http://wiki.mediagoblin.org/PluginSystemDesignDocument#Use_cases
2012-06-02T12:36:46  <willkg> i don't know what gallery2 is....
2012-06-02T12:36:52  <paroneayea> Elrond: you mean supporting their API, right?
2012-06-02T12:36:58  <paroneayea> willkg: PHP free software image gallery.
2012-06-02T12:37:03  <Elrond> willkg - gallery2 is a php based picture hosting software.
2012-06-02T12:37:10  <paroneayea> http://gallery.menalto.com/
2012-06-02T12:37:14  <Elrond> paroneayea - ACK.
2012-06-02T12:37:20  <willkg> ahh... ok.
2012-06-02T12:37:33  <willkg> mmm... that sounds kind of like a big project with only a bit of gnu mediagoblin plugin api bits in it.
2012-06-02T12:37:35  <Elrond> But as I said: Currently NO time.
2012-06-02T12:38:02  <willkg> if i had my druthers, i'd work on plugins that were small/easy tasks that forced us to flesh out plugin api bits.
2012-06-02T12:38:04  <Elrond> willkg - Most import needed hook: Hook into routes. That's about it.
2012-06-02T12:38:14  <paroneayea> willkg: I don't think it's that hard
2012-06-02T12:38:15  <willkg> ok. that'll get covered by flatpages.
2012-06-02T12:38:35  <paroneayea> it's just supporting a similar API for uploads... could do some good in factoring out our submission page
2012-06-02T12:38:38  <Elrond> Right, so flatpages will be a good start at it.
2012-06-02T12:38:41  <willkg> paroneayea: i didn't use the word "hard".... but it's probably big in that it needs to support a bunch of api stuff.
2012-06-02T12:38:44  <paroneayea> into more general pieces
2012-06-02T12:38:49  <paroneayea> ah yeah
2012-06-02T12:39:05  <willkg> flatpages should be like 100 lines of code tops, i think.
2012-06-02T12:39:08  <willkg> unless we do fancy stuff.
2012-06-02T12:39:09  <paroneayea> it seems to me mostly like it'll require the routes stuff and refactoring a bit of the submit views.
2012-06-02T12:39:17  <paroneayea> on the API end.
2012-06-02T12:39:19  <paroneayea> er
2012-06-02T12:39:23  * willkg nods.
2012-06-02T12:39:23  <paroneayea> on the mediagoblin core whatever end :)
2012-06-02T12:39:31  <paroneayea> willkg: okay!
2012-06-02T12:39:34  <paroneayea> I feel good about that direction
2012-06-02T12:39:46  <willkg> plugins for alleviating comment spam might be interesting.
2012-06-02T12:39:57  <paroneayea> willkg: I'm very interested in hooking into activityspam
2012-06-02T12:39:58  <Elrond> paroneayea - Well, it gets ugly, when you want to support more of the g2 api. Like listing users, ... etc.
2012-06-02T12:40:35  <Elrond> Anyway, flatpages will be a great start anyway.
2012-06-02T12:40:45  <Elrond> It will allow our tests to hook things into routes too!
2012-06-02T12:40:56  <paroneayea> https://github.com/evanp/activityspam
2012-06-02T12:41:02  <paroneayea> but also captcha support
2012-06-02T12:41:05  <paroneayea> would be a good plugin
2012-06-02T12:41:16  * willkg nods.
2012-06-02T12:41:28  <willkg> when're we thinking of doing the next release?
2012-06-02T12:41:40  <Elrond> I think, we'll do plugins as people ask for them and/or volunteer to write them?
2012-06-02T12:41:43  <paroneayea> well, we normally do releases on 2 month intervals is the plan
2012-06-02T12:41:47  <paroneayea> that would mean the end of june.
2012-06-02T12:41:51  <willkg> Elrond: i like that idea. +1 to that.
2012-06-02T12:42:17  <paroneayea> I'm nervous about the (perceived?) lull meaning we'll have a longer release cycle.
2012-06-02T12:42:36  <Elrond> So flatpages might even be a great "Start here if you need a really simply plugin to base yours on".
2012-06-02T12:42:42  <paroneayea> yeah
2012-06-02T12:42:45  * willkg nods.
2012-06-02T12:42:51  *** dejongge has joined #mediagoblin
2012-06-02T12:42:54  <paroneayea> willkg: how long do you think flatpages stuff will take
2012-06-02T12:42:58  <paroneayea> is maybe a good question?
2012-06-02T12:43:03  <willkg> if i had my druthers, the docs would be really awesome with examples of different kinds of plugins and all that.
2012-06-02T12:43:44  <freedeb> maybe we should ask for a few outside opinions on the plugin docs
2012-06-02T12:43:54  <willkg> the pyblosxom docs are getting there. http://pyblosxom.bluesock.org/1.5/dev_writing_plugins.html#writing-plugins
2012-06-02T12:44:10  <freedeb> just to make sure they are awesome
2012-06-02T12:44:18  <paroneayea> freedeb: it would definitely be good to have people do testruns of the docs
2012-06-02T12:44:19  <freedeb> for new contributors
2012-06-02T12:44:20  <paroneayea> once they're there
2012-06-02T12:44:23  <paroneayea> and collect feedback
2012-06-02T12:44:27  <willkg> lots of examples of how to do specific things that most plugin writers are going to want to do.
2012-06-02T12:44:39  <paroneayea> willkg: relatedly, I think once plugins come along
2012-06-02T12:44:40  <freedeb> ok, we should think of a few people that we could specifically ask for that input
2012-06-02T12:44:47  <paroneayea> it'll be easier to have a tutorial of getting into the project
2012-06-02T12:44:51  <paroneayea> "write this hello world plugin"
2012-06-02T12:44:59  <freedeb> and then ask them personally
2012-06-02T12:45:00  <willkg> possibly.
2012-06-02T12:45:00  <freedeb> ok
2012-06-02T12:45:16  <freedeb> aldeka would be a good person
2012-06-02T12:45:20  <willkg> if we're really thinking of this as an entry point for really new people, then the existing structure is probably too complicated.
2012-06-02T12:45:22  <freedeb> her talk on the beginner's mind
2012-06-02T12:45:39  <paroneayea> willkg: okay, don't worry about that yet.
2012-06-02T12:45:49  <paroneayea> we just need docs, period, that are great first
2012-06-02T12:45:53  <willkg> freedeb: i'm not against doing that. but i don't want to do that now unless those people want to write docs.
2012-06-02T12:46:01  <freedeb> was full of great ideas for explaining projects to people who know stuff
2012-06-02T12:46:09  <freedeb> ok
2012-06-02T12:46:28  <freedeb> I will hang on to that thought
2012-06-02T12:46:39  <willkg> getting opinions when we have a critical mass of stuff is useful, but we're definitely not there, yet.
2012-06-02T12:46:54  <paroneayea> okay, is that it for plugins'y stuff then?
2012-06-02T12:46:58  <willkg> i think so.
2012-06-02T12:47:04  <paroneayea> willkg: you and I should coordinate over the next couple weeks on getting rolling on that then
2012-06-02T12:47:15  <willkg> re: flatpages, it's probably a couple of days of work. but it's super duper hard to find free time right now.
2012-06-02T12:47:21  * paroneayea nods
2012-06-02T12:47:45  <willkg> i'd be game for slamdunking something soon, though.
2012-06-02T12:48:09  <paroneayea> okay, so approx 10 minutes left
2012-06-02T12:48:15  <paroneayea> next thing is joar's bit about unit tests
2012-06-02T12:48:21  <paroneayea> I agree about selenium/phantomjs
2012-06-02T12:48:29  <willkg> i have no opinions.
2012-06-02T12:48:36  <paroneayea> lunpa wrote some phantomjs stuff in cc.engine
2012-06-02T12:48:39  <paroneayea> might be worth looking at it
2012-06-02T12:48:46  <paroneayea> though notably jenkins isn't running it :)
2012-06-02T12:48:52  <willkg> should we create a ticket for it?
2012-06-02T12:49:02  <paroneayea> the problem with unit tests is that everyone agrees we need more and it's hard to get people to do them.
2012-06-02T12:49:07  <paroneayea> having a coverage script would help
2012-06-02T12:49:32  <willkg> mmm... sort of. coverage analysis almost always solves the wrong problem.
2012-06-02T12:49:37  <paroneayea> willkg: yes, I think we should make tickets both for making a coverage script and for phantomjs/selenium style testing probably
2012-06-02T12:49:39  <paroneayea> willkg: oh really?
2012-06-02T12:49:40  <paroneayea> how so?
2012-06-02T12:49:56  *** dangar4l has quit IRC
2012-06-02T12:50:32  <willkg> because all it tells you is whether a line of code has been gone through. it doesn't tell you what's appropriate to test or what contexts you're not testing or edge cases that were missed, ...
2012-06-02T12:50:37  *** dangar4l has joined #mediagoblin
2012-06-02T12:50:37  *** dangar4l has joined #mediagoblin
2012-06-02T12:50:38  <willkg> it's a bad feel-good metric.
2012-06-02T12:50:51  <paroneayea> hm interesting :)
2012-06-02T12:50:52  <paroneayea> okay.
2012-06-02T12:51:06  <paroneayea> well anwyay, I'll file a bug for functional testing after this
2012-06-02T12:51:15  <paroneayea> TODO (cwebber): file functional testing bug.
2012-06-02T12:51:21  <paroneayea> I think it's pretty low priority atm though.
2012-06-02T12:51:38  <paroneayea> so I guess I'll give my minor kuneco update
2012-06-02T12:51:42  <willkg> kuneco!!!
2012-06-02T12:52:10  <paroneayea> update is: I've written a system in the library that can serialize atom feeds properly
2012-06-02T12:52:17  <willkg> oh--one way to increase tests is to force all incoming changes to have appropriate test coverage.
2012-06-02T12:52:20  <willkg> that's the best way to do it.
2012-06-02T12:52:26  <paroneayea> and it has a plugin chain thing
2012-06-02T12:52:29  <paroneayea> and unit tests.
2012-06-02T12:52:36  <willkg> yay!
2012-06-02T12:52:39  <paroneayea> no activitystrea.ms suppport; but that's next.
2012-06-02T12:52:46  <paroneayea> there's not that much there.  But it does the above.
2012-06-02T12:52:49  <paroneayea> it needs docs.
2012-06-02T12:52:51  <willkg> wow--that's pretty awesome!
2012-06-02T12:53:07  <paroneayea> yeah I feel pretty good about it
2012-06-02T12:53:08  <willkg> i'd be game for looking at the code and project-ifying and documenting it.
2012-06-02T12:53:19  <paroneayea> willkg: totally.  Just git pull the kuneco repo
2012-06-02T12:53:22  <paroneayea> and look at where things are at
2012-06-02T12:53:23  <willkg> ok. will do.
2012-06-02T12:53:26  <paroneayea> the tests make it pretty clear.
2012-06-02T12:53:45  <paroneayea> we put on here working on an administrative panel / tools
2012-06-02T12:53:52  <paroneayea> but I think it's simply described as "we should have that"
2012-06-02T12:54:16  <paroneayea> and I'm not sure it's worth having a bigger conversation given it seems like the people at this meeting have already maxed out on tasks for the month
2012-06-02T12:54:39  <paroneayea> I'd be fine with calling the meeting off a few minutes early if you are and leaving it at what we have here
2012-06-02T12:54:52  * willkg nods.
2012-06-02T12:55:01  <willkg> i'm for pushing it off. we've got a lot on our plates now as it is.
2012-06-02T12:55:09  <willkg> unless someone wants to step up and work on it.
2012-06-02T12:55:15  <paroneayea> okay, cool
2012-06-02T12:55:23  <paroneayea> anyone else have anything?
2012-06-02T12:55:27  <paroneayea> if not, I say meeting adjourned
2012-06-02T12:55:31  <willkg> not that i can think of....
2012-06-02T12:55:34  <willkg> freedeb: anything?
2012-06-02T12:55:38  <freedeb> nope
2012-06-02T12:55:46  <paroneayea> h'okay!
2012-06-02T12:55:47  <freedeb> great work on kuneco!
2012-06-02T12:55:51  <paroneayea> thanks :)
2012-06-02T12:55:54  <freedeb> :)
2012-06-02T12:56:01  <willkg> paroneayea: where's the kuneco repository?
2012-06-02T12:56:14  <paroneayea> willkg: https://gitorious.org/kuneco/
2012-06-02T12:56:17  <paroneayea> you've committed to it! ;)
2012-06-02T12:56:23  <willkg> i have? oh, funky.
2012-06-02T12:56:36  <willkg> so i did!
2012-06-02T12:57:05  <freedeb> haha
2012-06-02T12:57:38  <paroneayea> alright then
2012-06-02T12:57:43  <paroneayea> I'm gonna file that bug then get to lunch!
2012-06-02T12:57:45  <paroneayea> later all!
2012-06-02T12:57:49  <willkg> sweet! laters!