eclipse-score / eclipse-score/inc_security_crypto

Consistent feature/module name usage

Open
#194 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
3
Forks
15
Avg merge
1d 22h
Merged PRs (30d)
23

Description

### What

We currently have two issues in the names as seen here: https://eclipse-score.github.io/.github/#naming and needs to be corrected.
Image

we need to agree on the name to be used and apply these changes uniformly.
Option 1: security_crypto
Option 2: crypto

Hint: Bazel module name will always have a prefix score_, so this basically means bazel module name will be either score_security_crypto or score_crypto.

### Acceptance Criteria (DoD)

feature and module names correctly used and there are no errors seen here (everything is GREEN): https://eclipse-score.github.io/.github/#naming

### How

Changes may be only in security_crypto and/or score repo. needs to be checked from where the error is coming and correct them.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the naming guidance at https://eclipse-score.github.io/.github/#naming and inspect the security_crypto and score repositories to identify where the inconsistent feature and Bazel module names originate. Confirm which naming option is agreed, apply it consistently, and verify that the naming page shows everything GREEN.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.