20070215
10178
Comment:
|
9235
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was renamed from ScribesTeam/MeetingNotes/20070215Meeting [[Navigation(siblings)]] |
|
Line 3: | Line 5: |
Line 5: | Line 6: |
Line 8: | Line 8: |
* PersonOne * PersonTwo |
* ChrisOattes * [:Ausimage] |
Line 28: | Line 28: |
* | '''[#ubotu Topic: Research of ubotu code -- Seeker`]''' |
Line 30: | Line 30: |
We decided to focus on the development of own bot in TCL for the time being to allow the freedom to experiement with new code. '''[#calendar Topic: Research on Calendars]''' Due to low attendance, it was decided to postpone the decision on whether to use only the fridge or the fridge in combination with other calendar software was postponed. It was decided that, for the time being, we should attempt to put any meetings that are submitted to the team on the fridge. '''[#summary Topic: Meeting Summary process write up -- Seeker`]''' Due to low attendance, the discussion of the Meeting Summary process was postponed. '''[#mootbot Topic: Update on the bot]''' 20:24:01 '''ACTION''' ausimage Seeker and AndrewWilliams will continue on the bot '''[#communication Topic: Team Communication]''' 20:25:16 '''IDEA''' ausimage Use WIKI page to show responsibilities for Meeting Summaries 20:27:13 '''ACTION''' ausimage Waiting for Mailing List on list.ubunut.com 20:27:44 '''ACTION''' ausimage Develop Meeting Summary Responsibility Page '''[#interest Topic: Review ways to raise interest]''' 20:30:26 '''ACTION''' ausimage Continue forward raising interest |
|
Line 33: | Line 60: |
* * |
|
Line 36: | Line 61: |
= Guide Lines = The chairman of the meeting should endeavour to ensure that key points are discussed in an appropriate time. Key Topics from the Agenda should be tabled in the channel using a market such as [ TOPIC ] or * TOPIC * Followed by the agenda item. Where Suggestions or Ideas are put forward and considered as acceptable to the group then it should be noted by the Chairman as [ IDEA ] or * IDEA * . Where a concept is discussed and agreed the use of [ AGREED ] or * AGREED * should be defined by the chairman and should signify the topic is discussed and the meeting is to move on. Be clear on the channel when the meeting is concluded and how and when the minutes will be posted. |
|
Line 43: | Line 62: |
''copied from my client'' --Ausimage | |
Line 45: | Line 63: |
(03:05:21 PM) ausimage: #startmeeting (03:05:22 PM) Mootbot: Meeting started at 20:00. The chair is ausimage. (03:05:48 PM) ausimage: Shall we take roll (03:06:03 PM) ausimage: PRESENT (03:06:07 PM) Seeker`: PRESENT (03:06:34 PM) ausimage: hmm everyone else is lurking?? (03:07:01 PM) ausimage: Ok... (03:07:23 PM) ausimage: [TOPIC] Research of ubotu code -- Seeker` (03:07:24 PM) Mootbot: New topic: Research of ubotu code -- Seeker` (03:07:57 PM) ausimage: Seeker`: What did you find out? (03:08:08 PM) Seeker`: I decided not to contact Seveas about integrating with ubotu (03:08:19 PM) Seeker`: Mainly for reasons discussed towards the end of the last meeting (03:08:37 PM) Seeker`: We wont have the control over the bot code, it would be much harder to test (03:08:53 PM) Seeker`: There are now two of us working on TCL (03:09:06 PM) Seeker`: I think it is something to consider down the line (03:09:10 PM) Seeker`: but it isn't right for the bot just yet (03:10:01 PM) ausimage: OK then we focus on our own bot then (03:10:19 PM) Seeker`: yeah, for now (03:10:28 PM) ausimage: [ACTION] Focus on development of own bot in TCL. (03:10:29 PM) Mootbot: ACTION received: Focus on development of own bot in TCL. (03:10:30 PM) Seeker`: I think that was the general consensus last meeting (03:10:40 PM) ausimage: I think you are right... (03:10:47 PM) Seeker`: next topic? (03:10:58 PM) ausimage: [TOPIC] Research on Calendars (03:10:59 PM) Mootbot: New topic: Research on Calendars (03:11:10 PM) ausimage: Thats Me :) (03:11:26 PM) medders [n=matt@unaffiliated/medders] entered the room. (03:11:36 PM) ausimage: I looked at Google Calendars... and also contacted the Fridge (03:11:52 PM) medders: hi (03:12:38 PM) ausimage: From my talk with the Fridge I think we need to support the efforts to improve the facilities there. (03:12:39 PM) Seeker`: ausimage: What did you find out? (03:13:31 PM) ausimage: I think the Fridge is worth supporting, but they have closed source calender that does not implement the entire calendar spec as I understand it. (03:13:58 PM) ausimage: They are willing to look into making plugins to improve it though. (03:14:02 PM) Seeker`: what can we do to support it? (03:14:48 PM) ausimage: I feel that if we start getting meetings we should forward them to the Fridge for inclusion. (03:15:21 PM) ausimage: Having more on the calendar in different locations may spur ideas of development.... (03:15:31 PM) Seeker`: yeah (03:15:55 PM) ausimage: [IDEA] forward meeting requests to the fridge (03:15:56 PM) Mootbot: IDEA received: forward meeting requests to the fridge (03:16:31 PM) ausimage: I also am of the opinion while the fridge should be our goal... (03:16:58 PM) ausimage: We should look at using something like Google Calendars that does support the spec... (03:17:09 PM) ausimage: while Fridge catches up.. (03:17:16 PM) Seeker`: hmm (03:17:17 PM) Seeker`: possibly (03:17:55 PM) ausimage: My reasons are because... it is easier to extract the information from a calendar that fully supports the spec.. (03:18:12 PM) Seeker`: 1. what spec (03:18:20 PM) Seeker`: 2. in what way does'nt fridge support the spec (03:19:30 PM) ausimage: The spec I refer to is the idea that calendars should support Name, Date, Time, Location, Description... at least... Fridge lacks a true location field... (03:19:48 PM) Seeker`: But they can add one? (03:19:55 PM) Seeker`: Our entry in the fridge had one? (03:20:29 PM) ausimage: They could but under great pain the code is closed source... plugins might be possible... (03:20:42 PM) Seeker`: its just that if you are thinking of extracting data with the bot, its easier to keep using the same tool rather than change from google to fridge (03:20:52 PM) ausimage: Um our entry utilized fudging in the Description field... (03:20:58 PM) Seeker`: because it will probably involve rewriting code. (03:21:46 PM) ausimage: Yeah.. that is why I think a dual approach is worth trying.... (03:22:14 PM) Seeker`: but a dual approach with involve even more coding (03:22:24 PM) Seeker`: i think we should postpone this until more people are present (03:17:45 PM) ausimage: K (03:18:24 PM) ausimage: [ACTION] Postpone decision on whether a dual approach is necessary (03:18:25 PM) Mootbot: ACTION received: Postpone decision on whether a dual approach is necessary (03:18:44 PM) ausimage: but we should support the fridge by forwarding meetings (03:19:12 PM) Seeker`: yes (03:19:27 PM) ausimage: [ACTION] Forward meeting requests to the Fridge (03:19:28 PM) Mootbot: ACTION received: Forward meeting requests to the Fridge (03:20:08 PM) ausimage: [TOPIC] Meeting Summary process write up -- Seeker` (03:20:09 PM) Mootbot: New topic: Meeting Summary process write up -- Seeker` (03:20:30 PM) Seeker`: I think we also need to postpone this until mor epeople are about (03:20:39 PM) ausimage: gotcha... (03:21:06 PM) ausimage: [ACTION] Postpone discussion of Meeting Summary process (03:21:07 PM) Mootbot: ACTION received: Postpone discussion of Meeting Summary process (03:21:27 PM) ausimage: [TOPIC] Update on the bot (03:21:28 PM) Mootbot: New topic: Update on the bot (03:21:54 PM) Seeker`: I haven't had time to get an SSH key to get in to AndrewWilliams's server (03:21:54 PM) ausimage: Seeker`: ?? (03:22:05 PM) Seeker`: However, i think he may have something basic running on there (03:22:12 PM) Seeker`: basically, there isn't anything new yet (03:22:27 PM) ausimage: how is the bot progressing?? (03:22:42 PM) Seeker`: I've defined some specs on launchpad (03:22:55 PM) Seeker`: AndrewWilliams has had a go at implementing one of them (03:22:55 PM) ausimage: url?? (03:23:02 PM) Seeker`: I'm going to try to do some more this week (03:23:13 PM) Seeker`: http://launchpad.net/mootbot i think (03:23:34 PM) ausimage: OK (03:24:00 PM) ausimage: [ACTION] Seeker and AndrewWilliams will continue on the bot (03:24:01 PM) Mootbot: ACTION received: Seeker and AndrewWilliams will continue on the bot (03:24:11 PM) ausimage: [TOPIC] Team Communication (03:24:12 PM) Mootbot: New topic: Team Communication (03:24:31 PM) Seeker`: I have sent an email about getting a mailing list (03:24:35 PM) Seeker`: I am watiing for a reply (03:24:45 PM) ausimage: good (03:25:15 PM) ausimage: [IDEA] Use WIKI page to show responsibilities for Meeting Summaries (03:25:16 PM) Mootbot: IDEA received: Use WIKI page to show responsibilities for Meeting Summaries (03:25:32 PM) ausimage: I mentioned with Vorian on this... (03:25:34 PM) Seeker`: I dont know if that is a good idea (03:25:45 PM) Seeker`: because hopefully, meetings will be summarised very quickly (03:25:55 PM) Seeker`: unless you mean for every meeting (03:26:06 PM) Seeker`: i.e. person x is reponsible for all meetings of team y (03:26:11 PM) ausimage: Yes (03:26:18 PM) Seeker`: ok (03:26:23 PM) Seeker`: sounds reasonable (03:26:30 PM) ausimage: So I know who to bug if a summary is not done.... (03:26:41 PM) ausimage: and I do not duplicate work (03:26:47 PM) Seeker`: yeah (03:27:13 PM) ausimage: [ACTION] Waiting for Mailing List on list.ubunut.com (03:27:14 PM) Mootbot: ACTION received: Waiting for Mailing List on list.ubunut.com (03:27:44 PM) ausimage: [ACTION] Develop Meeting Summary Responsibility Page (03:27:45 PM) Mootbot: ACTION received: Develop Meeting Summary Responsibility Page (03:28:13 PM) ausimage: [TOPIC] Review ways to raise interest (03:28:14 PM) Mootbot: New topic: Review ways to raise interest (03:28:29 PM) Seeker`: I think all we can do is keep plugging it (03:29:00 PM) ausimage: Yup... (03:29:17 PM) Seeker`: we have the slot in the loco meeting (03:29:19 PM) AndrewWilliams: sorry i'm late guys, dinner over run (03:29:22 PM) Seeker`: i dont see what else we can do (03:29:33 PM) Seeker`: AndrewWilliams: We are just about done now (03:29:41 PM) AndrewWilliams: sods law :) (03:29:58 PM) ausimage: We are on Raising Interest (03:30:26 PM) ausimage: [ACTION] Continue forward raising interest (03:30:26 PM) ***Seeker` has to go now (03:30:27 PM) Mootbot: ACTION received: Continue forward raising interest (03:30:28 PM) Seeker`: bye (03:30:32 PM) ausimage: later (03:30:59 PM) ausimage: OK... that is all that I have... any other business (03:31:17 PM) ausimage: Alrighty then (03:31:22 PM) ausimage: #endmeeting (03:31:23 PM) Mootbot: Meeting finished at 20:31. |
[20:01:00] <ausimage> Shall we take roll [20:01:15] <ausimage> PRESENT [20:01:19] <Seeker`> PRESENT [20:01:46] <ausimage> hmm everyone else is lurking?? [20:02:13] <ausimage> Ok... }}}[[Anchor(ubotu)]]{{{ [20:02:35] <ausimage> [TOPIC] Research of ubotu code -- Seeker` [20:03:09] <ausimage> Seeker`: What did you find out? [20:03:20] <Seeker`> I decided not to contact Seveas about integrating with ubotu [20:03:30] <Seeker`> Mainly for reasons discussed towards the end of the last meeting [20:03:48] <Seeker`> We wont have the control over the bot code, it would be much harder to test [20:04:05] <Seeker`> There are now two of us working on TCL [20:04:18] <Seeker`> I think it is something to consider down the line [20:04:22] <Seeker`> but it isn't right for the bot just yet [20:05:13] <ausimage> OK then we focus on our own bot then [20:05:31] <Seeker`> yeah, for now [20:05:40] <ausimage> [ACTION] Focus on development of own bot in TCL. [20:05:42] <Seeker`> I think that was the general consensus last meeting [20:05:52] <ausimage> I think you are right... [20:05:58] <Seeker`> next topic? }}}[[Anchor(calendars)]]{{{ [20:06:10] <ausimage> [TOPIC] Research on Calendars [20:06:23] <ausimage> Thats Me :) [20:06:48] <ausimage> I looked at Google Calendars... and also contacted the Fridge [20:07:04] <medders> hi [20:07:50] <ausimage> From my talk with the Fridge I think we need to support the efforts to improve the facilities there. [20:07:51] <Seeker`> ausimage: What did you find out? [20:08:43] <ausimage> I think the Fridge is worth supporting, but they have closed source calender that does not implement the entire calendar spec as I understand it. [20:09:10] <ausimage> They are willing to look into making plugins to improve it though. [20:09:14] <Seeker`> what can we do to support it? [20:10:00] <ausimage> I feel that if we start getting meetings we should forward them to the Fridge for inclusion. [20:10:32] <ausimage> Having more on the calendar in different locations may spur ideas of development.... [20:10:42] <Seeker`> yeah [20:11:07] <ausimage> [IDEA] forward meeting requests to the fridge [20:11:42] <ausimage> I also am of the opinion while the fridge should be our goal... [20:12:10] <ausimage> We should look at using something like Google Calendars that does support the spec... [20:12:21] <ausimage> while Fridge catches up.. [20:12:27] <Seeker`> hmm [20:12:28] <Seeker`> possibly [20:13:07] <ausimage> My reasons are because... it is easier to extract the information from a calendar that fully supports the spec.. [20:13:24] <Seeker`> 1. what spec [20:13:32] <Seeker`> 2. in what way does'nt fridge support the spec [20:14:42] <ausimage> The spec I refer to is the idea that calendars should support Name, Date, Time, Location, Description... at least... Fridge lacks a true location field... [20:15:00] <Seeker`> But they can add one? [20:15:06] <Seeker`> Our entry in the fridge had one? [20:15:41] <ausimage> They could but under great pain the code is closed source... plugins might be possible... [20:15:53] <Seeker`> its just that if you are thinking of extracting data with the bot, its easier to keep using the same tool rather than change from google to fridge [20:16:04] <ausimage> Um our entry utilized fudging in the Description field... [20:16:10] <Seeker`> because it will probably involve rewriting code. [20:16:57] <ausimage> Yeah.. that is why I think a dual approach is worth trying.... [20:17:26] <Seeker`> but a dual approach with involve even more coding [20:17:36] <Seeker`> i think we should postpone this until more people are present [20:17:45] <ausimage> K [20:18:25] <ausimage> [ACTION] Postpone decision on whether a dual approach is necessary [20:18:44] <ausimage> but we should support the fridge by forwarding meetings [20:19:12] <Seeker`> yes [20:19:28] <ausimage> [ACTION] Forward meeting requests to the Fridge }}}[[Anchor(summary)]]{{{ [20:20:09] <ausimage> [TOPIC] Meeting Summary process write up -- Seeker` [20:20:31] <Seeker`> I think we also need to postpone this until mor epeople are about [20:20:39] <ausimage> gotcha... [20:21:07] <ausimage> [ACTION] Postpone discussion of Meeting Summary process }}}[[Anchor(mootbot)]]{{{ [20:21:28] <ausimage> [TOPIC] Update on the bot [20:21:54] <Seeker`> I haven't had time to get an SSH key to get in to AndrewWilliams's server [20:21:55] <ausimage> Seeker`: ?? [20:22:06] <Seeker`> However, i think he may have something basic running on there [20:22:13] <Seeker`> basically, there isn't anything new yet [20:22:27] <ausimage> how is the bot progressing?? [20:22:43] <Seeker`> I've defined some specs on launchpad [20:22:56] <Seeker`> AndrewWilliams has had a go at implementing one of them [20:22:56] <ausimage> url?? [20:23:03] <Seeker`> I'm going to try to do some more this week [20:23:14] <Seeker`> http://launchpad.net/mootbot i think [20:23:34] <ausimage> OK [20:24:01] <ausimage> [ACTION] Seeker and AndrewWilliams will continue on the bot }}}[[Anchor(communication)]]{{{ [20:24:11] <ausimage> [TOPIC] Team Communication [20:24:31] <Seeker`> I have sent an email about getting a mailing list [20:24:35] <Seeker`> I am watiing for a reply [20:24:46] <ausimage> good [20:25:16] <ausimage> [IDEA] Use WIKI page to show responsibilities for Meeting Summaries [20:25:32] <ausimage> I mentioned with Vorian on this... [20:25:34] <Seeker`> I dont know if that is a good idea [20:25:46] <Seeker`> because hopefully, meetings will be summarised very quickly [20:25:56] <Seeker`> unless you mean for every meeting [20:26:06] <Seeker`> i.e. person x is reponsible for all meetings of team y [20:26:12] <ausimage> Yes [20:26:18] <Seeker`> ok [20:26:23] <Seeker`> sounds reasonable [20:26:30] <ausimage> So I know who to bug if a summary is not done.... [20:26:41] <ausimage> and I do not duplicate work [20:26:48] <Seeker`> yeah [20:27:13] <ausimage> [ACTION] Waiting for Mailing List on list.ubunut.com [20:27:44] <ausimage> [ACTION] Develop Meeting Summary Responsibility Page }}}[[Anchor(interest)]]{{{ [20:28:14] <ausimage> [TOPIC] Review ways to raise interest [20:28:30] <Seeker`> I think all we can do is keep plugging it [20:29:01] <ausimage> Yup... [20:29:17] <Seeker`> we have the slot in the loco meeting [20:29:19] <AndrewWilliams> sorry i'm late guys, dinner over run [20:29:22] <Seeker`> i dont see what else we can do [20:29:33] <Seeker`> AndrewWilliams: We are just about done now [20:29:41] <AndrewWilliams> sods law :) [20:29:59] <ausimage> We are on Raising Interest [20:30:26] <ausimage> [ACTION] Continue forward raising interest [20:30:27] * Seeker` has to go now [20:30:28] <Seeker`> bye [20:30:32] <ausimage> later [20:30:59] <ausimage> OK... that is all that I have... any other business [20:31:18] <ausimage> Alrighty then [20:31:23] <ausimage> #endmeeting |
Navigation(siblings) This is the 2nd meeting of the ScribesTeam, starting at 20:00 GMT and finishing at 20:31 GMT
Attendance
Please type PRESENT at the start of the meeting to ensure we are all clear who is online and paying attention. Active Atendees:
- [:Ausimage]
Agenda
When adding an agenda item please "sign" it by leaving your name next to it. If you won't be attending the meeting please also spell out your item in detail, otherwise we can't fruitfully discuss it.
Report: ChrisOattes research of ubotu code
- Report: Ausimage research on calendars
- Utilizing Fridge
Report: ChrisOattes on meeting Summay process write-up
- approval of process
- Update on the the bot
Update from AndrewWilliams on hosting the bot
- Team communication: mailing list
- Review ways to raise interest
- Any other business
Minutes
[#ubotu Topic: Research of ubotu code -- Seeker`]
- We decided to focus on the development of own bot in TCL for the time being to allow the freedom to experiement with new code.
[#calendar Topic: Research on Calendars]
- Due to low attendance, it was decided to postpone the decision on whether to use only the fridge or the fridge in combination with other calendar software was postponed. It was decided that, for the time being, we should attempt to put any meetings that are submitted to the team on the fridge.
[#summary Topic: Meeting Summary process write up -- Seeker`]
- Due to low attendance, the discussion of the Meeting Summary process was postponed.
[#mootbot Topic: Update on the bot]
20:24:01 ACTION ausimage Seeker and AndrewWilliams will continue on the bot
[#communication Topic: Team Communication]
20:25:16 IDEA ausimage Use WIKI page to show responsibilities for Meeting Summaries
20:27:13 ACTION ausimage Waiting for Mailing List on list.ubunut.com
20:27:44 ACTION ausimage Develop Meeting Summary Responsibility Page
[#interest Topic: Review ways to raise interest]
20:30:26 ACTION ausimage Continue forward raising interest
Any Other Business
IRC LOGS
[20:01:00] <ausimage> Shall we take roll [20:01:15] <ausimage> PRESENT [20:01:19] <Seeker`> PRESENT [20:01:46] <ausimage> hmm everyone else is lurking?? [20:02:13] <ausimage> Ok...
[20:02:35] <ausimage> [TOPIC] Research of ubotu code -- Seeker` [20:03:09] <ausimage> Seeker`: What did you find out? [20:03:20] <Seeker`> I decided not to contact Seveas about integrating with ubotu [20:03:30] <Seeker`> Mainly for reasons discussed towards the end of the last meeting [20:03:48] <Seeker`> We wont have the control over the bot code, it would be much harder to test [20:04:05] <Seeker`> There are now two of us working on TCL [20:04:18] <Seeker`> I think it is something to consider down the line [20:04:22] <Seeker`> but it isn't right for the bot just yet [20:05:13] <ausimage> OK then we focus on our own bot then [20:05:31] <Seeker`> yeah, for now [20:05:40] <ausimage> [ACTION] Focus on development of own bot in TCL. [20:05:42] <Seeker`> I think that was the general consensus last meeting [20:05:52] <ausimage> I think you are right... [20:05:58] <Seeker`> next topic?
[20:06:10] <ausimage> [TOPIC] Research on Calendars [20:06:23] <ausimage> Thats Me :) [20:06:48] <ausimage> I looked at Google Calendars... and also contacted the Fridge [20:07:04] <medders> hi [20:07:50] <ausimage> From my talk with the Fridge I think we need to support the efforts to improve the facilities there. [20:07:51] <Seeker`> ausimage: What did you find out? [20:08:43] <ausimage> I think the Fridge is worth supporting, but they have closed source calender that does not implement the entire calendar spec as I understand it. [20:09:10] <ausimage> They are willing to look into making plugins to improve it though. [20:09:14] <Seeker`> what can we do to support it? [20:10:00] <ausimage> I feel that if we start getting meetings we should forward them to the Fridge for inclusion. [20:10:32] <ausimage> Having more on the calendar in different locations may spur ideas of development.... [20:10:42] <Seeker`> yeah [20:11:07] <ausimage> [IDEA] forward meeting requests to the fridge [20:11:42] <ausimage> I also am of the opinion while the fridge should be our goal... [20:12:10] <ausimage> We should look at using something like Google Calendars that does support the spec... [20:12:21] <ausimage> while Fridge catches up.. [20:12:27] <Seeker`> hmm [20:12:28] <Seeker`> possibly [20:13:07] <ausimage> My reasons are because... it is easier to extract the information from a calendar that fully supports the spec.. [20:13:24] <Seeker`> 1. what spec [20:13:32] <Seeker`> 2. in what way does'nt fridge support the spec [20:14:42] <ausimage> The spec I refer to is the idea that calendars should support Name, Date, Time, Location, Description... at least... Fridge lacks a true location field... [20:15:00] <Seeker`> But they can add one? [20:15:06] <Seeker`> Our entry in the fridge had one? [20:15:41] <ausimage> They could but under great pain the code is closed source... plugins might be possible... [20:15:53] <Seeker`> its just that if you are thinking of extracting data with the bot, its easier to keep using the same tool rather than change from google to fridge [20:16:04] <ausimage> Um our entry utilized fudging in the Description field... [20:16:10] <Seeker`> because it will probably involve rewriting code. [20:16:57] <ausimage> Yeah.. that is why I think a dual approach is worth trying.... [20:17:26] <Seeker`> but a dual approach with involve even more coding [20:17:36] <Seeker`> i think we should postpone this until more people are present [20:17:45] <ausimage> K [20:18:25] <ausimage> [ACTION] Postpone decision on whether a dual approach is necessary [20:18:44] <ausimage> but we should support the fridge by forwarding meetings [20:19:12] <Seeker`> yes [20:19:28] <ausimage> [ACTION] Forward meeting requests to the Fridge
[20:20:09] <ausimage> [TOPIC] Meeting Summary process write up -- Seeker` [20:20:31] <Seeker`> I think we also need to postpone this until mor epeople are about [20:20:39] <ausimage> gotcha... [20:21:07] <ausimage> [ACTION] Postpone discussion of Meeting Summary process
[20:21:28] <ausimage> [TOPIC] Update on the bot [20:21:54] <Seeker`> I haven't had time to get an SSH key to get in to AndrewWilliams's server [20:21:55] <ausimage> Seeker`: ?? [20:22:06] <Seeker`> However, i think he may have something basic running on there [20:22:13] <Seeker`> basically, there isn't anything new yet [20:22:27] <ausimage> how is the bot progressing?? [20:22:43] <Seeker`> I've defined some specs on launchpad [20:22:56] <Seeker`> AndrewWilliams has had a go at implementing one of them [20:22:56] <ausimage> url?? [20:23:03] <Seeker`> I'm going to try to do some more this week [20:23:14] <Seeker`> http://launchpad.net/mootbot i think [20:23:34] <ausimage> OK [20:24:01] <ausimage> [ACTION] Seeker and AndrewWilliams will continue on the bot
[20:24:11] <ausimage> [TOPIC] Team Communication [20:24:31] <Seeker`> I have sent an email about getting a mailing list [20:24:35] <Seeker`> I am watiing for a reply [20:24:46] <ausimage> good [20:25:16] <ausimage> [IDEA] Use WIKI page to show responsibilities for Meeting Summaries [20:25:32] <ausimage> I mentioned with Vorian on this... [20:25:34] <Seeker`> I dont know if that is a good idea [20:25:46] <Seeker`> because hopefully, meetings will be summarised very quickly [20:25:56] <Seeker`> unless you mean for every meeting [20:26:06] <Seeker`> i.e. person x is reponsible for all meetings of team y [20:26:12] <ausimage> Yes [20:26:18] <Seeker`> ok [20:26:23] <Seeker`> sounds reasonable [20:26:30] <ausimage> So I know who to bug if a summary is not done.... [20:26:41] <ausimage> and I do not duplicate work [20:26:48] <Seeker`> yeah [20:27:13] <ausimage> [ACTION] Waiting for Mailing List on list.ubunut.com [20:27:44] <ausimage> [ACTION] Develop Meeting Summary Responsibility Page
[20:28:14] <ausimage> [TOPIC] Review ways to raise interest [20:28:30] <Seeker`> I think all we can do is keep plugging it [20:29:01] <ausimage> Yup... [20:29:17] <Seeker`> we have the slot in the loco meeting [20:29:19] <AndrewWilliams> sorry i'm late guys, dinner over run [20:29:22] <Seeker`> i dont see what else we can do [20:29:33] <Seeker`> AndrewWilliams: We are just about done now [20:29:41] <AndrewWilliams> sods law :) [20:29:59] <ausimage> We are on Raising Interest [20:30:26] <ausimage> [ACTION] Continue forward raising interest [20:30:27] * Seeker` has to go now [20:30:28] <Seeker`> bye [20:30:32] <ausimage> later [20:30:59] <ausimage> OK... that is all that I have... any other business [20:31:18] <ausimage> Alrighty then [20:31:23] <ausimage> #endmeeting
MeetingLogs/Scribes/20070215 (last edited 2008-08-06 16:36:32 by localhost)