Re: [DISCUSS] How to Increase Community Participation

[Julian Hyde]

One way to solve this is to think like a marketer. Who are the people who would 
like to use SDAP? Do they know that SDAP exists? Can you reach them where they 
are (e.g. at conferences or online forums)?

If they know that SDAP exists, what is presenting them from installing it and 
giving it a try? Would it help to include a a demo/tutorial/video for how to 
install the software and get started?

Is SDAP ’too big a meal’ to consume in one sitting? If so, are there smaller 
components that they can easily install that solve their current problems.

I attended Stepheny’s presentation at ApacheCon’22, and I found it an effective 
demonstration of that SDAP does. Keep doing things like that! I am not a target 
customer for SDAP, but I would imagine that demonstration would be compelling 
if presented to a conference of people managing geo/scientific data.

Julian



> On Aug 21, 2024, at 4:40 PM, Nga Chung  wrote:
> 
> Hi all,
> 
> During yesterday's monthly meeting, we had a great discussion on ideas
> for increasing participation from the community. As not everyone
> attends the monthly meeting, I'd like to also start this thread to
> seek ideas. You can find a summary of some of the ideas that came up
> during the meeting at
> https://cwiki.apache.org/confluence/display/SDAP/2024-08-20+SDAP+Monthly+Meeting
> 
> Thanks,
> Nga

Re: [REPORT] SDAP Board Report - July 2024

[Julian Hyde]

+1

Report looks good. Thanks for writing & submitting. Apologies for my late 
review.

Julian


> On Jul 2, 2024, at 9:27 PM, Nga Chung  wrote:
> 
> Hi all,
> 
> Below please find a draft of the SDAP board report. I plan to submit
> this on Tuesday, July 9.
> 
> Please let me know if you have any additions or corrections.
> 
> Thanks,
> Nga
> ---
> 
> ## Description:
> The mission of Apache SDAP is the creation and maintenance of software related
> to an integrated data analytic center for Big Science problems
> 
> ## Project Status:
> Current project status: New
> Issues for the board: none
> 
> ## Membership Data:
> Apache SDAP was founded 2024-04-16 (3 months ago)
> There are currently 21 committers and 15 PMC members in this project.
> The Committer-to-PMC ratio is 7:5.
> 
> Community changes, past quarter:
> - Grace Llewellyn was added to the PMC on 2024-06-23
> - Joe Roberts was added to the PMC on 2024-06-23
> - Grace Llewellyn was added as committer on 2024-06-19
> - Joe Roberts was added as committer on 2024-06-24
> 
> ## Project Activity:
> Most recent SDAP release was 1.3.0 on 2024-06-18. This marks the first release
> after TLP was established.
> 
> ## Community Health:
> 
> ### Mailing List
> Since last month, dev@sdap.apache.org had 2 new threads.
> 
> ### Contributors
> Since last month, the SDAP community has merged 8 PRs and
> created/updated 3 Jira issues.

Re: [REPORT] SDAP Board Report - May 2024

[Julian Hyde]

Thanks for writing this report, Nga.

I’m a bit surprised that there are 6 committers who are not PMC members. I 
thought that after graduation, anyone not in the initial PMC (approved by the 
motion to graduate the project) has no status. 

> On May 6, 2024, at 2:57 PM, Nga Chung  wrote:
> 
> Hi all,
> 
> Below please find a draft of the SDAP board report. I plan to submit
> this EOD tomorrow, May 7, 2024. Sorry for the short turnaround. For
> future reports, I will try to send a draft a week prior.
> 
> Please let me know if you have any additions or corrections.
> 
> Thanks,
> Nga
> ---
> 
> ## Description:
> The mission of Apache SDAP is the creation and maintenance of software related
> to an integrated data analytic center for Big Science problems
> 
> ## Project Status:
> Current project status: New
> Issues for the board: none
> 
> ## Membership Data:
> Apache SDAP was founded 2024-04-17 (20 days ago)
> There are currently 19 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 5:4.
> 
> Community changes, past quarter:
> - No new PMC members (project graduated recently).
> - No new committers were added.
> 
> ## Project Activity:
> SDAP community has not yet made a release after TLP was established.
> Most recent SDAP release was 1.2.0 on 2024-03-15
> 
> The community has discussed upcoming changes currently under
> development / in review.
> - 3D support: still in development, close to completion
> - Zarr support: ingester PR still open
> - CoG support: still in development
> 
> ## Community Health:
> 
> ### Mailing List
> 
> Since becoming a TLP, dev@sdap.apache.org had 3 new threads, 1 started
> by a non-committer asking for help with SDAP installation from
> quickstart guide.
> 
> ### Contributors
> 
> Since becoming a TLP, the SDAP community has merged 1 PR, affecting 3
> files, and created/updated 4 Jira issues.

Re: [DISCUSS] Move RTD files to their own repo

[Julian Hyde]

Something to consider is keeping the site and the code in the same repo, which 
is what Calcite does.

Calcite builds a site (hosted on Apache rather than RTD) based on a Git branch 
(called “site”) of our main repo. This allows us to update the site without 
making a release. 

But we sometimes want to hold back site updates until there is a release. For 
example, if a commit adds a Java interface we don’t want to add it to the 
generated javadoc until that interface appears in a release. But if we make 
someone a committer, we want that change to the site to appear immediately.

To achieve this, we have a CI job that cherry-picks from the main branch to the 
site branch, and part of the release process is to overwrite the site branch 
with the main branch.

This isn’t clearly better or worse than your proposed two-repo process. But one 
advantage is that you can have a single PR, and single commit, that updates the 
code and the associated documentation.

Julian


> On Apr 30, 2024, at 2:02 PM, Riley Kuttruff  wrote:
> 
> Hi everyone,
> 
> Our RTD pages [1][2] are currently built from the Nexus repo master branch. 
> Under our current branching strategy, this would require any updates, fixes, 
> improvements or additions to the RTD documentation be done through a full 
> release. Obviously, that is less than ideal.
> 
> I would suggest that we move those files to a new repo (eg, apache/sdap-docs) 
> which would allow quicker and easier updates to the docs.
> 
> What does the community think?
> 
> I will add this is kind of an important issue at the moment because a) our 
> docs builds are failing and b) an issue with the quickstart guide has been 
> found and needs fixing.
> 
> Thanks,
> Riley
> 
> [1] https://incubator-sdap-nexus.readthedocs.io/en/latest/
> [2] https://readthedocs.org/projects/incubator-sdap-nexus/

Re: Need access to reporter.apache.org

[Julian Hyde]

With help from the Incubator list, I managed to do it. I have
registered 1.2.0 (incubating) as released on 2024-03-15.

The link I used was https://reporter.apache.org/addrelease.html?incubator-sdap.

Julian

On Wed, Mar 20, 2024 at 7:20 AM Riley Kuttruff  wrote:
>
> I never received such an email for 1.0.0, idk if Nga got one for 1.1.0.
>
> Looking at what I can find, it seems that reporter.a.o is a tool to help 
> gather info on TLP releases for the PMC's report to the ASF Board [1]
>
> I could of course be wrong though.
>
> [1] https://www.apache.org/foundation/board/reporting#how
>
> On 2024/03/20 00:33:14 Julian Hyde wrote:
> > I know I need to do something to register the release. As an ASF member I 
> > know that I have the necessary karma to do this thing, and I’m happy to 
> > help. But I don’t recall what exactly I need to do. As RM, I think you 
> > should have received an email from Reporter?
> >
> > Julian
> >
> > > On Mar 19, 2024, at 3:24 PM, Stepheny Perez  wrote:
> > >
> > > Julian,
> > >
> > > I think I was mistaken in my previous email, instead of requesting access 
> > > to reporter.apache.org, I should have asked you to help us register the 
> > > 1.2.0 release on reporter. Is that something you can help us with?
> > >
> > > Thanks,
> > > Stepheny
> > >
> > > On 2024/03/15 21:47:16 Stepheny Perez wrote:
> > >> Hi Julian,
> > >>
> > >> As the release manager of 1.2.0, I believe I need access to 
> > >> reporter.apache.org so I can register the release. Can you grant me 
> > >> access so we can complete this release?
> > >>
> > >> Thank you!
> > >> Stepheny
> > >>
> >
> >

Re: Need access to reporter.apache.org

[Julian Hyde]

I know I need to do something to register the release. As an ASF member I know 
that I have the necessary karma to do this thing, and I’m happy to help. But I 
don’t recall what exactly I need to do. As RM, I think you should have received 
an email from Reporter?

Julian

> On Mar 19, 2024, at 3:24 PM, Stepheny Perez  wrote:
> 
> Julian,
> 
> I think I was mistaken in my previous email, instead of requesting access to 
> reporter.apache.org, I should have asked you to help us register the 1.2.0 
> release on reporter. Is that something you can help us with?
> 
> Thanks,
> Stepheny
> 
> On 2024/03/15 21:47:16 Stepheny Perez wrote:
>> Hi Julian,
>> 
>> As the release manager of 1.2.0, I believe I need access to 
>> reporter.apache.org so I can register the release. Can you grant me access 
>> so we can complete this release?
>> 
>> Thank you!
>> Stepheny
>> 

Re: [VOTE] Release Apache SDAP (incubating) 1.2.0-rc4

[Julian Hyde]

Sounds to me as if the ‘hiccup’ is just a bug and can be addressed by 
documenting it in the release notes (i.e. without needing a new RC). The bigger 
issue addressed by the release is the need to remove all category X 
dependencies. That said, I’m not the RM so it’s not my call.

+1 (binding)

Downloaded, checked hashes, NOTICE, DISCLAIMER, LICENSE, README, 
requirements.txt (dependencies) of the two artifacts, license headers.

Julian

> On Mar 6, 2024, at 12:55 PM, Riley Kuttruff  wrote:
> 
> Thanks, Nga. 
> 
> There's currently a small hiccup causing errors for the build for the 
> collection manager
> when run with the --no-cache option. This shouldn't be a blocker for anyone
> who has built the image before (if they use the cached layers; it's not a 
> step 
> involved with our code) or they could use a simple workaround.
> 
> I have a PR with a fix open. I'll defer to Stepheny if we want to do a new RC
> to address this or if we want to proceed as-is.
> 
> -Riley
> 
> On 2024/03/06 20:41:58 Nga Chung wrote:
>> Thank you, Riley and Stepheny, for getting this rc out with the
>> changes to use Poetry!
>> 
>> I verified the release as follows:
>> - Verified artifacts checksums and signatures
>> - Successfully built local images per build.rst
>> - Successfully ran through all steps in quickstart.rst and ran Jupyter 
>> notebook
>> 
>> +1 from me (binding)
>> 
>> Thanks,
>> Nga
>> 
>> On Tue, Mar 5, 2024 at 9:27 AM Stepheny Perez  wrote:
>>> 
>>> Hello everyone,
>>> 
>>> This is the vote to approve Apache SDAP (incubating) release candidate rc4 
>>> for version 1.2.0.
>>> 
>>> Changes made between previous candidate (rc3) and this one (rc4) are as 
>>> follows:
>>> - Updated SDAP to use Poetry package manager to more explicitly manage 
>>> dependencies and transitive dependencies. This was needed to ensure no GPL 
>>> license dependencies are used by the software.
>>> - Patch for domspurge helper script
>>> 
>>> Instructions for building docker images from source can be found here:
>>> https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc4/docs/build.rst
>>> Instructions for deploying locally to test can be found here:
>>> https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc4/docs/quickstart.rst
>>> The release files, including signatures, digests, etc. can be found at:
>>> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.2.0-rc4/
>>> 
>>> For convenience, the tags we built the release artifacts to be voted on
>>> from are 1.2.0-rc4:
>>> 
>>> - ingester:
>>> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.2.0-rc4
>>> - Commit: 5c116badfaf913734d017d41acc765ed3fd978a1
>>> 
>>> - nexus:
>>> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.2.0-rc4
>>> - Commit: 3fce31f08b9057db446036724e8bc62dd6d1560a
>>> 
>>> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are 
>>> voting on are as follows:
>>> 
>>> apache-sdap-ingester-1.2.0-incubating-src.tar.gz:
>>> 7301c54e765882c45f6efe4a06463b837ace62b6eea2ae5437113357466e52f1d905c3c9d46295f1b1058b9ecf5025942f8a89b2c53a1b0d6b69cd52a8890257
>>> 
>>> apache-sdap-nexus-1.2.0-incubating-src.tar.gz:
>>> 1a2907f9c36dbf0b4b25d54c095303ab0602fa9e0a9423deceae402ffd9a360e21ba832c3ea497d8eccbc6c91fedd2926b3b33181a14c22d50d0ec996282bc75
>>> 
>>> Release artifacts are signed with the following key:
>>> https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x2E8418801953621FAA322169D6F360887071C194
>>> 
>>> Please vote on releasing this package as Apache SDAP (incubating) 1.2.0-rc4.
>>> 
>>> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are 
>>> cast.
>>> 
>>> PLEASE NOTE: Do not reply with a vote from your work email as it can mangle 
>>> the links. To vote, go to 
>>> https://lists.apache.org/list.html?dev@sdap.apache.org, log in and send 
>>> your reply from there.
>>> 
>>> [ ] +1 Release this package as Apache SDAP (incubating) {version}
>>> [ ] +0 No opinion
>>> [ ] -1 Do not release this package because ...
>>> 
>>> Thank you,
>>> Stepheny
>> 

Re: [DISCUSS] Formal process for adding committers / PMC members

[Julian Hyde]

I've not seen any other project do that, but it would work.

The PMC chair would need to craft the wording of the emails: starting
a vote on the private list, announcing the result on the private list,
notice to the board, and inviting the contributor. They could do this
the first time that a vote occurs after graduation.

Would the individual have the right to ask for PMC membership at a
later date, without a PMC vote? Per [1] the invitation is sent only
after the board has been notified. So if they decline, all of the
necessary steps to make them a PMC member will already have been done.

Julian

[1] https://www.apache.org/dev/pmc.html#newpmc

On Thu, Feb 29, 2024 at 8:58 AM Frank Greguska  wrote:
>
> +1 to Nga's suggestion of default single tier including PMC membership with
> individual option to opt-out and receive committer-ship only.
>
> On Sun, Feb 25, 2024 at 4:18 PM Nga Chung  wrote:
>
> > Thanks Riley, Julian.
> >
> > I wonder if it would make sense to go with the one tier, but
> > optionally allow the invitee to opt out of PMC membership if they only
> > want committership. This way we keep it simple, but also don't scare
> > away potential contributors if PMC membership appears like more
> > responsibility (even if it really isn't) than they are ready for.
> >
> > Best,
> > Nga
> >
> > On Tue, Jan 16, 2024 at 3:43 PM Riley Kuttruff  wrote:
> > >
> > > I'm personally in favor of the two-tier solution as I think it would be
> > more suitable for
> > > growing our community. As Julian said it's a lower barrier to entry.
> > >
> > > On 2024/01/16 22:53:38 Julian Hyde wrote:
> > > > In favor of one tier (everyone who is a committer is on the PMC):
> > > >  * People perceive that there are two tiers to the project (and assume
> > that the PMC is doing something nefarious, when in fact it is usually,
> > quite correctly, doing very little).
> > > >  * Simplicity.
> > > >
> > > > In favor of two tiers (some committers are not PMC members):
> > > >  * The bar to committership is lowered. PMC members will give someone
> > the commit bit after just two or three code contributions, or some nice
> > work answering questions or giving conference talks.
> > > >
> > > > Julian
> > > >
> > > >
> > > > > On Jan 16, 2024, at 2:47 PM, Nga Chung  wrote:
> > > > >
> > > > > I also like the DISCUSS thread example for talking about future
> > > > > committers / PMC members.
> > > > >
> > > > > What is the pro / con of having committers who are not also a PMC
> > member?
> > > > >
> > > > > Thanks,
> > > > > Nga
> > > > >
> > > > > On Tue, Jan 16, 2024 at 7:13 AM Riley Kuttruff 
> > wrote:
> > > > >>
> > > > >> Hi Julian,
> > > > >>
> > > > >> That makes a lot of sense as a better alternative to the whole
> > nomination
> > > > >> process.
> > > > >>
> > > > >> On 2024/01/11 23:56:13 Julian Hyde wrote:
> > > > >>> I don't think the process needs to be very formal (e.g. included in
> > > > >>> the bylaws) or agreed before graduation. But it does need to be an
> > > > >>> organizational habit. This discussion thread, if it reaches
> > consensus,
> > > > >>> could be all the process we need.
> > > > >>>
> > > > >>> KVRocks' template email starts 'I nominate...'. I think it's
> > important
> > > > >>> to lower the bar to discussing new committers and PMC members, so
> > we
> > > > >>> can talk about people who "might be ready". Because often they
> > *are*
> > > > >>> ready. It could be a simple email to private@:
> > > > >>>
> > > > >>>> [DISCUSS] Alex Doe for committer
> > > > >>>>
> > > > >>>> I think Alex Doe has been  doing some good work recently[1]. They
> > have
> > > > >>>> made a couple of good PRs, one of which has been merged, and have
> > > > >>>> also been answering a lot of questions in the forums.
> > > > >>>>
> > > > >>>> Do you think Alex has earned enough merit, or should we wait a
> > couple of months?
> > > > >>>&g

Re: [DISCUSS] Formal process for adding committers / PMC members

[Julian Hyde]

In favor of one tier (everyone who is a committer is on the PMC):
 * People perceive that there are two tiers to the project (and assume that the 
PMC is doing something nefarious, when in fact it is usually, quite correctly, 
doing very little).
 * Simplicity.

In favor of two tiers (some committers are not PMC members):
 * The bar to committership is lowered. PMC members will give someone the 
commit bit after just two or three code contributions, or some nice work 
answering questions or giving conference talks.

Julian


> On Jan 16, 2024, at 2:47 PM, Nga Chung  wrote:
> 
> I also like the DISCUSS thread example for talking about future
> committers / PMC members.
> 
> What is the pro / con of having committers who are not also a PMC member?
> 
> Thanks,
> Nga
> 
> On Tue, Jan 16, 2024 at 7:13 AM Riley Kuttruff  wrote:
>> 
>> Hi Julian,
>> 
>> That makes a lot of sense as a better alternative to the whole nomination
>> process.
>> 
>> On 2024/01/11 23:56:13 Julian Hyde wrote:
>>> I don't think the process needs to be very formal (e.g. included in
>>> the bylaws) or agreed before graduation. But it does need to be an
>>> organizational habit. This discussion thread, if it reaches consensus,
>>> could be all the process we need.
>>> 
>>> KVRocks' template email starts 'I nominate...'. I think it's important
>>> to lower the bar to discussing new committers and PMC members, so we
>>> can talk about people who "might be ready". Because often they *are*
>>> ready. It could be a simple email to private@:
>>> 
>>>> [DISCUSS] Alex Doe for committer
>>>> 
>>>> I think Alex Doe has been  doing some good work recently[1]. They have
>>>> made a couple of good PRs, one of which has been merged, and have
>>>> also been answering a lot of questions in the forums.
>>>> 
>>>> Do you think Alex has earned enough merit, or should we wait a couple of 
>>>> months?
>>>> 
>>>> [1] https://github.com/apache/incubator-sdap-nexus/commits?author=alexdoe
>>> 
>>> In my experience, once there has been a good discussion, the voting
>>> process is very straightforward.
>>> 
>>> SDAP should also set a policy (if it doesn't have one) about whether
>>> it is possible to be a committer without being a PMC member.
>>> 
>>> Julian
>>> 
>>> On Wed, Jan 10, 2024 at 12:57 PM Riley Kuttruff  wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> While working through the maturity model, I noticed SDAP doesn't seem to 
>>>> have a documented, formal process for adding committers or PMC members (at 
>>>> least, none that I could find). I think we should make an effort to 
>>>> establish and ratify a process for this. I think the one outlined here [1] 
>>>> would be fine.
>>>> 
>>>> Let me know what you think or if you have any alternative processes in 
>>>> mind.
>>>> 
>>>> Thanks,
>>>> Riley
>>>> 
>>>> [1] https://kvrocks.incubator.apache.org/community/vote-a-core-developer/
>>> 

Re: [EXTERNAL] SDAP Monthly Meeting January 16 at 15:00 US/Pacific, 23:00 UTC

[Julian Hyde]

Since Thomas raises the point, I think it would be a bad idea to “discuss PMC 
process” at the meeting.

Riley started a thread on dev@ on an important topic — how to nominate and vote 
for committers and PMC members. We can agree on a process if people respond to 
the thread and we get to consensus. But right now only I have replied to the 
thread, so we have not achieved consensus, so the process has not been adopted.

As a reminder, the meeting cannot make decisions. It cannot even make the 
observation “There seemed to be general consensus for Riley’s proposal” if that 
observation is intended to be a decision.

I would urge whoever chairs the meeting to curtail discussion of such topics, 
and ask SDAP members to chime in on the dev list.

Julian



> On Jan 16, 2024, at 12:46 PM, Huang, Thomas (US 398F) 
>  wrote:
> 
> Sorry, I won't be able to join today's meeting. I guess we should discuss 
> about graduation status and PMC process. 
> 
> Public GitHub will be switching to require 2FA in March. Is SDAP affect?
> 
> https://github.blog/2023-03-09-raising-the-bar-for-software-security-github-2fa-begins-march-13/
> 
> 
> 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  
> 
> 
> 
> 
> On 1/15/24, 8:10 PM, "Nga Chung"  > wrote:
> 
> 
> Hi all,
> 
> 
> Just a friendly reminder that there is an SDAP monthly meeting tomorrow
> Tuesday, January 16 at 15:00 - 16:00 Pacific time.
> 
> 
> Join from the meeting link
> https://urldefense.us/v3/__https://jpl.webex.com/jpl/j.php?MTID=m6d205ee391099975ab22ae1b4a65df53__;!!PvBDto6Hs4WbVuu7!J5oYFTtLRmxZ9a3HJqDTW5UBAtwlIu4lYNkRWI4i263D90w6pUE157anxCSbUoAc3s1_XU8qScciG7_mZ5va62Q$
>  
> 
>  
> 
> 
> Join by meeting number
> Meeting number (access code): 2761 748 8734
> Meeting password: MjdFissq569
> 
> 
> Best,
> Nga
> 
> 
> 

Re: [DISCUSS] Formal process for adding committers / PMC members

[Julian Hyde]

I don't think the process needs to be very formal (e.g. included in
the bylaws) or agreed before graduation. But it does need to be an
organizational habit. This discussion thread, if it reaches consensus,
could be all the process we need.

KVRocks' template email starts 'I nominate...'. I think it's important
to lower the bar to discussing new committers and PMC members, so we
can talk about people who "might be ready". Because often they *are*
ready. It could be a simple email to private@:

> [DISCUSS] Alex Doe for committer
>
> I think Alex Doe has been  doing some good work recently[1]. They have
> made a couple of good PRs, one of which has been merged, and have
> also been answering a lot of questions in the forums.
>
> Do you think Alex has earned enough merit, or should we wait a couple of 
> months?
>
> [1] https://github.com/apache/incubator-sdap-nexus/commits?author=alexdoe

In my experience, once there has been a good discussion, the voting
process is very straightforward.

