Hi Chris, On Feb 5, 2012, at 12:38 PM, Mattmann, Chris A (388J) wrote:
>> 2) JIRA tasks - Currently the developers are adding issues on what they are >> working. This is undoubtedly helping to track commits to JIRA, but as a good >> development practice, we should add as many tasks as possible, and then when >> we start to work on an issue, we should assign it to ourselves and start >> coding. This way we know the active development areas ahead of time and >> community can if possible align. > > This is a fine suggestion: just watch out you may add too many tasks in JIRA > :) As a metric, Nutch (a project that's been > at the ASF since 2005 (and before)) just over this past year hit its 1000th > JIRA issue. Hadoop is well over 2x that, Tika > is still < 1000, and OODT is ~400-500. So, there's no real hard metric or > number here, just realize that the more you put in, > the more you'll have to actively triage as well. I think this will help us in this initial phases, but got the warning. >> 4) Improve architecture diagrams, data models, schema documentation, E-R >> diagrams what ever makes community to understand the code better. > > Yep that's a good idea. But I'll turn this question around. Who is asking for > this documentation? I haven't seen a ton of users here, > so they are likely out there somewhere, and asking you guys for it, but I'm > not seeing it on list. It would be great to see that > conversation shift to the list. Yes, I'm not perfect at this either and nor > is anyone, but just something to shoot for. Yes, we had some people ask for off the list and we are trying to encourage more and more communications in the list. But in general, Airavata is targeted more towards middleware developers who can add thin UI layers meeting to specific needs. The strength of airavata is its flexible and interoperable architecture where communities can pick and choose the components they would like and integrate it into existing environments. At same time, it can be used as a self-contained system, so good architecture diagrams and API documentation should make these integrations easier. More over we need to ease the development steps to receive contributions to a single component without having to understand the entire system. From what I can tell, from website OODT has done a good job on these aspects. Airavata needs to catch up. >> 5) Improve usability. Invite HCI usability experts to criticize at same time >> give suggestions to improve. > > Hmmm, good idea -- can you send some of them OODT's way?? :) We got some good feedback from HCI teams previously, but not sure we will succeed on this again. But sure if we see interested matching data management and related areas, we know where to point to. >> 7) Start developing web interfaces/gadgets to Airavata back end services and >> actively work with projects like Rave. > > Yep, feel free to ask for help on that on [email protected] too -- we have > some UI devs (Andrew Hart is one of them) > and some others who really enjoy working on UIs. Gasp -- I even like it too! > :) But I'm a huge Wicket guy so if you use Wicket, > you'll have a supporter (and potential coder) in me! I am an UI illiterate and do not understand the difference between wickets, gadgets and so on. To me Wicket is one of the stumps in the game of cricket :) >> Couple of brainstorming ideas: >> * Should we actively participate in Google summer of code? this not only >> helps us to break down the tasks, it also makes us think the next 6+ months >> of roadmap. If we are lucky, we might get good code contributions too. Ross, >> Chris, Any directions on how to proceed on this? > > +1 to participate in GSoC. I haven't managed to get to do it with OODT but > may try this year. Can't be free cycles! > And yes, Ross is right, jump over on [email protected] and ask there > for more info or check out: > > http://community.apache.org/gsoc.html Thanks to you and Ross for pointer to community. I see GSOC was announced earlier this week. We will get ready with the project ideas. Suresh >> * Invite Airavata to be used for capstone projects in programming and HCI >> courses? Answering student questions will improve our FAQ's greatly and as >> above we might expand community to both faculty and students. > > Yep I've found teaching OODT in my Search Engines and Software Architecture > courses really helps. > >> * Reach out to technical writers to seek their help in improving >> documentation? > > I wouldn't worry too much about this. > >> * How to address Marlon's comment on making the community feel that they >> need not write code to be part of the project and be pro-actively contribute >> to its future directions? > > Bingo! Just keep beating the drum. Or get people like Barbara hanging around > again (Barb, you there? :) ). Recognize people who > fly by on list with some interest, and maybe just an email but think about > how to get them more engaged. Offer them committership -- > giving that bit away on someone with interest doesn't hurt anything and we're > using a VC system -- if things mess up it can be reverted. > The good will you'll garner from making them though, won't be :) > > Cheers, > Chris > >> On Jan 31, 2012, at 12:13 PM, Mattmann, Chris A (388J) wrote: >> >>> Hi Marlon, >>> >>> Both of these are great suggestions and yes we can immediately cite a >>> synergy with OODT as well and some >>> pilot projects. Getting the conversation on list will be great for the >>> other direct contacts, but it's something we >>> struggled with originally in OODT and something that can be worked through. >>> >>> Great suggestions. >>> >>> Cheers, >>> Chris >>> >>> On Jan 31, 2012, at 6:18 AM, Marlon Pierce wrote: >>> >>>> -----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----- >>> >>> >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> Chris Mattmann, Ph.D. >>> Senior Computer Scientist >>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>> Office: 171-266B, Mailstop: 171-246 >>> Email: [email protected] >>> WWW: http://sunset.usc.edu/~mattmann/ >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> Adjunct Assistant Professor, Computer Science Department >>> University of Southern California, Los Angeles, CA 90089 USA >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> >> > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >
signature.asc
Description: Message signed with OpenPGP using GPGMail
