Trusted Web of Colleagues (TWebC)

From Dataspects
Jump to: navigation, search
"I not only use all the brains I have, but all I can borrow."

Woodrow Wilson, Speech to the National Press Club on March 20th 1914

THE PROBLEM: the Overstretch Challenge...[edit | edit source]

We are professionals. And we are honest. There are limits to our pertinent personal knowledge, experience and time resources — but not to our number of trusted competent colleagues.

We have customers that are happy to pay us for what we help them achieve. And they rely on us. Sometimes our customers require services of a certain kind and/or so quickly that it overstretches that pertinent personal knowledge and experience and those time resources of ours.

THE SOLUTION: a Trusted Web of Colleagues (TWebC)[edit | edit source]

Currently, there are the following fundamental aspects to TWebC:

TWebC Aspect "Deputy Service"[edit | edit source]

If we are unavailable to respond to a customer's request, he or she can contact another TWebC colleague:

  1. chosen from either a list that forms part of the SLA in place, or
  2. chosen from mwstake.org/TWebC/colleagues.

If applicable and due to our honesty, we do not hesitate to relay that customer's request to another TWebC colleague of course — deemed more competent and/or resourceful for the task at hand.

TWebC Aspect "Resources Contraction"[edit | edit source]

If we face an overstretch challenge, we can fall back to TWebC:

  1. We can ask a TWebC colleague directly for helping with or handling the task at hand.
  2. We can "auction off" the task at hand — relying on TWebC's "trust service" to ensure corresponding competence and resource requirements are met.

TWebC Aspect "Single Customer Relationship Manager"[edit | edit source]

From our customer's point of view, we remain his or her only relevant contact and assume the full responsibility for all services provided by TWebC colleagues. We invoice our customer and pay our colleague.

TWebC Aspect "Colleague Profile"[edit | edit source]

TWebC colleague profiles are where both customers and colleagues turn to for:

  1. finding help,
  2. gaining trust in colleagues and
  3. endorsing other colleagues for a usefully specific combination of aspects regarding tasks, subjects and actions.

How are colleague profiles organized?[edit | edit source]

TWebC matches tasks/competences and colleagues based on corresponding signals and features:

A task signals an action to be performed on a subject in a context. 
A colleague possesses a competence by featuring the resources to perform an action on a subject in a context.
Example MediaWiki[edit | edit source]
TWebC-Competences TWebC-Tasks
### PAGE: User:Bob
   {{TWebCCompetence
       |TWebCTask=TWebC-Task-7462094635
       |TWebCTaskCredentials=
           {{TWebCTaskCredential
               |Type=Testimonial
               |Content=Has helped User:Alice on July 15th 2016 with configuring CentOS crontab for self-optimizing $wgJobRunRate.
           }}
   }}
### PAGE: TWebC-Task-7462094635
   {{TWebCTask
       |PointersToSubject=
           {{PointerToSubject
               |1=MediaWiki >= 1.34 >> Operation
           }}
           {{PointerToSubject
               |1=MediaWiki >= 1.34 >> Optimization
           }}
       |Subject=Job Queue
       |Actions=
           {{TWebCTaskAction
               |Action=Configure to run regularly
           }}
           {{TWebCTaskAction
               |Action=Configure to run continuously
           }}
           {{TWebCTaskAction
               |Action=Configure to run on page requests
               |UsesSettings=$wgJobRunRate
           }}
       }}
   }}
   https://www.mediawiki.org/wiki/Manual:Job_queue

TWebC Ontology[edit | edit source]

https://github.com/dataspects/TrustedWebOfColleaguesOntology

TWebC Aspect "Colleague Trust Levels"[edit | edit source]

Which aspects of a colleague's competence are covered by an attributed trust level?[edit | edit source]

These aspects form part of TWebC's Decision Support System.

  • Customer relationship criticality (CRC): If you entrust a colleague with a task and the customer is not satisfied, can you rectify the issue yourself at a later time without jeopardizing your customer relationship?
  • Data safety and system security criticality (DSSS): If you entrust a colleague with a task, does carrying out that task potentially jeopardize data safety or system security?
    • E.g. unintentionally disable Apache SSL, remove backup cronjob, reset standard passwords
  • Funcionality criticality (FC): If you entrust a colleague with a task, does carrying out that task potentially disable or alter functionality?
    • E.g. unintentionally disable extensions, disable Ajax by introducing JS errors, slow down semantic data integrity and consistency by disabling runJobs.php

TL1: Entrust a colleague with immediately reversible, non-critical system management tasks without potential affection of non-focused functionality[edit | edit source]

  • CRC:Low, DSSSC:None, FC:Low/easily reversible
  • E.g. edit template instances, form definitions, form templates, common.css, etc.

TL2: Entrust a colleague with TL1 + system management tasks with potential affection of non-focused functionality[edit | edit source]

  • CRC:Medium, DSSSC:Low, FC:Medium
  • E.g. edit templates affecting data semantization; install, remove, configure extensions; edit common.js; add/edit/remove Lua modules, etc.

TL3: Entrust a colleague with TL2 + complex data layer tasks[edit | edit source]

TL4: Entrust a colleague with TL3 + system components architecture alteration and/or extension[edit | edit source]

  • CRC:High, DSSSC:High, FC:High
  • E.g. add Solr/Elasticsearch, alter storage backend, alter general infrastructure like web server, database, caching, etc.

TL5: Entrust a colleague with TL4 + initial and strategic customer relationship aspects[edit | edit source]

  • CRC:Very high, DSSSC:High, FC:High
  • E.g. advise large new/existing customers in strategic aspects and in your name