User:Enus Linden/Office Hours/2008 August 08

From Second Life Wiki
Jump to navigation Jump to search
  • [9:30] Tao Takashi: thanks for answering all those mails, Tess :)
  • [9:30] Tess Linden: sorry it took me so long to get to them
  • [9:31] Tao Takashi: well, let's see how long I need to reply again :)
  • [9:33] Mirt Tenk: accepted your inventory offer.
  • [9:33] Enus Linden: Hi everybody!!! :D :D :D
  • [9:33] Locklainn Linden: morning enus
  • [9:33] Malburns Writer: Hi all
  • [9:33] Locklainn Linden: and everyone else
  • [9:33] Enus Linden: morning!
  • [9:34] Enus Linden: i'm groggy today, so be nice : )
  • [9:34] Locklainn Linden: same here
  • [9:34] Locklainn Linden: 2.5 hours of sleep :)
  • [9:34] Locklainn Linden: so I feel ya!
  • [9:34] Enus Linden: so lock, congrats on having had the first pyogp teleport!
  • [9:34] Enus Linden: you were so excited you din sleep huh?
  • [9:34] Lillie Yifu: aw locklainn wooks swo cwoot!
  • [9:34] Locklainn Linden: haha
  • [9:34] Locklainn Linden: exactly
  • [9:35] Locklainn Linden: thanks anyway
  • [9:35] Locklainn Linden: working on presence now
  • [9:35] Enus Linden: so i sent out some updated testing docs, and need to get some help wrt testing OpenSIm
  • [9:35] Locklainn Linden: (btw, that isn't thanks anyway, that is anyway, thanks)
  • [9:36] Locklainn Linden:  :)
  • [9:36] Tess Linden: congrats Lock!
  • [9:36] Enus Linden: i'll work that as I can... I need to set up an OpenSim instance inside LL. I'll do that Monday or Tuesday
  • [9:36] Locklainn Linden: thnx tess
  • [9:36] Locklainn Linden: I'm not sure what I can do to help you enus
  • [9:37] Locklainn Linden: but I will if I can
  • [9:37] Tao Takashi: maybe I should discuss architecture with Locklainn if he's only had 2.5 hours of sleep ;-)
  • [9:37] Enus Linden: i got it Lock
  • [9:37] Saijanai Kuhn: resembles that remakr
  • [9:37] Locklainn Linden: ok cool
  • [9:37] Enus Linden: well, we want to talk architecture, and process yes?
  • [9:37] Lillie Yifu: links to the docs?
  • [9:37] Enus Linden: https://wiki.secondlife.com/wiki/Pyogp/Client_Lib/testing
  • [9:38] Tao Takashi: I think so, my proposal is here btw: [1]
  • [9:39] Tao Takashi: in other news I captured some packets which are going from the LL AD to opensim to see what's happening there
  • [9:39] Lillie Yifu: thank you!
  • [9:40] Enus Linden: so Tao, you are recommending a formal process we all would agree to, and we talked earlier and again recently about working in branches...
  • [9:40] Black Cat: Doll: ~^.^~ Meow!!! ~^o^~
  • [9:40] Tao Takashi: well, in general I think it would be good to talk more :)
  • [9:40] Tao Takashi: esp. before doing things
  • [9:41] Saijanai Kuhn: believes in coding first, then figuring out what you're trying to do later...
  • [9:41] Tao Takashi: and we should try to get everybody uptodate what the problem is we are solving next, how this problem looks like and how possible soltuions could look like
  • [9:41] Enus Linden: i agree... not much has been done in the library lately, save Locklainn's work on messaging
  • [9:41] Tao Takashi: well, coding first is ok if you don't expect it to be the final code
  • [9:41] Saijanai Kuhn: I mean before you know ANYTHING
  • [9:41] Enus Linden: :P
  • [9:41] Tao Takashi: esp. in this case here we seem to need a lot of experiments in order to find out what's really happening anyway
  • [9:41] Saijanai Kuhn: spontaneous art... ;-)
  • [9:42] Tao Takashi: but we should also write down what we find out
  • [9:42] Enus Linden: I agree Tao
  • [9:42] Tao Takashi: e.g. in some protocol definition on the wiki
  • [9:42] Enus Linden: where would we write it down so that the knowledge is shared?
  • [9:42] Tao Takashi: and once we know what the problem is we can then think about solutions
  • [9:42] Tao Takashi: there should be places on the wiki describing the protocol
  • [9:42] Tao Takashi: all the packets and so on
  • [9:43] Tao Takashi: so it shouldn't reside in the pyogp tree if it's general knowledge
  • [9:43] Tao Takashi: but maybe we should make some project page for some project we do and add links to the docs there
  • [9:43] Tao Takashi: name of branch etc.
  • [9:43] Enus Linden: hmm. could these be scratch pages first? that could be formatted nicely later? with a note to that effect at the top?
  • [9:43] Tao Takashi: design notes, architecture stuff
  • [9:43] Saijanai Kuhn: well, the logical place to do that is below each packet description on the wiki. But there's only a tiny handfu with any analysis at all
  • [9:44] Tao Takashi: Sai: so maybe we can help to add more
  • [9:44] Tao Takashi: or maybe we can push some Linden to do that ;-)
  • [9:44] Lillie Yifu: We might even have categories for "notes"/"draft"/"needs clean up"
  • [9:44] Lillie Yifu: that would create.... organization
  • [9:44] Lillie Yifu: gets a look ofshock and horror.
  • [9:44] Enus Linden:  :)
  • [9:44] Tao Takashi: I think for packet related stuff we might as well directly add this to the packet descriptions
  • [9:44] Malburns Writer: lol Lillie
  • [9:45] Tao Takashi: maybe with some note that it's not confirmed or so
  • [9:45] Saijanai Kuhn: there's always https://wiki.secondlife.com/wiki/Category:Pyogp_Kitchen_Sink
  • [9:45] Enus Linden: ok Tao, but a core page wrt pyogp should point to these additions. where we are dealing with the issues in pyogp and interested parties can see what's going on there
  • [9:45] Tao Takashi: yes, but this might be more general than just pyogp
  • [9:45] Tao Takashi: yep
  • [9:46] Enus Linden: remembers he needs to update the pyogp roadmp, and then remembers we need to figure out what the roadmap is first
  • [9:46] Tao Takashi: this basically would be point 3 in my proposal
  • [9:47] Tao Takashi: I am not sure we need a complete roadmap, for me next steps would be enough, these could then link to those subproject pages
  • [9:47] Enus Linden: I think the mailing list would be a good arena for raising problems/areas to focus
  • [9:47] Tao Takashi: with name of branch, links to documentation etc.
  • [9:47] Saijanai Kuhn: each message might require a differnt treatment on the wiki. E.G> https://wiki.secondlife.com/wiki/ImprovedInstantMessage
  • [9:47] Tao Takashi: yes, such a project maybe should be started on the mailinglist
  • [9:47] Enus Linden: i agree with you about next steps begin more important than a complete map...
  • [9:48] Tao Takashi: where you explain what this project is etc. Then a wiki page can be created as a starting point
  • [9:48] Tao Takashi: it should also contain a list of what might be blocking this project
  • [9:48] Tao Takashi: so this apparently needs to be done first
  • [9:48] Tao Takashi: we maybe should also revisit projects and see how we can refactor things
  • [9:49] Tao Takashi: as I doubt we will do it the best way in the first go
  • [9:49] Tao Takashi: so 4 might be writing some examples which work roughly but are not yet in the state you want it to be (like not componentized, not tested etc.)
  • [9:49] Lillie Yifu: https://wiki.secondlife.com/wiki/Category:Pyogp_Draft for a proposed example of such a category and how to use.
  • [9:49] Tao Takashi: like the example login code we have in examples/
  • [9:50] Tao Takashi: more a proof of concept
  • [9:50] Enus Linden: so should we work on the maling list on the curent open topics, the messaging system and networking?
  • [9:50] Tao Takashi: it's probably better to discuss this on the list and not here
  • [9:50] Enus Linden: yes
  • [9:51] Tao Takashi: poing 5 in my proposal would then be to write some high level example of how you would use it
  • [9:51] Enus Linden: per 4, playing around with rough code...
  • [9:51] Enus Linden: sandbox, or branch?
  • [9:51] Tao Takashi: sandbox probably
  • [9:51] Tao Takashi: I started some sandbox package
  • [9:52] Tao Takashi: you can add your own name to it if you want to
  • [9:52] Tao Takashi: what's inside mine is some example client based on a mix between the one in pyogp.lib.base and the examples/ udp loop
  • [9:52] Locklainn Linden: whats the difference between a sandbox and a branch?
  • [9:53] Tao Takashi: 5) could be some sort of doctest which would not pass at that point
  • [9:53] Lillie Yifu: btw wikiHUD works with the second life wiki, so it is possible to reda thedocs in world without a browser.
  • [9:53] Tao Takashi: well, in a sandbox you do something completely new which you might throw away again, playground
  • [9:53] Tao Takashi: a branch is something where you change the library directly
  • [9:53] Enus Linden: cool lillie!
  • [9:53] Locklainn Linden: oh ok
  • [9:53] Locklainn Linden: well then that's project dependent, you will use a sandbox when testing somethign new
  • [9:53] Locklainn Linden: and a branch when changing the code
  • [9:53] Locklainn Linden:  ;)
  • [9:53] Tao Takashi: but it could also be in a branch probably.. I think from 5) on it should live in a branch
  • [9:54] Lillie Yifu: useful because there is an ever growing list of opensim URLs, which means justlooking up that wiki page gives you a list ot explore.
  • [9:54] Lillie Yifu: in a copy and pasteable format
  • [9:54] Tao Takashi: because then you add a breaking doctest ;-)
  • [9:54] Tao Takashi: and this might break until you have finished
  • [9:54] Lillie Yifu: as a non-technical person
  • [9:54] Tao Takashi: to me at least it helps to have some example high level code to explore the objects and define those classes I want to use
  • [9:55] Lillie Yifu: what Tao is proposing makes a great deal of sense.
  • [9:55] Tao Takashi: thanks, Lillie :)
  • [9:55] Enus Linden: locklainn, as the other active pyogp dev, does this approach make sense to you?
  • [9:55] Enus Linden: i do like the notion of doing work in branches
  • [9:55] Tao Takashi: actually 6 was writing an example.. 5+6 should go together porbably as it might be a back and forth here
  • [9:55] Enus Linden: it allows the trunk to remain stable in some known state for some time
  • [9:56] Locklainn Linden: hmm, I guess I'm not sure what the question is
  • [9:56] Enus Linden: and prior to a merge we can take a look at a branch ...
  • [9:56] Locklainn Linden: isn't this how all projects work? branching and stuff?
  • [9:56] Tao Takashi: unfortunately if the trunk moves along it's getting harder to merge later with svn.. hg would really have benefits here
  • [9:56] Enus Linden: not so far with pyogp locklainn :)
  • [9:56] Locklainn Linden: right haha, so the idea is to START doing this
  • [9:56] Locklainn Linden: yes?
  • [9:57] Enus Linden: granted, we have been in a frantic sort of way, but i would like to see things settle
  • [9:57] Enus Linden: yeah lock
  • [9:57] Tao Takashi: well, the important bit for me is not the branching but understanding the problem domain and modelling a solution
  • [9:57] Lillie Yifu: also to label more clearly what you are doing, and which stage the work is in
  • [9:57] Locklainn Linden: ok cool
  • [9:57] Tao Takashi: and discussing this on the list
  • [9:57] Locklainn Linden: makes sense to me then
  • [9:57] Enus Linden: tao has explored netwroking, and grok, in branches...
  • [9:57] Lillie Yifu: and talk more on each step of the way about what you are doing.
  • [9:57] Tao Takashi: I was also trying to communicate what I am doing on the list
  • [9:58] Enus Linden: true tao, and i appreciate that effort..
  • [9:58] Tao Takashi: so 7 would then be implementing these components
  • [9:58] Tao Takashi: and maybe iterating over 5-6-7 in order to get to a more lower level
  • [9:58] Tao Takashi: basically thinking on each level how the next lower component mighth be modelled
  • [9:58] Tao Takashi: while you have your example code from your experiments which can grow from the bottom up so to say
  • [9:59] Tao Takashi: because this is most likely very low level
  • [9:59] Tao Takashi: and that's it basically... the group can do review then and decide if it's ready to be merged
  • [9:59] Tao Takashi: then the project owner can merge it
  • [9:59] Tao Takashi: and another question would be if there's a co-owner, too
  • [10:00] Lillie Yifu: https://wiki.secondlife.com/wiki/Pyogp/Client_Lib/The_Development_Sandbox notes, draft,wikify, clea-up?
  • [10:00] Tao Takashi: in the tradition of eXtreme Programming I'd think a co-owner is good and we should also aim towards shared code-ownership
  • [10:00] Tao Takashi: you see something you can improve, you do it (with discussion before probably)
  • [10:00] Tao Takashi: and make sure the tests still pass of course
  • [10:01] Locklainn Linden: I agree, except
  • [10:01] Locklainn Linden: "improve" is subjective
  • [10:01] Enus Linden: i wonder how that can work in our distributed situation?
  • [10:01] Tao Takashi: yes, Locklainn. that's why I added the discussion part ;-)
  • [10:01] Locklainn Linden: as we have found out Tao ;)
  • [10:01] Locklainn Linden: right
  • [10:02] Tao Takashi: but we might have some guidelines. And I would suggest "doing it like the other libs" could be one of them ;-)
  • [10:02] Tao Takashi: but we can discuss this later
  • [10:02] Lillie Yifu: That would be what notes are for, people could write down what they feel would be an "improvement."
  • [10:03] Tao Takashi: Lillie: Yes but I would discuss this on the list, not the wiki
  • [10:03] Enus Linden: the wiki can point the the list archives as needed...
  • [10:03] Tao Takashi: yep
  • [10:03] Lillie Yifu: For example "I feel the pyogp acronym could be made even more unpronounceable by the addition of a 'q' and a 'j'. Soemthing with a diacrtic mark would look cool too." or whatever.
  • [10:03] Tao Takashi: it's also temporary data, once a decision is made I think this is not too important anymore
  • [10:04] Lillie Yifu: But htat is why notes pages are notes.
  • [10:04] Tao Takashi: has a dislike for that wiki ;-)
  • [10:04] Lillie Yifu: And notes have the advantage that you could see what other people have written down, and contribute accordingly.
  • [10:04] Enus Linden: i do think the mailing list can serve that purpose lillie, it's just not as open as the wiki is i suppose
  • [10:05] Lillie Yifu: And then the person drafting soemthing could refer to the notes of the community as to what they have seen, rather than trying to grope through the mailing list.
  • [10:05] Tao Takashi: it's on gmane
  • [10:05] Lillie Yifu: It also doesn't compile things and doesn't act like a filter. Notes are things that people decide need to be remembered or pointed out.
  • [10:05] Tao Takashi: [2]
  • [10:05] Tao Takashi: has RSS and all
  • [10:05] Lillie Yifu: The mailing list is everything, including requests for help, chatter, and so on.
  • [10:06] Enus Linden: sans RSS - https://lists.secondlife.com/pipermail/pyogp/
  • [10:06] Tao Takashi: [3]
  • [10:07] Tao Takashi: so that's from me for the process
  • [10:07] Lillie Yifu: Which doesn't form neatly into the step by step and iteration process that you yourself are proposing. Discussion on the mailng list is good, bu codoification doesn't work well on a mailing list.
  • [10:07] Tao Takashi: no, the results will of course be on the wiki or in code
  • [10:07] Enus Linden: that would happen in the sandbox, or then branches
  • [10:07] Tao Takashi: like I said, there can be a project page with link to branch, sandbox, notes etc.
  • [10:08] Enus Linden: i think wiki should probably come after a branch is nearly mature, or as it merges. some wiki can point to "we are exploring this here"
  • [10:08] Enus Linden: but wikis describing what here is could be later
  • [10:08] Tao Takashi: I think the wiki page about the project should be started when the project starts
  • [10:08] Tao Takashi: it could hold links to documentation you need etc.
  • [10:09] Lillie Yifu: It should be much earlier, since documentation of how to use a branch would logically be on the wiki
  • [10:09] Tao Takashi: it can have example code on how you want to use it
  • [10:09] Tao Takashi: etc.
  • [10:09] Enus Linden: but what if it is dismissed Tao?
  • [10:09] Lillie Yifu: an d that by definition is well before maturity
  • [10:09] Lillie Yifu: "this is my proposed patch, here is the wiki page which documents how to apply it and use it."
  • [10:09] Tao Takashi: if the project isn't done?
  • [10:09] Tao Takashi: you delete the page?
  • [10:09] Enus Linden: has stale pages on the wiki
  • [10:09] Tess Linden: to Lillie's point, if we have notes on a particular page, the note is directly linked to the document its describing
  • [10:10] Lillie Yifu: nods
  • [10:10] Tao Takashi: I am just against doing discussion on the wiki
  • [10:10] Tess Linden: but I think we can also have discussions on mailing lists, its just a different tool
  • [10:10] Tao Takashi: because then I am lost ;-)
  • [10:10] Tess Linden: can we have both?
  • [10:10] Tao Takashi: I cannot answer directly etc.
  • [10:10] Tao Takashi: I don't even get what's changed on the page via email, just that it has changed.
  • [10:10] Tao Takashi: so to me wiki would be for noting down the results
  • [10:10] Tess Linden: Lillie: how about adding notes to a discussion page, before sending an email out so others who arent watching the page know about it?
  • [10:11] Tao Takashi: and the watch expires after it was changed once, right?
  • [10:11] Tao Takashi: and you need to look at it again
  • [10:11] Tess Linden: we often add our notes directly onto the wiki itself so anybody who reads it can seeit
  • [10:12] Tess Linden: like "note: This sux and is going away. Tess Aug 18
  • [10:12] Enus Linden: well, our comunication methods will evolve, but I think we are agreeing on the general approaches of 1. more communciation and 2. more process around dealing with problems and implementing their solutions
  • [10:12] Tao Takashi: well, this is ok if it's documentation and I then know I don't have to care about. But that's different from having a discussion on a wiki
  • [10:13] Lillie Yifu: Unless you want peopel tossing backa and forth entire pages which are the draft of soemthing on the mailing list all the time every time they are discussing whether to break a dependent clause into a sentence, it would be adviseable to ahve some line when soemthing needs to be moved to the wiki from the mailing list. Is "offlined" the right term? That way someone could say "I have this branch for testing something" People talk about it, but at a certain point the code woner will then need to write a wiki page which describes the project, which will link to notes pages that will describe people's attempts to use it, and be on its way to documentation as the code stabilizes.
  • [10:13] Lillie Yifu: adds Tao to the [[Category: Needs wikificiation]
  • [10:14] Tao Takashi: I am not talking about passing complete texts back and forth. This can happen on the wiki. But I would then send out an email explaining the changes and linking to the wiki
  • [10:14] Tao Takashi: but anyway, I think we will sort it out
  • [10:14] Enus Linden: yes we will : )
  • [10:14] Tess Linden: Lillie: lets just try it out on a few examples? and then we can see exactly what works and doesnt?
  • [10:15] Tao Takashi: so do we use that process then? ;-)
  • [10:15] Enus Linden: let's discuss on the wiki tao :P
  • [10:15] Lillie Yifu: That sounds like a good idea: try the process on developing the process.
  • [10:15] Tao Takashi: ok, you discuss and inform me then, please ;-)
  • [10:15] Enus Linden: um, i think that it is a fair proposal
  • [10:15] Tess Linden: I'm thinking Lillie has a specific example, and its hard to describe without actually just trying it out
  • [10:15] Lillie Yifu: If it works on developing itself, then it has at least some change of generally working.
  • [10:15] Lillie Yifu: Well I've just started doing it
  • [10:16] Tao Takashi: add to it that from here the wiki is also most of the time rather slow
  • [10:16] Lillie Yifu: I added the testing and The_Development_Sandbox to the Pyogp_draft categorey
  • [10:16] Lillie Yifu: I think the next logical step is to goand work through Tao's proposal in this same way
  • [10:16] Tess Linden: Lillie: just make sure somebody is aware of your concerns
  • [10:16] Lillie Yifu: discuss on the mailing list,
  • [10:16] Lillie Yifu: attempt to implment it on the wiki with notes and a draft
  • [10:16] Lillie Yifu: and see if people are comfortable with that
  • [10:17] Tao Takashi: I am adding a page with the proposal now
  • [10:17] Enus Linden: please let the list know, and we'll run with it Tao :)
  • [10:17] Lillie Yifu: The specific thing I am thinking about is that right now much of hte pyogp stuff is a bit hard to read and requires many many google searches to fill in missing links and so on
  • [10:17] Tao Takashi: and it loads and loads...
  • [10:17] Lillie Yifu: I'd like to wikify it
  • [10:17] Lillie Yifu: but don't know if it is ready ofr that.
  • [10:17] Tao Takashi: so that's my problem with that wiki, email is faster ;-)
  • [10:18] Lillie Yifu: hmmm It's faster to output
  • [10:18] Lillie Yifu: but not faster for the reader.
  • [10:18] Enus Linden: i agree, the pyogp docs on the wiki now need a cleanup. I haven't had time to maintain them lately...
  • [10:18] Lillie Yifu: I'd hate to have to look for sim urls using the mailing list. Or other documentation.
  • [10:18] Tao Takashi: another question would be if we should use Sphinx for documentation
  • [10:19] Bartholomew Kleiber: I think there are too much communication channels (wiki, mailing list, irc, sl meetings, occasional skypes). But unfortunately have no idea how to cut that down without loss.
  • [10:19] Lillie Yifu: kk well let's add a category
  • [10:19] Tao Takashi: Lillie: sim urls are not for the mailing list, I agree :)
  • [10:19] Lillie Yifu: and you can just add that to a page that you think is ready for people to go through and work on making it more readable and usable.
  • [10:20] Tess Linden: Lillie: could you instead put in stub wiki pages with topics that you'd like more information on? and put in what you think should be there?
  • [10:20] Lillie Yifu: And thereofre is sort of off your plate except to check on the work that has been done to make sure that the liberal arts majors haven't broken something or mis understood something
  • [10:20] Tao Takashi: so, the pyogp lib page is just about the message system right now.. I guess we need some reorganization
  • [10:21] Lillie Yifu: I'm actually doing that right now as we speak.
  • [10:21] Saijanai Kuhn: I stuck your category in the kitchen sink and pygop categories, Lillie
  • [10:21] Tao Takashi: ah, there is another one which isn't
  • [10:22] Saijanai Kuhn: so its a sub-category of both
  • [10:22] Lillie Yifu: nods to saij
  • [10:22] Tao Takashi: can the wiki also send out diffs ?
  • [10:22] Lillie Yifu: you can send out a diff link
  • [10:23] Enus Linden: Tao, per Sphinx: let's take that up next time around?
  • [10:23] Lillie Yifu: use history, click the two versions
  • [10:23] Lillie Yifu: that will display the diffs and that url will wor for others
  • [10:24] Tao Takashi: Enus: k
  • [10:24] Tao Takashi: Lillie:I mean via email ;-)
  • [10:24] Tao Takashi: when I get a notification I want to know what has changed ;-)
  • [10:25] Bartholomew Kleiber: IIRC you can subscribe the rss feed of the changes
  • [10:25] Tao Takashi: https://wiki.secondlife.com/wiki/Pyogp/Client_Lib/Development_Process
  • [10:26] Tao Takashi: for every page?
  • [10:26] Bartholomew Kleiber: which is different from an email of course
  • [10:26] Bartholomew Kleiber: I think so, yes
  • [10:26] Bartholomew Kleiber: lemme check
  • [10:26] Tao Takashi: yeah, and I don't get my rss feeds read anyway ;-)
  • [10:26] Bartholomew Kleiber: would add another nice channel ;-)
  • [10:26] Bartholomew Kleiber: to the 400 others
  • [10:26] Enus Linden: is scared of rss
  • [10:27] Enus Linden: information tidal wave = rss
  • [10:27] Tao Takashi: I am not but if you have it for every individual page it's kinda useless ;-)
  • [10:27] Bartholomew Kleiber: recent changes should also be subscribable
  • [10:27] Bartholomew Kleiber: but then you have *everything
  • [10:27] Tao Takashi: but that's the whole wiki, right?
  • [10:27] Tao Takashi: great ;-)
  • [10:28] Bartholomew Kleiber: again, I think there are too many chnnels already
  • [10:28] Tao Takashi: like "Pole Dancing"
  • [10:28] Tao Takashi: anyway, page is there.
  • [10:28] Tao Takashi: are there other topics?
  • [10:28] Lillie Yifu: You can add &feed=rss to a special page
  • [10:28] Lillie Yifu: and that will be the link to an rss feed version of that special page
  • [10:28] Tao Takashi: Locklainn fell asleep already..
  • [10:29] Bartholomew Kleiber: right, Lillie
  • [10:29] Enus Linden: poor lock
  • [10:29] Tao Takashi: yeah, I am torturing him..
  • [10:29] Enus Linden: so the hour draws to a close...
  • [10:29] Locklainn Linden: I'm here I'm here
  • [10:29] Locklainn Linden:  :)
  • [10:30] Tao Takashi: so, let me quickly send this abuse report...
  • [10:30] Enus Linden: thanks to all for a good discussion. i look forward to seeing you on the mailing list, in wiki, on irc, and in the 18 pyogp/gridnauts meetings
  • [10:30] Bartholomew Kleiber: lol
  • [10:30] Tao Takashi: I will try to get my AD up this weekend :)
  • [10:30] Enus Linden: but, i will be out this afternoon
  • [10:30] Enus Linden: so i will see you all again on Monday
  • [10:31] Locklainn Linden: alright
  • [10:31] Locklainn Linden: have a good weekend enus
  • [10:31] Locklainn Linden: and everyone
  • [10:31] Tao Takashi: and I will look through all the code :)
  • [10:31] Tao Takashi: yeah, have a great weekend everybody!
  • [10:31] Enus Linden: you too Tao
  • [10:31] Enus Linden: thanks all
  • [10:31] Tao Takashi: I have work to do ;-)
  • [10:31] Enus Linden: see yas...
  • [10:31] Locklainn Linden: thanks everyone, cya
  • [10:31] Tao Takashi: cyas!
  • [10:31] Malburns Writer: Thanks all
  • [10:31] Bartholomew Kleiber: bye all
  • [10:31] Mirt Tenk: take care