Very good, Joe Thomas
---- Thomas Huang Group Supervisor, Data Product Generation Software Instrument Software and Science Data Systems Jet Propulsion Laboratory, California Institute of Technology (818) 354-2747<tel:(818)%20354-2747> On Dec 5, 2023, at 1:03 PM, Jacob, Joseph C (US 398H) <joseph.c.ja...@jpl.nasa.gov.invalid> wrote: I'd also be in favor of leaving the science domain open as well. On the "Unity SDS" (science data system project) at JPL I have an SDAP deployment and ingested some planetary data to run time series as an experiment last year. Unity is mainly focused on Earth for now, but I recall hearing during the formulation stage that support for Earth, planetary, and astrophysics is in the long-term roadmap. To work with the planetary data, I had to repackage the input data into a CF-compliant NetCDF format that SDAP supports. Maybe in the future we will want to extend SDAP to directly support science data formats common in other domains like PDS4 and FITS. Joe On 12/5/23, 7:28 AM, "Riley Kuttruff" <r...@apache.org <mailto:r...@apache.org>> wrote: I think we shouldn't restrict ourselves to Earth science here. We could definitely point out that it is currently used in Earth science elsewhere, but we should avoid attaching that label to the project for the extended future in the (apparently likely) event we will branch out in application to planetary sciences. On 2023/12/05 00:37:32 Nga Chung wrote: This might just be me being nitpicky, but I think it should be analytics with an s and wondering if we should say "integrated data analytics center for big Earth science problems?" Should we emphasize Earth here versus science in general? Understandably, there isn't anything preventing SDAP from being used outside of the Earth Science domain, but emphasizing Earth science may make SDAP stand out from other data analytics solutions. Best, Nga On Mon, Dec 4, 2023 at 4:21 PM Riley Kuttruff <r...@apache.org <mailto:r...@apache.org>> wrote: So something like WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to an integrated data analytic center for Big Science problems. ... and so on I think that's much better! Thanks for the feedback! On 2023/12/05 00:18:38 Julian Hyde wrote: The phrase "focusing on technology integration, advancement and maturity” seems to be a little superfluous. It is not description, but more of a mission statement. Could you remove it? I think that SDAP is… an integrated data analytic center for Big Science problems is a perfect description (aka high concept pitch). It will also be the first line of every board report and conference presentation for the next ten years. So make sure you like it and are comfortable saying it. :) You can also have a mission statement that is 1 - 2 sentences in length. Don’t try to force it into a single phrase. Just my two cents (wearing my marketing hat). Julian On Dec 4, 2023, at 4:08 PM, Riley Kuttruff <r...@apache.org <mailto:r...@apache.org>> wrote: Already done! (Pending PMC choices) --- WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to an integrated data analytic center for Big Science problems focusing on technology integration, advancement and maturity. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache SDAP Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache SDAP Project be and hereby is responsible for the creation and maintenance of software related to an integrated data analytic center for Big Science problems focusing on technology integration, advancement and maturity; and be it further RESOLVED, that the office of "Vice President, Apache SDAP" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache SDAP Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache SDAP Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache SDAP Project: * NAME EMAIL NOW, THEREFORE, BE IT FURTHER RESOLVED, that **TBD** be appointed to the office of Vice President, Apache SDAP, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache SDAP Project be and hereby is tasked with the migration and rationalization of the Apache Incubator SDAP podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator SDAP podling encumbered upon the Apache Incubator PMC are hereafter discharged. On 2023/12/05 00:06:14 Julian Hyde wrote: Might be worth generating a draft graduation resolution. In that resolution there are a couple of things to discuss — a description of the project, initial PMC (are there any committers/PPMC members who do NOT want to join the PMC) and initial PMC chair. On Dec 4, 2023, at 3:59 PM, Riley Kuttruff <r...@apache.org <mailto:r...@apache.org>> wrote: Ok, I've cleared all the red flags. I used today's date for dates I didn't know. I don't know if that's ok. Still waiting for the name search before we can proceed. I think once that's done and (hopefully) approved, we can proceed to vote! On 2023/12/01 22:07:09 Julian Hyde wrote: I checked SDAP’s roster page on Whimsy [1], and there are 4 red items that need to be done before graduation. I don’t know which of you are allowed to see this page, so I’ve pasted them below. Let’s start working on these. Licensing * No Software Grant and No IP Clearance Filed * No Release Yet/Missing ASF Copyright Headers on Source Code * No Release Yet/Binary has licensing issues Naming * No Podling Name Search on file [2] Julian [1] https://urldefense.us/v3/__https://whimsy.apache.org/roster/ppmc/sdap__;!!PvBDto6Hs4WbVuu7!PZFl086CsxgClAcGiS8QUAefUu8KRayt0vKwdm5kAKa-4ABd2Sc_HUPTYaHVpllBHvd5psVGvgJUgcVdPzztAg$ <https://urldefense.us/v3/__https://whimsy.apache.org/roster/ppmc/sdap__;!!PvBDto6Hs4WbVuu7!PZFl086CsxgClAcGiS8QUAefUu8KRayt0vKwdm5kAKa-4ABd2Sc_HUPTYaHVpllBHvd5psVGvgJUgcVdPzztAg$> [2] https://urldefense.us/v3/__https://incubator.apache.org/guides/names.html <https://urldefense.us/v3/__https://incubator.apache.org/guides/names.html>*name-search__;Iw!!PvBDto6Hs4WbVuu7!PZFl086CsxgClAcGiS8QUAefUu8KRayt0vKwdm5kAKa-4ABd2Sc_HUPTYaHVpllBHvd5psVGvgJUgcVBvK9hTw$ On Nov 17, 2023, at 1:16 PM, Huang, Thomas (US 398F) <thomas.hu...@jpl.nasa.gov.inva <mailto:thomas.hu...@jpl.nasa.gov.inva>LID> wrote: Yes indeed. It’s my 2023 Christmas wish. I know we are not big on marketing, but it might be a good idea to update the official website. Thanks Thomas ---- Thomas Huang Group Supervisor, Data Product Generation Software Instrument Software and Science Data Systems Jet Propulsion Laboratory, California Institute of Technology (818) 354-2747<tel:(818)%20354-2747> On Nov 17, 2023, at 1:07 PM, Nga Chung <nch...@apache.org <mailto:nch...@apache.org>> wrote: I think we're ready to graduate. We've come a long way and have learned to follow the Apache Way for software releases. We're also in the process of deciding on an official SDAP logo! Best, Nga On Thu, Nov 16, 2023 at 12:00 PM Riley Kuttruff <r...@apache.org <mailto:r...@apache.org>> wrote: As we work on the 1.2.0 release, I think we should begin our discussion of graduating SDAP in earnest. Over the past year or so, we've: - Successfully ran through the release process twice - Improved our code to be compliant with ASF rules, and now, hopefully, we should be free of any licensing issues with our dependencies - Further promoted SDAP within the scientific community through seminars, social media, integration with ongoing projects, etc What does the community think? Are we ready to graduate or do you feel there are any issues that are holding us back? Thanks, Riley
