I am OK with doing interop planning in the Technical committee. If it turns out that only a subset of people are interested in the interop activities then we can form a sub-commitee.
John B. On 2010-01-20, at 6:08 PM, Chris Messina wrote: > To build on what Brian said -- if there are warm bodies "shovel ready", then > a subcomittee could make sense. In practice though, sustaining momentum and > buyin has proven challenging, and I think one way to curb that issue is to > give committees a window of time to operate in, be evaluated, and then > continued only if progress is being made. > > So, I could go either way as well, but would be swayed by commitment and/or > dedicated interest in accomplishing specific objectives. > > Chris > > Sent from my iPhone 2G > > On Jan 20, 2010, at 14:15, Brian Kissel <[email protected]> wrote: > >> It could be a subcommittee or its own committee, I don't feel strongly >> either way, but would suggest that a number of folks who will be on the >> technical committee will also be on an interop committee, so that group is >> probably in the best position to recommend how to organize themselves to >> achieve their collective goals. From personal experience, trying to >> get/keep committees active and productive is harder than we'd like, so >> limiting the fragmentation of groups when possible is advantageous since >> there is overhead associated with managing groups. But if there is a >> passionate and focused group that wants to work explicitly and exclusively >> on interop, we should take advantage of that desire and create the right >> organizational capability for them to make those contributions. >> >> Cheers, >> >> Brian >> ___________ >> >> Brian Kissel >> CEO - JanRain, Inc. >> [email protected] >> Mobile: 503.342.2668 | Fax: 503.296.5502 >> 519 SW 3rd Ave. Suite 600 Portland, OR 97204 >> >> Increase registrations, engage users, and grow your brand with RPX. Learn >> more at www.rpxnow.com >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of John Bradley >> Sent: Wednesday, January 20, 2010 10:45 AM >> To: [email protected] >> Cc: [email protected] >> Subject: Re: [OpenID board] Commitees >> >> It was Pam's idea:) >> >> So you think it should be a subcommittee of the Technical committee? >> >> John B. >> On 2010-01-20, at 3:39 PM, Brian Kissel wrote: >> >>> Good suggestion John. I'd suggest that once the Technical Committee is >>> officially organized for 2010 (members and chair(s)), that group should >>> make a recommendation on whether to also create an Interop committee. I'd >>> also advocate that the Adoption Committee decide if they feel we should >>> also have a "Marketing" committee. >>> >>> Cheers, >>> >>> Brian >>> ___________ >>> >>> Brian Kissel >>> CEO - JanRain, Inc. >>> [email protected] >>> Mobile: 503.342.2668 | Fax: 503.296.5502 >>> 519 SW 3rd Ave. Suite 600 Portland, OR 97204 >>> >>> Increase registrations, engage users, and grow your brand with RPX. Learn >>> more at www.rpxnow.com >>> >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of John Bradley >>> Sent: Wednesday, January 20, 2010 9:40 AM >>> To: [email protected] >>> Cc: [email protected] >>> Subject: [OpenID board] Commitees >>> >>> I was talking to Pam about the committee structure. >>> >>> Should we have a committee on interoperability and testing separate from >>> the Technical committee? >>> >>> In the past we have mostly relied on OSIS organizing events, and scenarios. >>> As one of the OSIS co-chairs I am not suggesting we stop participating in >>> joint events, however it may be time to start organizing some of that work >>> as part of the OIDF. >>> >>> John Bradley >>> >>> >>> >>> _______________________________________________ >>> board mailing list >>> [email protected] >>> http://lists.openid.net/mailman/listinfo/openid-board >>> _______________________________________________ >>> board mailing list >>> [email protected] >>> http://lists.openid.net/mailman/listinfo/openid-board >> >> _______________________________________________ >> board mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-board >> _______________________________________________ >> board mailing list >> [email protected] >> http://lists.openid.net/mailman/listinfo/openid-board > _______________________________________________ > board mailing list > [email protected] > http://lists.openid.net/mailman/listinfo/openid-board _______________________________________________ board mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-board
