search

planetarysoftware / ISIS_TC

ISIS Technical Committee
https://github.com/USGS-Astrogeology/ISIS3
6 stars 11 forks source link

added Feb meeting stub #197

Closed Kelvinrr closed 5 months ago

Kelvinrr commented 7 months ago

The meeting tomorrow is going to be canceled, been out sick for some time and we dont have much in terms of discussion topics.

We can use this to add topics for March.

thareUSGS commented 7 months ago

Not sure I have this correct -- maybe a couple items.

  1. option for short-term meeting or "pair-programming" for PRs... maybe
  2. You talked about an RFC for the C++ complier version. Not sure that needs TC support.
KrisBecker commented 7 months ago

Yes that is what we discussed as potential topics for the next meeting.

Regarding the C++ complier issue, we would like to discuss the implications/impact of adopting the C++17 standard for ISIS and its dependencies.

AndrewAnnex commented 7 months ago

I'd also like to add a point about ensuring there are additional maintainers on relevant conda-forge feedstocks exclusively serving ISIS3. I have requested being added to 2-3 repos some weeks ago and I think there should be some redundancy/bi-annual review for all ISIS dependencies to ensure things are running smoothly with dependency updates

jlaura commented 7 months ago

@AndrewAnnex :+1: I think that is a great discussion. Within that, perhaps we can discuss whether folks need to be contributors to the source repo or if we are at a point (I think we are) where we can have different groups, some that are contributing to the code base and some that are supporting the packaging and delivery. This might be a very tangible place where the broader community can help the core development team a lot. Thanks for bringing it up!

KrisBecker commented 7 months ago

Hmm, looks like ISIS was recently updated to use the c++17 standard. However, ALE and USGSCSM are still at c++11. SpiceQL uses c++17 and c++20.

Isn't that a problem? Maybe not?

Kelvinrr commented 6 months ago

@KrisBecker The fact that it was already updated is a bit concerning, but it seemed to be updated specifically because we needed it to be up to date with other libraries. So it seems like it was more of a problem to be stuff in 11. We should probably get everything to at least 17 at this point.