WikiDeal:Minimum Viable Product: Difference between revisions
Add missing intros per Theo's 20s rule |
|||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{KidsIntro|WikiDeal helps people share and build contracts together, like Wikipedia does with information. You pick the pieces you need, fill in your details, and get a custom contract ready to use.}} | |||
{{ExpertIntro|We are heading towards a hybrid architecture where MediaWiki serves as a decentralized repository for contract clauses and models while external instance applications handle personalized data, signing workflows, and federated storage. This emerging trend suggests that open-source contract governance benefits from separating community-curated legal templates from secure, user-controlled document management infrastructures.}} | |||
== Abstract == | == Abstract == | ||
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution. | WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution. | ||
| Line 21: | Line 24: | ||
== Key features == | == Key features == | ||
Also see: [[Key | Also see: [[:Category:Key Feature WikiDeal|Key features]] | ||
* '''Contract Models''': Templates for agreements open for community editing and discussion. | * '''Contract Models''': Templates for agreements open for community editing and discussion. | ||
| Line 27: | Line 30: | ||
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats. | * '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats. | ||
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed). | * '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed). | ||
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms. | * '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms. With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management. Feature nice to have on the MVP, or will be done in a second phase : | ||
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place. | * '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place. | ||
Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed. | Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed. | ||
== Planing == | == Planing == | ||
# | # Preparing and submit the MVP proposal to NLnet (done, not to be funded) NB : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing. | ||
# '''Users Needs analysis with experts.''' | # '''Users Needs analysis with experts.''' | ||
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt: | #: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt: | ||
| Line 63: | Line 64: | ||
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO] | #:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO] | ||
#:and perhaps some others. | #:and perhaps some others. | ||
# '''Ontology planning:''' defining metadata scheme for clauses | # '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc. | ||
# '''Development activities:''' implementing the core features identified in the earlier stages. | # '''Development activities:''' implementing the core features identified in the earlier stages. | ||
# '''Testing''' individual components. | # '''Testing''' individual components. | ||
| Line 96: | Line 70: | ||
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements. | # '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements. | ||
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations. | # '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations. | ||