Hi Seungwon, That’s a good start, however, perhaps I could suggest even an alternative to that. Rather than reporting notes *after* a meeting has happened, bring the discussion items from the meeting to the list *ahead* of time. Discuss the answers and replies from your team(s) in email. Let the discussion play out over the list. Then there’s no need to send any summary - the list simply becomes the record of the meeting. This also provides an opportunity for others to join in on the discussion *while it’s going on* rather than after the fact. This is an important element to (open-source) community building as it allows others to feel included in your project. In particular it also allows effective oversight and help to be provided to the project.
I hope you will consider doing the above. I think it would help to alleviate many of the concerns that have been raised so far. Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: "Lee, Seungwon (398K)" <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, August 11, 2015 at 9:50 AM To: "[email protected]" <[email protected]>, Greg Reddin <[email protected]>, Jia Zhang <[email protected]> Cc: "Pan, Lei (398K)" <[email protected]>, "Zhai, Chengxing (398K)" <[email protected]>, "Tang, Benyang (398J)" <[email protected]>, Wei Wang <[email protected]>, Xing Wei <[email protected]> Subject: Re: Project Activity >Sounds good. I will just report our project meeting note to this list >every week. > >-- >Dr. Seungwon Lee >Technical Group Supervisor >Science Data Modeling and Computing (398K) >Instrument Software and Science Data System Section (398) >Jet Propulsion Laboratory >California Institute of Technology >Tel: 818-393-7720 >Cell: 818-397-2284 > >From: "Mattmann, Chris A (3980)" ><[email protected]<mailto:[email protected]>> >Reply-To: >"[email protected]<mailto:[email protected]>" ><[email protected]<mailto:[email protected]>> >Date: Tuesday, August 11, 2015 at 9:48 AM >To: "[email protected]<mailto:[email protected]>" ><[email protected]<mailto:[email protected]>>, >Greg Reddin <[email protected]<mailto:[email protected]>>, Jia Zhang ><[email protected]<mailto:[email protected]>> >Cc: Lei Pan <[email protected]<mailto:[email protected]>>, "Zhai, >Chengxing (398K)" ><[email protected]<mailto:[email protected]>>, "Tang, >Benyang (398J)" ><[email protected]<mailto:[email protected]>>, Wei Wang ><[email protected]<mailto:[email protected]>>, Xing Wei ><[email protected]<mailto:[email protected]>> >Subject: Re: Project Activity > >Great work, now the catch is, all of this development needs to be >happening out in the open at Apache. It’s something that is required >of any open source project at the ASF. > >So, the next cycle of reporting, let’s say next month, we need >to have all the of the below type of actions, but to have them play >out on list, and not in meeting rooms at JPL where others can’t >participate. > >Does that make sense? > >Cheers, >Chris > >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >Chris Mattmann, Ph.D. >Chief Architect >Instrument Software and Science Data Systems Section (398) >NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >Office: 168-519, Mailstop: 168-527 >Email: [email protected]<mailto:[email protected]> >WWW: http://sunset.usc.edu/~mattmann/ >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >Adjunct Associate Professor, Computer Science Department >University of Southern California, Los Angeles, CA 90089 USA >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > >-----Original Message----- >From: "Lee, Seungwon (398K)" ><[email protected]<mailto:[email protected]>> >Reply-To: >"[email protected]<mailto:[email protected]>" ><[email protected]<mailto:[email protected]>> >Date: Tuesday, August 11, 2015 at 9:46 AM >To: Greg Reddin <[email protected]<mailto:[email protected]>>, Jia Zhang ><[email protected]<mailto:[email protected]>> >Cc: "[email protected]<mailto:[email protected]>" ><[email protected]<mailto:[email protected]>>, >"Pan, >Lei (398K)" <[email protected]<mailto:[email protected]>>, "Zhai, >Chengxing (398K)" ><[email protected]<mailto:[email protected]>>, "Tang, >Benyang (398J)" ><[email protected]<mailto:[email protected]>>, Wei Wang ><[email protected]<mailto:[email protected]>>, Xing Wei ><[email protected]<mailto:[email protected]>> >Subject: Re: Project Activity > >Hi all, > >I have joined the CMDA dev list. How can I see who is in the list? Lei, >Chengzing, Benyang, Wei, Jia, please join the CMDA dev list and let me >know after you get a confirmation. > >I want to summarize some of the development activities we were involved >since we started the Apache incubator, based on our project meeting >notes. Lei, Chengxing, Benyang, please add or modify my list below. > > * We developed three new diagnostic analysis algorithms: Random >Forest for feature importance ranking, Multi-dimensional conditional >sampling, time-lagged correlation. > * We implemented the algorithms in web services. > * We developed an efficient data regridding algorithm and implemented >it in a web service. > * We improved our web-service front end in handling the data source >and available variable list. The available data source and variable pairs >used to be hard-coded in each HTML file. Now the pairs are read from a >database and stored in a dictionary and used as a common function by all >the front end HTML files. > * We incorporated a new technology called “webification” to access >data directly through a URL. > * We had added new datasets that can be used by our web services: >AIRS surface air temperature, MODIS surface air temperature, CMIP5 RCP >4.5 experiment model outputs, ECMWF daily data products for cloud, MODIS >daily data products for low cloud fraction. > * We are developing a new diagnostic analysis algorithm called >“conditional probability density distribution.” > * We are working with CMU (Carnegie Mellon University) to develop a >provenance support system. The CMU team will provide more details about >it. > >-- >Dr. Seungwon Lee >Technical Group Supervisor >Science Data Modeling and Computing (398K) >Instrument Software and Science Data System Section (398) >Jet Propulsion Laboratory >California Institute of Technology >Tel: 818-393-7720 >Cell: 818-397-2284 > >From: Greg Reddin ><[email protected]<mailto:[email protected]><mailto:[email protected]>> >Date: Monday, August 10, 2015 at 3:56 PM >To: Jia Zhang ><[email protected]<mailto:[email protected]><mailto:[email protected] >.edu>> >Cc: >"[email protected]<mailto:[email protected]><mailt >o:[email protected]>" ><[email protected]<mailto:[email protected]><mailt >o:[email protected]>>, >"[email protected]<mailto:[email protected]><mailto:Seungw >[email protected]>" ><[email protected]<mailto:[email protected]><mailto:Seungw >[email protected]>>, Lei Pan ><[email protected]<mailto:[email protected]><mailto:[email protected] >.gov>>, "Zhai, Chengxing >(398K)" ><[email protected]<mailto:[email protected]><mailto:ch >[email protected]>>, "Tang, >Benyang (398J)" ><[email protected]<mailto:[email protected]><mailto:Benyan >[email protected]>>, Wei Wang ><[email protected]<mailto:[email protected]><mailto:[email protected] >u>>, Xing Wei ><[email protected]<mailto:[email protected]><mailto:[email protected] >u>> >Subject: Re: Project Activity > >On Mon, Aug 10, 2015 at 5:34 PM, Jia Zhang ><[email protected]<mailto:[email protected]><mailto:[email protected] >.edu>> wrote: >The team has been working hard to create Version 1.0 to be posted - in >addition, we have been trying to explore a way to host the runnable to >Docker running on AWS. We are pretty much done, and we will start to >publish >to Apache this week. > >Thanks for the response, Jia. It sounds like maybe you're working on >Version 1.0 and the Docker runtime on proprietary code that cannot be >shared yet. Is that correct? If so, that explains that the work is not >being done on-list. However, it would be really nice if the >Docker-related discussions could happen on-list. That way others could >at least have visibility into what's going on - even if we can't offer >much. Also, it would get you guys into the habit of discussing >on-list, which is a good thing. > >Thanks! Looking forward to more coming. > >Greg > > >