SDAP should also set a policy (if it doesn't have one) about whether
it is possible to be a committer without being a PMC member.

Julian

On Wed, Jan 10, 2024 at 12:57 PM Riley Kuttruff  wrote:
>
> Hi all,
>
> While working through the maturity model, I noticed SDAP doesn't seem to have 
> a documented, formal process for adding committers or PMC members (at least, 
> none that I could find). I think we should make an effort to establish and 
> ratify a process for this. I think the one outlined here [1] would be fine.
>
> Let me know what you think or if you have any alternative processes in mind.
>
> Thanks,
> Riley
>
> [1] https://kvrocks.incubator.apache.org/community/vote-a-core-developer/

Re: [QUESTION] Handling of licensing issues for dependencies of dependencies

[Julian Hyde]

I don’t have a good answer to that. In the java world, we use maven or gradle, 
and there may be plugins to assert that the license is acceptable for an ASF 
project (and remains acceptable each time the dependency is upgrade), but I’m 
not fully aware of those plugins. For other languages my knowledge is near zero.

This would be a good question to ask on the incubator list.

Julian


> On Jan 9, 2024, at 10:11 AM, Riley Kuttruff  wrote:
> 
> I was performing a more thorough check of our dependencies in preparation of 
> opening graduation discussions with the Incubator PMC and found at least one 
> package that, while not directly used in the code, is installed as a 
> dependency of multiple top-level dependencies that is LGPL licensed. The 
> dependencies that rely on this are themselves not a license issue (BSD-3 & 
> MIT licenses). How is this situation usually handled? 
> 
> I also found a package that has a license that isn't listed on the 3rd party 
> licenses page: HPND [1][2] which, from what I can tell, is similar to the 
> BSD-3 or MIT licenses, though I just wanted to double-check on that...
> 
> [1] https://github.com/python-pillow/Pillow/blob/main/LICENSE
> [2] https://en.wikipedia.org/wiki/Historical_Permission_Notice_and_Disclaimer

Re: [VOTE] Graduate Apache SDAP (Incubating) as a Top Level Project

[Julian Hyde]

+1 (binding)

On Thu, Dec 21, 2023 at 12:07 PM Riley Kuttruff  wrote:
>
> Hi everyone,
>
> After a little over 6 years in the ASF Incubator, we now would like to ask 
> the community
> to vote on graduating SDAP to a Top Level Project.
>
> The following 13 people have elected to join the Apache SDAP PMC upon 
> graduation:
>
> - Nga Thien Chung (chair)
> - Edward M Armstrong
> - Thomas Cram
> - Frank Greguska
> - Thomas Huang
> - Julian Hyde
> - Joseph C. Jacob
> - Jason Kang
> - Riley Kuttruff
> - Thomas G Loubrieu
> - Kevin Marlis
> - Stepheny Perez
> - Wai Linn Phyo
>
> All final requirements listed in our DISCUSS thread [1][2][3] (The threading 
> on the
> site broke) have been addressed successfully.
>
> The following is the proposed graduation resolution:
>
> Establish the Apache SDAP Project
>
> 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.
>
> 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; 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:
>
> - Edward M Armstrong 
> - Nga Thien Chung 
> - Thomas Cram 
> - Frank Greguska 
> - Thomas Huang 
> - Julian Hyde 
> - Joseph C. Jacob 
> - Jason Kang 
> - Riley Kuttruff 
> - Thomas G Loubrieu 
> - Kevin Marlis 
> - Stepheny Perez 
> - Wai Linn Phyo 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nga Thien Chung
> 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.
>
> ~~
>
> If this vote passes, we'll proceed to discussion and voting on the IPMC's
> general@ mailing list.
>
> Please vote on graduating Apache SDAP (Incubating) as a Top Level
> Project.
>
> The vote will remain open for at least 72 hours and passes with a majority
> of at least 3 binding +1 PPMC votes.
>
> [] +1: Yes, graduate Apache SDAP (Incubating) as a Top Level Project
> [] 0: I have no opinion
> [] -1: Apache SDAP (Incubating) is not ready to graduate because...
>
> [1] https://lists.apache.org/thread/vjwjmp0h2f22dv423h262cvdg5x7jl03
> [2] https://lists.apache.org/thread/m9vqwv23jdsofwgmhgxg25f5l1v2j7nz
> [3] https://lists.apache.org/thread/4o1qjsk2cly2ppxcsmm2swzd6pcg3lxj
>
> Thank you,
> Riley

Re: SDAP Monthly Meeting December 19 at 15:00 US/Pacific, 23:00 UTC

[Julian Hyde]

Thank you, Nga!

> On Dec 19, 2023, at 3:41 PM, Nga Chung  wrote:
> 
> Hi all,
> 
> Meeting minutes from today's meeting can be found here:
> https://cwiki.apache.org/confluence/display/SDAP/2023-12-19+SDAP+Monthly+Meeting
> 
> Thanks,
> Nga
> 
> On Mon, Dec 18, 2023 at 9:13 PM Nga Chung  wrote:
>> 
>> Hi all,
>> 
>> Just a friendly reminder that there is an SDAP monthly meeting tomorrow
>> Tuesday, December 19 at 15:00 - 16:00 Pacific time.
>> 
>> Join from the meeting link
>> https://jpl.webex.com/jpl/j.php?MTID=m6d205ee391099975ab22ae1b4a65df53
>> 
>> Join by meeting number
>> Meeting number (access code): 2761 748 8734
>> Meeting password: MjdFissq569
>> 
>> Best,
>> Nga

Re: [EXTERNAL] [DISCUSS] SDAP Graduation

[Julian Hyde]

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  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  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://whimsy.apache.org/roster/ppmc/sdap
>>>> [2] https://incubator.apache.org/guides/names.html#name-search 
>>>> 
>>>>> On Nov 17, 2023, at 1:16 PM, Huang, Thomas (US 398F) 
>>>>>  wrote:
>>>>> 
>>>>> Yes indeed. It’s my 2023 Christmas 

Re: [EXTERNAL] [DISCUSS] SDAP Graduation

[Julian Hyde]

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  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://whimsy.apache.org/roster/ppmc/sdap
>> [2] https://incubator.apache.org/guides/names.html#name-search 
>> 
>>> On Nov 17, 2023, at 1:16 PM, Huang, Thomas (US 398F) 
>>>  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
>>> 
>>> On Nov 17, 2023, at 1:07 PM, Nga Chung  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  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
>> 
>> 

Re: [EXTERNAL] [DISCUSS] SDAP Graduation

[Julian Hyde]

You should document what you did, and what you discovered, in the Jira case. 
Evidence that you have searched and found nothing will help get this to 
approval. SDAP is an unusual name, so it’s no surprise to me that there are few 
clashes.

> On Dec 4, 2023, at 9:08 AM, Riley Kuttruff  wrote:
> 
> Hey Julian,
> 
> I'm also starting up with a Podling Name Search, though I'm having 
> difficulties with the USPTO search. I followed the syntax documented in [1] 
> but was receiving syntax errors. I instead tried a field tag search for 
> 'CM:SDAP' and 'CM:"Science Data Analytics Platform"' with no results, though 
> I'm not certain if that's adequate. I also did searched: Canada trademarks, 
> WIPO and EUIPO with some live matches for SDAP, but none that seem to 
> conflict with us.
> 
> [1] https://www.apache.org/foundation/marks/naming.html#regsearch
> 
> 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://whimsy.apache.org/roster/ppmc/sdap
>> [2] https://incubator.apache.org/guides/names.html#name-search 
>> 
>>> On Nov 17, 2023, at 1:16 PM, Huang, Thomas (US 398F) 
>>>  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
>>> 
>>> On Nov 17, 2023, at 1:07 PM, Nga Chung  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  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
>> 
>> 

Re: [EXTERNAL] [DISCUSS] SDAP Graduation

[Julian Hyde]

Thomas,

Thanks for looking into it. Sorry it was a false alarm. It’s likely that those 
red flags exist because the incubation metadata is out of date. 

It’s worthwhile to spend the time updating the metadata. I believe the 
following are the important files:
 * https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml 
 * 
https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/sdap.xml
 
 * https://incubator.apache.org/projects/sdap.html 

As far as I can tell, the name search still needs to be done. Maybe others too.

Julian



> On Dec 2, 2023, at 10:39 AM, Huang, Thomas (US 398F) 
>  wrote:
> 
> Hi Julian,
> 
> I searched my old email archive and found the original Software Grant I 
> submitted to secret...@apache.org <mailto:secret...@apache.org> on October 
> 26, 2017. I received the attached response from Apache conforming receiving 
> the document and has been filed. I also attached the original signed SGA 
> here. Please let me know if we need to submit additional information.
> 
> 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  
> 
> 
> 
> 
> On 12/1/23, 2:08 PM, "Julian Hyde"  <mailto:jhyde.apa...@gmail.com> <mailto:jhyde.apa...@gmail.com>> 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!N4d7YJ0dzoPK0cgdeZWRIOWykSSnCF7-eZ5vwnxREAOjGFTl6dki4kapTMlYli0S8v5tOEuuXyVaPpo9AplNP404lX17SQ$<https://urldefense.us/v3/__https://whimsy.apache.org/roster/ppmc/sdap__;!!PvBDto6Hs4WbVuu7!N4d7YJ0dzoPK0cgdeZWRIOWykSSnCF7-eZ5vwnxREAOjGFTl6dki4kapTMlYli0S8v5tOEuuXyVaPpo9AplNP404lX17SQ$>
>  
> [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!N4d7YJ0dzoPK0cgdeZWRIOWykSSnCF7-eZ5vwnxREAOjGFTl6dki4kapTMlYli0S8v5tOEuuXyVaPpo9AplNP437rLbTvg$
>  
> 
> 
>> On Nov 17, 2023, at 1:16 PM, Huang, Thomas (US 398F) 
>> mailto: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
>> 
>> On Nov 17, 2023, at 1:07 PM, Nga Chung > <mailto: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 > <mailto: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
> 
> 
> 
> 
> 
> 

Re: [EXTERNAL] [DISCUSS] SDAP Graduation

[Julian Hyde]

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://whimsy.apache.org/roster/ppmc/sdap
[2] https://incubator.apache.org/guides/names.html#name-search 

> On Nov 17, 2023, at 1:16 PM, Huang, Thomas (US 398F) 
>  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
> 
> On Nov 17, 2023, at 1:07 PM, Nga Chung  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  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

Re: [VOTE] Release Apache SDAP (incubating) 1.2.0-rc3

[Julian Hyde]

+1 (binding)

Downloaded; checked hashes; checked LICENSE, NOTICE, DISCLAIMER; verified that 
chardet has gone.

Julian


Stepheny, I assume you’re ‘+1’ but you should vote explicitly.



> On Nov 28, 2023, at 10:20 AM, Riley Kuttruff  wrote:
> 
> I verified: 
> - Release commits 
> - Artifacts have incubating in names
> - Artifact signatures & checksums 
> - Images built successfully 
> - chardet is not present in any of the images
> - Components work successfully locally and in cloud deployment
> 
> +1 (binding)
> 
> -Riley
> 
> On 2023/11/28 00:11:15 Stepheny Perez wrote:
>> Hello everyone,
>> 
>> This is the vote to approve Apache SDAP (incubating) release candidate rc3 
>> for version 1.2.0.
>> 
>> Changes made between previous candidate (rc2) and this one (rc3) are as 
>> follows:
>> 
>> - Removed chardet dependency from all components
>> - Upgraded cassandra helm chart to version 9.1.7
>> - Upgraded cassandra protocol version from 3 to 4
>> - Improved documentation
>> 
>> Instructions for building docker images from source can be found here:  
>> https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc3/docs/build.rst 
>>  
>> Instructions for deploying locally to test can be found here:  
>> https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc3/docs/quickstart.rst
>>
>> The release files, including signatures, digests, etc. can be found at:  
>> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.2.0-rc3/
>> 
>> For convenience, the tags we built the release artifacts to be voted on  
>> from are 1.2.0-rc3:  
>> 
>> - ingester:  
>> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.2.0-rc3
>> - Commit: dc36ff6fc163f170759a1c1b49a7be867d15f6ab  
>> 
>> - nexus:  
>> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.2.0-rc3
>> - Commit: 56a841c63a96d66dcca780249d5bb194a8ec32be  
>> 
>> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are 
>> voting on are as follows:  
>> 
>> apache-sdap-ingester-1.2.0-incubating-src.tar.gz:  
>> a49401178f631ea50dfaad0f2c4627c7f9f373393db7594de388ce8abdc0ada699ebc5dcb843d41a63af2e5572ca3aeeeb5cf2de7747c0173b07ff4a00420f81
>>   
>> 
>> apache-sdap-nexus-1.2.0-incubating-src.tar.gz:  
>> 09d50fe899979c962f023e033ea7a8c8c0acdb00bbfbe03a16d6810e0a34744f4106a130d202b5d4c4a1bd20cb3c12851e2f7752286ca1e9f5b117c7fcfe2f43
>>   
>> 
>> Release artifacts are signed with the following key:  
>> https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x2E8418801953621FAA322169D6F360887071C194
>> 
>> Please vote on releasing this package as Apache SDAP (incubating) 1.2.0.  
>> 
>> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are 
>> cast.  
>> 
>> PLEASE NOTE: Do not reply with a vote from your work email as it can mangle 
>> the links. To vote, go to 
>> https://lists.apache.org/list.html?dev@sdap.apache.org, log in and send your 
>> reply from there.  
>> 
>> [ ] +1 Release this package as Apache SDAP (incubating) 1.2.0  
>> [ ] +0 No opinion  
>> [ ] -1 Do not release this package because ...  
>> 
>> Thank you,  
>> Stepheny
>> 

Re: Summary of SDAP Monthly Meeting 2023-11-29

[Julian Hyde]

Thank you for this summary. If it’s not a policy to send a summary after every 
monthly meeting, could we make it so?

As you know, the project should not be making decisions at meetings. 
Discussions are fine, but sometimes there is no clear line between discussions 
and decisions. So, a good pattern is for the meeting to assign to people the 
task of starting an online discussion thread for each non-trivial topic.

I saw that you did that with the question about the PMC Chair. And the 
discussion/vote about the logo was excellent. Let’s have more of that.

Julian


> On Nov 29, 2023, at 8:20 AM, Riley Kuttruff  wrote:
> 
> Hi everyone,
> 
> Here is a summary of the topics discussed in yesterday's meeting:
> 
> - Graduation: DISCUSS thread needs more engagement
>  - QUESTION: When it's time to graduate, how do we select a PMC chair & what 
> are their responsibilities?
> - 1.2.0 release status: rc2 failed IPMC vote due to dependency license 
> issues, rc3 resolves those issues and is currently up for PPMC vote
> - Website updates:
>  - Currently updating the website ahead to graduation
>  - Trying to feature both publications about SDAP and public projects that 
> are powered by SDAP
>  - Minor updates for now, with some PPMC members volunteering to work on a 
> more thorough redesign 
> - SDAP @ AGU
>  - SDAP members planning to attend and give a demo at AGU went over their 
> plans for their demo for feedback & suggestions
> 
> Meeting notes can be found here: 
> https://cwiki.apache.org/confluence/display/SDAP/2023-11-28+Meeting+notes
> 
> Thanks,
> Riley

Re: [QUESTION] For graduation: PMC Chair

[Julian Hyde]

The link says it very well. The main job of the Chair (aka VP) is to 
communicate with the board. They don’t have any greater power than any other 
PMC member, although they “hold the microphone” and so can help start and shape 
the discussions.

Typically one, two or three candidates volunteer, or are nominated. And then 
there’s a vote, which is not very contentious because no one *really* wants to 
do the job. :)

In my opinion, Nga, Riley and Stepheny (in no particular order) would each do 
an excellent job.

The vote is often on the private@ list but, in Calcite at least, we decided to 
call for nominations on the dev@ list.

A few projects have a policy where the chair stands down after a 12 month term 
and holds a new election (often on the anniversary of graduation). In my 
opinion this works well, because it brings in new blood, and prevents one 
person being seen as the ‘benevolent dictator for life’ (BDFL).

Julian


> On Nov 29, 2023, at 6:59 AM, Riley Kuttruff  wrote:
> 
> At today's monthly meeting, there were 2 questions brought up regarding the 
> role of PMC chair upon graduation:
> 
> 1. What is the process for selecting the proposed chair? Is it a vote held on 
> the mailing list or is it a position volunteered for by anyone on the PPMC?
> 
> 2. What role / responsibilities does the PMC chair take on? Is there anything 
> beyond what is listed at [1]?
> 
> We're hoping to get to a vote on graduation soon, so knowing this would be 
> very helpful, thanks!
> 
> -Riley
> 
> [1] https://apache.org/foundation/governance/pmcs.html#legal

[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789579#comment-17789579
 ] 

Julian Hyde commented on SDAP-491:
--

Good points. Thank you, [~curcuru]!

> Adopt an official logo for SDAP and add it to the website
> -
>
> Key: SDAP-491
> URL: https://issues.apache.org/jira/browse/SDAP-491
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Riley Kuttruff
>Assignee: Riley Kuttruff
>Priority: Major
> Attachments: SDAP logo Apache TM.png, SDAP logo bold Apache TM.png, 
> SDAP logo bold.png, SDAP logo.png, more_sdap_logos.jpg, 
> sdap_logo_finalists.png
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788874#comment-17788874
 ] 

Julian Hyde commented on SDAP-491:
--

[~rkk], No, the project vote just sets broad direction (and demonstrates 
consensus) and execution is left to the discretion of people doing the work.

> Adopt an official logo for SDAP and add it to the website
> -
>
> Key: SDAP-491
> URL: https://issues.apache.org/jira/browse/SDAP-491
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Riley Kuttruff
>Assignee: Riley Kuttruff
>Priority: Major
> Attachments: SDAP logo Apache TM.png, SDAP logo bold Apache TM.png, 
> SDAP logo bold.png, SDAP logo.png, more_sdap_logos.jpg, 
> sdap_logo_finalists.png
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788871#comment-17788871
 ] 

Julian Hyde commented on SDAP-491:
--

