Attending: Alex, Kim, Michael, Danny, Bernie, Ricardo Test Sprint - <ol><li> Review of test plans on the wiki </li><li> Test Activity </li><li> Tinderbox </li></ol> <ul><li> Michael summarized the Test Activity logging feature: purpose is to reduce the cost of testing by distributing the testing and automate the logging upload. In the short term, we should focus on getting the logging <ul><li> Modify sugar to put a wrapper around an activity to turn on its logging. Then a crash or a user initiated activity close will zip up files and send them to a central server. </li><li> The central server can start off with a generic account (perhaps password-less smtp, or something). Could possibly have a local smtp server to send an email with attachment. </li><li> Start with a list of the system status (build version, firmware versions, maybe some of Yani's network config info) </li><li> Is there a lot of overlap with syslog? Bernie can probably help with getting the logs </li></ul> </li></ul> <ul><li> The three pieces that need to work for this are: <ol><li> Local collection of logs </li><li> Packaging of the logs for sending </li><li> Reliable delivery in the face of network downtime </li></ol> </li></ul> Things we learned from sprint: <ul><li> Takes too long to get outside developers up to speed and contributing <ul><li> focused documentation </li><li> too much overhead to get hosting for access to git repository </li></ul> </li></ul> <ul><li>On the manual side, we also didn't have enough planning to get people going quickly: <ul><li> Need to get on Trac </li><li> Need to get on mailing lists </li><li> Need to get on irc </li><li> Need to edit wiki pages </li></ul> </li></ul> Should we have someone spend a few hours on the getting started wiki pages so that new developers or testers really can get started. Should we hire someone to organize the community efforts; answer their questions (<a href="http://wiki.laptop.org/go/TestMtg%252C_2007-10-22">http://wiki.laptop.org/go/TestMtg%2C_2007-10-22</a>)