Merge pull request #28 from vinomaster/master

Fix Issue #27

UTILITY_LIST.md

@@ -8,6 +8,8 @@ See the [Utility Project Lifecycle Management Guide](./workflow/UTILITY_WORKFLOW
 
 Listed herein, are those endeavors that seek to be listed and that have minimally reached the **Convene** phase.
 
+If you wish to have your public identity utility listed, please [follow these instructions](https://github.com/trustoverip/utility-foundry-wg/blob/master/workflow/UTILITY_WORKFLOW.md#utility-projects).
+
 ## Utility Directory
 
 | Name | Convener | Workflow Phase | Status | Layer 1 Tech | Support TIPs |
@@ -16,4 +18,3 @@ Listed herein, are those endeavors that seek to be listed and that have minimall
 | [Sovrin MainNet](https://www.sovrin.org) | [Sovrin Foundation](https://www.sovrin.org), Utah, USA | Maintain |Running | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | [SaturnV](https://github.com/trustoverip/technical-stack-wg/blob/master/_proposals/saturn-v-tip.md) |
 | [Bedrock Business Utility](https://bedrock-consortium.github.io/bbu-gf/) | [Bedrock Consortium](https://bedrockconsortium.org/) | Create| Membership Campaign and Project setup. | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | [SaturnV](https://github.com/trustoverip/technical-stack-wg/blob/master/_proposals/saturn-v-tip.md) |
 | [Indicio Network ](https://indicio.tech/indicio-testnet) | [Indicio.tech](https://indicio.tech), USA | Implement | TestNet Running | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | [SaturnV](https://github.com/trustoverip/technical-stack-wg/blob/master/_proposals/saturn-v-tip.md) |
-| [CanaCred](https://www.canacred.ca)| [Canadian Credential Network (CanaCred)](https://www.canacred.ca) | Convene | Planning phase, member recruitment | [Hyperledger Indy](https://www.hyperledger.org/use/hyperledger-indy) | TBD |

workflow/UTILITY_WORKFLOW.md

@@ -68,7 +68,8 @@ Initially, key decision topics will include:
 ### Convene
 One or more prospective stakeholders will typically emerge as the early convener(s) of a Utility Project. The Convener will help organize an initial set of prospective stakeholders. This group will gather to address some important topics:
 
-1. Why do we need a Utility?
+1. Who are the Conveners and/or Sponsors?
+2. Why do we need a Utility?
 2. What is unique about the desired Utility?
 3. Who will participate?
 4. What are the common stakeholder motivators?
@@ -111,8 +112,13 @@ Our **Utility Foundry Workflow** is a *work-in-progress*. Each workflow step wil
 ### Stories
 As the UFWG refines the * Utility Foundry Workflow Model*, sample descriptive experiences or hypothetical cases will be leveraged by the UFWG to validate our workflow model.
 
-1. [Bedrock Business Utility](./stories/bbu.md)
-2. [Indicio](./stories/indicio.md)
+The current list of stories is available [here](https://github.com/trustoverip/utility-foundry-wg/tree/master/workflow/stories).
 
 ### Utility Projects
 Refer to the list of [Utility Projects](../UTILITY_LIST.md).
+
+If you desire to have your public utility project listed, please do the following:
+
+1. Join the UFWG and have a representative regularly attend UFWG meetings.
+2. Provide answers to questions that will help demonstrate your projects status at the `Convene` phase. You can submit this information to the [UFWG Mailing List](mailto: [email protected])
+3. Submit a PR containing a new [Workflow Story](https://github.com/trustoverip/utility-foundry-wg/tree/master/workflow/stories)?