opengeospatial / opengeospatial/bblocks
Naming convention for bblocks independent of register
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
A plan is underway for building block registers to be created for different governance domains and evolution processes.
The BuildingBlocks processing tools have a register import configuration and a bblocks:// resolver that allows for bblocks to be developed in one context then migrated to a new one.
The various status semantics need to be defined/explained in accordance with this process, which needs to be established.
@dr-shorthair and @rob-metalinkage are actively working to develop this proposal, and plan to prepare appropriate draft P&P to support a robust bblock development, testing and publishing cycle.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the BuildingBlocks processing tools' register import configuration and the bblocks:// resolver described in the issue. Define the status semantics and naming rules for moving building blocks between governance domains and evolution processes, with a documented development, testing, and publishing cycle as the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100