The vote is currently under way, but both of the finalists use the 'worm' font 
for the TM mark. It is conventional to use an ordinary sans serif font for the 
TM (see 
[examples|https://brandmarketingblog.com/articles/design/logos-with-tm/]) and 
we should fix that before the logo is finalized.

I don't know what are the branding best practices but I suspect an SVG version 
and/or a version with transparent background would be useful. 

> Adopt an official logo for SDAP and add it to the website
> -
>
> Key: SDAP-491
> URL: https://issues.apache.org/jira/browse/SDAP-491
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Riley Kuttruff
>Assignee: Riley Kuttruff
>Priority: Major
> Attachments: SDAP logo Apache TM.png, SDAP logo bold Apache TM.png, 
> SDAP logo bold.png, SDAP logo.png, more_sdap_logos.jpg, 
> sdap_logo_finalists.png
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [VOTE] Choose SDAP's official logo

[Julian Hyde]

I vote for logo B.

Julian



> On Nov 22, 2023, at 11:09 AM, Joseph C. Jacob  wrote:
> 
> I vote for logo B.
> 
> Thanks,
> 
> Joe
> 
> On 2023/11/22 18:25:17 Riley Kuttruff wrote:
>> Hi everyone,
>> 
>> After the discussion, we have 2 clear front-runners: 5 and 3.
>> 
>> So now we will start the final vote on which to choose.
>> 
>> The candidates are here: 
>> https://issues.apache.org/jira/secure/attachment/13064618/sdap_logo_finalists.png
>> 
>> Please vote in this thread for the logo you wish to be SDAP's logo:
>> 
>> [ ] A: I prefer logo A
>> [ ] B: I prefer logo B
>> 
>> Quick reminder to please respond via your @apache.org email if possible. 
>> 
>> This vote will remain open for a week (since it's a holiday weekend) or 
>> until we receive >= 6 votes not resulting in a tie, whichever is first.
>> 
>> Thanks!
>> Riley
>> 

Re: [EXTERNAL] [DISCUSS] SDAP Logo Candidates

[Julian Hyde]

My favorites are 4, 5.

(Bringing back the Nasa worm font was a brilliant idea.)


> On Nov 21, 2023, at 12:04 PM, Kang, Jason (US 398F) 
>  wrote:
> 
> P.S. For 3 and 5, there needs to be some white space separating top hexagon 
> and bottom hexagon.
> 
> From: Kang, Jason (US 398F) 
> Date: Tuesday, November 21, 2023 at 12:02 PM
> To: dev@sdap.apache.org 
> Subject: Re: [EXTERNAL] Re: [DISCUSS] SDAP Logo Candidates
> I prefer simplicity so my votes are: 3, 5.
> 
> Thanks,
> Jason K.
> 
> From: Kevin Marlis 
> Date: Tuesday, November 21, 2023 at 11:45 AM
> To: dev@sdap.apache.org 
> Subject: Re: [EXTERNAL] Re: [DISCUSS] SDAP Logo Candidates
> My vote is for 4 as I think it is the most unique logo and also abstractly 
> conveys what SDAP does in a visually appealing way.
> 
> My second and third choices are for 3 and 5 respectively. I understand the 
> thought behind the left hexagon representing expandability, but visually the 
> inconsistent spacing between the three hexagons looks unintentional. Maybe 
> that's getting too nitpick-y, but it is something that caught my eye.
> 
> Thanks,
> 
> Kevin
> 
> On 2023/11/21 19:26:54 "Joseph C. Jacob" wrote:
>> My top 3 in preference order are: 5 (best), 3, 4
>> 
>> Thanks,
>> 
>> Joe
>> 
>> On 2023/11/21 19:21:29 "Loubrieu, Thomas G (US 398F)" wrote:
>>> Hello,
>>> 
>>> My top 3 is: 5, 3, 4
>>> 
>>> Thanks,
>>> 
>>> Thomas
>>> 
>>> From: Llewellyn, Grace (US 398H) 
>>> Date: Tuesday, November 21, 2023 at 1:19 PM
>>> To: dev@sdap.apache.org 
>>> Subject: Re: [EXTERNAL] Re: [DISCUSS] SDAP Logo Candidates
>>> My top choices are 3, 5, 4
>>> 
>>> Thanks,
>>> Grace
>>> 
>>> --
>>> Grace Llewellyn
>>> NASA Jet Propulsion Laboratory
>>> Science Apps & Data Interaction Engineer | 398H
>>> 
>>> From: Thomas Huang 
>>> Date: Tuesday, November 21, 2023 at 10:16 AM
>>> To: dev@sdap.apache.org 
>>> Subject: [EXTERNAL] Re: [DISCUSS] SDAP Logo Candidates
>>> Here are my votes: 5 (C) is my first choice - I like the NASA worm red; 3 
>>> (A) is my second choice - simple and clean
>>> 
>>> thanks
>>> 
>>> Thomas.
>>> 
>>> On 2023/11/21 18:10:24 Nga Chung wrote:
>>>> My top choices are 5 and 4.
>>>> 
>>>> Thanks,
>>>> Nga
>>>> 
>>>> 
>>>> On Tue, Nov 21, 2023 at 9:27 AM Julian Hyde  wrote:
>>>>> 
>>>>> My top choices are 4 and 5.
>>>>> 
>>>>> I suggest that the VOTE thread is a “runoff” between the 2 logos that 
>>>>> occur most often in people’s favorites. (Or 3 if there are no 2 clear 
>>>>> leaders.)
>>>>> 
>>>>>> On Nov 21, 2023, at 9:20 AM, Riley Kuttruff  wrote:
>>>>>> 
>>>>>> Hi everyone,
>>>>>> 
>>>>>> Here are the current candidates for SDAP's logo. Please respond to this 
>>>>>> thread with your top choices starting with your most preferred:
>>>>>> 
>>>>>> 1: 
>>>>>> https://urldefense.us/v3/__https://issues.apache.org/jira/secure/attachment/13064497/SDAP*20logo*20Apache*20TM.png__;JSUl!!PvBDto6Hs4WbVuu7!JdIKWLBkvjjGX6q3moA9X7d9mEDec7Sihh6yaIYzQ5Hs7Bkqa5i8xOApRl1YSI9AdfwvtZHaqk_WPtqhguykvpYL$<https://urldefense.us/v3/__https:/issues.apache.org/jira/secure/attachment/13064497/SDAP*20logo*20Apache*20TM.png__;JSUl!!PvBDto6Hs4WbVuu7!JdIKWLBkvjjGX6q3moA9X7d9mEDec7Sihh6yaIYzQ5Hs7Bkqa5i8xOApRl1YSI9AdfwvtZHaqk_WPtqhguykvpYL$><https://urldefense.us/v3/__https:/issues.apache.org/jira/secure/attachment/13064497/SDAP*20logo*20Apache*20TM.png__;JSUl!!PvBDto6Hs4WbVuu7!JdIKWLBkvjjGX6q3moA9X7d9mEDec7Sihh6yaIYzQ5Hs7Bkqa5i8xOApRl1YSI9AdfwvtZHaqk_WPtqhguykvpYL$%3chttps:/urldefense.us/v3/__https:/issues.apache.org/jira/secure/attachment/13064497/SDAP*20logo*20Apache*20TM.png__;JSUl!!PvBDto6Hs4WbVuu7!JdIKWLBkvjjGX6q3moA9X7d9mEDec7Sihh6yaIYzQ5Hs7Bkqa5i8xOApRl1YSI9AdfwvtZHaqk_WPtqhguykvpYL$%3e><https://urldefense.us/v3/__https:/issues.apache.org/jira/secure/attachment/13064497/SDAP*20logo*20Apache*20TM.png__;JSUl!!PvBDto6Hs4WbVuu7!JdIKWLBkvjjGX6q3moA9X7d9mEDec7Sihh6yaIYzQ5Hs7Bkqa5i8xOApRl1YSI9AdfwvtZHaqk_WPtqhguykvpYL$%3chttps:/urldefense.us/v3/__https:/issues.apache.org/jira/secure/attachment/13064497/SDAP*20logo*20Apache*20TM.png__;JSUl!!PvBDto6Hs4WbVuu7!JdIKWLBkvjjGX6q3moA9X7d9mEDec7Sihh6yaIYzQ5Hs7Bkqa5i8xOApRl1YSI9AdfwvtZHaqk_WPtqhguykvpYL$%3e%3chttps:/

Re: [EXTERNAL] SDAP logo consideration

[Julian Hyde]

Let’s move discussion to other thread. I think you and I have similar 
instincts; we need a clear choice to vote on. 

> On Nov 21, 2023, at 9:26 AM, Riley Kuttruff  wrote:
> 
> Hey Julian,
> 
> I just started a discussion thread to rank preferences on the various 
> candidates with the idea of holding a vote to ratify the favorite. We can 
> replace that with this kind of vote if it's easier; I went for a two-step 
> process as I was under the impression formal votes were more yes/no than 
> multiple-option.
> 
>> On 2023/11/21 17:21:37 Julian Hyde wrote:
>> What are the options to vote on? I presume A, B, C in more-sdap-logos.jpg, 
>> plus the original proposal (in any of its variants, with and without Apache 
>> and TM).
>> 
>> If so, let’s convert to a simple voting form
>> 
>> [   ] logo A
>> [   ] logo B
>> [   ] logo C
>> [   ] original
>> 
>> and launch a [VOTE] thread. If people write in extra preferences - which 
>> they are welcome to do - then we may need a run-off vote. Democracy is messy.
>> 
>> Julian
>> 
>> 
>> 
>>>> On Nov 21, 2023, at 9:06 AM, Huang, Thomas (US 398F) 
>>>>  wrote:
>>> 
>>> Hi community,
>>> 
>>> There have three professionally designed SDAP logos (see 
>>> more_sdap_logos.jpg) ready for your vote.
>>> 
>>> https://issues.apache.org/jira/browse/SDAP-491
>>> 
>>> Logo meaning
>>> - SDAP was originated from NASA's research in private cloud computing. It 
>>> would be appropriate to include something that represents its NASA 
>>> heritage, hence the use of the NASA worm font (options A and C)
>>> - Hexagon is a symbol for strength. It is the building block of honeycombs.
>>> - Honeycomb represents expandable storage. The left hexagon in options A 
>>> and C represent expandability (moving to connect with other hexagons).
>>> - A honeycomb also provides a place for parallel operations.
>>> - The use of different color represents inclusive and diversity.
>>> 
>>> We would like to start using our selected new logo at the December AGU 
>>> event in San Francisco. Voting is now open. Please cast your vote by this 
>>> Saturday 11/25/2023.
>>> 
>>> 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 
>>> 
>>> 
>>> 
>>> 
>>> On 11/19/23, 3:53 PM, "Huang, Thomas (US 398F)" >> <mailto:thomas.hu...@jpl.nasa.gov>> wrote:
>>> 
>>> 
>>> Great ideas, Thomas L. I am added your suggestion to the list for the 
>>> community to choose from. I should have a revision early this week.
>>> 
>>> 
>>> 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 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> On 11/18/23, 4:07 PM, "Loubrieu, Thomas G (US 398F)" 
>>>> >>> <mailto:thomas.g.loubr...@jpl.nasa.gov.inva> 
>>>> <mailto:thomas.g.loubr...@jpl.nasa.gov.inva 
>>>> <mailto:thomas.g.loubr...@jpl.nasa.gov.inva>>LID> wrote:
>>> 
>>> 
>>> 
>>> 
>>> Hi,
>>> 
>>> 
>>> 
>>> 
>>> That looks great, I like the colors and the overall idea of logo with these 
>>> hexagonal cells connected.
>>> 
>>> 
>>> 
>>> 
>>> I was thinking, for the readibility of SDAP acronym that would be better to 
>>> have all the letters on one horizontal line.
>>> One idea could be to keep 2 hexagonal cells, the one filled with the 
>>> colored sub cells, and one on the top left with the full acronym SDAP in a 
>>> single line. We would remove the 3 other cells. It feels to me that that 
>>> would also lighten the overall design so that it can more easily be used in 
>>> smaller sizes.
>>> 
>>> 
>>> 
>>> 
>>> Thanks,
>>> 
>>> 
>>> 
>>>

Re: [DISCUSS] SDAP Logo Candidates

[Julian Hyde]

My top choices are 4 and 5. 

I suggest that the VOTE thread is a “runoff” between the 2 logos that occur 
most often in people’s favorites. (Or 3 if there are no 2 clear leaders.)

> On Nov 21, 2023, at 9:20 AM, Riley Kuttruff  wrote:
> 
> Hi everyone,
> 
> Here are the current candidates for SDAP's logo. Please respond to this 
> thread with your top choices starting with your most preferred:
> 
> 1: 
> https://issues.apache.org/jira/secure/attachment/13064497/SDAP%20logo%20Apache%20TM.png
> 2: 
> https://issues.apache.org/jira/secure/attachment/13064496/SDAP%20logo%20bold%20Apache%20TM.png
> 3, 4, 5: 
> https://issues.apache.org/jira/secure/attachment/13064587/more_sdap_logos.jpg
> 
> My top choices would be: 5, 4, 3
> 
> Once we determine the community's favorite, we can do a quick vote to ratify 
> it!
> 
> Thanks,
> Riley

Re: [EXTERNAL] SDAP logo consideration

[Julian Hyde]

What are the options to vote on? I presume A, B, C in more-sdap-logos.jpg, plus 
the original proposal (in any of its variants, with and without Apache and TM). 

If so, let’s convert to a simple voting form

 [   ] logo A
 [   ] logo B
 [   ] logo C
 [   ] original

and launch a [VOTE] thread. If people write in extra preferences - which they 
are welcome to do - then we may need a run-off vote. Democracy is messy. 

Julian



> On Nov 21, 2023, at 9:06 AM, Huang, Thomas (US 398F) 
>  wrote:
> 
> Hi community,
> 
> There have three professionally designed SDAP logos (see more_sdap_logos.jpg) 
> ready for your vote.
> 
> https://issues.apache.org/jira/browse/SDAP-491
> 
> Logo meaning
> - SDAP was originated from NASA's research in private cloud computing. It 
> would be appropriate to include something that represents its NASA heritage, 
> hence the use of the NASA worm font (options A and C)
> - Hexagon is a symbol for strength. It is the building block of honeycombs.
> - Honeycomb represents expandable storage. The left hexagon in options A and 
> C represent expandability (moving to connect with other hexagons).
> - A honeycomb also provides a place for parallel operations.
> - The use of different color represents inclusive and diversity.
> 
> We would like to start using our selected new logo at the December AGU event 
> in San Francisco. Voting is now open. Please cast your vote by this Saturday 
> 11/25/2023.
> 
> 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 
> 
> 
> 
> 
> On 11/19/23, 3:53 PM, "Huang, Thomas (US 398F)"  <mailto:thomas.hu...@jpl.nasa.gov>> wrote:
> 
> 
> Great ideas, Thomas L. I am added your suggestion to the list for the 
> community to choose from. I should have a revision early this week.
> 
> 
> 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 
> 
> 
> 
> 
> 
> 
> 
> 
> On 11/18/23, 4:07 PM, "Loubrieu, Thomas G (US 398F)" 
>  <mailto:thomas.g.loubr...@jpl.nasa.gov.inva> 
> <mailto:thomas.g.loubr...@jpl.nasa.gov.inva 
> <mailto:thomas.g.loubr...@jpl.nasa.gov.inva>>LID> wrote:
> 
> 
> 
> 
> Hi,
> 
> 
> 
> 
> That looks great, I like the colors and the overall idea of logo with these 
> hexagonal cells connected.
> 
> 
> 
> 
> I was thinking, for the readibility of SDAP acronym that would be better to 
> have all the letters on one horizontal line.
> One idea could be to keep 2 hexagonal cells, the one filled with the colored 
> sub cells, and one on the top left with the full acronym SDAP in a single 
> line. We would remove the 3 other cells. It feels to me that that would also 
> lighten the overall design so that it can more easily be used in smaller 
> sizes.
> 
> 
> 
> 
> Thanks,
> 
> 
> 
> 
> Thomas
> 
> 
> 
> 
> 
> 
> 
> 
> Get Outlook for 
> iOS<https://urldefense.us/v3/__https://aka.ms/o0ukef__;!!PvBDto6Hs4WbVuu7!PY1u1SmML9_ZeRBpM2ZJx5Hji6xeo8xc2gayPV-bfC7d2stEnELCQqRaMp1UjP_wfwkBoRdwcdg4SuiqwJ3pxAn-YI_Cl7MiAUvu1oPhwuyQHXY$
>  
> <https://urldefense.us/v3/__https://aka.ms/o0ukef__;!!PvBDto6Hs4WbVuu7!PY1u1SmML9_ZeRBpM2ZJx5Hji6xeo8xc2gayPV-bfC7d2stEnELCQqRaMp1UjP_wfwkBoRdwcdg4SuiqwJ3pxAn-YI_Cl7MiAUvu1oPhwuyQHXY$>
>  
> <https://urldefense.us/v3/__https://aka.ms/o0ukef__;!!PvBDto6Hs4WbVuu7!PY1u1SmML9_ZeRBpM2ZJx5Hji6xeo8xc2gayPV-bfC7d2stEnELCQqRaMp1UjP_wfwkBoRdwcdg4SuiqwJ3pxAn-YI_Cl7MiAUvu1oPhwuyQHXY$
>  
> <https://urldefense.us/v3/__https://aka.ms/o0ukef__;!!PvBDto6Hs4WbVuu7!PY1u1SmML9_ZeRBpM2ZJx5Hji6xeo8xc2gayPV-bfC7d2stEnELCQqRaMp1UjP_wfwkBoRdwcdg4SuiqwJ3pxAn-YI_Cl7MiAUvu1oPhwuyQHXY$>>
>  >
> 
> From: Julian Hyde mailto:jhyde.apa...@gmail.com> 
> <mailto:jhyde.apa...@gmail.com <mailto:jhyde.apa...@gmail.com>>>
> Sent: Friday, November 17, 2023 5:36:07 PM
> To: dev@sdap.apache.org <mailto:dev@sdap.apache.org> 
> <mailto:dev@sdap.apache.org <mailto:dev@sdap.apache.org>> 
> mailto:dev@sdap.apache.org> <mailto:dev@sdap.apache.org 
> <mailto:dev@sdap.apache.org>>>
> Subject: Re: [EXTERNAL] SDAP logo consideration
> 
> 
> 
> 
> I prefer the bold font, with the Apache/TM.
> 
> 
> 
> 
> A couple of suggestions: move Apache to the top-left corner, 

Re: [EXTERNAL] SDAP logo consideration

[Julian Hyde]

I prefer the bold font, with the Apache/TM.

A couple of suggestions: move Apache to the top-left corner, and move the TM as 
a suffix to the ‘P’, so you can (kind of) read ‘Apache SDAP TM’ left-to-right.

Also add a small white border (maybe 2 pixels) so that the logo can be used on 
a dark background.

Julian
 

> On Nov 17, 2023, at 12:54 PM, Nga Chung  wrote:
> 
> Thanks Thomas for providing additional updates to the logo.
> 
> All, please provide your feedback on the logo design and whether you
> like the regular or bolded lettering.
> 
> Regular: 
> https://issues.apache.org/jira/secure/attachment/13064470/SDAP%20logo.png
> Bold: 
> https://issues.apache.org/jira/secure/attachment/13064498/SDAP%20logo%20bold.png
> 
> Regular with Apache TM:
> https://issues.apache.org/jira/secure/attachment/13064497/SDAP%20logo%20Apache%20TM.png
> Bold with Apache TM:
> https://issues.apache.org/jira/secure/attachment/13064496/SDAP%20logo%20bold%20Apache%20TM.png
> 
> Thanks,
> Nga
> 
> On Thu, Nov 16, 2023 at 4:25 PM Julian Hyde  wrote:
>> 
>> Thanks for the slack invite, Riley.
>> 
>> I see the logo is now attached to the Jira case:
>> https://issues.apache.org/jira/secure/attachment/13064470/SDAP%20logo.png
>> 
>> I like the design and the beehive concept.
>> 
>> It's useful if the logo includes the word 'Apache' and the superscript
>> 'TM'. That way, by including the logo on the first slide of a
>> presentation, you've immediately addressed a number of branding
>> issues.
>> 
>> Julian
>> 
>> 
>> On Thu, Nov 16, 2023 at 3:43 PM Riley Kuttruff  wrote:
>>> 
>>> I added you to the channel.
>>> 
>>> On 2023/11/16 23:39:53 Julian Hyde wrote:
>>>> Curious fact. I have never seen the Slack channel. And I have never
>>>> been able to discover its URL.
>>>> 
>>>> On Thu, Nov 16, 2023 at 3:37 PM Huang, Thomas (US 398F)
>>>>  wrote:
>>>>> 
>>>>> I also posted my logo design on the Apache #sdap slack channel.
>>>>> 
>>>>> 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 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On 11/16/23, 3:36 PM, "Huang, Thomas (US 398F)" 
>>>>> >>>> <mailto:thomas.hu...@jpl.nasa.gov.inva>LID> wrote:
>>>>> 
>>>>> 
>>>>> Strange. My JPL email was marked as invalid on the SDAP list. Reattached.
>>>>> 
>>>>> 
>>>>> 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 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On 11/16/23, 3:33 PM, "Riley Kuttruff" >>>> <mailto:r...@apache.org> <mailto:r...@apache.org 
>>>>> <mailto:r...@apache.org>>> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Hey Thomas,
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> The image isn't displaying for me on any of my devices.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> -Riley
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On 2023/11/16 23:29:21 "Huang, Thomas (US 398F)" wrote:
>>>>>> Hi everyone,
>>>>>> 
>>>>>> SDAP is a parallel data management and analysis platform. When talking 
>>>>>> about parallel systems, I always use a beehive as an analogy (Riley and 
>>>>>> Josh, I hope you still remember this in the lecture). Each worker bee 
>>>>>> works independently, but at some point, they would communicate with one 
>>>>>> another (synchronization). Together, they construct and maintain a 
>>>>>> beehive (a system). I am using the Apache colors here, because they 
>>>>>> represent free and open to me. Since we will have a poster at the 
>>>>>> December AGU, it would be great to have a logo on the poster.
>>>>>> 
>>>>>> Vote? Suggestion?
>>>>>> 
>>>>>> 
>>>>>> [cid:image001.png@01DA18A1.ABFD <mailto:image001@01da18a1.abfd> 
>>>>>> <mailto:image001@01da18a1.abfd 
>>>>>> <mailto:image001@01da18a1.abfd>>33B0]
>>>>>> 
>>>>>> 
>>>>>> 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
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 

Re: [EXTERNAL] Re: SDAP logo consideration

[Julian Hyde]

Thanks for the slack invite, Riley.

I see the logo is now attached to the Jira case:
https://issues.apache.org/jira/secure/attachment/13064470/SDAP%20logo.png

I like the design and the beehive concept.

It's useful if the logo includes the word 'Apache' and the superscript
'TM'. That way, by including the logo on the first slide of a
presentation, you've immediately addressed a number of branding
issues.

Julian


On Thu, Nov 16, 2023 at 3:43 PM Riley Kuttruff  wrote:
>
> I added you to the channel.
>
> On 2023/11/16 23:39:53 Julian Hyde wrote:
> > Curious fact. I have never seen the Slack channel. And I have never
> > been able to discover its URL.
> >
> > On Thu, Nov 16, 2023 at 3:37 PM Huang, Thomas (US 398F)
> >  wrote:
> > >
> > > I also posted my logo design on the Apache #sdap slack channel.
> > >
> > > 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 
> > >
> > >
> > >
> > >
> > > On 11/16/23, 3:36 PM, "Huang, Thomas (US 398F)" 
> > >  > > <mailto:thomas.hu...@jpl.nasa.gov.inva>LID> wrote:
> > >
> > >
> > > Strange. My JPL email was marked as invalid on the SDAP list. Reattached.
> > >
> > >
> > > 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 
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 11/16/23, 3:33 PM, "Riley Kuttruff"  > > <mailto:r...@apache.org> <mailto:r...@apache.org 
> > > <mailto:r...@apache.org>>> wrote:
> > >
> > >
> > >
> > >
> > > Hey Thomas,
> > >
> > >
> > >
> > >
> > > The image isn't displaying for me on any of my devices.
> > >
> > >
> > >
> > >
> > > -Riley
> > >
> > >
> > >
> > >
> > > On 2023/11/16 23:29:21 "Huang, Thomas (US 398F)" wrote:
> > > > Hi everyone,
> > > >
> > > > SDAP is a parallel data management and analysis platform. When talking 
> > > > about parallel systems, I always use a beehive as an analogy (Riley and 
> > > > Josh, I hope you still remember this in the lecture). Each worker bee 
> > > > works independently, but at some point, they would communicate with one 
> > > > another (synchronization). Together, they construct and maintain a 
> > > > beehive (a system). I am using the Apache colors here, because they 
> > > > represent free and open to me. Since we will have a poster at the 
> > > > December AGU, it would be great to have a logo on the poster.
> > > >
> > > > Vote? Suggestion?
> > > >
> > > >
> > > > [cid:image001.png@01DA18A1.ABFD <mailto:image001@01da18a1.abfd> 
> > > > <mailto:image001@01da18a1.abfd 
> > > > <mailto:image001@01da18a1.abfd>>33B0]
> > > >
> > > >
> > > > 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
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >

Re: [EXTERNAL] Re: SDAP logo consideration

[Julian Hyde]

Curious fact. I have never seen the Slack channel. And I have never
been able to discover its URL.

On Thu, Nov 16, 2023 at 3:37 PM Huang, Thomas (US 398F)
 wrote:
>
> I also posted my logo design on the Apache #sdap slack channel.
>
> 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 
>
>
>
>
> On 11/16/23, 3:36 PM, "Huang, Thomas (US 398F)" 
> mailto:thomas.hu...@jpl.nasa.gov.inva>LID> 
> wrote:
>
>
> Strange. My JPL email was marked as invalid on the SDAP list. Reattached.
>
>
> 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 
>
>
>
>
>
>
>
>
> On 11/16/23, 3:33 PM, "Riley Kuttruff"   >> 
> wrote:
>
>
>
>
> Hey Thomas,
>
>
>
>
> The image isn't displaying for me on any of my devices.
>
>
>
>
> -Riley
>
>
>
>
> On 2023/11/16 23:29:21 "Huang, Thomas (US 398F)" wrote:
> > Hi everyone,
> >
> > SDAP is a parallel data management and analysis platform. When talking 
> > about parallel systems, I always use a beehive as an analogy (Riley and 
> > Josh, I hope you still remember this in the lecture). Each worker bee works 
> > independently, but at some point, they would communicate with one another 
> > (synchronization). Together, they construct and maintain a beehive (a 
> > system). I am using the Apache colors here, because they represent free and 
> > open to me. Since we will have a poster at the December AGU, it would be 
> > great to have a logo on the poster.
> >
> > Vote? Suggestion?
> >
> >
> > [cid:image001.png@01DA18A1.ABFD  
> > >33B0]
> >
> >
> > 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
> >
>
>
>
>
>
>
>
>
>

Re: [EXTERNAL] Re: SDAP logo consideration

[Julian Hyde]

ASF email strips images. Because you know what happens if you allow
posting of images to public archived mailing lists.

Suggest you upload to a site like https://pastebin.com/ and post a URL.

On Thu, Nov 16, 2023 at 3:35 PM Huang, Thomas (US 398F)
 wrote:
>
> Strange. My JPL email was marked as invalid on the SDAP list. Reattached.
>
> 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 
>
>
>
>
> On 11/16/23, 3:33 PM, "Riley Kuttruff"  > wrote:
>
>
> Hey Thomas,
>
>
> The image isn't displaying for me on any of my devices.
>
>
> -Riley
>
>
> On 2023/11/16 23:29:21 "Huang, Thomas (US 398F)" wrote:
> > Hi everyone,
> >
> > SDAP is a parallel data management and analysis platform. When talking 
> > about parallel systems, I always use a beehive as an analogy (Riley and 
> > Josh, I hope you still remember this in the lecture). Each worker bee works 
> > independently, but at some point, they would communicate with one another 
> > (synchronization). Together, they construct and maintain a beehive (a 
> > system). I am using the Apache colors here, because they represent free and 
> > open to me. Since we will have a poster at the December AGU, it would be 
> > great to have a logo on the poster.
> >
> > Vote? Suggestion?
> >
> >
> > [cid:image001.png@01DA18A1.ABFD 33B0]
> >
> >
> > 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
> >
>
>
>

[DISCUSS] A meta-discussion about graduation discussions

[Julian Hyde]

I am genuinely puzzled why SDAP has not started talking about
graduation on the dev list. Graduation in the ASF basically consists
of a discussion followed by a vote on the dev list, and a discussion
followed by a vote on the Incubator list. There are some housekeeping
tasks in the middle, and there is a vote by the Apache board at the
end, but the email threads drive the process.

I thought it might be useful to see how another project that I
mentored, Hop, went through the process. You could use their emails as
a template for your process.

Can someone (Nga, Stepheny, Riley, ...?) start a discussion thread?

0. 2020-09-26 Hop starts incubation
https://lists.apache.org/thread/74r29h49n54705fpfgnv84rbsnkgsbvv
1. 2021-08-11 Discussion on dev@hop
https://lists.apache.org/thread/470xwxw8x8qmm4fp82ckqys5zmrq9416
2. 2021-09-10 Second discussion on dev@hop
https://lists.apache.org/thread/lx1yhd7qocgczzm5tg88xz49mrbnt2c8
3. 2021-10-15 Discussion on general@incubator
https://lists.apache.org/thread/jj46blkwrhf0l31srtzo5j5dcv7zsqz3
4. 2021-11-21 Vote on dev@hop
https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
5. 2021-11-24 Result of vote on dev@hop
https://lists.apache.org/thread/sqyps8crdsjpckks37336psz5wvj4q70
6. 2021-11-25 Second discussion on general@incubator
https://lists.apache.org/thread/mrx8g5w1xfzx80wtg9l3mrm3q1lkh6ss
7. 2021-12-02 Vote on general@incubator
https://lists.apache.org/thread/l1ttdddl5hl2s4b726q1w3obj1kb7j3g
8. 2021-21-08 Result of vote on general@incubator
https://lists.apache.org/thread/x4yrl2n2w5wyym6xmlf7obwydj9b5h72
9. 2021-12-15 Minutes of board meeting voting to establish Hop
https://www.apache.org/foundation/records/minutes/2021/board_minutes_2021_12_15.txt

Julian

Re: [REPORT] November 2023 Report Feedback Requested

[Julian Hyde]

I signed off. Thanks for the reminder.

I also asked Google Bard to design a logo. (If someone can feed this into a 
graphics GenAI I think we’re done!)

$ generate a logo for apache sdap

> Sure, here is a logo for Apache SDAP:
>
> The logo is designed to be simple and easy to understand. It is
> also designed to be modern and eye-catching. The globe
> represents the global nature of Apache SDAP, and the data
> center represents the technology that powers it. The colors
> of the Apache Software Foundation are used to show that
> Apache SDAP is a part of the Apache family of projects.
>
> Here are some additional details about the logo:
>
> The font used for the text is called "Ubuntu".
> The colors used for the globe are #0059B3, #00A950, and #FFEB3B.
> The logo is 500 pixels wide and 300 pixels tall.
> I hope this is what you were looking for!

Julian


> On Nov 1, 2023, at 1:18 PM, Nga Chung  wrote:
> 
> Hi Julian,
> 
> Just wanted to make sure this is on your radar. Can you please comment
> and sign off on the report when you get a chance?
> 
> Thanks,
> Nga
> 
> 
> On Mon, Oct 30, 2023 at 2:27 PM Nga Chung  wrote:
>> 
>> Sorry all, wrong subject in original email. I meant the November 2023 Report.
>> 
>> Thanks,
>> Nga
>> 
>> On Mon, Oct 30, 2023 at 2:26 PM Nga Chung  wrote:
>>> 
>>> Hi everyone,
>>> 
>>> A draft of SDAP status report has been added to the wiki:
>>> https://cwiki.apache.org/confluence/display/INCUBATOR/November2023#sdap
>>> 
>>> Please review and let me know if changes are needed. Report is due by
>>> end of day Wednesday, November 1st.
>>> 
>>> Thanks,
>>> Nga

Re: Donating new code to Apache SDAP

[Julian Hyde]

Apache has a process for that, called “IP clearance”. It is administered by
the Incubator but is used by all ASF projects; for example, you’ll notice
several contributions to Arrow (top-level project) in the past 12 months.

Julian

[1] https://incubator.apache.org/ip-clearance/

On Nov 2, 2023, at 12:46 PM, Huang, Thomas (US 398F) <
thomas.hu...@jpl.nasa.gov> wrote:

Hi @Julian Hyde 

We have new data transformation solutions approved for open-source release
that we are considering adding to the Apache SDAP umbrella. Currently,
Caltech has the copyright to the source code. It’s been a few years since
we released SDAP to Apache. Do we need to have Caltech release its
copyright to Apache? Do you know who we should contact at Apache?

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 <(818)%20354-2747>*

Re: [RESULT][VOTE] Release Apache SDAP (incubating) 1.2.0-rc2

[Julian Hyde]

Stepheny, 

The next step is to start a vote thread on general@incubator.a.o. 

Julian

> On Nov 1, 2023, at 2:27 PM, Stepheny Perez  wrote:
> 
> Hi everyone,
> 
> Correction; my message incorrectly states 1.2.0-rc1 has passed, when in 
> reality 1.2.0-rc2 has passed. Sorry for the confusion.
> 
> Stepheny
> 
>> On 2023/11/01 21:21:56 Stepheny Perez wrote:
>> Hello everyone,
>> 
>> The vote for 1.2.0-rc1 has passed with count of +3.
>> 
>> Binding +1 votes:
>> - Riley Kuttruff
>> - Nga Chung
>> - Julian Hyde
>> - Stepheny Perez
>> 
>> Binding -1 votes:  
>> None
>> 
>> Thank you everyone for your feedback and help with this SDAP release. The 
>> SDAP team will take the steps to complete this release and will have it 
>> announced shortly.
>> 
>> Thank you,
>> 
>> Stepheny Perez
>> 

Re: [VOTE] Release Apache SDAP (incubating) 1.2.0-rc2

[Julian Hyde]

+1 (binding)

Downloaded, checked signatures, LICENSE, NOTICE, DISCLAIMER; compared
against git tags; ran docker build; checked licenses.

Note: I followed the instructions at
https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html.
Copy-pasting  twenty or so shell commands to perform a build seemed
like rather a lot. If there's any way to reduce that effort (e.g.
shipping a build script) I would appreciate it.

Julian


On Fri, Oct 27, 2023 at 9:50 AM Riley Kuttruff  wrote:
>
> I verified:
> - Release commits
> - Artifact signatures & checksums
> - Images built successfully
> - Components work successfully
>
> +1 (binding)
>
> -Riley
>
> On 2023/10/27 04:23:57 Stepheny Perez wrote:
> > Hello everyone,
> >
> > This is the vote to approve Apache SDAP (incubating) release candidate rc2 
> > for version 1.2.0.
> >
> > CHANGELOG for version 1.2.0 are available here:
> > https:/github.com/apache/incubator-sdap-ingester/blob/1.2.0-rc2/CHANGELOG.md
> > https:/github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc2/CHANGELOG.md
> >
> > Changes made between previous candidate (rc1) and this one (rc2) are as 
> > follows:
> >
> > - Fix build issues with Apple Silicon M1/M2
> > - Install protobuf through PyPi instead of from source
> >
> > Instructions for building docker images from source can be found here:
> > https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc2/docs/build.rst
> > Instructions for deploying locally to test can be found here:
> > https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc2/docs/quickstart.rst
> > The release files, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.2.0-rc2/
> >
> > For convenience, the tags we built the release artifacts to be voted on
> > from are 1.2.0-rc2:
> >
> > - ingester:
> > - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.2.0-rc2
> > - Commit: a9f0673abdd8fc5aebbbcd3051ba43f6f7f040fe
> >
> > - nexus:
> > - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.2.0-rc2
> > - Commit: 955938afddd8824b1240b1582355f941f2139dec
> >
> > For verification, the hashes (SHA-512) of the .tar.gz artifacts we are 
> > voting on are as follows:
> >
> > apache-sdap-ingester-1.2.0-incubating-src.tar.gz:
> > 9717675657a7f6cdf38f6a965fcee70fc602a4d1d879c45f93df5824d09375a088a81e9f5ffdba4b8c9aeb46ccec89fff732fb3899734b4a59eaf99668ee6c15
> >
> > apache-sdap-nexus-1.2.0-incubating-src.tar.gz:
> > ea5eb29f69d4955c0bfdca9af0be193eb0ed0c5fc6750cbb51f2b5e1796fa8fe73e17b72a92a22831fd7fdefa1b33378a753a083697913c95dc645c76c5a
> >
> > Release artifacts are signed with the following key:
> > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x2E8418801953621FAA322169D6F360887071C194
> >
> > Please vote on releasing this package as Apache SDAP (incubating) 1.2.0.
> >
> > The vote is open for 72 hours and passes if at least 3 +1 PMC votes are 
> > cast.
> >
> > PLEASE NOTE: Do not reply with a vote from your work email as it can mangle 
> > the links. To vote, go to 
> > https://lists.apache.org/list.html?dev@sdap.apache.org, log in and send 
> > your reply from there.
> >
> > [ ] +1 Release this package as Apache SDAP (incubating) 1.2.0
> > [ ] +0 No opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thank you,
> > Stepheny
> >

[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767308#comment-17767308
 ] 

Julian Hyde commented on SDAP-491:
--

The most important thing is to reach consensus, and that's done by discussion. 
You can take a vote, if you wish, to record that consensus. Once there is 
consensus, the vote should be a formality.

If the decision process is complicated, like choosing a logo, you can devise 
your methods for an online discussion. Maybe ask people to rank their top 3 
choices? Maybe people will say 'I love design #2 but I wish it was blue'. In 
which case you generate some more logos and have a second round of discussion. 
Maybe just put the most popular 2 designs to a vote.

> Adopt an official logo for SDAP and add it to the website
> -
>
> Key: SDAP-491
> URL: https://issues.apache.org/jira/browse/SDAP-491
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Riley Kuttruff
>Assignee: Riley Kuttruff
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767245#comment-17767245
 ] 

Julian Hyde commented on SDAP-491:
--

I would expect to see a discussion or vote on the dev list about logo 
candidates. This is a project decision, not merely a code review.

> Adopt an official logo for SDAP and add it to the website
> -
>
> Key: SDAP-491
> URL: https://issues.apache.org/jira/browse/SDAP-491
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Riley Kuttruff
>Assignee: Riley Kuttruff
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757144#comment-17757144
 ] 

