Jump to content
Gov  ·  Market  ·  Community  ·  Policies  ·  Funding  ·  Open Calls  ·  Get started

WikiDeal:Minimum Viable Product: Difference between revisions

WikiVisor (talk | contribs)
Add missing intros per Theo's 20s rule
 
(19 intermediate revisions by 4 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 12: Line 15:


WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.  
WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.  
Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.


So, the whole project can consist of two main parts:
So, the whole project can consist of two main parts:
Line 19: Line 24:


== Key features ==
== Key features ==
Also see: [[Key Features]]
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 25: 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.
With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.


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.'''  '''1a) 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 : usecase scenarios - mockups   - workflows - development rules/structure (such as metatada/ontology principles) 1b) Studying the code of existing mediawiki extensions before developing, such as :   Pageforms, Semantic wiki, Cite extension, Wikibase client, abstract (reference : [[mediawikiwiki:Category:All_extensions|list of 1447 existing mediawiki extensions]]) <br />
# '''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:  
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:  
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Approved_Revs Approved Revs],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Cite Cite],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CommentStreams CommentStreams],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Data_Transfer Data Transfer],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Expiry Expiry],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:External_Data External Data],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth OAuth],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Mpdf Mpdf],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Page_Forms Page Forms],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageOwnership PageOwnership],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageProperties PageProperties],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:ParserFunctions ParserFunctions],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PerPageLanguage PerPageLanguage],
#:* [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:VisualEditor VisualEditor],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Wikibase Wikibase] (Wikidata client),
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
#:and perhaps some others.
# '''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.
#'''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
#'''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.
 
== Rough time estimates ==
Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions.
 
==== Customization of contract templates and clauses (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.
 
JavaScript for frontend: estimated 80-100 hours.
 
==== Basic contract creation (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.
 
JavaScript for frontend: estimated 80-100 hours.
 
==== Advanced contract creation & Post-Deal support (instance application) ====
Development: estimated at 140-160 hours.
 
==== Negotiation & Signing (instance application) ====
Development: approximately 160-180 hours.
 
=== Totals ===
''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.''
 
Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation)