A little more doc work.

CONTRIBUTING

@@ -29,6 +29,11 @@ contribution.
 
 Other Guidelines:
 
+- Please do not use the nc_* namespace for projects you will be
+  releasing directly to the public, e.g. via ContentDB, Forums, etc.
+  This namespace should only be for things that will be included in
+  the base game.
+
 - Non-included contributions to the project, such as hosting or other
   services, content such as videos/streams, screenshots/galleries,
   reviews, stories and other publicity do not need to follow the

WISHLIST

@@ -45,11 +45,6 @@ to the project!
 	  way to handle "visinv" nodes, i.e. stacks, storage boxes,
 	  and other container nodes.
 
-- Help maintaining the hint system.
-	- Development of hints often lags behind development of new
-	  features, sometimes significantly.
-	- Hint organization and content is subject to improvement.
-
 - Improved versions of any art assets (sounds, textures, models).
 	- A custom skybox, preferably that looks good at limited
 	  resolution.
@@ -75,16 +70,5 @@ to the project!
 	- Let the developers know if you have shared something about
 	  NodeCore, or would like guidance creating something to share.
 
-- Door animations.
-	- These need to be relatively efficient, i.e. not involve
-	  a ton of node manipulation or spawning lots of entities.
-	  Of particular concern is network packet load on clients.
-	- Something using animated entities (which could represent
-	  multiple nodes sharing an axis) could work well.
-	- Alternatively, a reasonable particle effect?  Something
-	  abstract is fine too, as long as it conveys a sense of
-	  movement to help players visualize what's moving and in
-	  what direction.
-
 ........................................................................
 ========================================================================

docs/ideas.txt

@@ -190,5 +190,16 @@ IDEAS: Possible future additions/improvements to the game
 - Allow metalworking with wood tools?
 	- Eat a lot of extra durability?
 
+- Door animations.
+	- These need to be relatively efficient, i.e. not involve
+	  a ton of node manipulation or spawning lots of entities.
+	  Of particular concern is network packet load on clients.
+	- Something using animated entities (which could represent
+	  multiple nodes sharing an axis) could work well.
+	- Alternatively, a reasonable particle effect?  Something
+	  abstract is fine too, as long as it conveys a sense of
+	  movement to help players visualize what's moving and in
+	  what direction.
+
 ........................................................................
 ========================================================================

docs/issues-docs.txt

@@ -12,15 +12,16 @@ ISSUES-DOCS: Issues related to documentation
 - Add a code of conduct to project
 	- Cover chat rules from discord, servers?
 
-- Add guidelines about namespacing to contribution guide, i.e. don't
-  use nc_* names as those are reserved for NodeCore itself.
-
 - Add a credits file with more extensive/specific credits, including
   non-copyrightable contributions to core project...?
 
 - Add a README to the official screenshot world explaining how to use
 
 - Design doc needs another shakedown.
+	- Expecially: what has "nodecorian" come to mean?
+
+- Need to clean out issues in wishlist.
+	- Put some issues unlikely to be resolved on ice.
 
 ........................................................................
 ========================================================================