(no commit message)

diff --git a/HDL_workflow.mdwn b/HDL_workflow.mdwn
index cbd4de971b846bcb6c7e4a86f186b00e4117cd7b..c16ea85433e9c856b10783a6d73b1ccb63ee1f2b 100644 (file)
--- a/HDL_workflow.mdwn
+++ b/HDL_workflow.mdwn
@@ -18,15 +18,15 @@ mailing list. Everything goes through there. <http://lists.libre-riscv.org/mailm
 * Use inline replies i.e. reply at the point in the relevant part of the conversation, as if you were actually having a conversation.
 * Follow standard IETF reply formatting, using ">" for cascaded indentation of other people's replies.  If using gmail, please: SWITCH OFF RICH TEXT EDITING.
 * Please for god's sake do not use "my replies are in a different colour". Only old and highly regarded people still using AOL are allowed to get away with that (such as Mitch).
-* Start a new topic with a relevant topic. If an existing discussion changes direction, change the topic (or start a new conversation)
-* DMARC is a pain on the neck. Try to avoid GPG signed messages.
-* Don't send massive attachments. Put them online (no, not on facebook or google drive or anywhere else that demands privacy violations) and provide the link.  Which should not require any kind of login to access.
+* Start a new topic with a relevant subject line. If an existing discussion changes direction, change the subject line to reflect the new topic (or start a new conversation entirely, without using the "reply" button)
+* DMARC is a pain on the neck. Try to avoid GPG signed messages. sigh.
+* Don't send massive attachments. Put them online (no, not on facebook or google drive or anywhere else that demands privacy violations) and provide the link.  Which should not require any kind of login to access. ask the listadmin if you don't have anywhere suitable: FTP access can be arranged.
 
-If discussions result in any actionable items, it is important not to lose track of them. Create a bugreport, find the discussion in the archives <http://lists.libre-riscv.org/pipermail/libre-riscv-dev/>, and put the link actually in the bugtracker.  
+If discussions result in any actionable items, it is important not to lose track of them. Create a bugreport, find the discussion in the archives <http://lists.libre-riscv.org/pipermail/libre-riscv-dev/>, and put the link actually in the bugtracker as one of the comments.  
 
-At some point it may become better to use the bugtracker itself to continue the discussion rather than to keep on dropping copies of links into the bugtracker.  The bugtracker sends copies of comments *to* the list however this is 'one-way'.
+At some point it may become better to use  <http://bugs.libre-riscv.org> itself to continue the discussion rather than to keep on dropping copies of links into the bugtracker.  The bugtracker sends copies of comments *to* the list however this is 'one-way' (note from lkcl: because this involves running an automated perl script from email, on every email, on the server, that is a high security risk, and i'm not doing it. sorry.)
 
-Also, please do not use the mailing list as an "information or document store". We have the wiki for that.  Edit a page and tell people what you did and include the link to the page.
+Also, please do not use the mailing list as an "information or document store". We have the wiki for that.  Edit a page and tell people what you did (summarise rather than drop the entire contents at the list) and include the link to the page.
 
 Or, if it is more appropriate, commit a document (or source code) into the relevant git repository then look up the link in the gitweb source tree browser and post that (in the bugtracker or mailing list) See <http://git.libre-riscv.org>