From: Davin McCall <davmac@davmac.org>
Date: Thu, 11 Jul 2019 11:33:59 +0000 (+1000)
Subject: Update TODO, CONTRIBUTING
X-Git-Tag: v0.6.0~4
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=6dcffe15556c459dbaa6d54d40c0cc24a1f276a8;p=oweals%2Fdinit.git

Update TODO, CONTRIBUTING
---

diff --git a/TODO b/TODO
index 926a863..28319d8 100644
--- a/TODO
+++ b/TODO
@@ -5,7 +5,8 @@ For version 0.6.0:
   interrupt/ctrl+alt+del when they are prompted to press enter, to allow halt/rebooting instead of
   re-launching the boot service.  [DONE][ even better, you can now choose from several options! ]
 * Basic resource limits setting. [DONE, mostly. OpenBSD compilation issues, others need testing].
-* Per-service environment.
+* Per-service environment. [DONE].
+* shares_console processes should not be set as foreground process group [DONE]
 * Process start failure: track where in the launch process we get failure (i.e. we send errno over a pipe,
   we should send a state value as well).
 
@@ -13,11 +14,16 @@ For version 0.7.0:
 ------------------
 * dinitctl: Warn when stopping a service would cause a dependent to stop. Require a force flag to proceed.
 * dinitctl: implement "restart" command. 
+* provide a way to check configuration for errors (maybe a dinitctl command)
+  - eg. check a service and all dependencies
 
 For version 1.0:
 ----------------
 * "triggered" service type: external process notifies Dinit when the service
   has started. (maybe?)
+  - key thing is we want some way to eg mount filesystem once the disk comes up,
+    configure network when device comes up, etc, potentially relying an an external
+    tool/daemon.
 * on shutdown, after repeated intervals with no activity, display information
   about services we are waiting on (or, do this when prompted via ^C or C-A-D).
 * Documentation must be complete (see section below).
diff --git a/doc/CONTRIBUTING b/doc/CONTRIBUTING
index cd81ae5..ce5ecbb 100644
--- a/doc/CONTRIBUTING
+++ b/doc/CONTRIBUTING
@@ -20,8 +20,8 @@ reasonable standard of conduct (see Contributor Conduct below), or because I dee
 contribution includes features outside the intended scope. Feel free to contact me to sound
 out whether I would be likely to accept a submission for a particular feature.
 
-Contributors should feel free to create (or add themselves to) a CONTRIBUTORS list as part of
-the patch/pull request.
+Contributors should feel free to add themselves to the CONTRIBUTORS list as part of the patch/pull
+request.
 
 I will endeavour to respond to all offered contributions with civility and respect, even if I
 choose not to accept them.