Julian Hyde commented on SDAP-483:
--

I saw you merged [PR 
85|https://github.com/apache/incubator-sdap-ingester/pull/85]. Now lots of new 
blue ink on the 
[incubator-sdap-ingester|https://github.com/apache/incubator-sdap-ingester] 
home page. Looks great!

> Configure GitHub to automatically convert Jira references to hyperlinks
> ---
>
> Key: SDAP-483
> URL: https://issues.apache.org/jira/browse/SDAP-483
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>    Reporter: Julian Hyde
>Assignee: Riley Kuttruff
>Priority: Major
>
> Configure GitHub to automatically convert Jira references to hyperlinks. 
> GitHub calls this capability 
> [autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources].
> For an example, see Calcite's [commit 
> history|https://github.com/apache/calcite/commits/main] and note that text 
> like "CALCITE-5640" is a blue hyperlink. Autolinking also happens in other 
> places, such as PR comments.
> If you would like this functionality in SDAP, let me know, and I'll implement 
> it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756587#comment-17756587
 ] 

Julian Hyde commented on SDAP-483:
--

Thanks. I've added those 3 to the list. It's best that we have the same policy 
on all repositories, to avoid surprises.

There's probably a process to retire/archive git repositories, but I'm not 
aware of the details.

> Configure GitHub to automatically convert Jira references to hyperlinks
> ---
>
> Key: SDAP-483
> URL: https://issues.apache.org/jira/browse/SDAP-483
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Julian Hyde
>Priority: Major
>
> Configure GitHub to automatically convert Jira references to hyperlinks. 
> GitHub calls this capability 
> [autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources].
> For an example, see Calcite's [commit 
> history|https://github.com/apache/calcite/commits/main] and note that text 
> like "CALCITE-5640" is a blue hyperlink. Autolinking also happens in other 
> places, such as PR comments.
> If you would like this functionality in SDAP, let me know, and I'll implement 
> it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks

[Julian Hyde (Jira)]

 [ 
https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Hyde updated SDAP-483:
-
Issue Type: Task  (was: Bug)

> Configure GitHub to automatically convert Jira references to hyperlinks
> ---
>
> Key: SDAP-483
> URL: https://issues.apache.org/jira/browse/SDAP-483
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>    Reporter: Julian Hyde
>Priority: Major
>
> Configure GitHub to automatically convert Jira references to hyperlinks. 
> GitHub calls this capability 
> [autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources].
> For an example, see Calcite's [commit 
> history|https://github.com/apache/calcite/commits/main] and note that text 
> like "CALCITE-5640" is a blue hyperlink. Autolinking also happens in other 
> places, such as PR comments.
> If you would like this functionality in SDAP, let me know, and I'll implement 
> it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756582#comment-17756582
 ] 

Julian Hyde commented on SDAP-483:
--

I have logged INFRA-24912. [~rkk], please check that I have the details correct.

> Configure GitHub to automatically convert Jira references to hyperlinks
> ---
>
> Key: SDAP-483
> URL: https://issues.apache.org/jira/browse/SDAP-483
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>    Reporter: Julian Hyde
>Priority: Major
>
> Configure GitHub to automatically convert Jira references to hyperlinks. 
> GitHub calls this capability 
> [autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources].
> For an example, see Calcite's [commit 
> history|https://github.com/apache/calcite/commits/main] and note that text 
> like "CALCITE-5640" is a blue hyperlink. Autolinking also happens in other 
> places, such as PR comments.
> If you would like this functionality in SDAP, let me know, and I'll implement 
> it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks

[Julian Hyde (Jira)]

Julian Hyde created SDAP-483:


 Summary: Configure GitHub to automatically convert Jira references 
to hyperlinks
 Key: SDAP-483
 URL: https://issues.apache.org/jira/browse/SDAP-483
 Project: Apache Science Data Analytics Platform
  Issue Type: Bug
Reporter: Julian Hyde


Configure GitHub to automatically convert Jira references to hyperlinks. GitHub 
calls this capability 
[autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources].

For an example, see Calcite's [commit 
history|https://github.com/apache/calcite/commits/main] and note that text like 
"CALCITE-5640" is a blue hyperlink. Autolinking also happens in other places, 
such as PR comments.

If you would like this functionality in SDAP, let me know, and I'll implement 
it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [REPORT] August 2023 Report Feedback Requested

[Julian Hyde]

I have signed off the report. Thank you for submitting it in a timely manner.

These were my comments on the report:

> I think SDAP is ready to graduate. In my opinion, a third
> release is not a necessary condition for graduation. The
> low participation in the graduation discussion is a little
> concerning, but not unexpected, because SDAP has
> never been very active on dev@.

Julian

> On Aug 2, 2023, at 11:39 AM, Nga Chung  wrote:
> 
> Thanks Riley.
> 
> Julian, when you get a chance, can you please comment and sign off on
> the report?
> 
> Thanks,
> Nga
> 
> On Tue, Aug 1, 2023 at 10:42 AM Riley Kuttruff  wrote:
>> 
>> Disregard that last comment; I neglected to read the section header.
>> 
>> On 2023/08/01 17:41:04 Riley Kuttruff wrote:
>>> Looks pretty good. Though I think we mentioned adding Jason as a committer 
>>> in our last report.
>>> 
>>> On 2023/08/01 17:36:44 Nga Chung wrote:
 Hi everyone,
 
 A draft of SDAP status report has been added to the wiki:
 https://cwiki.apache.org/confluence/display/INCUBATOR/August2023#sdap
 
 Please review and let me know if changes are needed. Report is due by
 end of day tomorrow, August 2nd.
 
 Thanks,
 Nga
 
>>> 

Re: Inclusion of public NASA data in releases

[Julian Hyde]

If we are distributing components from outside the project, our
obligation is to comply with the licensing requirements of their
authors/copyright holders.

It seems that NASA imposes no requirements, other than that we do not
imply endorsement by NASA. So we're good.

The NOTICE file exists because the Apache license mentions it:

  If the Work includes a "NOTICE" text file as part of its distribution,
  then any Derivative Works that You distribute must include a
  readable copy of the attribution notices contained within such NOTICE file

The NOTICE file is somewhat of a burden. We are obligated to include
the contents of NOTICE files of any projects we include, and any
projects that include us have to include our NOTICE file. To decrease
the burden on downstream projects, I suggest that we don't include
anything in our NOTICE file that we don't have to.

That said, I think that giving credit to our sources is courteous,
interesting, useful for tracking down bugs, and just the Right Thing
to do. I would put that credit in places such as README files, online
documentation, or commit messages. Downstream projects are under no
obligation to copy it.

Julian

On Tue, Jun 20, 2023 at 8:36 AM Riley Kuttruff  wrote:
>
> I'm looking into getting our components migrated away from DISCLAIMER-WIP in 
> preparation for graduation. One of the components (ingester) has some data 
> for tests [1] that comes from NASA which is freely and openly available 
> without (I believe) copyright. [2] Would it be required/recommended to 
> mention this in the component's NOTICE file? If so, is there a standard 
> format for entries in NOTICE?
>
> [1] 
> https://github.com/apache/incubator-sdap-ingester/tree/dev/granule_ingester/tests/granules
> [2] https://www.earthdata.nasa.gov/learn/use-data/data-use-policy

Re: June 2023 Report

[Julian Hyde]

I signed off. (I corrected the release version from 1.0.0 to 1.1.0. Hope that’s 
right.)

Thanks for getting the report done in time.

I’m hoping to see a graduation discussion on this list very soon.

Julian

PS And don’t call me Shirley.

> On Jun 6, 2023, at 11:22 AM, Nga Chung  wrote:
> 
> Sorry, I meant, Julian not Trevor. Need to stop multitasking.
> 
> Best,
> Nga
> 
> On Tue, Jun 6, 2023 at 11:20 AM Nga Chung  wrote:
>> 
>> Hi Trevor, all,
>> 
>> SDAP status report has been manually added to
>> https://cwiki.apache.org/confluence/display/INCUBATOR/June2023#sdap
>> 
>> Thanks,
>> Nga
>> 
>> On Tue, Jun 6, 2023 at 10:43 AM Julian Hyde  wrote:
>>> 
>>> It’s possible that June isn’t when SDAP is scheduled to report, and equally 
>>> possible that there is an error in the scripts that generate that page.
>>> 
>>> In any case, you can file a report. You should add the boilerplate by hand 
>>> (perhaps copying from the previous SDAP report).
>>> 
>>> When you’ve added the report, reply to this thread, and I will sign off.
>>> 
>>> Also send a note to general@incubator that you have manually added a report.
>>> 
>>> Julian
>>> 
>>> PS I haven’t seen it mentioned on the dev@ list but with two releases 
>>> completed I think SDAP should be considering graduation. Hopefully the 
>>> report will contain an update on that.
>>> 
>>>> On Jun 6, 2023, at 10:13 AM, Nga Chung  wrote:
>>>> 
>>>> Hi everyone,
>>>> 
>>>> We need to submit the June report by tomorrow, June 7th, but I don't
>>>> see a section for SDAP here
>>>> https://cwiki.apache.org/confluence/display/INCUBATOR/June2023.
>>>> 
>>>> I tried asking in #incubator slack yesterday on how to get the SDAP
>>>> section added, but haven't received a response.
>>>> 
>>>> Does anyone know what the process is to add SDAP to the report? Seems
>>>> like we shouldn't copy from the section an old report?
>>>> 
>>>> Thanks,
>>>> Nga
>>> 

Re: June 2023 Report

[Julian Hyde]

It’s possible that June isn’t when SDAP is scheduled to report, and equally 
possible that there is an error in the scripts that generate that page.

In any case, you can file a report. You should add the boilerplate by hand 
(perhaps copying from the previous SDAP report).

When you’ve added the report, reply to this thread, and I will sign off.

Also send a note to general@incubator that you have manually added a report.

Julian

PS I haven’t seen it mentioned on the dev@ list but with two releases completed 
I think SDAP should be considering graduation. Hopefully the report will 
contain an update on that.

> On Jun 6, 2023, at 10:13 AM, Nga Chung  wrote:
> 
> Hi everyone,
> 
> We need to submit the June report by tomorrow, June 7th, but I don't
> see a section for SDAP here
> https://cwiki.apache.org/confluence/display/INCUBATOR/June2023.
> 
> I tried asking in #incubator slack yesterday on how to get the SDAP
> section added, but haven't received a response.
> 
> Does anyone know what the process is to add SDAP to the report? Seems
> like we shouldn't copy from the section an old report?
> 
> Thanks,
> Nga

Re: Registering SDAP 1.1.0 Release

[Julian Hyde]

Done. I also registered release 1.0.0 (incubating) for 2023-01-18. I
used the URL https://reporter.apache.org/addrelease.html?incubator-sdap.

On Tue, May 16, 2023 at 2:23 PM Nga Chung  wrote:
>
> Hi Julian (or anyone else who has permission),
>
> Can you please help us register the SDAP 1.1.0 release at
> https://reporter.apache.org using the information below? Looks like I
> don't have permission to do so as I get this error "Error: User nchung
> not a member of PMC incubator-sdap nor an ASF member "
>
> Committee:
>   incubator-sdap
> Full version name: (Note: use a product name prefix if the PMC
> releases multiple products)
>   1.1.0 (incubating)
> Date of release (-MM-DD): (Note: use 1970-01-01 to remove a release)
>   2023-05-16
>
> Thank you!
> Nga

Re: [VOTE] Release Apache SDAP (incubating) 1.1.0-rc0

[Julian Hyde]

Thanks for pointing this out. I have re-sent my reply to general@.


> On May 1, 2023, at 4:51 PM, Riley Kuttruff  wrote:
> 
> Hey Julian,
> 
> It looks like this was sent to the dev@ thread and not the general@ thread. 
> Not sure what happened there, Nga's email appeared to go to both.
> 
> On 2023/05/01 23:39:37 Julian Hyde wrote:
>> (I am a mentor of SDAP but was too late to vote in the thread on dev@sdap.)
>> 
>> +1 (binding)
>> 
>> Checked signatures/hashes, compared with git, checked NOTICE, LICENSE.txt, 
>> DISCLAIMER-WIP; built Collection Manager and Granule Infester using Docker, 
>> following the instructions in README.
>> 
>> Notes:
>> * You should remove ‘APPENDIX: How to apply the Apache License to your work’ 
>> and onwards from LICENSE.txt.
>> * ‘Apache-SDAP’ directory prefix in the tar.gz files is a bit unusual, but 
>> fine.
>> * DISCLAIMER-WIP lists a couple of issues (missing headers and potential 
>> licensing issue with test data); with SDAP approaching graduation, when do 
>> you plan to solve this issues?
>> 
>> Julian
>> 
>> 
>> 
>>> On May 1, 2023, at 10:20 AM, Nga Chung  wrote:
>>> 
>>> Hello Incubator PMC,
>>> 
>>> This is a call for a vote to release Apache SDAP (incubating) version
>>> 1.1.0-rc0.
>>> 
>>> The Apache SDAP community has voted to approve the release of Apache SDAP
>>> (incubating) version 1.1.0-rc0.
>>> 
>>> We now request the Incubator PMC review and vote on this release.
>>> 
>>> SDAP community thread:
>>> https://lists.apache.org/thread/z5llljrb10zrq39368xvpm7h0bto65kh
>>> 
>>> CHANGELOG for version 1.1.0 are available here:
>>> https://github.com/apache/incubator-sdap-ingester/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
>>> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
>>> 
>>> Instructions for building docker images from source can be found here:
>>> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/build.rst
>>> Instructions for deploying locally to test can be found here:
>>> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/quickstart.rst
>>> 
>>> The release files, including signatures, digests, etc. can be found at:
>>> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.1.0-rc0/
>>> 
>>> For convenience, the tags we built the release artifacts to be voted on
>>> from are 1.1.0-rc0:
>>> 
>>> - ingester:
>>> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.1.0-rc0
>>> - Commit: 8632b262eef9a33c816ec9b733c1ddc0156fa4c5
>>> 
>>> - nexus:
>>> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.1.0-rc0
>>> - Commit: 370190db8c4db86ce7837bc9fb3889c6658fac7f
>>> 
>>> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are
>>> voting on are as follows:
>>> 
>>> apache-sdap-ingester-1.1.0-incubating-src.tar.gz:
>>> ab243d84d0ab7dd33bc61ab84129080b1de0dc22f15d519950dda55ade41bf65cc8b02fe0b131c6640e0782613978c8ba9e9e573156a8657cb7ce14c599fbe7c
>>> 
>>> apache-sdap-nexus-1.1.0-incubating-src.tar.gz:
>>> c51340b040ffb4e82cdd9c8ba02ba3e8b54a9194826486bac781e966218491b700685b92effc200fd8a97ee10cffb301b618e6e9c73a3a21cd42d1b75a54670e
>>> 
>>> Release artifacts are signed with the following key:
>>> https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x1392A8A11801359247A803D8D2449E0EB5EF1E73
>>> 
>>> Please vote on releasing this package as Apache SDAP (incubating) 1.1.0.
>>> 
>>> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
>>> cast.
>>> 
>>> [ ] +1 Release this package as Apache SDAP (incubating) {version}
>>> [ ] +0 No opinion
>>> [ ] -1 Do not release this package because ...
>>> 
>>> Thank you,
>>> Nga
>> 
>> 

Re: [VOTE] Release Apache SDAP (incubating) 1.1.0-rc0

[Julian Hyde]

(I am a mentor of SDAP but was too late to vote in the thread on dev@sdap.)

+1 (binding)

Checked signatures/hashes, compared with git, checked NOTICE, LICENSE.txt, 
DISCLAIMER-WIP; built Collection Manager and Granule Infester using Docker, 
following the instructions in README.

Notes:
 * You should remove ‘APPENDIX: How to apply the Apache License to your work’ 
and onwards from LICENSE.txt.
 * ‘Apache-SDAP’ directory prefix in the tar.gz files is a bit unusual, but 
fine.
 * DISCLAIMER-WIP lists a couple of issues (missing headers and potential 
licensing issue with test data); with SDAP approaching graduation, when do you 
plan to solve this issues?

Julian

 

> On May 1, 2023, at 10:20 AM, Nga Chung  wrote:
> 
> Hello Incubator PMC,
> 
> This is a call for a vote to release Apache SDAP (incubating) version
> 1.1.0-rc0.
> 
> The Apache SDAP community has voted to approve the release of Apache SDAP
> (incubating) version 1.1.0-rc0.
> 
> We now request the Incubator PMC review and vote on this release.
> 
> SDAP community thread:
> https://lists.apache.org/thread/z5llljrb10zrq39368xvpm7h0bto65kh
> 
> CHANGELOG for version 1.1.0 are available here:
> https://github.com/apache/incubator-sdap-ingester/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
> 
> Instructions for building docker images from source can be found here:
> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/build.rst
> Instructions for deploying locally to test can be found here:
> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/quickstart.rst
> 
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.1.0-rc0/
> 
> For convenience, the tags we built the release artifacts to be voted on
> from are 1.1.0-rc0:
> 
> - ingester:
> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.1.0-rc0
> - Commit: 8632b262eef9a33c816ec9b733c1ddc0156fa4c5
> 
> - nexus:
> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.1.0-rc0
> - Commit: 370190db8c4db86ce7837bc9fb3889c6658fac7f
> 
> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are
> voting on are as follows:
> 
> apache-sdap-ingester-1.1.0-incubating-src.tar.gz:
> ab243d84d0ab7dd33bc61ab84129080b1de0dc22f15d519950dda55ade41bf65cc8b02fe0b131c6640e0782613978c8ba9e9e573156a8657cb7ce14c599fbe7c
> 
> apache-sdap-nexus-1.1.0-incubating-src.tar.gz:
> c51340b040ffb4e82cdd9c8ba02ba3e8b54a9194826486bac781e966218491b700685b92effc200fd8a97ee10cffb301b618e6e9c73a3a21cd42d1b75a54670e
> 
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x1392A8A11801359247A803D8D2449E0EB5EF1E73
> 
> Please vote on releasing this package as Apache SDAP (incubating) 1.1.0.
> 
> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
> cast.
> 
> [ ] +1 Release this package as Apache SDAP (incubating) {version}
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> Thank you,
> Nga

Re: [RESULT] [VOTE] Release Apache SDAP (incubating) 1.1.0-rc0

[Julian Hyde]

Sorry I missed this vote. As a mentor, I consider it my duty to vote on all 
podling releases, but my email inbox has been full for the past few days, so I 
missed this one.

I saw the vote on general@ and I’ll vote shortly.

There were one or two votes that were a simple ‘+1’. I would ask those people 
to next time include rationale for their vote (checksums, headers, build, 
tests, which platform you used) because this encourages everyone to do a more 
thorough validation. When SDAP is a top-level project (hopefully soon!) then 
the voting PMC members are the only line of defense preventing a bad release.

Julian


> On May 1, 2023, at 9:33 AM, Nga Chung  wrote:
> 
> Hello everyone,
> 
> The vote has passed with 4 +1 votes.
> 
> Binding +1 votes:
> Thomas Huang
> Riley Kuttruff
> Stepheny Perez
> Thomas Loubrieu
> 
> Will start a vote on general@incubator
> 
> Thank you,
> Nga
> 
> On Wed, Apr 26, 2023 at 1:45 PM Nga Chung  wrote:
> 
>> Hello everyone,
>> 
>> This is the vote to approve Apache SDAP (incubating) release candidate rc0
>> for version 1.1.0.
>> 
>> CHANGELOG for version 1.1.0 are available here:
>> 
>> https://github.com/apache/incubator-sdap-ingester/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
>> 
>> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
>> 
>> Instructions for building docker images from source can be found here:
>> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/build.rst
>> Instructions for deploying locally to test can be found here:
>> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/quickstart.rst
>> 
>> The release files, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.1.0-rc0/
>> 
>> For convenience, the tags we built the release artifacts to be voted on
>> from are 1.1.0-rc0:
>> 
>> - ingester:
>> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.1.0-rc0
>> - Commit: 8632b262eef9a33c816ec9b733c1ddc0156fa4c5
>> 
>> - nexus:
>> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.1.0-rc0
>> - Commit: 370190db8c4db86ce7837bc9fb3889c6658fac7f
>> 
>> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are
>> voting on are as follows:
>> 
>> apache-sdap-ingester-1.1.0-incubating-src.tar.gz:
>> 
>> ab243d84d0ab7dd33bc61ab84129080b1de0dc22f15d519950dda55ade41bf65cc8b02fe0b131c6640e0782613978c8ba9e9e573156a8657cb7ce14c599fbe7c
>> 
>> apache-sdap-nexus-1.1.0-incubating-src.tar.gz:
>> 
>> c51340b040ffb4e82cdd9c8ba02ba3e8b54a9194826486bac781e966218491b700685b92effc200fd8a97ee10cffb301b618e6e9c73a3a21cd42d1b75a54670e
>> 
>> Release artifacts are signed with the following key:
>> https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x1392A8A11801359247A803D8D2449E0EB5EF1E73
>> 
>> Please vote on releasing this package as Apache SDAP (incubating) 1.1.0.
>> 
>> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
>> cast.
>> 
>> PLEASE NOTE: Do not reply with a vote from your work email as it can
>> mangle the links. To vote, go to
>> https://lists.apache.org/list.html?dev@sdap.apache.org, log in and send
>> your reply from there.
>> 
>> [ ] +1 Release this package as Apache SDAP (incubating) 1.1.0
>> [ ] +0 No opinion
>> [ ] -1 Do not release this package because ...
>> 
>> Thank you,
>> Nga
>> 

Re: [REPORT] February 2023 Report Feedback Requested

[Julian Hyde]

Good catch. Thank you. Fixed.

> On Jan 31, 2023, at 3:03 PM, Nga Chung  wrote:
> 
> Hi Julian,
> 
> I noticed that you provided comments under signed-off-by, but that the
> actual checkmark is missing. Not sure if it matters, but just wanted to
> point that out.
> 
> Thanks,
> Nga
> 
> On Mon, Jan 30, 2023 at 10:23 PM Nga Chung  wrote:
> 
>> Thanks Julian. The report has been updated accordingly.
>> 
>> Best,
>> Nga
>> 
>> 
>> 
>> On Mon, Jan 30, 2023 at 7:08 PM Julian Hyde 
>> wrote:
>> 
>>> Thanks for completing this in good time. I will sign off now, but feel
>>> free to make any of the following edits:
>>> 
>>> * I don’t think "Provide promotional materials (news article, video
>>> tutorials, etc.)” is a blocker to graduation.
>>> 
>>> * I’d remove the lists of completed, new/updated issues in ‘How has the
>>> project developed’. The main item in that section is the first release. You
>>> can mention X bugs completed and Y bugs new/updated if you wish.
>>> 
>>> * Change the line “[X] Working towards next release” to “[X] Working
>>> towards first release”. The first release is a significant milestone, and
>>> now it’s done. :)
>>> 
>>> * Replace "One new member was invited to join in October 2022.” with
>>> “ was added as a committer on ” provided that that person
>>> accepted the invitation.
>>> 
>>> 
>>> Julian
>>> 
>>>> On Jan 30, 2023, at 5:41 PM, Nga Chung  wrote:
>>>> 
>>>> Hi everyone,
>>>> 
>>>> A draft of SDAP status report has been added to the wiki:
>>>> https://cwiki.apache.org/confluence/display/INCUBATOR/February2023#sdap
>>>> 
>>>> Please review and let me know if changes are needed. Report is due this
>>>> Wednesday, February 1st. Sorry for the last minute request.
>>>> 
>>>> Thanks,
>>>> Nga
>>> 
>>> 

Re: [REPORT] February 2023 Report Feedback Requested

[Julian Hyde]

Thanks for completing this in good time. I will sign off now, but feel free to 
make any of the following edits:

* I don’t think "Provide promotional materials (news article, video tutorials, 
etc.)” is a blocker to graduation.

* I’d remove the lists of completed, new/updated issues in ‘How has the project 
developed’. The main item in that section is the first release. You can mention 
X bugs completed and Y bugs new/updated if you wish.

* Change the line “[X] Working towards next release” to “[X] Working towards 
first release”. The first release is a significant milestone, and now it’s 
done. :)

* Replace "One new member was invited to join in October 2022.” with “ 
was added as a committer on ” provided that that person accepted the 
invitation.


Julian

> On Jan 30, 2023, at 5:41 PM, Nga Chung  wrote:
> 
> Hi everyone,
> 
> A draft of SDAP status report has been added to the wiki:
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2023#sdap
> 
> Please review and let me know if changes are needed. Report is due this
> Wednesday, February 1st. Sorry for the last minute request.
> 
> Thanks,
> Nga

Re: Release Next Steps

[Julian Hyde]

I want to repeat the point about making the next release.

Plan to make a new release, in about 2 months from now, with a
different release manager, and carry out the whole process on the dev
list.

Showing that the release process is reproducible is the single most
important thing that SDAP can do to get to graduation. The second
release will be much easier than the first.

Julian

