Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expend use of Group for metadata #106

Open
vturpin opened this issue Sep 8, 2022 · 3 comments
Open

Expend use of Group for metadata #106

vturpin opened this issue Sep 8, 2022 · 3 comments
Labels
1.X For stuff to postpone and resolve only after the 1.0 release question Further information is requested
Milestone

Comments

@vturpin
Copy link
Member

vturpin commented Sep 8, 2022

Moderator: @OceanGlidersCommunity/format-maintainers

Can we expend the use of groups to

  • DEPLOYMENT_INFORMATION
  • PLATFORM_INFORMATION
  • FIELD_COMPARISON_INFORMATION
  • HARDWARE_INFORMATION
  • TELECOM_INFORMATION

Currently, those information are stored in variable. This would be coherent with the introduction of group in the format.

@vturpin vturpin added the question Further information is requested label Sep 8, 2022
@castelao
Copy link
Member

castelao commented Sep 8, 2022

Yes, I agree. I've been thinking about that. What is not clear to me yet is what would be the best structure and groups. There is no limitation on the number of groups to be used, but we might want to use no more than necessary. Did you have a structure in mind?

@vturpin
Copy link
Member Author

vturpin commented Sep 9, 2022

I agree, I would keep it simple.
I see two options :
Keeping it like this. 5 extra groups.
Or :
We could regroup DEPLOYMENT* and FIELD* under group DEPLOYMENT
And regroup PLATFORM, HARDWARE and TELECOM under HARDWARE.
That would be 2 extra groups.

We could consider a more hierarchical organisation but I think it is too early.

@vturpin vturpin added the 1.0 For stuff that must be resolved before we are able to release 1.0 label Sep 22, 2022
@castelao
Copy link
Member

Somehow I see all those in one single logical group. There is no hardware change once a deployment is initiated. But some failures could result in a hardware swap and re-deploy. Maybe the platform might be at a higher level, but I have the impression that all the rest would be within a deployment.

@castelao castelao added this to the OG-1.0 milestone Sep 24, 2022
@justinbuck justinbuck added 1.X For stuff to postpone and resolve only after the 1.0 release and removed 1.0 For stuff that must be resolved before we are able to release 1.0 labels Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.X For stuff to postpone and resolve only after the 1.0 release question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants