Positive practices: Difference between revisions
m Category:Common terms (any better ideas?) |
Expanded to include source availability. |
||
| Line 33: | Line 33: | ||
* Does it have any dependencies, and can those dependencies become redundant? | * Does it have any dependencies, and can those dependencies become redundant? | ||
** ''Example: Products designed for a limited set of Operating Systems that may become outdated'' | ** ''Example: Products designed for a limited set of Operating Systems that may become outdated'' | ||
=== Source Availability === | |||
Often times companies will not provide or [[Security Through Obscurity|actively obscure]] details about how a product works. This exacerbates potential pitfalls mentioned above, but when information is provided it can eliminate many of them. | |||
==== Physical Good Considerations ==== | |||
* Does the product provide schematics? | |||
* Are parts available? | |||
** ''This helps product longevity by making repair easier, regardless of who does it.'' | |||
* Are there anti-repair measures in place? | |||
==== Digital Good Considerations ==== | |||
* Is the source code available? | |||
** ''This can allow patches if unwanted updates are pushed or support is dropped.'' | |||
* Are there [[DRM]] measures or in place? | |||
[[Category:Common terms]] | [[Category:Common terms]] | ||