move PRIV to a dedicated repository #77
Description
Problem
PRIV is central for pretty much all matters at blindnet, especially:
- product development (product-management)
- documentation (blindnet.dev)
- devrel (devrel-management)
- communication (communication-management)
Defining it in only a subdirectory inside product-management:
- makes it challenging to maintain, track and promote.
- gives the impression it is only used as an internal specification for blindnet product development
Proposed Solutions
Warning
Previous URLs pointing to a specific document in product-management would still need to work.
Each document's content would therefore need to be replaced with a warning e.g. "this document has been moved to ".Ping @milstan for an opinion on the following options, and preferred schedule.
1 - move to blindnet.dev
➕ pros
I'd personally recommend this option, and propose moving PRIV to a dedicated section (i.e. separated from docs, community and blog, with its own menu).
- Ease linking with the devkit documentation (as broken links are directly identified during build)
- No need for additional website development, configuration and upkeep (can be 100% done in < 1 day)
- Ease promotion (as part of the devkit's promotion)
➖ cons
- Proposing PRIV to a standards organization would still require moving or at least copying it to another dedicated place. However, this can be easily done subsequently and whenever needed using git subtrees.
2 - move to a dedicated repository
➕ pros
- help for all matters which only involve PRIV specifically (share, maintain, interact, propose as a standard)
- easily allow publishing PRIV on a dedicated website, with a dedicated domain name
➖ cons
- low incentive to additionally check other blindnet projects