I'll be submitting this report at some point over the weekend, probably Saturday night because I'm an exciting and social fellow. So please get any comments in before then.
Cheers, Tom Grammar and spelling have been sacrificed on the altar of messaging via mobile device. On 9 Aug 2011 23:04, "Tom Hobbs" <tvho...@googlemail.com> wrote: > That'll teach me. > > This was me moving from private@ to @dev but not editing the email well > enough. I did make the rest of the suggested edits though. > > > > Grammar and spelling have been sacrificed on the altar of messaging via > mobile device. > > On 9 Aug 2011 20:30, "Christopher Dolan" <christopher.do...@avid.com> wrote: >> Sure, go ahead and move the discussion to dev@. >> >> :-) >> >> Chris >> >> -----Original Message----- >> From: Tom Hobbs [mailto:tvho...@googlemail.com] >> Sent: Tuesday, August 09, 2011 2:20 PM >> To: dev@river.apache.org >> Subject: [DRAFT][REPORT] River Board Report August 2011 >> >> Comments always welcome, due date is 15th August. >> >> Sent to private@ because I thought there might be a couple of things >> that should remain so. I'm happy to move it onto dev@ if people think >> that's unnecessary. >> >> Below is the August board report for River >> >> Apache River is a distributed computing architecture, based on the JSK >> Starter Kit Source code donated by Sun Microsystems, for the Jini >> Specification. >> >> Releases: >> Our first TLP release (2.2.0) was finally made available on 28th July. >> Progress: >> As usual, the community is there but activity on dev@ is pretty slow. >> There's usually a flurry of activity when one of our number manages to >> find sme time and get something done. We believe this proves that, >> although small, the community exists and is still functioning well. >> >> Community: >> We made one invitation to committer/PMC status this period but it was >> implicitly turned down (no response to offer email). On the other >> hand, the arguments which plagued the early days of River aren't >> happening. We're also getting involvement from Jini old hands. >> >> Issues: >> No board issues at this time. >> >> Website/Trademark Checklist: >> - Project Website Basics : homepage is project.apache.org (COMPLETE) >> - Project Naming And Descriptions : use proper Apache forms, describe >> product, etc. (COMPLETE) >> - Website Navigation Links : navbar links included, link to >> www.apache.org included (COMPLETE) >> - Trademark Attributions : attribution for all ASF marks included in >> footers, etc. (INCOMPLETE, NOT CHECKED) >> - Logos and Graphics : include TM, use consistent product logo on your >> site (INCOMPLETE, NOT CHECKED) >> - Project Metadata : DOAP file checkedin and up to date (INCOMPLETE, >> NOT CHECKED) >> >> The board also asked to make sure that all PMC members had read the >> PMC trademark/branding responsibilities. [1] 4/11 PMC members >> confirmed that they'd read it, although I suspect that some of the >> others had already read it given their involement with other Apache >> projects. There was a very brief discussion that it wasn't >> immediately obvious/clear when signing up for PMC duties that >> "trademark enforcer" was part of the role. It seemed a fair comment >> but I hope that by outlining the support provided by ASF we don't have >> to be legal experts in this field to be able to keep an eye on how >> other entities use the Apache River marks. >> >> [1] http://www.apache.org/foundation/marks/responsibility.html
