further update

team-best-practices.md

@@ -10,16 +10,21 @@ This document is not in its final version, **a team meeting which aim to address
 This document link to other specialised best practices (like coding best practices).
 
 Related links:
+ - Public WebSite: https://remix-project.org
  - Remix basic FAQ: https://hackmd.io/KVooMJhWRImCGq6zkDgW9A
  - Remix live: https://remix.ethereum.org
  - Remix alpha live: https://remix-alpha.ethereum.org
+ - Remix beta live: https://remix-beta.ethereum.org
  - Remix-ide NPM module: https://www.npmjs.com/package/remix-ide
  - Remix-lib NPM module: https://www.npmjs.com/package/remix-lib
+ - Remix-tests NPM module: https://www.npmjs.com/package/remix-test
  - Remix-solidity NPM module: https://www.npmjs.com/package/remix-solidity
  - Remix-debug NPM module: https://www.npmjs.com/package/remix-debug
  - Remix documentation: http://remix-ide.readthedocs.io/en/latest/
  - General gitter channel: https://gitter.im/ethereum/remix
  - Dev gitter channel: https://gitter.im/ethereum/remix-dev
+ - Dev plugin gitter channel: https://gitter.im/ethereum/remix-dev-plugin
+ 
  
 ---
 
@@ -37,7 +42,7 @@ Related links:
 
  - A milestone standup - scheduled before the beginning of each milestone, roughly on a monthly basis - which aim to define what will be included in the **next milestone** and who will work on what. This standup also help to set a clear long term vision.
  
- - A retrospective standup - after each released - which aim to talk about **best practices in general**: what is good, what is bad, how we can improve workflows.
+ - A retrospective standup - after each releases - which aim to talk about **best practices in general**: what is good, what is bad, how we can improve workflows.
 
  - A tour standup - Just after a release or whenever it is needed - which aim to demo, **explain in details** features, bug fixes or any part of the codebase.
  
@@ -67,7 +72,7 @@ Before starting coding, we should ensure all devs / contributors are aware of:
 
 # Story / Bug fix
 
-- Prioritised list of PRs / issues are tracked in a Github Project.
+- Prioritised list of PRs / issues are tracked in a Github Project, Remix IDE issues are managed by a prioritized backlog.
 - Every story can be executed by a single developer or a group of 2 or more developers (depending on the size and complexity)
 - Each dev should take the part he/she feels the most confortable with.
 - Later progress and discussion is updated directly on the issue or pull request (github).