On Wed, Jan 18, 2023 at 3:16 PM Julian Hyde  wrote:
>
> The downloads page shows up on both sdap.apache.org and
> sdap.incubator.apache.org for me. That you saw some inconsistency is
> not surprising - a little bit of caching on client and/or server side.
>
> That old saying about British weather equally applies to ASF
> infrastructure: if you don't like it, just wait five minutes. :)
>
> Julian
>
> On Wed, Jan 18, 2023 at 3:12 PM Riley Kuttruff  wrote:
> >
> > We have the download page live now so I think we can try to go for today 
> > unless you'd advise waiting a couple days for some more site work (namely 
> > the team page). Come to think of it, let's release on Friday (2023-01-20) 
> > to give us a little time to get everything in order.
> >
> > By the way, when adding the downloads page, I noticed it shows on 
> > sdap.apache.org but not sdap.incubator.apache.org. Is that expected?
> >
> > -Riley
> >
> > On 2023/01/18 23:06:46 Julian Hyde wrote:
> > > Ah, I can do that, as I’m on the Incubator PMC. Here are the fields 
> > > needed by the tool [1], and the values I intend to provide:
> > >
> > > Committee:
> > >   incubator-sdap
> > > Full version name: (Note: use a product name prefix if the PMC releases 
> > > multiple products)
> > >   1.0.0 (incubating)
> > > Date of release (-MM-DD): (Note: use 1970-01-01 to remove a release)
> > >   2023-01-??
> > >
> > > Let me know what you decide to be the release date.
> > >
> > > Julian
> > >
> > > [1] https://reporter.apache.org/addrelease.html?incubator-sdap
> > >
> > >
> > > > On Jan 18, 2023, at 2:38 PM, Riley Kuttruff  wrote:
> > > >
> > > > Julain,
> > > >
> > > > I'm attempting to register the release with the link you provided, but 
> > > > I am unable to do anything on that page. I just see a message saying 
> > > > "It doesn't look like you are on any PMCs"
> > > >
> > > > -Riley
> > > >
> > > > On 2023/01/18 02:44:35 Julian Hyde wrote:
> > > >> Congratulations to SDAP on getting the first release through the
> > > >> voting process! And thank you Riley for your huge efforts as release
> > > >> manager.
> > > >>
> > > >> The basic steps are to send a '[RESULT]' email, move the artifacts,
> > > >> add a "downloads" page to the site, and send an announcement. Here is
> > > >> a detailed list of steps:
> > > >>
> > > >> 1. Send the [RESULT] email to general@incubator.
> > > >>
> > > >> 2. Choose a release date. (I generally publish a release before ~4pm
> > > >> pacific time, so that my local date is the same as the UTC date.
> > > >> Prevents website inconsistencies.)
> > > >>
> > > >> 3. Register the release at https://reporter.apache.org.
> > > >>
> > > >> 4. It's worth checking that the site complies with branding
> > > >> requirements, since the announcement will generate traffic and
> > > >> scrutiny.
> > > >>
> > > >> 5. Compose the announcement, and send it to annou...@apache.org. They
> > > >> are moderated. They generally have a particular format, in particular,
> > > >> starting with a description of the project, and a description of why
> > > >> the release is notable. (Plenty of examples in the archive [1].) I'm
> > > >> conservative and write in plain text formatted at 60 characters, so
> > > >> that no one's client will do stupid wrapping. The first draft might be
> > > >> rejected, so I wouldn't send the announcement to dev@ until the
> > > >> message to announce@ goes through.
> > > >>
> > > >> 6. Add a template for the announcement email to the 'howto" for the
> > > >> next release manager.
> > > >>
> > > >> 7. Send out a tweet. Optionally, do some other promotional stuff, like
&g

Re: Release Next Steps

[Julian Hyde]

The downloads page shows up on both sdap.apache.org and
sdap.incubator.apache.org for me. That you saw some inconsistency is
not surprising - a little bit of caching on client and/or server side.

That old saying about British weather equally applies to ASF
infrastructure: if you don't like it, just wait five minutes. :)

Julian

On Wed, Jan 18, 2023 at 3:12 PM Riley Kuttruff  wrote:
>
> We have the download page live now so I think we can try to go for today 
> unless you'd advise waiting a couple days for some more site work (namely the 
> team page). Come to think of it, let's release on Friday (2023-01-20) to give 
> us a little time to get everything in order.
>
> By the way, when adding the downloads page, I noticed it shows on 
> sdap.apache.org but not sdap.incubator.apache.org. Is that expected?
>
> -Riley
>
> On 2023/01/18 23:06:46 Julian Hyde wrote:
> > Ah, I can do that, as I’m on the Incubator PMC. Here are the fields needed 
> > by the tool [1], and the values I intend to provide:
> >
> > Committee:
> >   incubator-sdap
> > Full version name: (Note: use a product name prefix if the PMC releases 
> > multiple products)
> >   1.0.0 (incubating)
> > Date of release (-MM-DD): (Note: use 1970-01-01 to remove a release)
> >   2023-01-??
> >
> > Let me know what you decide to be the release date.
> >
> > Julian
> >
> > [1] https://reporter.apache.org/addrelease.html?incubator-sdap
> >
> >
> > > On Jan 18, 2023, at 2:38 PM, Riley Kuttruff  wrote:
> > >
> > > Julain,
> > >
> > > I'm attempting to register the release with the link you provided, but I 
> > > am unable to do anything on that page. I just see a message saying "It 
> > > doesn't look like you are on any PMCs"
> > >
> > > -Riley
> > >
> > > On 2023/01/18 02:44:35 Julian Hyde wrote:
> > >> Congratulations to SDAP on getting the first release through the
> > >> voting process! And thank you Riley for your huge efforts as release
> > >> manager.
> > >>
> > >> The basic steps are to send a '[RESULT]' email, move the artifacts,
> > >> add a "downloads" page to the site, and send an announcement. Here is
> > >> a detailed list of steps:
> > >>
> > >> 1. Send the [RESULT] email to general@incubator.
> > >>
> > >> 2. Choose a release date. (I generally publish a release before ~4pm
> > >> pacific time, so that my local date is the same as the UTC date.
> > >> Prevents website inconsistencies.)
> > >>
> > >> 3. Register the release at https://reporter.apache.org.
> > >>
> > >> 4. It's worth checking that the site complies with branding
> > >> requirements, since the announcement will generate traffic and
> > >> scrutiny.
> > >>
> > >> 5. Compose the announcement, and send it to annou...@apache.org. They
> > >> are moderated. They generally have a particular format, in particular,
> > >> starting with a description of the project, and a description of why
> > >> the release is notable. (Plenty of examples in the archive [1].) I'm
> > >> conservative and write in plain text formatted at 60 characters, so
> > >> that no one's client will do stupid wrapping. The first draft might be
> > >> rejected, so I wouldn't send the announcement to dev@ until the
> > >> message to announce@ goes through.
> > >>
> > >> 6. Add a template for the announcement email to the 'howto" for the
> > >> next release manager.
> > >>
> > >> 7. Send out a tweet. Optionally, do some other promotional stuff, like
> > >> adding a 'news' item to the site, posting a video to youtube. (What
> > >> about a quick video of downloading the release and starting a server
> > >> or whatever you consider to be the minimal 'smoke test' demo?)
> > >>
> > >> 8. In Calcite, we mark bugs 'fixed' as the patches are merged, and we
> > >> only mark the bugs 'closed' after the release has happened. If SDAP
> > >> has a similar process, close those bugs.
> > >>
> > >> 9. Finalize that 'howto' for the next release manager, add it
> > >> somewhere that they can find it, and post it to dev@.
> > >>
> > >> Maybe someone else could help with the site and promotional work?
> > >> Ril

Re: Release Next Steps

[Julian Hyde]

Ah, I can do that, as I’m on the Incubator PMC. Here are the fields needed by 
the tool [1], and the values I intend to provide:

Committee:
  incubator-sdap
Full version name: (Note: use a product name prefix if the PMC releases 
multiple products)
  1.0.0 (incubating)
Date of release (-MM-DD): (Note: use 1970-01-01 to remove a release)
  2023-01-??

Let me know what you decide to be the release date.

Julian

[1] https://reporter.apache.org/addrelease.html?incubator-sdap


> On Jan 18, 2023, at 2:38 PM, Riley Kuttruff  wrote:
> 
> Julain,
> 
> I'm attempting to register the release with the link you provided, but I am 
> unable to do anything on that page. I just see a message saying "It doesn't 
> look like you are on any PMCs"
> 
> -Riley
> 
> On 2023/01/18 02:44:35 Julian Hyde wrote:
>> Congratulations to SDAP on getting the first release through the
>> voting process! And thank you Riley for your huge efforts as release
>> manager.
>> 
>> The basic steps are to send a '[RESULT]' email, move the artifacts,
>> add a "downloads" page to the site, and send an announcement. Here is
>> a detailed list of steps:
>> 
>> 1. Send the [RESULT] email to general@incubator.
>> 
>> 2. Choose a release date. (I generally publish a release before ~4pm
>> pacific time, so that my local date is the same as the UTC date.
>> Prevents website inconsistencies.)
>> 
>> 3. Register the release at https://reporter.apache.org.
>> 
>> 4. It's worth checking that the site complies with branding
>> requirements, since the announcement will generate traffic and
>> scrutiny.
>> 
>> 5. Compose the announcement, and send it to annou...@apache.org. They
>> are moderated. They generally have a particular format, in particular,
>> starting with a description of the project, and a description of why
>> the release is notable. (Plenty of examples in the archive [1].) I'm
>> conservative and write in plain text formatted at 60 characters, so
>> that no one's client will do stupid wrapping. The first draft might be
>> rejected, so I wouldn't send the announcement to dev@ until the
>> message to announce@ goes through.
>> 
>> 6. Add a template for the announcement email to the 'howto" for the
>> next release manager.
>> 
>> 7. Send out a tweet. Optionally, do some other promotional stuff, like
>> adding a 'news' item to the site, posting a video to youtube. (What
>> about a quick video of downloading the release and starting a server
>> or whatever you consider to be the minimal 'smoke test' demo?)
>> 
>> 8. In Calcite, we mark bugs 'fixed' as the patches are merged, and we
>> only mark the bugs 'closed' after the release has happened. If SDAP
>> has a similar process, close those bugs.
>> 
>> 9. Finalize that 'howto' for the next release manager, add it
>> somewhere that they can find it, and post it to dev@.
>> 
>> Maybe someone else could help with the site and promotional work?
>> Riley has done a huge amount of work over the holiday period to get
>> this release out. While you're adding a downloads page to the site,
>> update the team page [2], and a link to Slack.
>> 
>> 10. Make another release in 2 months, to prove that the muscle still works.
>> 
>> Julian
>> 
>> [1] https://lists.apache.org/list?annou...@apache.org
>> 
>> [2] https://sdap.apache.org/team
>> 
>> On Tue, Jan 17, 2023 at 6:36 PM Riley Kuttruff  wrote:
>>> 
>>> So it looks like the IPMC vote passed. I'm assuming the next/final steps 
>>> are 1) moving the release artifacts to the dist/release area and 2) sending 
>>> an announcement, correct?
>>> 
>>> - Riley
>>> 
>>> On 2023/01/17 17:46:31 Nga Chung wrote:
>>>> This was announced in the DISCUSS thread here [1] so maybe it was missed by
>>>> folks.
>>>> 
>>>> Thanks for your guidance regarding the meeting format. We'll make sure to
>>>> follow and send out a summary.
>>>> 
>>>> Best,
>>>> Nga
>>>> 
>>>> [1] https://lists.apache.org/thread/b2z796mfzfl6h0gj7m8mo8x25yt4dxoh
>>>> 
>>>> On Tue, Jan 17, 2023 at 9:38 AM Julian Hyde  wrote:
>>>> 
>>>>> Thanks for the heads up. Was this announced earlier?
>>>>> 
>>>>> In Apache we need to be inclusive of people who prefer asynchronous
>>>>> communication (in other time zones, for example) so be sure to not
>>>>> make any decisions at the meeting, and send a summary of the meeting
>>>>> to this list. A good pattern is to start discussions at the meeting
>>>>> and then convert them into email discussions on the dev list.
>>>>> 
>>>>> Julian
>>>>> 
>>>>> On Tue, Jan 17, 2023 at 9:24 AM Nga Chung  wrote:
>>>>>> 
>>>>>> Hi all,
>>>>>> 
>>>>>> Our first SDAP monthly meeting is today at 15:00 - 16:00 Pacific time.
>>>>>> 
>>>>>> Join from the meeting link
>>>>>> https://jpl.webex.com/jpl/j.php?MTID=m6d205ee391099975ab22ae1b4a65df53
>>>>>> 
>>>>>> Join by meeting number
>>>>>> Meeting number (access code): 2761 748 8734
>>>>>> Meeting password: MjdFissq569
>>>>>> 
>>>>>> Best,
>>>>>> Nga
>>>>> 
>>>> 
>> 

Re: Release Next Steps

[Julian Hyde]

Congratulations to SDAP on getting the first release through the
voting process! And thank you Riley for your huge efforts as release
manager.

The basic steps are to send a '[RESULT]' email, move the artifacts,
add a "downloads" page to the site, and send an announcement. Here is
a detailed list of steps:

1. Send the [RESULT] email to general@incubator.

2. Choose a release date. (I generally publish a release before ~4pm
pacific time, so that my local date is the same as the UTC date.
Prevents website inconsistencies.)

3. Register the release at https://reporter.apache.org.

4. It's worth checking that the site complies with branding
requirements, since the announcement will generate traffic and
scrutiny.

5. Compose the announcement, and send it to annou...@apache.org. They
are moderated. They generally have a particular format, in particular,
starting with a description of the project, and a description of why
the release is notable. (Plenty of examples in the archive [1].) I'm
conservative and write in plain text formatted at 60 characters, so
that no one's client will do stupid wrapping. The first draft might be
rejected, so I wouldn't send the announcement to dev@ until the
message to announce@ goes through.

6. Add a template for the announcement email to the 'howto" for the
next release manager.

7. Send out a tweet. Optionally, do some other promotional stuff, like
adding a 'news' item to the site, posting a video to youtube. (What
about a quick video of downloading the release and starting a server
or whatever you consider to be the minimal 'smoke test' demo?)

8. In Calcite, we mark bugs 'fixed' as the patches are merged, and we
only mark the bugs 'closed' after the release has happened. If SDAP
has a similar process, close those bugs.

9. Finalize that 'howto' for the next release manager, add it
somewhere that they can find it, and post it to dev@.

Maybe someone else could help with the site and promotional work?
Riley has done a huge amount of work over the holiday period to get
this release out. While you're adding a downloads page to the site,
update the team page [2], and a link to Slack.

10. Make another release in 2 months, to prove that the muscle still works.

Julian

[1] https://lists.apache.org/list?annou...@apache.org

[2] https://sdap.apache.org/team

On Tue, Jan 17, 2023 at 6:36 PM Riley Kuttruff  wrote:
>
> So it looks like the IPMC vote passed. I'm assuming the next/final steps are 
> 1) moving the release artifacts to the dist/release area and 2) sending an 
> announcement, correct?
>
> - Riley
>
> On 2023/01/17 17:46:31 Nga Chung wrote:
> > This was announced in the DISCUSS thread here [1] so maybe it was missed by
> > folks.
> >
> > Thanks for your guidance regarding the meeting format. We'll make sure to
> > follow and send out a summary.
> >
> > Best,
> > Nga
> >
> > [1] https://lists.apache.org/thread/b2z796mfzfl6h0gj7m8mo8x25yt4dxoh
> >
> > On Tue, Jan 17, 2023 at 9:38 AM Julian Hyde  wrote:
> >
> > > Thanks for the heads up. Was this announced earlier?
> > >
> > > In Apache we need to be inclusive of people who prefer asynchronous
> > > communication (in other time zones, for example) so be sure to not
> > > make any decisions at the meeting, and send a summary of the meeting
> > > to this list. A good pattern is to start discussions at the meeting
> > > and then convert them into email discussions on the dev list.
> > >
> > > Julian
> > >
> > > On Tue, Jan 17, 2023 at 9:24 AM Nga Chung  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Our first SDAP monthly meeting is today at 15:00 - 16:00 Pacific time.
> > > >
> > > > Join from the meeting link
> > > > https://jpl.webex.com/jpl/j.php?MTID=m6d205ee391099975ab22ae1b4a65df53
> > > >
> > > > Join by meeting number
> > > > Meeting number (access code): 2761 748 8734
> > > > Meeting password: MjdFissq569
> > > >
> > > > Best,
> > > > Nga
> > >
> >

Re: SDAP Monthly Meeting January 17 at 15:00 US/Pacific, 23:00 UTC

[Julian Hyde]

Thanks for the heads up. Was this announced earlier?

In Apache we need to be inclusive of people who prefer asynchronous
communication (in other time zones, for example) so be sure to not
make any decisions at the meeting, and send a summary of the meeting
to this list. A good pattern is to start discussions at the meeting
and then convert them into email discussions on the dev list.

Julian

On Tue, Jan 17, 2023 at 9:24 AM Nga Chung  wrote:
>
> Hi all,
>
> Our first SDAP monthly meeting is today at 15:00 - 16:00 Pacific time.
>
> Join from the meeting link
> https://jpl.webex.com/jpl/j.php?MTID=m6d205ee391099975ab22ae1b4a65df53
>
> Join by meeting number
> Meeting number (access code): 2761 748 8734
> Meeting password: MjdFissq569
>
> Best,
> Nga

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc3

[Julian Hyde]

Downloaded artifacts, checked signatures and hashes, checked NOTICE
(noted updated year), LICENSE, DISCLAIMER-WIP, file headers.

I compared each tarball with the contents of git as of the commit
described in the voe email. I noted that gradle-wrapper.jar is no
longer in apache-sdap-nexusproto tarball.

Thanks for adding a prefix to the files in the tar.gz files; per
standard practice I would have skipped the 'Apache-SDAP' prefix and
left only the 'apache-sdap-xxx-1.0.0-incubating-src' prefix; this is
not a reason to vote against.

Here is my vote: +1 (binding)

Julian

On Wed, Jan 4, 2023 at 1:52 PM Riley Kuttruff  wrote:
>
> Hello everyone,
>
> This is the vote to approve Apache SDAP (incubating) release candidate rc3 
> for version 1.0.0.
>
> Changes made between previous candidate (rc2) and this one (rc3) are as
> follows:
> - Switched to DISCLAIMER-WIP
> - Removed Gradle wrapper from nexusproto source distribution & updated 
> developer build instruction for nexusproto
> - Updated release artifact structure to extract to single common directory & 
> updated release build instructions accordingly
> - Corrected NOTICE file and updated copyright statement to reflect correct 
> years
> - Updated naming for release artifacts 
> (apache-sdap-{module}-{version}-src.tar.gz -> 
> apache-sdap-{module}-{version}-incubating-src.tar.gz)
>
> Instructions for building docker images from source can be found here:
> https://github.com/apache/incubator-sdap-nexus/blob/b6d002cc7f7192820ce9f4443cee9867d3bdbdd0/docs/build.rst
> Instructions for deploying locally to test can be found here:
> https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc3/
>
> For convenience, the tags we built the release artifacts to be voted on from 
> are 1.0.0-rc3:
>
> - nexusproto:
> - URL: https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc3
> - Commit: cc35046cd72d9e749a33b697c58e5ca9ccec5711
> - ingester:
> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc3
> - Commit: ae25aae70cc9b91bd0b05788e88e77edc77f0fd3
> - nexus:
> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc3
> - Commit: bf65205c8dae838d95843de34c94d6d46a579308
>
> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are voting 
> on are as follows:
>
> apache-sdap-ingester-1.0.0-incubating-src.tar.gz:
> f97f932d3f9c937316fd07f17d27af6f567681c9b9c5e3a4d9813a3372673e829455c96eed10e356200d7a6829d0ec178aff458b8138f0656698f06ca0e8d413
>
> apache-sdap-nexus-1.0.0-incubating-src.tar.gz:
> 10d491484ff23cf670fd955c576deadea99d976e776b07457f0b38df9c8b06018e0a54888a5ee0704d44a01b83e57b518de6d72ad6d5b28b14cf557054ea54ca
>
> apache-sdap-nexusproto-1.0.0-incubating-src.tar.gz:
> 1a42e02e859de639fc44a4900dccfa9815dbbde8aabf705600478ccf0d6d46cb98d2a8f76841cbce3bff15f08739725dc39af5e0e8ca052fe6dbf2ed2ed26032
>
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x4e98c4a32026656e14e0b570fc20035a010e3b7b
>
> Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.
>
> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are cast.
>
> PLEASE NOTE: Do not reply with a vote from your work email as it can mangle 
> the links. To vote, go to 
> https://lists.apache.org/list.html?dev@sdap.apache.org, log in and send your 
> reply from there.
>
> [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Thank you,
> Riley

[jira] [Commented] (SDAP-424) Inclusion of precompiled code (gradle-wrapper.jar) in release

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654319#comment-17654319
 ] 

Julian Hyde commented on SDAP-424:
--

We had the same problem in CALCITE-4575. The solution was to exclude 
{{gradlew.bat}}, {{gradlew}} and {{gradle/wrapper/*}} from the src.tar.gz file. 
(We did not remove these files from the git repo).

We also modified the build instructions to say that if you were building from a 
source tarball you must use '{{gradle build}}'. (If building from git you can 
use '{{./gradlew build}}'.)

> Inclusion of precompiled code (gradle-wrapper.jar) in release
> -
>
> Key: SDAP-424
> URL: https://issues.apache.org/jira/browse/SDAP-424
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Riley Kuttruff
>Priority: Major
>
> In nexusproto
>  
> This is not permitted by ASF policy
>  
> See: https://issues.apache.org/jira/browse/LEGAL-570



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] RC2 IPMC vote thread

[Julian Hyde]

Thanks for your answer, Frank. I thought I'd ask just in case the
project had gotten stuck in a place not needed by current
requirements.

Let's definitely continue the discussion after the release. All of the
components that are part of a project should be released from time to
time, and, I dare say, at least once before graduation. As a reviewer,
it's of course easier to review a single release that contains a
single .tar.gz file (even if it contains the source code of ten
components). But that wouldn't make sense if those components are
versioned independently.

We're almost there with the release. The toughest part of every
podling's life cycle is the first time Justin Mclean reviews their
release artifacts. He doesn't miss a thing. We're over that hump now
-- huge thanks, Riley! -- so let's keep going. I predict there will be
one more RC and it will sail through both the dev@sdap and the
general@incubator votes.

Julian


On Tue, Jan 3, 2023 at 3:00 PM Frank Greguska  wrote:
>
> I'll do my best.
>
> Technically, SDAP has 10 repositories:
> https://github.com/apache?utf8=%E2%9C%93&q=incubator-sdap&type=&language=
>
> A few of those should be archived/cleaned up at this point but that hasn't
> been a priority. In general though, SDAP is not one piece of software. It
> is a suite of software needed to accomplish the goal of running an
> integrated data analytic center for Big Science problems. This has been the
> subject of discussion for a while; should SDAP have one single major
> version that encompasses all components or should they each be
> versioned/packaged independently? We've decided for this first go around to
> just create one artifact with the most important/commonly used components
> needed to say SDAP is installed.
>
> - Frank
>
> On Tue, Jan 3, 2023 at 2:35 PM Julian Hyde  wrote:
>
> > Can someone explain why SDAP has 3 separate GitHub repositories rather
> > than one?
> >
> > It's not my place to suggest changes. But if the separate repositories
> > are causing more pain than joy, it might be worth reconsidering.
> > (Several times I have typed in
> > https://github.com/apache/incubator-sdap/ and been surprised that
> > there's nothing there.)
> >
> > Julian
> >
> > On Tue, Jan 3, 2023 at 2:20 PM Riley Kuttruff  wrote:
> > >
> > > Thanks. This change will require an update to the build instructions. I
> > have an open pull request to get that done [1] that I would like to get
> > approved and merged before trying the next rc.
> > >
> > > [1] https://github.com/apache/incubator-sdap-nexus/pull/225
> > >
> > > On 2023/01/03 21:50:30 Frank Greguska wrote:
> > > > Makes sense to me.
> > > >
> > > > - Frank
> > > >
> > > > On Tue, Jan 3, 2023 at 1:16 PM Riley Kuttruff  wrote:
> > > >
> > > > > I've been looking into better structuring our release artifacts and
> > was
> > > > > wondering if anyone had any opinions on how I've updated it:
> > > > >
> > > > >
> > > > > > (sdap-nexus) rileykk@MT-110978 apache-sdap-1.0.0-rc3 % tar -tf
> > > > > apache-sdap-nexusproto-1.0.0-src-incubating.tar.gz
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/.gitignore
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/CONTRIBUTING.md
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/DISCLAIMER-WIP
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/LICENSE
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/NOTICE
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/README
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/README.md
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/build.gradle
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle.properties
> > > > > >
> > > > >
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle/wrapper/gradle-wrapper.jar
> > > > > >
> > > > >
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle/wrapper/gradle-wrapper.properties
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradlew
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradlew.bat
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/jenkins/Jenkinsfile
> > > > > >
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/jenkins/pipeline-syntax.gdsl
> > > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/nexuspro

Re: [DISCUSS] RC2 IPMC vote thread

[Julian Hyde]

Can someone explain why SDAP has 3 separate GitHub repositories rather than one?

It's not my place to suggest changes. But if the separate repositories
are causing more pain than joy, it might be worth reconsidering.
(Several times I have typed in
https://github.com/apache/incubator-sdap/ and been surprised that
there's nothing there.)

Julian

On Tue, Jan 3, 2023 at 2:20 PM Riley Kuttruff  wrote:
>
> Thanks. This change will require an update to the build instructions. I have 
> an open pull request to get that done [1] that I would like to get approved 
> and merged before trying the next rc.
>
> [1] https://github.com/apache/incubator-sdap-nexus/pull/225
>
> On 2023/01/03 21:50:30 Frank Greguska wrote:
> > Makes sense to me.
> >
> > - Frank
> >
> > On Tue, Jan 3, 2023 at 1:16 PM Riley Kuttruff  wrote:
> >
> > > I've been looking into better structuring our release artifacts and was
> > > wondering if anyone had any opinions on how I've updated it:
> > >
> > >
> > > > (sdap-nexus) rileykk@MT-110978 apache-sdap-1.0.0-rc3 % tar -tf
> > > apache-sdap-nexusproto-1.0.0-src-incubating.tar.gz
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/.gitignore
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/CONTRIBUTING.md
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/DISCLAIMER-WIP
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/LICENSE
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/NOTICE
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/README
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/README.md
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/build.gradle
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle.properties
> > > >
> > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle/wrapper/gradle-wrapper.jar
> > > >
> > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle/wrapper/gradle-wrapper.properties
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradlew
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradlew.bat
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/jenkins/Jenkinsfile
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/jenkins/pipeline-syntax.gdsl
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/nexusproto.iml
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/settings.gradle
> > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/proto/DataTile.proto
> > > >
> > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/python/nexusproto/__init__.py
> > > >
> > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/python/nexusproto/serialization.py
> > > >
> > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/python/nexusproto/setup.py
> > > > (sdap-nexus) rileykk@MT-110978 apache-sdap-1.0.0-rc3 % tar -tf
> > > apache-sdap-nexus-1.0.0-src-incubating.tar.gz
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/.gitignore
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/CHANGELOG.md
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/CONTRIBUTING.md
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/DISCLAIMER-WIP
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/LICENSE
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/NOTICE
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/README
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/README.md
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/VERSION.txt
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.gitignore
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/analysis.iml
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/encodings.xml
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/misc.xml
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/modules.xml
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/vcs.xml
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/README.md
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/__init__.py
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/conda-requirements.txt
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/package-list.txt
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/setup.py
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/static/index.html
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/test.py
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/README.md
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/__init__.py
> > > >
> > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms/StandardDeviationSearch_test.py
> > > >
> > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms/longitudelatitudemap_test.py
> > > >
> > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms/test_base_doms_handler.py
> > > >
> > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms/test_subsetter.py
> > > >
> > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms_spark/__init__.py
> > > >
> > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms_spark/test_matchup.py
> > > >
> > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms_spark/test_timeseriesspark.py
> > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/test

[jira] [Commented] (SDAP-422) Prefix release tarball paths with top level directory for easy cleanup post build

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654196#comment-17654196
 ] 

Julian Hyde commented on SDAP-422:
--

A more conventional structure would be to use the base name of the tar file, 
like this:
{code}
% tar -tf apache-sdap-ingester-1.0.0-src-incubating.tar.gz
apache-sdap-ingester-1.0.0-src-incubating/.github/workflows/github-dev-release.yml
apache-sdap-ingester-1.0.0-src-incubating/.github/workflows/pypi-tag-release.yml
apache-sdap-ingester-1.0.0-src-incubating/.gitignore
{code}

For extra credit -- feel free to skip this one if it's not easy -- the release 
name is 'Apache SDAP Ingester 1.0.0 (incubating)' and therefore the prefix 
should be 'apache-sdap-ingester-1.0.0-incubating-src'. This transposes 'src' 
and 'incubating'.

> Prefix release tarball paths with top level directory for easy cleanup post 
> build
> -
>
> Key: SDAP-422
> URL: https://issues.apache.org/jira/browse/SDAP-422
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Riley Kuttruff
>Priority: Minor
>
> This will require minor changes to release packaging workflow & the build 
> documentation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [EXTERNAL] Re: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

Yes, I'm sure the IPMC would appreciate that courtesy. (No need to
restart the vote, just send a follow-up email to the vote thread.)

(If the votes are still trickling in slowly as we approach the
deadline, there's no need to stop at the deadline. The 72 hours - or
whatever period you choose in your email - is just a *minimum*
duration. As we approach the deadline, I'll start nagging people to
vote, if necessary.)

Julian

On Fri, Dec 23, 2022 at 10:51 AM Riley Kuttruff  wrote:
>
> Also, I'm wondering if it would be possible/worthwhile to extend the 
> timeframe of the vote in general@, given that it's coming up on a holiday 
> weekend.
>
> On 2022/12/23 17:44:44 Julian Hyde wrote:
> > Did you see my remark about tar file structure in
> > https://lists.apache.org/thread/8h5fw3cpx81w7nmm385hlx261sbo9m0n ?
> >
> > On Thu, Dec 22, 2022 at 7:21 PM Riley Kuttruff  wrote:
> >
> > > I understand. Jira cases have been created and the general@ thread has
> > > been made as well.
> > >
> > > On 2022/12/23 00:12:17 Julian Hyde wrote:
> > > > Yes. I didn’t want to use the word “issue” twice in one sentence.
> > > >
> > > > Julian
> > > >
> > > > > On Dec 22, 2022, at 15:51, Riley Kuttruff  wrote:
> > > > >
> > > > > Thanks Julian, I'll try to get the thread started by EOD.
> > > > >
> > > > > Can I ask what you mean by logging cases? Is that like creating issues
> > > on Jira?
> > > > >
> > > > > Thanks,
> > > > > Riley
> > > > >
> > > > >> On 2022/12/22 23:37:44 Julian Hyde wrote:
> > > > >> PS Don’t make a new RC. The IPMC will vote on the exact same
> > > artifacts.
> > > > >>
> > > > >> Julian
> > > > >>
> > > > >>>> On Dec 22, 2022, at 15:20, Julian Hyde 
> > > wrote:
> > > > >>>
> > > > >>> Next step is to carry out a vote on the
> > > gene...@incubator.apache.org list.
> > > > >>>
> > > > >>> This may seem like unnecessary bureaucracy; for which I apologize.
> > > The reason is that only a PMC (in this case the Incubator PMC, IPMC) may
> > > release code on behalf of the ASF.
> > > > >>>
> > > > >>> Practically speaking, the release will receive due diligence by
> > > experts in the IPMC. It’s likely that they will find problems, and if so,
> > > we may need another RC, and two votes, to resolve them. Please be patient,
> > > because this is the learning process.
> > > > >>>
> > > > >>> Riley, Glad to see that you have sent a RESULT email already. Please
> > > start a vote thread on general@, referencing the thread on dev@. Good
> > > luck!
> > > > >>>
> > > > >>> Can you also log cases for the issues I noted during the vote. The
> > > IPMC tends to be lenient for the first release, especially if the podling
> > > is learning and improving.
> > > > >>>
> > > > >>> Julian
> > > > >>>
> > > > >>>> On Dec 22, 2022, at 11:44, Riley Kuttruff  wrote:
> > > > >>>>
> > > > >>>> So the vote for rc2 passed. What are our next steps? Do I push the
> > > .tar.gz and .asc files to
> > > https://dist.apache.org/repos/dist/incubator/sdap ?
> > > > >>>>
> > > > >>>>>> On 2022/12/14 20:04:29 Riley Kuttruff wrote:
> > > > >>>>> I verified, built and tested the release tarballs in the same
> > > manner I did before and it passed just the same.
> > > > >>>>>
> > > > >>>>> I believe it's compliant with ASF policy but I'm not 100% sure so
> > > I'm holding off on the vote.
> > > > >>>>> - We added DISCLAIMER & README files to all release tarballs
> > > > >>>>> - I went through and checked MOST of the files for the ASF license
> > > headers and added them where needed though I may have missed something
> > > > >>>>>
> > > > >>>>>> On 2022/12/13 19:36:26 Nga Chung wrote:
> > > > >>>>>> HI all,
> > > > >>>>>>
> > > > >>>>>> I started a VOTE thread for 1.0.0rc2, but

Re: [EXTERNAL] Re: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

Did you see my remark about tar file structure in
https://lists.apache.org/thread/8h5fw3cpx81w7nmm385hlx261sbo9m0n ?

On Thu, Dec 22, 2022 at 7:21 PM Riley Kuttruff  wrote:

> I understand. Jira cases have been created and the general@ thread has
> been made as well.
>
> On 2022/12/23 00:12:17 Julian Hyde wrote:
> > Yes. I didn’t want to use the word “issue” twice in one sentence.
> >
> > Julian
> >
> > > On Dec 22, 2022, at 15:51, Riley Kuttruff  wrote:
> > >
> > > Thanks Julian, I'll try to get the thread started by EOD.
> > >
> > > Can I ask what you mean by logging cases? Is that like creating issues
> on Jira?
> > >
> > > Thanks,
> > > Riley
> > >
> > >> On 2022/12/22 23:37:44 Julian Hyde wrote:
> > >> PS Don’t make a new RC. The IPMC will vote on the exact same
> artifacts.
> > >>
> > >> Julian
> > >>
> > >>>> On Dec 22, 2022, at 15:20, Julian Hyde 
> wrote:
> > >>>
> > >>> Next step is to carry out a vote on the
> gene...@incubator.apache.org list.
> > >>>
> > >>> This may seem like unnecessary bureaucracy; for which I apologize.
> The reason is that only a PMC (in this case the Incubator PMC, IPMC) may
> release code on behalf of the ASF.
> > >>>
> > >>> Practically speaking, the release will receive due diligence by
> experts in the IPMC. It’s likely that they will find problems, and if so,
> we may need another RC, and two votes, to resolve them. Please be patient,
> because this is the learning process.
> > >>>
> > >>> Riley, Glad to see that you have sent a RESULT email already. Please
> start a vote thread on general@, referencing the thread on dev@. Good
> luck!
> > >>>
> > >>> Can you also log cases for the issues I noted during the vote. The
> IPMC tends to be lenient for the first release, especially if the podling
> is learning and improving.
> > >>>
> > >>> Julian
> > >>>
> > >>>> On Dec 22, 2022, at 11:44, Riley Kuttruff  wrote:
> > >>>>
> > >>>> So the vote for rc2 passed. What are our next steps? Do I push the
> .tar.gz and .asc files to
> https://dist.apache.org/repos/dist/incubator/sdap ?
> > >>>>
> > >>>>>> On 2022/12/14 20:04:29 Riley Kuttruff wrote:
> > >>>>> I verified, built and tested the release tarballs in the same
> manner I did before and it passed just the same.
> > >>>>>
> > >>>>> I believe it's compliant with ASF policy but I'm not 100% sure so
> I'm holding off on the vote.
> > >>>>> - We added DISCLAIMER & README files to all release tarballs
> > >>>>> - I went through and checked MOST of the files for the ASF license
> headers and added them where needed though I may have missed something
> > >>>>>
> > >>>>>> On 2022/12/13 19:36:26 Nga Chung wrote:
> > >>>>>> HI all,
> > >>>>>>
> > >>>>>> I started a VOTE thread for 1.0.0rc2, but can someone else please
> volunteer
> > >>>>>> to take over as release manager because I will be away 12/16/22 -
> 1/16/23.
> > >>>>>>
> > >>>>>> I captured initial release instructions here
> > >>>>>>
> https://github.com/ngachung/incubator-sdap-nexus/blob/SDAP-414/docs/release.rst
> > >>>>>>
> > >>>>>> Thanks,
> > >>>>>> Nga
> > >>>>>>
> > >>>>>>
> > >>>>>>> On Wed, Dec 7, 2022 at 1:07 AM Julian Hyde 
> wrote:
> > >>>>>>
> > >>>>>>> By the way, I wouldn't create a new RC for the vote. Just vote
> on the
> > >>>>>>> RC1 you already have. We know we'll need to iterate through a
> few RCs
> > >>>>>>> before we get a good one.
> > >>>>>>>
> > >>>>>>> On Wed, Dec 7, 2022 at 1:05 AM Julian Hyde 
> wrote:
> > >>>>>>>>
> > >>>>>>>> Hey, that looks pretty good! In fact it looks a lot like an
> Apache
> > >>>>>>> release.
> > >>>>>>>>
> > >>>>>>>> A few things:
> > >>>>>>>

Re: [EXTERNAL] Re: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

Yes. I didn’t want to use the word “issue” twice in one sentence.

Julian

> On Dec 22, 2022, at 15:51, Riley Kuttruff  wrote:
> 
> Thanks Julian, I'll try to get the thread started by EOD.
> 
> Can I ask what you mean by logging cases? Is that like creating issues on 
> Jira?
> 
> Thanks,
> Riley
> 
>> On 2022/12/22 23:37:44 Julian Hyde wrote:
>> PS Don’t make a new RC. The IPMC will vote on the exact same artifacts. 
>> 
>> Julian
>> 
>>>> On Dec 22, 2022, at 15:20, Julian Hyde  wrote:
>>> 
>>> Next step is to carry out a vote on the gene...@incubator.apache.org list. 
>>> 
>>> This may seem like unnecessary bureaucracy; for which I apologize. The 
>>> reason is that only a PMC (in this case the Incubator PMC, IPMC) may 
>>> release code on behalf of the ASF. 
>>> 
>>> Practically speaking, the release will receive due diligence by experts in 
>>> the IPMC. It’s likely that they will find problems, and if so, we may need 
>>> another RC, and two votes, to resolve them. Please be patient, because this 
>>> is the learning process. 
>>> 
>>> Riley, Glad to see that you have sent a RESULT email already. Please start 
>>> a vote thread on general@, referencing the thread on dev@. Good luck!
>>> 
>>> Can you also log cases for the issues I noted during the vote. The IPMC 
>>> tends to be lenient for the first release, especially if the podling is 
>>> learning and improving. 
>>> 
>>> Julian
>>> 
>>>> On Dec 22, 2022, at 11:44, Riley Kuttruff  wrote:
>>>> 
>>>> So the vote for rc2 passed. What are our next steps? Do I push the 
>>>> .tar.gz and .asc files to 
>>>> https://dist.apache.org/repos/dist/incubator/sdap ?
>>>> 
>>>>>> On 2022/12/14 20:04:29 Riley Kuttruff wrote:
>>>>> I verified, built and tested the release tarballs in the same manner I 
>>>>> did before and it passed just the same. 
>>>>> 
>>>>> I believe it's compliant with ASF policy but I'm not 100% sure so I'm 
>>>>> holding off on the vote. 
>>>>> - We added DISCLAIMER & README files to all release tarballs
>>>>> - I went through and checked MOST of the files for the ASF license 
>>>>> headers and added them where needed though I may have missed something
>>>>> 
>>>>>> On 2022/12/13 19:36:26 Nga Chung wrote:
>>>>>> HI all,
>>>>>> 
>>>>>> I started a VOTE thread for 1.0.0rc2, but can someone else please 
>>>>>> volunteer
>>>>>> to take over as release manager because I will be away 12/16/22 - 
>>>>>> 1/16/23.
>>>>>> 
>>>>>> I captured initial release instructions here
>>>>>> https://github.com/ngachung/incubator-sdap-nexus/blob/SDAP-414/docs/release.rst
>>>>>> 
>>>>>> Thanks,
>>>>>> Nga
>>>>>> 
>>>>>> 
>>>>>>> On Wed, Dec 7, 2022 at 1:07 AM Julian Hyde  wrote:
>>>>>> 
>>>>>>> By the way, I wouldn't create a new RC for the vote. Just vote on the
>>>>>>> RC1 you already have. We know we'll need to iterate through a few RCs
>>>>>>> before we get a good one.
>>>>>>> 
>>>>>>> On Wed, Dec 7, 2022 at 1:05 AM Julian Hyde  wrote:
>>>>>>>> 
>>>>>>>> Hey, that looks pretty good! In fact it looks a lot like an Apache
>>>>>>> release.
>>>>>>>> 
>>>>>>>> A few things:
>>>>>>>> 
>>>>>>>> 1. I saw you added dist/dev/incubator/sdap/KEYS; can you move that
>>>>>>>> file so that its path is dist/release/incubator/sdap/KEYS. Its main
>>>>>>>> purpose will be for people who download the release after it has been
>>>>>>>> released and want to verify the signatures. Putting it in 'release'
>>>>>>>> will ensure that it is automatically mirrored to
>>>>>>>> https://downloads.apache.org
>>>>>>>> 
>>>>>>>> 2. I got the following output from gpg:
>>>>>>>> 
>>>>>>>> gpg: Signature made Mon 05 Dec 2022 10:52:22 PM PST
>>>>>>>> gpg: 

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

[Julian Hyde]

They are implicitly binding iff the voter is a PPMC member. Saying “(binding)” 
is just a courtesy to the RM. 

When announcing the result the RM should distinguish binding from non- binding 
votes. 

Non-binding votes don’t “count” but can alert the PPMC to problems and so are 
worth taking seriously.

Julian

> On Dec 22, 2022, at 10:15, Riley Kuttruff  wrote:
> 
> Julian,
> 
> Are PPMC votes implicitly binding or does it need to be explicitly stated?
> 
> Riley
> 
>> On 2022/12/22 17:27:09 Julian Hyde wrote:
>> Thomas, (and others on this thread), it is helpful if you provide rationale 
>> for your vote. What steps did you take to verify the release? Did you 
>> encounter any matters of concern?
>> 
>> Julian
>> 
>>>> On Dec 21, 2022, at 3:05 PM, Thomas G Loubrieu  
>>>> wrote:
>>> 
>>> +1
>>> 
>>>> On 2022/12/20 16:12:07 Julian Hyde wrote:
>>>> If NASA has contributed these files to SDAP we’re fine. 
>>>> 
>>>> Julian
>>>> 
>>>>>> On Dec 19, 2022, at 5:51 PM, Stepheny Perez  wrote:
>>>>> 
>>>>> Hi Julian,
>>>>> 
>>>>> Those are test files, some are custom but some aren’t. For example 
>>>>> 2018123109-JPL-L4_GHRSST-SSTfnd-MUR25-GLOB-v02.0-fv04.2.nc is a 
>>>>> publicly accessible NASA file. Would you advise us to remove these? 
>>>>> 
>>>>> Thanks,
>>>>> Stepheny
>>>>> 
>>>>> 
>>>>>> On 2022/12/20 00:17:00 Julian Hyde wrote:
>>>>>> The vote email is much improved; thank you!
>>>>>> 
>>>>>> I downloaded the artifacts using svn, checked signatures (.asc files),
>>>>>> LICENSE, NOTICE, DISCLAIMER, VERSION.txt, file headers; I verified
>>>>>> that the contents of each tar file matches the corresponding git
>>>>>> commit. Checked for binary files.
>>>>>> 
>>>>>> I see that hashes of the src.tar.gz files have changed since the
>>>>>> previous rc2 vote, and they are signed with your key rather than Nga's
>>>>>> key. That's OK.
>>>>>> 
>>>>>> I see that sdap-ingester contains some large binary files with .nc,
>>>>>> .h5 and .nc4 suffixes. Are those files covered by the Apache license?
>>>>>> Are they generated? (It's OK to include binary files in a release,
>>>>>> provided that the project owns the copyright, but not OK to include
>>>>>> generated files.) I am going to assume that they are owned by the
>>>>>> project and not generated; please let me know if I am mistaken.
>>>>>> 
>>>>>> +1 (binding)
>>>>>> 
>>>>>> Julian
>>>>>> 
>>>>>> PS Riley: Yes, you definitely can vote. RMs usually add the following
>>>>>> line to their vote emails: "Here's my vote: +1 (binding)".
>>>>>> 
>>>>>> PPS Since we have one only one active mentor, I am going to ask other
>>>>>> IPMC members to take a look at these artifacts and vote. Even if they
>>>>>> discover problems that I have not, it will still help us get to a good
>>>>>> release faster.
>>>>>> 
>>>>>>> On Mon, Dec 19, 2022 at 11:17 AM Riley Kuttruff  wrote:
>>>>>>> 
>>>>>>> +1 from me too if I can.
>>>>>>> 
>>>>>>> Riley
>>>>>>> 
>>>>>>> On 2022/12/19 19:05:43 Stepheny Perez wrote:
>>>>>>>> +1
>>>>>>>> 
>>>>>>>> Stepheny
>>>>>>>> 
>>>>>>>> On 2022/12/19 18:58:47 Riley Kuttruff wrote:
>>>>>>>>> Hello everyone,
>>>>>>>>> 
>>>>>>>>> This is the second attempt to approve Apache SDAP (incubating) 
>>>>>>>>> release candidate rc2 for version 1.0.0.
>>>>>>>>> 
>>>>>>>>> There were no changes to the code between this and the previous 
>>>>>>>>> attempt to release rc2.
>>>>>>>>> 
>>>>>>>>> Changes made between previous candidate (rc1) and this one (rc2) are 
>>>>>>>>> as
>>>>&

Re: [EXTERNAL] Re: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

PS Don’t make a new RC. The IPMC will vote on the exact same artifacts. 

Julian

> On Dec 22, 2022, at 15:20, Julian Hyde  wrote:
> 
> Next step is to carry out a vote on the gene...@incubator.apache.org list. 
> 
> This may seem like unnecessary bureaucracy; for which I apologize. The reason 
> is that only a PMC (in this case the Incubator PMC, IPMC) may release code on 
> behalf of the ASF. 
> 
> Practically speaking, the release will receive due diligence by experts in 
> the IPMC. It’s likely that they will find problems, and if so, we may need 
> another RC, and two votes, to resolve them. Please be patient, because this 
> is the learning process. 
> 
> Riley, Glad to see that you have sent a RESULT email already. Please start a 
> vote thread on general@, referencing the thread on dev@. Good luck!
> 
> Can you also log cases for the issues I noted during the vote. The IPMC tends 
> to be lenient for the first release, especially if the podling is learning 
> and improving. 
> 
> Julian
> 
>> On Dec 22, 2022, at 11:44, Riley Kuttruff  wrote:
>> 
>> So the vote for rc2 passed. What are our next steps? Do I push the .tar.gz 
>> and .asc files to https://dist.apache.org/repos/dist/incubator/sdap ?
>> 
>>>> On 2022/12/14 20:04:29 Riley Kuttruff wrote:
>>> I verified, built and tested the release tarballs in the same manner I did 
>>> before and it passed just the same. 
>>> 
>>> I believe it's compliant with ASF policy but I'm not 100% sure so I'm 
>>> holding off on the vote. 
>>> - We added DISCLAIMER & README files to all release tarballs
>>> - I went through and checked MOST of the files for the ASF license headers 
>>> and added them where needed though I may have missed something
>>> 
>>>> On 2022/12/13 19:36:26 Nga Chung wrote:
>>>> HI all,
>>>> 
>>>> I started a VOTE thread for 1.0.0rc2, but can someone else please volunteer
>>>> to take over as release manager because I will be away 12/16/22 - 1/16/23.
>>>> 
>>>> I captured initial release instructions here
>>>> https://github.com/ngachung/incubator-sdap-nexus/blob/SDAP-414/docs/release.rst
>>>> 
>>>> Thanks,
>>>> Nga
>>>> 
>>>> 
>>>>> On Wed, Dec 7, 2022 at 1:07 AM Julian Hyde  wrote:
>>>> 
>>>>> By the way, I wouldn't create a new RC for the vote. Just vote on the
>>>>> RC1 you already have. We know we'll need to iterate through a few RCs
>>>>> before we get a good one.
>>>>> 
>>>>> On Wed, Dec 7, 2022 at 1:05 AM Julian Hyde  wrote:
>>>>>> 
>>>>>> Hey, that looks pretty good! In fact it looks a lot like an Apache
>>>>> release.
>>>>>> 
>>>>>> A few things:
>>>>>> 
>>>>>> 1. I saw you added dist/dev/incubator/sdap/KEYS; can you move that
>>>>>> file so that its path is dist/release/incubator/sdap/KEYS. Its main
>>>>>> purpose will be for people who download the release after it has been
>>>>>> released and want to verify the signatures. Putting it in 'release'
>>>>>> will ensure that it is automatically mirrored to
>>>>>> https://downloads.apache.org
>>>>>> 
>>>>>> 2. I got the following output from gpg:
>>>>>> 
>>>>>> gpg: Signature made Mon 05 Dec 2022 10:52:22 PM PST
>>>>>> gpg:using RSA key
>>>>> 1392A8A11801359247A803D8D2449E0EB5EF1E73
>>>>>> gpg: Good signature from "Nga Chung (CODE SIGNING KEY)
>>>>>> " [unknown]
>>>>>> gpg: WARNING: This key is not certified with a trusted signature!
>>>>>> gpg:  There is no indication that the signature belongs to the
>>>>> owner.
>>>>>> 
>>>>>> This means that the artifacts are signed correctly, but you are not in
>>>>>> my web of trust. Soon after the release, we should have a key-signing
>>>>>> party (or you should get your key signed by a colleague who has a
>>>>>> well-connected key).
>>>>>> 
>>>>>> 3. At first glance, the contents of the .tar.gz files look pretty
>>>>>> good. I haven't checked the headers etc. yet. There seems to be a
>>>>>> LICENSE.txt and NOTICE in each, which is good. You should also add a
>>

Re: [EXTERNAL] Re: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

Next step is to carry out a vote on the gene...@incubator.apache.org list. 

This may seem like unnecessary bureaucracy; for which I apologize. The reason 
is that only a PMC (in this case the Incubator PMC, IPMC) may release code on 
behalf of the ASF. 

Practically speaking, the release will receive due diligence by experts in the 
IPMC. It’s likely that they will find problems, and if so, we may need another 
RC, and two votes, to resolve them. Please be patient, because this is the 
learning process. 

Riley, Glad to see that you have sent a RESULT email already. Please start a 
vote thread on general@, referencing the thread on dev@. Good luck!

Can you also log cases for the issues I noted during the vote. The IPMC tends 
to be lenient for the first release, especially if the podling is learning and 
improving. 

Julian

> On Dec 22, 2022, at 11:44, Riley Kuttruff  wrote:
> 
> So the vote for rc2 passed. What are our next steps? Do I push the .tar.gz 
> and .asc files to https://dist.apache.org/repos/dist/incubator/sdap ?
> 
>> On 2022/12/14 20:04:29 Riley Kuttruff wrote:
>> I verified, built and tested the release tarballs in the same manner I did 
>> before and it passed just the same. 
>> 
>> I believe it's compliant with ASF policy but I'm not 100% sure so I'm 
>> holding off on the vote. 
>> - We added DISCLAIMER & README files to all release tarballs
>> - I went through and checked MOST of the files for the ASF license headers 
>> and added them where needed though I may have missed something
>> 
>>> On 2022/12/13 19:36:26 Nga Chung wrote:
>>> HI all,
>>> 
>>> I started a VOTE thread for 1.0.0rc2, but can someone else please volunteer
>>> to take over as release manager because I will be away 12/16/22 - 1/16/23.
>>> 
>>> I captured initial release instructions here
>>> https://github.com/ngachung/incubator-sdap-nexus/blob/SDAP-414/docs/release.rst
>>> 
>>> Thanks,
>>> Nga
>>> 
>>> 
>>>> On Wed, Dec 7, 2022 at 1:07 AM Julian Hyde  wrote:
>>> 
>>>> By the way, I wouldn't create a new RC for the vote. Just vote on the
>>>> RC1 you already have. We know we'll need to iterate through a few RCs
>>>> before we get a good one.
>>>> 
>>>> On Wed, Dec 7, 2022 at 1:05 AM Julian Hyde  wrote:
>>>>> 
>>>>> Hey, that looks pretty good! In fact it looks a lot like an Apache
>>>> release.
>>>>> 
>>>>> A few things:
>>>>> 
>>>>> 1. I saw you added dist/dev/incubator/sdap/KEYS; can you move that
>>>>> file so that its path is dist/release/incubator/sdap/KEYS. Its main
>>>>> purpose will be for people who download the release after it has been
>>>>> released and want to verify the signatures. Putting it in 'release'
>>>>> will ensure that it is automatically mirrored to
>>>>> https://downloads.apache.org
>>>>> 
>>>>> 2. I got the following output from gpg:
>>>>> 
>>>>>  gpg: Signature made Mon 05 Dec 2022 10:52:22 PM PST
>>>>>  gpg:using RSA key
>>>> 1392A8A11801359247A803D8D2449E0EB5EF1E73
>>>>>  gpg: Good signature from "Nga Chung (CODE SIGNING KEY)
>>>>> " [unknown]
>>>>>  gpg: WARNING: This key is not certified with a trusted signature!
>>>>>  gpg:  There is no indication that the signature belongs to the
>>>> owner.
>>>>> 
>>>>> This means that the artifacts are signed correctly, but you are not in
>>>>> my web of trust. Soon after the release, we should have a key-signing
>>>>> party (or you should get your key signed by a colleague who has a
>>>>> well-connected key).
>>>>> 
>>>>> 3. At first glance, the contents of the .tar.gz files look pretty
>>>>> good. I haven't checked the headers etc. yet. There seems to be a
>>>>> LICENSE.txt and NOTICE in each, which is good. You should also add a
>>>>> DISCLAIMER and/or DISCLAIMER-WIP file (required by the incubation
>>>>> process [1]). I also recommend adding a top-level README in each
>>>>> .tar.gz that describes the purpose of the file, and how to build it
>>>>> (for example see Calcite's README [2])
>>>>> 
>>>>> A good next step would be to start a vote. Craft an email with the
>>>>> same general structure as Apache Hop

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

[Julian Hyde]

Thomas, (and others on this thread), it is helpful if you provide rationale for 
your vote. What steps did you take to verify the release? Did you encounter any 
matters of concern?

Julian

> On Dec 21, 2022, at 3:05 PM, Thomas G Loubrieu  wrote:
> 
> +1
> 
>> On 2022/12/20 16:12:07 Julian Hyde wrote:
>> If NASA has contributed these files to SDAP we’re fine. 
>> 
>> Julian
>> 
>>>> On Dec 19, 2022, at 5:51 PM, Stepheny Perez  wrote:
>>> 
>>> Hi Julian,
>>> 
>>> Those are test files, some are custom but some aren’t. For example 
>>> 2018123109-JPL-L4_GHRSST-SSTfnd-MUR25-GLOB-v02.0-fv04.2.nc is a 
>>> publicly accessible NASA file. Would you advise us to remove these? 
>>> 
>>> Thanks,
>>> Stepheny
>>> 
>>> 
>>>> On 2022/12/20 00:17:00 Julian Hyde wrote:
>>>> The vote email is much improved; thank you!
>>>> 
>>>> I downloaded the artifacts using svn, checked signatures (.asc files),
>>>> LICENSE, NOTICE, DISCLAIMER, VERSION.txt, file headers; I verified
>>>> that the contents of each tar file matches the corresponding git
>>>> commit. Checked for binary files.
>>>> 
>>>> I see that hashes of the src.tar.gz files have changed since the
>>>> previous rc2 vote, and they are signed with your key rather than Nga's
>>>> key. That's OK.
>>>> 
>>>> I see that sdap-ingester contains some large binary files with .nc,
>>>> .h5 and .nc4 suffixes. Are those files covered by the Apache license?
>>>> Are they generated? (It's OK to include binary files in a release,
>>>> provided that the project owns the copyright, but not OK to include
>>>> generated files.) I am going to assume that they are owned by the
>>>> project and not generated; please let me know if I am mistaken.
>>>> 
>>>> +1 (binding)
>>>> 
>>>> Julian
>>>> 
>>>> PS Riley: Yes, you definitely can vote. RMs usually add the following
>>>> line to their vote emails: "Here's my vote: +1 (binding)".
>>>> 
>>>> PPS Since we have one only one active mentor, I am going to ask other
>>>> IPMC members to take a look at these artifacts and vote. Even if they
>>>> discover problems that I have not, it will still help us get to a good
>>>> release faster.
>>>> 
>>>>> On Mon, Dec 19, 2022 at 11:17 AM Riley Kuttruff  wrote:
>>>>> 
>>>>> +1 from me too if I can.
>>>>> 
>>>>> Riley
>>>>> 
>>>>> On 2022/12/19 19:05:43 Stepheny Perez wrote:
>>>>>> +1
>>>>>> 
>>>>>> Stepheny
>>>>>> 
>>>>>> On 2022/12/19 18:58:47 Riley Kuttruff wrote:
>>>>>>> Hello everyone,
>>>>>>> 
>>>>>>> This is the second attempt to approve Apache SDAP (incubating) release 
>>>>>>> candidate rc2 for version 1.0.0.
>>>>>>> 
>>>>>>> There were no changes to the code between this and the previous attempt 
>>>>>>> to release rc2.
>>>>>>> 
>>>>>>> Changes made between previous candidate (rc1) and this one (rc2) are as
>>>>>>> follows:
>>>>>>> - Added README
>>>>>>> - Added DISCLAIMER
>>>>>>> 
>>>>>>> Instructions for building docker images from source can be found here:
>>>>>>> https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html
>>>>>>> Instructions for deploying locally to test can be found here:
>>>>>>> https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html
>>>>>>> 
>>>>>>> The tags to be voted on are 1.0.0-rc2:
>>>>>>> 
>>>>>>> - nexusproto:
>>>>>>>   - URL: 
>>>>>>> https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc2
>>>>>>>   - Commit: f3c726e69997436dd9ee6f9a993d4c95ee490b6f
>>>>>>> - ingester:
>>>>>>>   - URL: 
>>>>>>> https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc2
>>>>>>>   - Commit: 2c8a9d35320f11a5db2534802f43366ddaff2fea
>>>>>>> - nexus:
>>>>>>>   - URL: https://github.com/apa

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc1

[Julian Hyde]

Riley, as interim release manager, can you please send a [CANCEL] email. Every 
vote thread needs to be finished. 

Julian 

> On Dec 21, 2022, at 3:04 PM, Thomas G Loubrieu  wrote:
> 
> +1
> 
>> On 2022/12/08 22:40:48 Riley Kuttruff wrote:
>> All release files have been verified, built and tested successfully; 
>> however, they are missing some required files (DISCLAIMER).
>> 
>> -1 (binding) from me
>> 
>>> On 2022/12/08 22:33:25 Nga Chung wrote:
>>> Hi all,
>>> 
>>> This is the first release candidate of Apache SDAP (incubating) version
>>> 1.0.0
>>> 
>>> Instructions for building docker images from source can be found here:
>>> https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html
>>> Instructions for deploying locally to test can be found here:
>>> https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html
>>> 
>>> The tags to be voted on are 1.0.0-rc1:
>>> 
>>> https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc1
>>> https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc1
>>> https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc1
>>> 
>>> The release files, including signatures, digests, etc. can be found at:
>>> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc1/
>>> 
>>> Release artifacts are signed with the following key:
>>> https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xD2449E0EB5EF1E73
>>> 
>>> Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.
>>> 
>>> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
>>> cast.
>>> 
>>> [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
>>> [ ] +0 No opinion
>>> [ ] -1 Do not release this package because ...
>>> 
>>> Thanks,
>>> Nga
>>> 
>> 

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

[Julian Hyde]

If NASA has contributed these files to SDAP we’re fine. 

Julian

> On Dec 19, 2022, at 5:51 PM, Stepheny Perez  wrote:
> 
> Hi Julian,
> 
> Those are test files, some are custom but some aren’t. For example 
> 2018123109-JPL-L4_GHRSST-SSTfnd-MUR25-GLOB-v02.0-fv04.2.nc is a publicly 
> accessible NASA file. Would you advise us to remove these? 
> 
> Thanks,
> Stepheny
> 
> 
>> On 2022/12/20 00:17:00 Julian Hyde wrote:
>> The vote email is much improved; thank you!
>> 
>> I downloaded the artifacts using svn, checked signatures (.asc files),
>> LICENSE, NOTICE, DISCLAIMER, VERSION.txt, file headers; I verified
>> that the contents of each tar file matches the corresponding git
>> commit. Checked for binary files.
>> 
>> I see that hashes of the src.tar.gz files have changed since the
>> previous rc2 vote, and they are signed with your key rather than Nga's
>> key. That's OK.
>> 
>> I see that sdap-ingester contains some large binary files with .nc,
>> .h5 and .nc4 suffixes. Are those files covered by the Apache license?
>> Are they generated? (It's OK to include binary files in a release,
>> provided that the project owns the copyright, but not OK to include
>> generated files.) I am going to assume that they are owned by the
>> project and not generated; please let me know if I am mistaken.
>> 
>> +1 (binding)
>> 
>> Julian
>> 
>> PS Riley: Yes, you definitely can vote. RMs usually add the following
>> line to their vote emails: "Here's my vote: +1 (binding)".
>> 
>> PPS Since we have one only one active mentor, I am going to ask other
>> IPMC members to take a look at these artifacts and vote. Even if they
>> discover problems that I have not, it will still help us get to a good
>> release faster.
>> 
>>> On Mon, Dec 19, 2022 at 11:17 AM Riley Kuttruff  wrote:
>>> 
>>> +1 from me too if I can.
>>> 
>>> Riley
>>> 
>>> On 2022/12/19 19:05:43 Stepheny Perez wrote:
>>>> +1
>>>> 
>>>> Stepheny
>>>> 
>>>> On 2022/12/19 18:58:47 Riley Kuttruff wrote:
>>>>> Hello everyone,
>>>>> 
>>>>> This is the second attempt to approve Apache SDAP (incubating) release 
>>>>> candidate rc2 for version 1.0.0.
>>>>> 
>>>>> There were no changes to the code between this and the previous attempt 
>>>>> to release rc2.
>>>>> 
>>>>> Changes made between previous candidate (rc1) and this one (rc2) are as
>>>>> follows:
>>>>> - Added README
>>>>> - Added DISCLAIMER
>>>>> 
>>>>> Instructions for building docker images from source can be found here:
>>>>> https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html
>>>>> Instructions for deploying locally to test can be found here:
>>>>> https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html
>>>>> 
>>>>> The tags to be voted on are 1.0.0-rc2:
>>>>> 
>>>>> - nexusproto:
>>>>>- URL: 
>>>>> https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc2
>>>>>- Commit: f3c726e69997436dd9ee6f9a993d4c95ee490b6f
>>>>> - ingester:
>>>>>- URL: https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc2
>>>>>- Commit: 2c8a9d35320f11a5db2534802f43366ddaff2fea
>>>>> - nexus:
>>>>>- URL: https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc2
>>>>>- Commit: f60e98331ac29b57ca40322f8f96e98a5c69e553
>>>>> 
>>>>> The release files, including signatures, digests, etc. can be found at:
>>>>> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/
>>>>> 
>>>>> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are 
>>>>> voting on are as follows:
>>>>> 
>>>>> apache-sdap-ingester-1.0.0-src.tar.gz:
>>>>> db380c3002351e65ec3581a3ff0cacbb7092f46292b0a656a78a919e1409738442e845731050a2160a556a7818f22b2ab4bb6da437200bc0a62419332de49ad7
>>>>> 
>>>>> apache-sdap-nexus-1.0.0-src.tar.gz:
>>>>> da34e9830cf5126bac498180d7cdd95bc2cfc13535c7b4355ba51de64e3589a385a969e0cf1a89fa77e436b30c99a48abffab4b4ef03b23982aa33c2e83e8dbd
>>>>> 
>>>>> apache-sdap-nexusproto-1.0.0-src.tar.gz:
>>>>> 05dc8e96d9c49207750c1da13f630493e8d08f5e68733742c157ac6c85ede29aca25f3c94cd706acbbe21cee41ebc052a880b4d6ce859bf510bcc2d66d8f88b2
>>>>> 
>>>>> Release artifacts are signed with the following key:
>>>>> https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x4e98c4a32026656e14e0b570fc20035a010e3b7b
>>>>> 
>>>>> Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.
>>>>> 
>>>>> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
>>>>> cast.
>>>>> 
>>>>> PLEASE NOTE: Do not reply with a vote from your work email as it can 
>>>>> mangle the links. To vote, go to 
>>>>> https://lists.apache.org/list.html?dev@sdap.apache.org, log in and send 
>>>>> your reply from there.
>>>>> 
>>>>> [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
>>>>> [ ] +0 No opinion
>>>>> [ ] -1 Do not release this package because ...
>>>>> 
>>>>> Thank you,
>>>>> Riley
>>>>> 
>>>> 
>> 

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

[Julian Hyde]

The vote email is much improved; thank you!

I downloaded the artifacts using svn, checked signatures (.asc files),
LICENSE, NOTICE, DISCLAIMER, VERSION.txt, file headers; I verified
that the contents of each tar file matches the corresponding git
commit. Checked for binary files.

I see that hashes of the src.tar.gz files have changed since the
previous rc2 vote, and they are signed with your key rather than Nga's
key. That's OK.

I see that sdap-ingester contains some large binary files with .nc,
.h5 and .nc4 suffixes. Are those files covered by the Apache license?
Are they generated? (It's OK to include binary files in a release,
provided that the project owns the copyright, but not OK to include
generated files.) I am going to assume that they are owned by the
project and not generated; please let me know if I am mistaken.

+1 (binding)

Julian

PS Riley: Yes, you definitely can vote. RMs usually add the following
line to their vote emails: "Here's my vote: +1 (binding)".

PPS Since we have one only one active mentor, I am going to ask other
IPMC members to take a look at these artifacts and vote. Even if they
discover problems that I have not, it will still help us get to a good
release faster.

On Mon, Dec 19, 2022 at 11:17 AM Riley Kuttruff  wrote:
>
> +1 from me too if I can.
>
> Riley
>
> On 2022/12/19 19:05:43 Stepheny Perez wrote:
> > +1
> >
> > Stepheny
> >
> > On 2022/12/19 18:58:47 Riley Kuttruff wrote:
> > > Hello everyone,
> > >
> > > This is the second attempt to approve Apache SDAP (incubating) release 
> > > candidate rc2 for version 1.0.0.
> > >
> > > There were no changes to the code between this and the previous attempt 
> > > to release rc2.
> > >
> > > Changes made between previous candidate (rc1) and this one (rc2) are as
> > > follows:
> > > - Added README
> > > - Added DISCLAIMER
> > >
> > > Instructions for building docker images from source can be found here:
> > > https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html
> > > Instructions for deploying locally to test can be found here:
> > > https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html
> > >
> > > The tags to be voted on are 1.0.0-rc2:
> > >
> > > - nexusproto:
> > > - URL: 
> > > https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc2
> > > - Commit: f3c726e69997436dd9ee6f9a993d4c95ee490b6f
> > > - ingester:
> > > - URL: 
> > > https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc2
> > > - Commit: 2c8a9d35320f11a5db2534802f43366ddaff2fea
> > > - nexus:
> > > - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc2
> > > - Commit: f60e98331ac29b57ca40322f8f96e98a5c69e553
> > >
> > > The release files, including signatures, digests, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/
> > >
> > > For verification, the hashes (SHA-512) of the .tar.gz artifacts we are 
> > > voting on are as follows:
> > >
> > > apache-sdap-ingester-1.0.0-src.tar.gz:
> > > db380c3002351e65ec3581a3ff0cacbb7092f46292b0a656a78a919e1409738442e845731050a2160a556a7818f22b2ab4bb6da437200bc0a62419332de49ad7
> > >
> > > apache-sdap-nexus-1.0.0-src.tar.gz:
> > > da34e9830cf5126bac498180d7cdd95bc2cfc13535c7b4355ba51de64e3589a385a969e0cf1a89fa77e436b30c99a48abffab4b4ef03b23982aa33c2e83e8dbd
> > >
> > > apache-sdap-nexusproto-1.0.0-src.tar.gz:
> > > 05dc8e96d9c49207750c1da13f630493e8d08f5e68733742c157ac6c85ede29aca25f3c94cd706acbbe21cee41ebc052a880b4d6ce859bf510bcc2d66d8f88b2
> > >
> > > Release artifacts are signed with the following key:
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x4e98c4a32026656e14e0b570fc20035a010e3b7b
> > >
> > > Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.
> > >
> > > The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
> > > cast.
> > >
> > > PLEASE NOTE: Do not reply with a vote from your work email as it can 
> > > mangle the links. To vote, go to 
> > > https://lists.apache.org/list.html?dev@sdap.apache.org, log in and send 
> > > your reply from there.
> > >
> > > [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
> > > [ ] +0 No opinion
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thank you,
> > > Riley
> > >
> >

Re: [EXTERNAL] [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

[Julian Hyde]

I don't see any reason why not. The release manager just needs to be
an SDAP committer, and able to sign the artifacts. If someone were to
volunteer to be RM I'm sure Nga would be delighted that the process is
moving forward.

Julian

On Sat, Dec 17, 2022 at 10:37 PM Riley Kuttruff  wrote:
>
> Not sure if it's appropriate to reply here, but is it possible to designate 
> an interim release manager to kick off the next vote as Nga is out of the 
> country and will be until 1/16?
>
> On 2022/12/18 06:31:15 Julian Hyde wrote:
> > I downloaded the artifacts using svn, checked signatures (.asc files),
> > LICENSE, NOTICE, DISCLAIMER, file headers; I verified that the
> > contents of apache-sdap-nexus-1.0.0-src.tar.gz are equal to the
> > contents of the git commit tagged with 1.0.0-rc2. Checked for binary
> > files. That all looks good.
> >
> > But there are several aspects of the vote email that make it
> > unsuitable for a release vote:
> >  * The URLs have been mangled with a urldefense.us prefix and I am not
> > able to view them.
> >  * Git tags are mutable and therefore are not a permanent record of
> > the state of the repository;
> > you should use git commit SHAs instead.
> >  * I was not able to check hashes because the vote email does not contain 
> > them.
> >This guarantees that I am voting on the same artifacts produced by
> > the release manager.
> >
> > I am not sure how the URLs got mangled. Maybe it is because the RM
> > used their work email server to post the vote email? If so, go to
> > https://lists.apache.org/list.html?dev@sdap.apache.org, log in, and
> > post from there.
> >
> > My vote is -1 because of the above issues with the vote email. I think
> > that you can cancel this vote, send an email starting a new vote on
> > the same release candidate (rc2).
> >
> > It would be convenient if the files in, say,
> > apache-sdap-nexus-1.0.0-src.tar.gz had a prefix of
> > apache-sdap-nexus-1.0.0-src. It makes it easier to clean up. Not a
> > blocker for this release, but you should do it next release.
> >
> > Julian
> >
> > On Wed, Dec 14, 2022 at 3:26 PM Perez, Stepheny K (US 398F)
> >  wrote:
> > >
> > > This release is working well for me. +1.
> > >
> > > 
> > > From: Nga Chung 
> > > Sent: Tuesday, December 13, 2022 11:10 AM
> > > To: dev@sdap.apache.org 
> > > Subject: [EXTERNAL] [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2
> > >
> > > Hi all,
> > >
> > > This is the second release candidate of Apache SDAP (incubating) version
> > > 1.0.0.
> > >
> > > Changes made between previous candidate (rc1) and this one (rc2) are as
> > > follows:
> > > - Added README
> > > - Added DISCLAIMER
> > >
> > > Instructions for building docker images from source can be found here:
> > > https://urldefense.us/v3/__https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKYSXxpmw$
> > > Instructions for deploying locally to test can be found here:
> > > https://urldefense.us/v3/__https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKphBkEF8$
> > >
> > > The tags to be voted on are 1.0.0-rc2:
> > >
> > > https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc2__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKF0EW64U$
> > > https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc2__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKxmhlaSc$
> > > https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc2__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKUEr4BgY$
> > >
> > > The release files, including signatures, digests, etc. can be found at:
> > > https://urldefense.us/v3/__https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKnXyvhrk$
> > >
> > > Release artifacts are signed with the following key:
> > > https://urldefense.us/v3/__https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xD2449E0EB5EF1E73__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKdFIqqj8$
> > >
> > > Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.
> > >
> > > The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
> > > cast.
> > >
> > > [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
> > > [ ] +0 No opinion
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thanks,
> > > Nga
> >

Re: [EXTERNAL] [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

[Julian Hyde]

I downloaded the artifacts using svn, checked signatures (.asc files),
LICENSE, NOTICE, DISCLAIMER, file headers; I verified that the
contents of apache-sdap-nexus-1.0.0-src.tar.gz are equal to the
contents of the git commit tagged with 1.0.0-rc2. Checked for binary
files. That all looks good.

But there are several aspects of the vote email that make it
unsuitable for a release vote:
 * The URLs have been mangled with a urldefense.us prefix and I am not
able to view them.
 * Git tags are mutable and therefore are not a permanent record of
the state of the repository;
you should use git commit SHAs instead.
 * I was not able to check hashes because the vote email does not contain them.
   This guarantees that I am voting on the same artifacts produced by
the release manager.

I am not sure how the URLs got mangled. Maybe it is because the RM
used their work email server to post the vote email? If so, go to
https://lists.apache.org/list.html?dev@sdap.apache.org, log in, and
post from there.

My vote is -1 because of the above issues with the vote email. I think
that you can cancel this vote, send an email starting a new vote on
the same release candidate (rc2).

It would be convenient if the files in, say,
apache-sdap-nexus-1.0.0-src.tar.gz had a prefix of
apache-sdap-nexus-1.0.0-src. It makes it easier to clean up. Not a
blocker for this release, but you should do it next release.

Julian

On Wed, Dec 14, 2022 at 3:26 PM Perez, Stepheny K (US 398F)
 wrote:
>
> This release is working well for me. +1.
>
> 
> From: Nga Chung 
> Sent: Tuesday, December 13, 2022 11:10 AM
> To: dev@sdap.apache.org 
> Subject: [EXTERNAL] [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2
>
> Hi all,
>
> This is the second release candidate of Apache SDAP (incubating) version
> 1.0.0.
>
> Changes made between previous candidate (rc1) and this one (rc2) are as
> follows:
> - Added README
> - Added DISCLAIMER
>
> Instructions for building docker images from source can be found here:
> https://urldefense.us/v3/__https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKYSXxpmw$
> Instructions for deploying locally to test can be found here:
> https://urldefense.us/v3/__https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKphBkEF8$
>
> The tags to be voted on are 1.0.0-rc2:
>
> https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc2__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKF0EW64U$
> https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc2__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKxmhlaSc$
> https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc2__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKUEr4BgY$
>
> The release files, including signatures, digests, etc. can be found at:
> https://urldefense.us/v3/__https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKnXyvhrk$
>
> Release artifacts are signed with the following key:
> https://urldefense.us/v3/__https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xD2449E0EB5EF1E73__;!!PvBDto6Hs4WbVuu7!a8nUi_smQN818mWuAEPnw5cIK4sVjNaqWGy47tW1JMb-0EJdftv6755yunjZlymzT1rKdFIqqj8$
>
> Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.
>
> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
> cast.
>
> [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Nga

Re: [EXTERNAL] Re: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

By the way, I wouldn't create a new RC for the vote. Just vote on the
RC1 you already have. We know we'll need to iterate through a few RCs
before we get a good one.

On Wed, Dec 7, 2022 at 1:05 AM Julian Hyde  wrote:
>
> Hey, that looks pretty good! In fact it looks a lot like an Apache release.
>
> A few things:
>
> 1. I saw you added dist/dev/incubator/sdap/KEYS; can you move that
> file so that its path is dist/release/incubator/sdap/KEYS. Its main
> purpose will be for people who download the release after it has been
> released and want to verify the signatures. Putting it in 'release'
> will ensure that it is automatically mirrored to
> https://downloads.apache.org
>
> 2. I got the following output from gpg:
>
>   gpg: Signature made Mon 05 Dec 2022 10:52:22 PM PST
>   gpg:using RSA key 1392A8A11801359247A803D8D2449E0EB5EF1E73
>   gpg: Good signature from "Nga Chung (CODE SIGNING KEY)
> " [unknown]
>   gpg: WARNING: This key is not certified with a trusted signature!
>   gpg:  There is no indication that the signature belongs to the 
> owner.
>
> This means that the artifacts are signed correctly, but you are not in
> my web of trust. Soon after the release, we should have a key-signing
> party (or you should get your key signed by a colleague who has a
> well-connected key).
>
> 3. At first glance, the contents of the .tar.gz files look pretty
> good. I haven't checked the headers etc. yet. There seems to be a
> LICENSE.txt and NOTICE in each, which is good. You should also add a
> DISCLAIMER and/or DISCLAIMER-WIP file (required by the incubation
> process [1]). I also recommend adding a top-level README in each
> .tar.gz that describes the purpose of the file, and how to build it
> (for example see Calcite's README [2])
>
> A good next step would be to start a vote. Craft an email with the
> same general structure as Apache Hop (incubating) 0.99-rc2 [3] and
> send it to dev@. Then PPMC members should vote on the release, each
> describing the checks that they made. Then finish the vote with an
> email with a [RESULT][VOTE] or [CANCEL][VOTE] subject line. (We know
> the vote will fail, due to the missing DISCLAIMER file, but it's good
> to practice the process, and with many people scrutinizing the release
> we will find issues faster.)
>
> You'll also want to craft release notes (they don't have to be in the
> release, but they should be somewhere accessible for people to read).
>
> And you should be writing that "how to" guide as you go along, if
> you're not already.
>
> Julian
>
> [1] https://incubator.apache.org/policy/incubation.html#disclaimers
> [2] https://github.com/apache/calcite/blob/main/README
> [3] https://lists.apache.org/thread/ncnok4clt6k491zv6c3v4kk2fc41qsz2
>
> On Mon, Dec 5, 2022 at 11:06 PM Nga Chung  wrote:
> >
> > Riley, thank you for adding all the missing ASF header and the NOTICE.
> >
> > Riley's changes have been merged and rc1 artifacts have been uploaded to
> > https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc1/
> >
> >
> > Has anyone had any success testing rc0?
> >
> > Julian, any suggestions on next steps?
> >
> > Thanks,
> > Nga
> >
> > On Thu, Dec 1, 2022 at 1:03 PM Kuttruff, Riley K (US 398F-Affiliate)
> >  wrote:
> >
> > > It appears some of the source files are missing the ASF header. I did a
> > > check for all the Python files across the repositories and added them 
> > > where
> > > needed in a pair of PRs (nexus & ingester; nexusproto had no .py files
> > > missing the header).
> > >
> > > I still have yet to check for any non-python source files.
> > >
> > > Riley
> > >
> > > On 11/30/22, 4:29 PM, "Nga Chung"  wrote:
> > >
> > > Hi everyone,
> > >
> > > So this email thread probably needs renaming or we can start a new one
> > > if
> > > we're proceeding with a Version 1.0.0 release instead of 0.4.5a56.
> > >
> > > Anyways, with help from many folks we now have a release candidate
> > > that can
> > > be found here:
> > >
> > > https://urldefense.us/v3/__https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc0/__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtGjkf-Wmw$
> > >
> > >
> > > Instructions for building docker images from source can be found here:
> > >
> > > https://urldefense.us/v3/__https://incuba

Re: [EXTERNAL] Re: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

tructions into github but
> > wanted to get all this out first for your review.
> >
> > git clone --branch release/1.0.0
> >
> > https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-nexusproto.git__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtGbmDU9OM$
> >
> > cd incubator-sdap-nexusproto*/*
> >
> > git ls-files > /tmp/manifest.txt
> >
> > tar cvfz apache-sdap-nexusproto-1.0.0-src.tar.gz -T /tmp/manifest.txt
> >
> > gpg --armor --output apache-sdap-nexusproto-1.0.0-src.tar.gz.asc
> > --detach-sig apache-sdap-nexusproto-1.0.0-src.tar.gz
> >
> > shasum -a 512 apache-sdap-nexusproto-1.0.0-src.tar.gz >
> > apache-sdap-nexusproto-1.0.0-src.tar.gz.sha512
> >
> >
> > git clone --branch release/1.0.0
> >
> > https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-ingester.git__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtGgkAuYFg$
> >
> > cd incubator-sdap-ingester/
> >
> > git ls-files > /tmp/manifest.txt
> >
> > tar cvfz apache-sdap-ingester-1.0.0-src.tar.gz -T /tmp/manifest.txt
> >
> > gpg --armor --output apache-sdap-ingester-1.0.0-src.tar.gz.asc
> > --detach-sig
> > apache-sdap-ingester-1.0.0-src.tar.gz
> >
> > shasum -a 512 apache-sdap-ingester-1.0.0-src.tar.gz >
> > apache-sdap-ingester-1.0.0-src.tar.gz.sha512
> >
> >
> > git clone --branch release/1.0.0
> >
> > https://urldefense.us/v3/__https://github.com/apache/incubator-sdap-nexus.git__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtG19U3rPQ$
> >
> > cd incubator-sdap-nexus/
> >
> > git ls-files > /tmp/manifest.txt
> >
> > tar cvfz apache-sdap-nexus-1.0.0-src.tar.gz -T /tmp/manifest.txt
> >
> > gpg --armor --output apache-sdap-nexus-1.0.0-src.tar.gz.asc
> > --detach-sig
> > apache-sdap-nexus-1.0.0-src.tar.gz
> >
> > shasum -a 512 apache-sdap-nexus-1.0.0-src.tar.gz >
> > apache-sdap-nexus-1.0.0-src.tar.gz.sha512
> >
> > svn co
> > https://urldefense.us/v3/__https://dist.apache.org/repos/dist/dev/incubator/sdap__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtG8upBcY0$
> > sdap
> > mkdir sdap/apache-sdap-1.0.0-rc0
> > cp incubator-sdap-nexusproto/apache-sdap-nexusproto-1.0.0-src.tar.gz*
> > sdap/apache-sdap-1.0.0-rc0/.
> > cp incubator-sdap-ingester/apache-sdap-ingester-1.0.0-src.tar.gz*
> > sdap/apache-sdap-1.0.0-rc0/.
> > cp incubator-sdap-nexus/apache-sdap-nexus-1.0.0-src.tar.gz*
> > sdap/apache-sdap-1.0.0-rc0/.
> >
> > svn add apache-sdap-1.0.0-rc0
> >
> > svn ci -m "Uploading release candidate Apache SDAP
> > apache-sdap-1.0.0-rc0 to
> > dev area" apache-sdap-1.0.0-rc0
> >
> >
> > Thanks,
> > Nga
> >
> > On Wed, Nov 9, 2022 at 4:26 PM Julian Hyde 
> > wrote:
> >
> > > hanks for volunteering to be release manager!
> > >
> > > The artifacts to be voted on will be in the following directory (or
> > > something very much like it):
> > >
> > >
> > >
> > >
> > https://urldefense.us/v3/__https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-0.4.5a56-rc0/__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtGsl1T6OQ$
> > >
> > > with
> > > * “dev” being the place for candidate releases (to be replaced by
> > “release”
> > > when the release is final)
> > > * “sdap” being the project name (prefixed with “incubator/“ while
> > sdap is
> > > incubating)
> > > * “apache-sdap” being the component
> > > * “0.4.5a56” being the version
> > > * “rc0” being the release candidate label
> > >
> > > On release, you will copy the artifacts to
> > >
> > >
> > >
> > >
> > https://urldefense.us/v3/__https://dist.apache.org/repos/dist/release/incubator/sdap/apache-sdap-0.4.5a56/__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtGQnZZiUU$
> > >
> > > Note that ‘dev’ became ‘release’ and the ‘rc0’ label was removed.
> > And by
> > > the time you release, you'll also need a KEYS file similar to the
> > one in
> > > the bRPC pr

Re: [DISCUSS] Monthly SDAP Meeting

[Julian Hyde]

A monthly meeting sounds like a good idea. It will allow project
members to get to know each other, and should help build momentum.

Monthly meetings of this kind are fairly common in Apache projects.
However, the projects need to be careful that the meeting doesn't
exclude people from the decision-making process, such as people who
are in a different time zone, or who have other responsibilities at
the time of the meeting. A few suggestions for mitigating this:
 * Have discussions during the meeting, but if there are significant
decisions to be made, make them on the dev list.
 * Send out minutes after each meeting.
 * Poll the community for preferred times and if there is no single
time that works for everyone consider varying the time of the meeting.

For example, if you read through the minutes of the Arrow sync call
[1] there are several good habits in evidence: they speak of 'coming
to a consensus' but decisions are 'pending a vote'; there is a
proposal, but one of the action items is for someone to start a
discussion of that proposal on the mailing list.

Julian

[1] https://lists.apache.org/thread/cmt59phs7tzd5dcdqnr7qn66womd1odx

On Wed, Nov 30, 2022 at 4:34 PM Nga Chung  wrote:
>
> Hi all,
>
> I'm not sure if there is any official guidance on hosting public monthly
> project meetings. This could be a good venue for PMC
> members/committers/users/etc. to discuss project roadmap, releases, usage,
> etc. Thoughts?
>
> Thanks,
> Nga

[jira] [Commented] (SDAP-414) Release SDAP v1.0.0

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638009#comment-17638009
 ] 

Julian Hyde commented on SDAP-414:
--

Was this plan/decision made on any mailing list? The most recent email 
discussion that I am aware of is "[[DISCUSS] Towards release 
0.4.5a56|https://lists.apache.org/thread/bfb2kgf601crh9gt4bwgnzqs8hrpsgfo]";.

> Release SDAP v1.0.0
> ---
>
> Key: SDAP-414
> URL: https://issues.apache.org/jira/browse/SDAP-414
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Nga Thien Chung
>Assignee: Nga Thien Chung
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (SDAP-414) Release SDAP v1.0.0

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637509#comment-17637509
 ] 

