Open Source Meeting/Agenda
Open source meeting - Thursday, 2pm PT.
Teleport to the Linden Open Source Project headquarters.
Please try to add your items as early as possible in the week to give Rob a chance to round up any Lindens that may be appropriate to the discussion. Please also bring items up on SLDev before or concurrently with adding them as agenda items here.
Agenda
- Next item? Your name? (sign with "~~~~" which will be converted to your name + timestamp)
Default agenda (barring agenda above):
- Update from the Lindens (standing item) - Rob Linden
- Threaded Local File System (LLFSThread class) - what are LLs plans for it? Carjay McGinnis 10:51, 17 June 2008 (PDT)
- Triage of issues listed here: http://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=11240
- Meta Agenda:
| How do you feel about relative C++ noobs (*waves!*) jumping headfirst into the client source to explore it? Do you prefer that only people with years of prior C++ experience try to be involved with the open source project? ("Come back when you've actually used a multimap in a program!")
I am wondering if showing up at the open source meeting and asking what may seem as "stupid beginner's questions" would be perceived as annoying and a waste of your professional time. (For example, why is ll_apr_file used for open/read/write/etc rather than just apr_file? Is llapr.cpp a shim library, to make transitioning from the LLLFS easier? And IS the LLLFS being replaced by the APR? I can't find any official coding policy or notes pointing in that direction. Is it okay to discuss this in SL-Dev or not?) My interest and involvement in the source is mostly because I want the VFS expunged, and the overall caching performance improved... but since this coding task is apparently not on anyone else's agenda, I guess there's room for a QBASIC/LSL2/Apple II 6502-assembly programmer to explore the issue. (Note, the only thing I've ever threaded is a needle.) Scalar Tardis 10:23, 19 June 2008 (PDT) |
- Discuss the changes to llTextureFetch and llTextureCache recently discussed on SLDEV, any issues that may arise from moving the decode and network fetch operations to llTextureCache (or possibly more or less combining the two classes into one), and other "uncompressed cache" issues. Buckaroo Mu 12:10, 19 June 2008 (PDT)