-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We've been recruiting several groups to participate, and I expect an increase 
in communications on the list from java cyberinfrastructure developers from 
Iowa State and University of Minnesota.  We also have met with Chris Mattman 
and others from Apache OODT, which is doing complementary things.  We have 
discussed pilot projects with OODT, so I think this is something we can do 
immediately to broaden the community.

Two issues I have seen: 1) we tend to get contacted directly by collaborators 
instead of through the dev list, so we need to encourage (or insist) that more 
traffic goes on airavata-dev; and 2) we have many collaborators who are not 
java developers but who have valuable requirements, usage scenarios, feedback, 
complaints, etc that also need to go on the list. We need to make it clear to 
the second group that there are many ways to contribute besides submitting code 
patches.


Marlon


On 1/31/12 8:55 AM, Ross Gardler wrote:
> First off, I've been a little remiss in my duties as a mentor here.
> Appologies for that and thanks to Chris for keeping things moving. I
> hope to find more time to spend on this project in the near future.
> 
> I would like to see the project members discussing how we can go about
> building community diversity in the project.
> 
> What simple actions can we take to raise awareness (over and above the
> lower barriers and make releases items in the board report)?
> 
> I'm particularly interested in hearing from people who are lurking
> here but not yet contributing. What is stopping you from de-lurking?
> How can we help you take those first initial steps?
> 
> For those active in the project how do we communicate the value of
> Airavata to the rest of the world? Are there any often requested items
> that people can work on as a first step into the project community?
> 
> Any other ideas?
> 
> My goal is for us to come up with 3-5 concrete actions that we can
> include in our next board report.
> 
> Ross
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPJ/gqAAoJEEfVXEODPFIDHZAH/i6Zna9sHcis0GLEfTfotrzO
l2feAQMbG2I6IO/BOxM8lXtVPbjJGE7DhiFuskbjaommDl+v5Y83UP1lPUTkUIZy
1qVCSlIY/7R0ey9ogYA4Yq4rOM7vC+udGlXM5c3Hob/uboctT5io573jx7nGBlqw
V857RAgbbJdXBVecr25FdEh0jU+It7oJGksERBJnH01EJEvQFof9/1GeuGmnJou4
rd+LZJZNIhjXa1ZL/uR9BP7kPkMpk4dKVW6xq5d1pg2gJzU9/RE75DYY8r+fsRum
fUc37om165goIqSHjgq5kRfQdIAHliMwyH/cpp5yjd7a68hASkg5evHo2WxX+l8=
=6TAH
-----END PGP SIGNATURE-----

Reply via email to