Julian Hyde commented on SDAP-414:
--

How much work needs to be done to get the code and doc into shape for a 1.0 
release?

I ask because, if the goal is to make an Apache release, it might be a lot less 
effort to just release the code that we have now. For an Apache release, there 
will be changes for legal reasons (e.g. licenses and file headers) and 
usability (e.g. a good README file) but no changes in functionality (bugs and 
feature requests) are required. So I would suggest releasing what we already 
have first, and only then move on to a 1.0 release.

> Release SDAP v1.0.0
> ---
>
> Key: SDAP-414
> URL: https://issues.apache.org/jira/browse/SDAP-414
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Nga Thien Chung
>Assignee: Nga Thien Chung
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

hanks for volunteering to be release manager!

The artifacts to be voted on will be in the following directory (or
something very much like it):


https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-0.4.5a56-rc0/

with
* “dev” being the place for candidate releases (to be replaced by “release”
when the release is final)
* “sdap” being the project name (prefixed with “incubator/“ while sdap is
incubating)
* “apache-sdap” being the component
* “0.4.5a56” being the version
* “rc0” being the release candidate label

On release, you will copy the artifacts to


https://dist.apache.org/repos/dist/release/incubator/sdap/apache-sdap-0.4.5a56/

Note that ‘dev’ became ‘release’ and the ‘rc0’ label was removed. And by
the time you release, you'll also need a KEYS file similar to the one in
the bRPC project:

  https://dist.apache.org/repos/dist/release/incubator/brpc/KEYS

