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.

Sign up for GitHub

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

Jump to bottom

Adhere to Go naming conventions and design principles in the OCM library #114

Closed
3 tasks
Tracked by #39
morri-son opened this issue Jul 12, 2023 · 0 comments
Closed
3 tasks
Tracked by #39

Adhere to Go naming conventions and design principles in the OCM library #114

morri-son opened this issue Jul 12, 2023 · 0 comments
Labels
area/ipcei Important Project of Common European Interest area/quality Output qualification (tests, checks, scans, automation in general, etc.) related component/ocm-core Open Component Model Core aka. go API lifecycle/stale Nobody worked on this for 6 months (will further age)

Comments

@morri-son
Copy link
Contributor

morri-son commented Jul 12, 2023 •
edited
Loading

User Story: Adhere to Go naming conventions, design principles and "Effective Go" practices in the OCM library

Description:
As a developer, I want the software library to adhere to Go naming conventions, design principles and "Effective Go" practices, so that the code is intuitive and easy to work with and possible contributors can easily be onboarded.

Acceptance criteria:

  • The OCM library follows Go naming conventions
  • The code in the library follows "Effective Go" practices
  • The code is intuitive and easy to understand for any Go developer.
This was referenced Jul 12, 2023
Closed
Closed
Closed
Closed
@In-Ko In-Ko mentioned this issue Mar 17, 2024
Closed
15 tasks
@morri-son morri-son mentioned this issue Aug 2, 2023
Closed
6 tasks
@morri-son morri-son added the area/ipcei Important Project of Common European Interest label Feb 6, 2024
@morri-son morri-son added the area/quality Output qualification (tests, checks, scans, automation in general, etc.) related label Feb 15, 2024
@morri-son morri-son transferred this issue from open-component-model/ocm Mar 17, 2024
@morri-son morri-son added the component/ocm-core Open Component Model Core aka. go API label Mar 17, 2024
@morri-son morri-son moved this from 🆕 ToDo to 📋 Next-UP in OCM Backlog Board May 5, 2024
@morri-son morri-son moved this from 📋 Next-UP to 🆕 ToDo in OCM Backlog Board Oct 18, 2024
@morri-son morri-son added lifecycle/rotten lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/icebox labels Oct 22, 2024
@github-project-automation github-project-automation bot moved this from 🆕 ToDo to 🍺 Done in OCM Backlog Board Nov 14, 2024
@ocmbot ocmbot bot moved this from 🍺 Done to 🔒Closed in OCM Backlog Board Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ipcei Important Project of Common European Interest area/quality Output qualification (tests, checks, scans, automation in general, etc.) related component/ocm-core Open Component Model Core aka. go API lifecycle/stale Nobody worked on this for 6 months (will further age)
Projects
OCM Backlog Board
Status: 🔒Closed
Milestone
No milestone
Development

No branches or pull requests
1 participant
@morri-son