Skip to content

Commit 4733330

Browse files
committed
Meeting notes of August 27, 2024.
Signed-off-by: Jeff Lait <[email protected]>
1 parent 6719224 commit 4733330

File tree

1 file changed

+117
-0
lines changed

1 file changed

+117
-0
lines changed

tsc/meetings/2024-08-27.md

Lines changed: 117 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,117 @@
1+
Minutes from OpenVDB TSC meeting, August 27th, 2024
2+
3+
Attendees: *Jeff* L., *Greg* H., *Rich* J, *Ken* M., *Andre* P., *Dan* B.
4+
5+
Regrets: *Nick* A., *Ken* M.
6+
7+
Additional Attendees:
8+
Dhruv Govil (Apple), Jonathan Swartz (NVIDIA), Barry Dempsey
9+
10+
Agenda:
11+
12+
1) Confirm quorum
13+
2) Secretary
14+
3) VDB 12 Release Items
15+
4) License Changes
16+
5) Maintainer List
17+
6) CI Issues
18+
7) PRs to merge
19+
8) Next meeting
20+
21+
------------
22+
23+
1) Confirm quorum
24+
25+
Quorum is present.
26+
27+
2) Secretary
28+
29+
Secretary is Jeff Lait.
30+
31+
3) VDB 12 Release Items
32+
33+
a) Half support for v12
34+
35+
Should half grid be a REAL grid? Ie, should the macros for REAL grid
36+
type include it? Conclusion was they should not. Instead a
37+
higher-level named macro should contain Half.
38+
39+
With this decided it is a v12 candidate. Proxy grid test is
40+
failing, but other than that seems good. The problem is we can't
41+
instantiate a proxy tree at the moment.
42+
43+
b) fVDB
44+
45+
Will be a feature branch. Can we have a cadence separate from main VDB?
46+
Can binaries be released on a different place, like Anaconda?
47+
48+
NanoVDB has a separate release system.
49+
50+
Tags can be created on branches to mark a release point.
51+
52+
This would require the fVDB release to be based against a stable
53+
version of VDB.
54+
55+
Currently NanoVDB and fVDB are tightly coupled - improvements to
56+
NanoVDB are coming from fVDB. This suggests NanoVDB needs to match
57+
fVDB.
58+
59+
4) License Changes
60+
61+
Still trying to set up the second repo to verify CLAs.
62+
63+
5) Maintainer List
64+
65+
Unanimous for changing Committer to Maintainer
66+
67+
Unanimous that it is two maintainers to commit.
68+
69+
Unanimous that all current TSC member are also maintainers.
70+
71+
Unanimous that Jonathan Swartz to be added as a maintainer.
72+
73+
Jeff will attempt to update the relevant policy docs.
74+
75+
6) CI Issues
76+
77+
No good tricks to speed up CI debugging. Can sometimes turn off
78+
unnecessary runners, but some runners just take a long time until the
79+
first possible error.
80+
81+
The secret is for the Houdini download.
82+
83+
cudann download seemed to be failing. This is likely not from our
84+
runner side.
85+
86+
Need notes for the PR for CI to explain why some of the unusual
87+
solutions are present.
88+
89+
Why certain versions of clang? This is likely to try to match the g++
90+
of the VFX platform, but we are not sure. The docker images came from
91+
the ASWF. We have clang at all to catch more issues than g++ alone.
92+
93+
VDB12 will likely drop support for gcc9.
94+
95+
7) PRs to merge
96+
97+
a) 744 - remove boost any
98+
99+
Someone must approve by next meeting or it will be approved then.
100+
101+
b) 1723 - boost conversion traits
102+
103+
Waiting on the Half PR? We should take it out of the Half PR so this
104+
can get in, Half PR can rebase on top of the resulting change.
105+
106+
c) 1789, 1775 - Makes adaptive grid easier
107+
108+
1789 is needed so you can use the same Grid with different custom Trees.
109+
110+
1775 explores all possible instantiations and ensures they are handled.
111+
112+
These are both on schedule to be decided on by the next meeting.
113+
114+
8) Next Meeting
115+
116+
Next meeting is on September 10th, 2024. 2pm-3pm EDT (GMT-4).
117+

0 commit comments

Comments
 (0)