Browse https://dist.apache.org/repos/dist/dev/ and you’ll see that all
projects use this directory structure.

Let’s look at the artifacts that were in Calcite’s last release. In the
directory
https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.31.0-rc2/ sh
you’ll see the following files:

 * apache-calcite-1.31.0-src.tar.gz # source tar ball
 * apache-calcite-1.31.0-src.tar.gz.asc # armored signature generated by PGP
 * apache-calcite-1.31.0-src.tar.gz.sha512 # SHA512 checksum of the
src.tar.gz file

SDAP will need equivalent files.

Now, how to write to dist.apache.org? That web server is a view onto an ASF
source code repository managed by the Subversion source control system. ASF
uses it for content management of releases.

First, install subversion. "sudo apt-get install subversion” or similar.

Then checkout the tree:

  svn co https://dist.apache.org/repos/dist/dev/incubator/sdap/trunk sdap
  cd sdap
  mkdir apache-sdap-0.4.5a56-rc0

Create some files, then check them in:

  svn add apache-sdap-0.4.5a56-rc0
  svn ci -m’Uploading release candidate Apache SDAP sdap-0.4.5a56-rc0 to
dev area’ apache-sdap-0.4.5a56-rc0

These instructions are from memory, so there might be a few mistakes.
Hopefully you get the general idea. Do some Google searches and you’ll
probably find the release instructions used by other projects.

You'll need to log into subversion using your ASF username and password,
but I don’t remember the details.

Be sure to write a ‘how to’ so that the next release manager can follow
your steps, and add it to the source code when you’re done. And maybe one
or two shell scripts.

I also recommend that you create a bug with the title ‘Release SDAP
0.4.5a56’. It will be a useful place to have discussions, link to other
bugs, release notes, etc.

Julian


On Nov 9, 2022, at 3:32 PM, Nga Chung  wrote:

I'm going to be the release manager for this first release. Where exactly
do we upload the 3 .tar.gz (1 per repository) to?

Thanks,
Nga

On Thu, Nov 3, 2022 at 5:12 PM Julian Hyde  wrote:

Regarding testing. I recommend that the release manager creates a
recipe ("HOWTO") for the steps to create a release. One of those steps
is a manual smoke test (e.g. am I able to start the server and do x,
y, and z simple operations).

Other people voting on the release can do their own smoke tests.

But do bear in mind that if there are bugs, this does not prevent a
release. Clearly you don't want show-stopper bugs like code that
doesn't compile.

Julian


On Wed, Nov 2, 2022 at 3:47 PM Perez, Stepheny K (US 398F)
 wrote:


Hi everyone,

I’d like to start the conversation regarding our first official Apache

release. From what I can tell, these are the major items that need to be
completed before we can move forward:



1.   Identify a release manager. Any volunteers?

2.   Create release tarball

3.   Write release notes

4.   Write installation instructions from source (Riley Kuttruff has

started this work)


5.   Push docker images to Dockerhub (and update quickstart with

these versions)


Another important task before moving forward would be testing the latest

SDAP analysis image 0.4.5a56. I have personally used this version without
any issues. Has anyone else upgraded to this latest alpha version?


Thank you!
Stepheny

Re: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

Regarding testing. I recommend that the release manager creates a
recipe ("HOWTO") for the steps to create a release. One of those steps
is a manual smoke test (e.g. am I able to start the server and do x,
y, and z simple operations).

Other people voting on the release can do their own smoke tests.

But do bear in mind that if there are bugs, this does not prevent a
release. Clearly you don't want show-stopper bugs like code that
doesn't compile.

Julian


On Wed, Nov 2, 2022 at 3:47 PM Perez, Stepheny K (US 398F)
 wrote:
>
> Hi everyone,
>
> I’d like to start the conversation regarding our first official Apache 
> release. From what I can tell, these are the major items that need to be 
> completed before we can move forward:
>
>
> 1.   Identify a release manager. Any volunteers?
>
> 2.   Create release tarball
>
> 3.   Write release notes
>
> 4.   Write installation instructions from source (Riley Kuttruff has 
> started this work)
>
> 5.   Push docker images to Dockerhub (and update quickstart with these 
> versions)
>
> Another important task before moving forward would be testing the latest SDAP 
> analysis image 0.4.5a56. I have personally used this version without any 
> issues. Has anyone else upgraded to this latest alpha version?
>
> Thank you!
> Stepheny

Re: Ex: [DISCUSS] Towards release 0.4.5a56

[Julian Hyde]

I suggest doing the simplest thing. Generally the simplest thing is to
do one release from each git repository, so that you can say release
x.y.z is made from commit abcd1234, you can make the release from one
directory, and when you have CI there's only one CI job to validate
the software.

(I don't know the rationale for splitting into separate git
repositories. If the rationale was to decouple the versions in the
repositories then separate releases makes sense, because you might
want the release schedules to drift apart in future, and you don't
want something that is one tarball today become 2 or 3 tarballs in
future.)

And for the first ASF release, while you're debugging the process,
pick just one repository. You can always repeat the process on the
other two repositories a week later.

Julian

On Wed, Nov 2, 2022 at 4:13 PM Frank Greguska  wrote:
>
> I believe we settled on 3 artifacts:
>
> apache/sdap-nexus-webapp
> apache/sdap-collection-manager
> apache/sdap-granule-ingester
>
> There was still some active discussion on if these should share a version
> number or not. For sake of argument, let's say they do.
>
> So tarball would be something like
>
>- apache-sdapv1.0.0
>   - sdap-nexus-webapp
>  - source code
>  - sdap-collection-manager
>  - source code
>  - sdap-granule-ingester
>  - source code
>
>
> Github repos would all have v1.0.0 tags/releases
> Docker repos would all have v1.0.0 tag
>
> On Wed, Nov 2, 2022 at 3:52 PM Riley K. Kuttruff  wrote:
>
> > Will there be a tarball corresponding to the Nexus & Ingester repos or
> > will both be consolidated into one tatball?
> >
> > Sent from my Verizon, Samsung Galaxy smartphone
> > Get Outlook for Android
> > 
> > From: Perez, Stepheny K (US 398F) 
> > Sent: Wednesday, November 2, 2022 3:47:25 PM
> > To: dev@sdap.apache.org 
> > Subject: Ex: [DISCUSS] Towards release 0.4.5a56
> >
> > Hi everyone,
> >
> > I’d like to start the conversation regarding our first official Apache
> > release. From what I can tell, these are the major items that need to be
> > completed before we can move forward:
> >
> >
> > 1.   Identify a release manager. Any volunteers?
> >
> > 2.   Create release tarball
> >
> > 3.   Write release notes
> >
> > 4.   Write installation instructions from source (Riley Kuttruff has
> > started this work)
> >
> > 5.   Push docker images to Dockerhub (and update quickstart with these
> > versions)
> >
> > Another important task before moving forward would be testing the latest
> > SDAP analysis image 0.4.5a56. I have personally used this version without
> > any issues. Has anyone else upgraded to this latest alpha version?
> >
> > Thank you!
> > Stepheny
> > CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise
> > caution when clicking links or opening attachments. Please forward
> > suspicious email to suspectem...@cpp.edu.
> >
> >

Re: [EXTERNAL] November Apache SDAP report draft

[Julian Hyde]

It’s not a release for Apache’s purposes because it hasn’t been through the 
signing/vote/publish/announce process. An Apache release is a legal and 
community action more than it is a piece of code. The software quality of the 
release (e.g. ‘alpha’) is irrelevant to Apache, but the process of creating the 
release is all-important.

Yes, I think you should remove the release from the report. If you do that I’ll 
amend my comments.

I am happy to work with SDAP committers on an Apache-style release. We can 
probably use the 0.4.5a56 tag as a starting point. A good starting point would 
be an email to the dev list with the subject “[DISCUSS] Towards release 
0.4.5a56” asking when would be a good time for a release, volunteer for release 
manager, agree on a list of tasks, etc.

Julian




> On Nov 2, 2022, at 11:38 AM, Perez, Stepheny K (US 398F) 
>  wrote:
> 
> Julian,
> 
> The release I was referring to in our report was 0.4.5a56 which is an alpha 
> release. Would specifying this in the report make it more accurate? If not, I 
> can remove that from the report altogether. Thanks for your feedback.
> 
> Stepheny
> 
> From: Julian Hyde 
> Date: Wednesday, November 2, 2022 at 11:22 AM
> To: dev@sdap.apache.org 
> Subject: [EXTERNAL] Re: November Apache SDAP report draft
> Thanks for writing and submitting the report, Stepheny.
> 
> I signed off and made the following comments:
> 
>> The report says that there has been a release. I dispute
>> that. There is no release vote on dev@, no mention of the
>> release on dev@, nothing on announce@, and no downloads page.
>> 
>> As far as I can tell, this project has never made an Apache
>> release.
>> 
>> SDAP's number 1 problem is their use of dev@. There is activity
>> in the project (including commit messages going to dev@) but
>> questions asked on dev@ go unanswered, and therefore
>> conversations don't happen. Even the report is drafted on
>> private@ rather than dev@.  I think I can work with SDAP and get
>> them to graduate but only if they engage on dev@.
>> 
>> I have given notice that I will resign as a mentor by Dec 31st if
>> I don't see activity, namely a plan to graduate, and activity to
>> carry out that plan.
> 
> Julian
> 
> 
> On 2022/11/02 00:57:44 "Perez, Stepheny K (US 398F)" wrote:
>> Hello,
>> 
>> Attached you will find a draft of the November 2022 Apache SDAP report. In 
>> this report, I’ve included details about what steps we still need to take 
>> before graduating and a target date for graduating. Please provide feedback 
>> on the contents, as I’ll be submitting the reporting today at C.O.B.
>> 
>> Thank you!
>> Stepheny
>> 
>> 

Re: November Apache SDAP report draft

[Julian Hyde]

Thanks for writing and submitting the report, Stepheny.

I signed off and made the following comments:

> The report says that there has been a release. I dispute
> that. There is no release vote on dev@, no mention of the
> release on dev@, nothing on announce@, and no downloads page.
>
> As far as I can tell, this project has never made an Apache
> release.
>
> SDAP's number 1 problem is their use of dev@. There is activity
> in the project (including commit messages going to dev@) but
> questions asked on dev@ go unanswered, and therefore
> conversations don't happen. Even the report is drafted on
> private@ rather than dev@.  I think I can work with SDAP and get
> them to graduate but only if they engage on dev@.
>
> I have given notice that I will resign as a mentor by Dec 31st if
> I don't see activity, namely a plan to graduate, and activity to
> carry out that plan.

Julian


On 2022/11/02 00:57:44 "Perez, Stepheny K (US 398F)" wrote:
> Hello,
> 
> Attached you will find a draft of the November 2022 Apache SDAP report. In 
> this report, I’ve included details about what steps we still need to take 
> before graduating and a target date for graduating. Please provide feedback 
> on the contents, as I’ll be submitting the reporting today at C.O.B.
> 
> Thank you!
> Stepheny
> 
> 

Re: Podling Sdap Report Reminder - November 2022

[Julian Hyde]

The report needs to be submitted in a few days. Is there a volunteer to write 
it?

There has been some discussion about graduation this month. In the report I 
would like to see a plan for how SDAP intends to graduate, and a timeline for 
when that can happen.

As I have said before, I came on board as a mentor to give SDAP a push over the 
finishing line, if that is what it needs. But if the project doesn't want to 
graduate, I can't do anything about that and I will be wasting my time. If I 
don't see a commitment to graduate and active steps to make it happen, I shall 
be gone by Dec 31st.

Julian

On 2022/10/23 04:08:45 jmcl...@apache.org wrote:
> Dear podling,
> 
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
> 
> The board meeting is scheduled for Wed, 16 November 2022.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, November 02).
> 
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
> 
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
> 
> Thanks,
> 
> The Apache Incubator PMC
> 
> Submitting your Report
> 
> --
> 
> Your report should contain the following:
> 
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/November2022
> 
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
> 
> Note: The format of the report has changed to use markdown.
> 
> Mentors
> ---
> 
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
> 
> Incubator PMC
> 

Re: [DISCUSS] Steps to graduation

[Julian Hyde]

Thanks to everyone who joined the discussion.

It looks to me as if the project has a healthy level of ongoing development, 
and the community works together effectively on the mailing lists.

There are only two things missing: 
 (1) a release,
 (2) for the community to say 'yes! we're ready to graduate!'.

Sure, continuous integration (CI) is nice. But it's not essential. A 
well-running Apache community will create CI if they need it. So if you don't 
have CI, I guess you don't need it.

Under Apache, a release is a legal act, not a piece of software engineering. 
You need to collect the source code into a tar ball (tar.gz file, or similar), 
write release notes, write instructions for someone who has downloaded the 
release to build it (or otherwise get it running), check that the appropriate 
headers, license and notices are present, and then vote that the tar ball looks 
like a valid release.

The software engineering steps in a release are rather simple. You don't need 
Maven to create the tar ball; the following two shell commands are probably 
good enough:

  git ls-files > /tmp/manifest.txt
  tar cvfz sdap-x.y.tar.gz -T /tmp/manifest.txt

You will need to sign the release tar ball, and you will need to publish the 
KEYS file that contains the PGP key that was used to sign the release. After 
the release you will need to add a Downloads page to the web site, and the 
release manager should publish the steps that they used to perform the release, 
so that you can repeat the process.

That's it, really. If someone volunteers to be release manager (RM), they can 
roll a first release candidate, the mentors can critique it, and we can iterate 
until we have a good release. So, are ready to get started? :)

Julian

On 2022/10/14 19:30:10 Nga Chung wrote:
> Hi all,
> 
> I am an active member as well and am currently invovled with several NASA
> funded projects that leverage and contribute to SDAP.
> 
> As both Trevor and Frank had already mentioned, getting an official release
> out has been the biggest hurdle.
> 
> We had an attempt last year to set up GitHub Actions to automate the build
> process but ran into a hurdle with pushing images to Docker Hub, so that
> was left unfinished.
> 
> Besides a formal release, I've heard from Stepheny that we also need to
> identify a PMC chair, though I'm not clear what the process for that is.
> 
> We could really use a clear checklist of items we must complete in order to
> graduate.
> 
> Thanks,
> Nga
> 
> On Fri, Oct 14, 2022 at 10:57 AM Frank Greguska  wrote:
> 
> > Hi Julian,
> >
> > I am an active member but mostly just admin stuff at this point; not able
> > to provide much development support. I agree with Trevor's assessment that
> > the hardest part has been trying to get a release together for review by
> > Apache. There's a lot of history there I won't get into but I know there is
> > a current effort underway to try again.
> >
> > - Frank
> >
> > On Fri, Oct 14, 2022 at 9:52 AM Trevor Grant 
> > wrote:
> >
> > > Based on what I've seen from the project for the last couple of years,
> > > here's my short synopsis of the status wrt graduating.
> > >
> > > To graduate, a project must cut an official release. This is the main
> > point
> > > holding SDAP back from graduation. Apache as an organization was designed
> > > for creating and releasing Java projects, SDAP is a Python project.
> > (There
> > > are Python projects elsewhere in the ASF, but I will stand by my original
> > > statement, that Java is first class, everything else should adapt to
> > Java).
> > > SDAP as a community has focused the majority of its cycles to supporting
> > > existing deployments of their software as opposed to refactoring to
> > conform
> > > with ASF things. I don't think there exists undue stress from the ASF to
> > > conform- just a lack of documentation for non-Java paths.
> > >
> > > My recommendation in terms of cutting a release (and thus removing the
> > > largest hurdle to graduation) would be to
> > > 1. call a code freeze
> > > 2. tag / create a zip file of the current code base.
> > > 3. have various PPMC member test the code (what ever that means in
> > relation
> > > to SDAP)
> > > 4. vote
> > > 5.manually push the zip file to whatever repository that is needed.
> > >
> > > I know there are lots of maven plugins that automate #5, that will be
> > > effectively unusable since this isn't a Java project. Just get ahold of
> > > someone at Infra and ask them what you need to do to manually release a
> > > source tar ball. Then document it, maybe put it on the website- and make
> > a
> > > plan to do it again once a year to keep the board off your back. I know
> > > your real life users don't care about official releases anyway, so it's
> > > just a formality that has to happen every so often.
> > >
> > > My .02
> > >
> > > tg
> > >
> > >
> > > On Thu, Oct 13, 2022 at 1:17 PM Justin Mclean 
> > wrote:
> > >
> > > > Hi Julian,
> > > >
> > > > Thanks for reachin

[DISCUSS] Steps to graduation

[Julian Hyde]

I attended Stepheny's talk at ApacheCon in New Orleans last week, and
was impressed at the set of software you have all built. But also
surprised that after five years the project has still not graduated
[1].

With Trevor as the only active mentor, it seems that you could use
another mentor; I offered on the private@ list, and Nga was positive
about the idea, so I have signed up.

Let me briefly introduce myself. I am a member of the Apache Software
Foundation (most active in Calcite, but also a PMC member of Arrow,
Drill, Druid, Hop, Incubator Kylin) and have mentored several
podlings, most recently Hop and Baremaps. My day-job is as a staff
engineer at Google, writing database/Business Intelligence software.

If you are an active member of SDAP, can you reply to this email? I am
interested in people who are working on code, but also people who are
using SDAP, and PPMC members who are available to vote on releases and
help with administrative tasks.

Do you think SDAP is ready to graduate? If it is close to graduation,
what steps are left to do?

Julian

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/October2022#sdap