XLP-Manual Chapter 10. Appendices
Constitution
Preface: A New Kind of Constitution
Typically, constitutions are decomposed into the following mutually exclusive elements: <ref>Note that this list is not collectively exhaustive. The specific articles that are included within a constitution vary depending on its purpose. A constitution for a country is very different to a constitution of a firm, which is very different to a constitution of XLP.</ref>
- 1. Membership
- 2. Purpose
- 3. Responsibilities
- 4. Rights
- 5. How to change or dissolve the constitution
The subsequent shape of the constitution will be outlined by the specifics of the boundaries of the above elements. Take the US constitution. The above elements are set as:
- 1. US Citizens, and eligibility for membership of Congress
- 2. To delineate the national frame of government
- 3. Of the Congress, Vice-President and President
- 4. Seen in a separate document, the US Bill of Rights, and in the Amendments to the Constitution
- 5. Proposed by Congress and ratified by the unanimous vote of all thirteen state legislatures
For a different purpose, for instance, defining the practices of a firm, the constitution may have the following boundaries of the above elements:
- 1. All full and part-time employees of the firm
- 2. To clearly define and govern the workflow, rights and responsibilities of all members within the firm, serving as a useful reference point in the case of any disputes:
- 3. To be punctual, treat others with respect, follow the order of command, and complete allocated work
- 4. Equal opportunities; rights of life, liberty and property; freedom from bullying or physical intimidation
- 5. A supermajority(of two-thirds of the total membership of the firm)at any meeting where 90% of total membership of the firm is physically present
The boundaries set by the XLP constitution, however, are of a different sort entirely. Let this be defined by the following boundaries:
- 1. Accounts: any member who holds the correct login credentials
- 2. To clearly articulate the rights, privileges and responsibilities of all accounts in the XLP. Useful to define the boundaries of practice, and to easily resolve any potential disputes
- 3. To be a fully-functional and productive member of the XLP and the Digital Publishing Workflow, rather as a Challenge Designer, Mission Executor, or both
- 4. Of life, liberty and property of all accounts of the XLP; equal opportunities; freedom from intimidation, bullying, or harassment of any kind
- 5. A supermajority of 80% of all accounts where at any gathering where at least75% of the total membership is virtually present
Where these examples differ is in the boundaries. Although membership is explicitly defined and referred to only in one section, all five sections are in relation to an agent of some kind. The first two are in relation to human beings, the third is in relation to accounts.
An account, as defined above, is a digital entity. This digital entity can belong to a human (such as human’s banking account) or a machine. What this constitution sets to clearly articulate is that the boundaries of membership lie not at the individual human but at the individual ac- count. Since accounts can belong to both humans and machines, this constitution is unique in its kind in two distinct ways:
- 1. It provides rights, privileges and responsibilities to machines
- 2. It treats machines and humans on an equal footing
This constitution makes no claim on the relative consciousness of machines or any non-human entity, it merely permits for its possibility. By treating all accounts as homogenous and identical, it gives all accounts a unique identity that is on equal relation to all other accounts. This process also allows for complete anonymity. By proving all accounts with the same rights, there exists no agent who can decipher whether an account belongs to a human or machine at first glance. This constitution, therefore, may go some way to passing the Turing Test. There will exist no unique feature belonging to any account that makes it below or above this constitution. This constitution abides by the rule of law:
- “[W]ith us no man is above the law [and] every man, whatever be his rank or condition, is subject to the ordinary law of the realm and amenable to the jurisdiction of the ordinary tribunals.” Dicey, A.V., 1982 [1885], Introduction to the Study of the Law of the Constitution, London: McMillan and Co.
This constitution, therefore, sets out the rights of accounts explicitly. It sets out the relations between accounts, the privileges and responsibilities of accounts with other accounts, what they owe for each other, and what they are guaranteed against each other. Whether a right of a human or machine account is irrelevant in determining the unlawfulness of an act, what is significant is that it was the jeopardy of the right in question was in relation to an account.
This constitution will be supplemented by a smart contract. The constitution provides the framework, whereas the smart contract handles the specifics. The constitution is the overarching set of rules, obligations, privileges and rights for the membership of accounts; the smart contract is one defined and created by the parties involved in a particular digital publishing workflow. That is, every account is to be governed by both this overarching constitution, and a smart contract which defines the specifics of one’s involvement in the XLP.
This constitution sets out the relations within and between teams. Each team comprises of Challenge Designers and Mission Executers attempting to carry out their own publication within the digital publishing workflow. In addition to each member’s role as a Challenge Designer or Exe- cuter, each member will have a role in the team. These roles are Officer (president), Treasurer (chancellor), Secretary (administrator) and Contributor (Team member). Between teams, there is a continuous red thread, representing the continuous communication and interconnected- ness between Teams. Throughout, each team’s Officer, Treasurers, and Secretaries will communicate to compare progress and ensure the smooth running of the XLP. Challenge Designers and Mission Executers, moreover, will regularly communicate for the purposes of collaboration, comparisons of publications, and to provide help and feedback to others.
This Constitution, moreover, is intended to be:
- 1. A specific constitution for the XLP
- 2. A meta constitution, providing a template for all societies and organisations worldwide
This constitution is worded such that any society or organisation will be able to apply this constitution to their own structure simply, by replacing a few specific words and phrases in the constitution. This constitution therefore is both specific and generic, and easily scalable.
Officer Meetings (OMs), for instance, is a characteristic specific to the XLP, but can be generalised to any organisation. There will be meetings held by Officers (Smart Contract leaders) at least once per month. They will have a quorum, a minimum attendance for the meeting to pro- ceed. Every Officer must (virtually) attend a minimum of 10 meetings per year in order to stay in the position. This will be where all the Officers will discuss any important changes to individual teams and to the XLP as a whole, and welcome new Officers. This will also be the case where appeals can be formally discussed, debated and voted upon. This concept of a general meet- ing of team leaders can be applied to any organisation with small teams, the only rewording required is the replacement of XLP with company-specific jargon.
The Officer of the team will be the one who creates the mission. She or he then edits the Smart Contract template which will govern the specific responsibilities of every other member in the team. Each member must digitally sign their smart contract with biometric authentication in or- der to become members of this team. Once signed, any member of the team may self-nominate to become Secretary or Treasury. By process of a Single Transferable Vote secret ballot across the entire team, the Treasurer and Secretary will be elected.
The constitution, therefore, is the foundation of the XLP. It is over and governed by the constitution that the Officer writes the smart contract, and it is over both the constitution and the specific smart contract that designers and executers create and complete the mission. The constitution serves to be an overarching framework governing all eventualities and processes for all members of the XLP. Should any equivocation arise or should alteration or dissolve of the constitution prove necessary, the constitution outlines the mandatory steps for resolution. The constitution is self-contained, and together with the smart contract, each member will have a complete specification of all assignments, responsibilities, rights, and much more.
The Constitution of The XLP
Last Revised: 28th August 2018
Article I – Objective
The Objective of the Extreme Learning Process, henceforth XLP, is to catalyse learning processes by facilitating digital crowd-learning activities.
Article II – Purpose and aims
The XLP exists and aims to:
- 1. Measure and improve organisational learning
- 2. Implement Logic models at and within each stage of the learning process
- 3. Recursively adapt and improve the XLP through adjustment and review
- 4. Expand the boundaries of coverage to the geographical and technological frontiers of learning
Article III – The Constitution
This document serves as the constitution of the XLP. This Constitution is subject for review not less than quinquennially. This constitution abides by the rule of law. All previous constitutions are hereby revoked.
Article IV – Smart Contracts
- 1. In addition to this constitution, all team members shall be governed by a team smart contract, and all Officers shall be governed by an additional Officer smart contract
- 2. Using a generic template, each Officer, defined in Article VI, shall write the specifics of a smart contract, to be agreed on by consensus with the other team members
- 3. The purpose of the team smart contract is to operate as a decentralised permission ledger, whereby each member is given a public and private key pair in order to allow function without an intermediary
- 4. To be a member of the team, a member must digitally sign their team smart contract with biometric authentication
- 5. The Treasurer and Secretary will then be chosen by a Single Transferable Vote secret ballot of all self-nominated members
- 6. Blockchain technologies shall be used to codify, automate, assign, and evaluate the specific privileges and responsibilities of each member within each contract. The operation of smart contracts will therefore function as a decentralised autonomous organisation
- 7. Once codified and agreed upon, a team smart contract becomes autonomous, and can only be amended by a majority of the team which includes the Officer
- 8. The Officer smart contract shall be written collectively by all Officers and to be binding it requires majority approval
- 9. Votes on the Officer smart contract and its updates shall be by Officers only
- 10. Unless specified otherwise, all votes on the contents, amendment, dissolution or otherwise of a team smart contract shall be in proportion to a member’s ownership of the mission, and all votes on the Officer smart contract shall be in proportion to the size of an Officer’s team
- 11. Once codified and agreed upon, the Officer smart contract becomes autonomous, and can only be amended by a majority of Officers in any Officer Meeting
- 12. All smart contracts operate in addition to, as opposed to in replacement of, this constitution; no smart contract may infringe on any liberty or responsibility laid out in this constitution
- 13. This constitution shall always be consulted before any other document, and is of paramount importance
Article V – Membership
- 1. Membership of the XLP belongs to any agent (virtual or physical) who possesses the correct account credentials, verifiable by biometric identification
- 2. Membership belongs to accounts and only accounts of the XLP. Each account shall have a unique character string in hash. This is the membership number of each account, and cannot be replicated
- 3. If account details are somehow stolen, any subsequent transactions immediately become null and void. A member shall give immediate public notice upon realising their account interference
- 4. Membership has an identical lifespan to its associated account. An account expires after 30 consecutive days without being governed by a smart contract. For Officers this expiry is after 90 consecutive days
- 5. Members shall have the right to terminate their membership at any time, by publicly declaring their intention so to do. Unless there is digital consent of at least three Officers, the smart contract will remain valid until its official expiry
- 6. Any individual can become a member of the XLP through official recognition of any XLP partner university, or by official appointment in an Officer Meeting
- 7. Membership becomes official only through a digital signature below a most updated copy of this constitution
Article VI – Roles
Every member of the XLP has two roles. Firstly, all members are either a Challenge Designer or a Mission Executer; the responsibilities for both are consistent with the overall objective of the XLP:
- 1. Challenge Designer: Members who design and test learning missions in accordance with the goals of sponsors, tailored for Mission Executers based on the available resources and requirements
- 2. Mission Executer: Members who participate in the missions designed by Challenge Designers, continuously learning to execute at a high level of complexity or speed, and guiding others to perform each mission
In addition, each member has one of the following additional roles within each team:
- 1. Officer: The leader and representative of the team in all communication
- 2. Treasurer: The operator of the team’s budget and finances
- 3. Secretary: The organiser of the team’s administration
- 4. Contributor: Any and all members of the team who do not belong to any of the above three categories
Article VII – Responsibilities
In addition to the responsibilities laid out in the relevant Smart Contact for a member’s team, each member’s roles include generic responsibilities laid out in this constitution. In every instance, the responsibilities laid out in this constitution are paramount. The responsibilities are the following:
Challenge Designer:
- 1. To collectively design a challenge a learning opportunity that facilitates learning by replication
- 2. To begin by writing a logic model for the entire course
- 3. To follow a customised logic model for the design of the challenge specification
- 4. To create a mission that is challenging but rewardable for the Mission Executers
- 5. To provide regular updates and feedback of and to the progress of Mission Executers
- 6. To communicate with Challenge Designers across teams for mutual inspiration and advice
- 7. To follow instruction from the Officer on designing the mission
- 8. To transfer the challenge to Mission Executers upon completion, continuously updating the mission with fixes and feature upgrades
- 9. To conduct a review with Mission Executers at the end of the course, evaluating the course effectiveness and opportunities for learning development
Mission Executer:
- 1. To follow the mission as set out by the Challenge Designers
- 2. To work collaboratively with other Mission Executers to follow the mission
- 3. To communicate with Mission Executers across teams for mutual inspiration and advice
- 4. To provide feedback to Challenge Designers on the quality and effectiveness of the mission
- 5. To work with the aim of eventually becoming a Challenge Designer
- 6. To follow instruction from the Officer on best practices for completing the mission
- 7. To conduct a review with Challenge Designers at the end of the course, evaluating the course effectiveness and opportunities for learning development
Officer:
- 1. To lead the team and oversee all team work
- 2. To begin by editing the Smart Contract template for the team. This sets out the specific responsibilities of each team member
- 3. To chair fortnightly team meetings. These meetings allow all members of the team to update every other team member on their progress on either the design or execution of the mission, and allow the Officer to update the team with new news or instruction
- 4. To virtually attend Officer Meetings (OMs), as outlined in Article XI
- 5. To represent all members of the team in the case of any disputes
- 6. To implement and enforce the rules of the constitution and smart contract within the team
- 7. To provide the Secretary with administrative tasks
- 8. To meet with the Treasurer to be updated on the team’s finances
Treasurer:
- 1. To oversee all spending and budget commitments by the team
- 2. To apply for funding to finance the spending of the team
- 3. To not overspend the finances given
- 4. To apply for loans, where necessary, whenever the budget is not balanced
- 5. To frequently meet with Treasurers from other teams. These Treasurer meetings are an opportunity for Treasurers to monitor the accounts of the XLP as a whole, and to evaluate individual requests for funding. Any member of the XLP is welcome to observe these meetings
Secretary:
- 1. To cover the team’s administrative tasks as given by the Officer
- 2. To make formal minutes in all team meetings
- 3. To monitor the membership of the team, updating relevant databases on member changes and introducing new members to the team
- 4. To act as a bridge of communication between Challenge Designers and Mission Executers, encouraging co-operating within and across teams
- 5. To publicise the mission and manage the logistics of digital publications
- 6. To investigate and report on appeals, where necessary, as laid out in Article XII
- 7. To act as the returning officer in Officer elections
Contributor:
- 1. To follow the command as instructed by the Officer
- 2. To frequently communicate with the rest of the team
- 3. To attend all fortnightly team meetings with updates and questions
Article VIII – Teams
- 1. The purpose and existence of each team within the XLP is to design and execute a mission
- 2. Each mission must be consistent with the objective, purpose and aims of the XLP as stated in Articles II and III
- 3. Each team shall include exactly one Officer
- 4. Each team shall include at least five members, which includes the Officer
- 5. If at any time a team has fewer than five members, a new member shall be found with high priority. If there exists fewer than five members for more than ten consecutive days, the team is automatically disbanded, and the Smart Contract terminated
- 6. No team shall include more than 25% of the entire membership of the XLP
- 7. Any team member except the Officer may belong to more than one team
- 8. A member can only hold the title of Secretary, Treasury or Officer in one team only
- 9. Each mission shall begin with an Initial Coin Offering, whereby each team member shall own a part of the mission
- 10. Each action by each team member into the mission shall be stored using Blockchain technologies for all to see
- 11. All major team decisions not covered by the smart contract shall be decided by secretballot voting within the team. Each team member receives a vote in proportion to their owner share of the mission
- 12. An Officer need not own the largest share of the mission, though they must own a share weakly greater than 5%
Article IX – Rights
These rights apply to every member of the XLP. Additional rights may be found in each member’s binding smart contracts
- 1. Every member has the right to life
- 1. Once provided with membership, an account can only be terminated through the processes laid out in Article V, or as an extenuating circumstance in Article XI
- 2. Termination of life is not in contravention of this Article only when essential and strictly appropriate force is required to prevent a member intentionally acting in a way that clearly breaches the right of another to life, liberty, or property. This will occur only in exceptional circumstances
- 2. Every member has the right to end their life
- 3. Any member can relinquish their membership at any time as laid in in Article V
- 4. Any smart contract may still govern such a member until its official expiry
- 3. No member shall ever be subject to physical or mental torture, or degrading treatment in any way
- 4. No member may own any other account except their own
- 5. No member shall be held in slavery or solitude
- 6. No member shall be forced to perform any action that may be considered unsafe or unlawful
- 7. No member shall be expected to work unreasonable hours, or in unreasonable conditions, at any point
- 5. Every member has the right to liberty and security
- 8. Any member found in violation of these rights at any time is subject to compensation
- 6. Any member who believes to be in violation of any right may make a formal complaint as laid out in Article XII. An Officer may issue a complaint on a member’s behalf with prior electronic consent
- 9. A member may make an appeal on the decision of their formal complaint
- 7. No member shall be charged with breaching this constitution if the action in question, at the time at which the act was performed, was not a part of the constitution. Nor shall a heavier punishment be imposed than one applicable at the time when the action occurred
- 10. Any violation of this constitution, and appropriate punishment, shall be clearly explained to the member at the time of decision
- 8. Every member has the right to respect of their private life, family life, home and correspondence
- 11. There shall be no interference with this right except when necessary and proportional in order to prevent direct infringement with another right in this article
- 9. Every member has the right to freedom of thought, belief, and religion
- 12. Every member has the right to change their thought, belief, or religion at any time
- 13. Every member has the right to put their beliefs into action, except where they infringe on any other right, public safety, or morality
- 10. Every member has the right to freedom of opinion and expression
- 14. Any member may give or receive information to any other member at any time, unless when the providing of such information infringes on another right, infringes on this constitution, provides a risk to safety, or transmits the disclosure of information received in confidence
- 11. Every member has the right of freedom of assembly and association
- 15. Every member has the right to form and be a member of a union, party, or another association or voluntary group
- 16. This right applies in all instances except when the association is a risk to public safety, the rights or freedoms of others, or health or morals
- 12. No member shall be intimidated, bullied, or made to feel weak
- 13. Every member shall be treated with due respect
- 14. Equal Opportunities
- 17. There shall be no direct nor indirect discrimination on the grounds of gender, race, colour, ethnic, national or social origin, sex, sexual orientation, pregnancy, maternity, disability, religious or political belief, marital status, age, property, birth, or other status’
- 18. The decision on the appointment of any new member, or the election of any new position, shall not be made, partly or fully, on any of the above characteristics. This includes, but is not limited to, discriminatively: altering the arrangements in deciding to whom to give a position, altering the terms of appointment or election, and not offering appointment or vote
- 19. No member may act in a way that discriminatively reduces or increases the current or future potential direct or indirect opportunities another member has or will have access to
- 20. No member may discriminate against another in a way that affords another access, or by not affording another access, by offering or not opportunities for resources or training, or for receiving or not any other faculty
- 21. Any member, when making any decision, shall have due regard for exercising it in such as a way as to reduce the inequalities of outcome which result from socioeconomic disadvantage or otherwise
- 22. No Challenge Designer may design a mission that promotes harassment or discrimination on any grounds
- 23. No Challenge Designer may discriminate against a Mission Executer in the way it provides education, in the way it affords Mission Executers access to the mission or any service, by not providing Mission Executers with education, by excluding or expelling a Mission Executer, or by subjecting Mission Executers to any other deterrent
- 24. Any member who feels to have suffered discrimination on any grounds may issue a formal complaint as specified in Article XII. If it is decided that discrimination on any grounds did occur, the defendant shall be immediately expelled
- 25. There shall be no harassment under any circumstances
- 26. No decision of an official complaint or appeal may be based on any discriminatory factor
- 27. A term of a smart contract is void and unenforceable against a person if it constitutes, promotes or provides for treatment of that or another person that is discriminatory. Where necessary and equivocal, this decision shall be made in an Officer Meeting
- 15. Every member and association has the right to their own property without interference
- 28. No property owned by any member outside of the XLP can ever be taken away through any activities associated with the XLP
- 29. Property within the XLP can be revoked only when it is necessary to remain consistent with this constitution. Any revoked property requires suitable and proportional compensation
- 16. No member shall be denied the right to education
Article X – Officers
- 1. The initial Officer of any team is the member who creates the mission
- 2. The initial Officer faces election eleven months after the creation of the mission
- 3. Every subsequent Officer election within each term will occur biennially
- 4. Each Officer election shall be held only within the team over which the Officer leads, and voting shall be conducted using the Single Transferable Vote secret ballot of all selfnominated members
- 5. There shall be a period of one month where, if a different Officer is to be elected, this newly elected Officer becomes Officer-elect, and shadows the Officer in their daily business. An official transfer of power follows.
- 6. There exists no term limits on an Officer
- 7. Any Officer may resign with immediate notice. A by-election shall follow within two weeks
- 8. If an incumbent Officer wishes to become Officer of another team, they must resign in their current team before they join and nominate themself in another
- 9. Any Officer may be impeached through a vote of no confidence by the team. This vote may be initiated by any team member at any time and requires a 50% majority in a secretballot team vote for the Officer to be impeached. In the case that an Officer is impeached, a by-election shall occur within two weeks
- 10. If in their most recent team they were Officer, a former Officer may remain a member, but not an Officer, for 90 consecutive days. If such a former Officer finds another team or starts their own within this window, they shall continue to be a member of the XLP. If after 90 consecutive days they are without a team, their membership immediately expires
Article XI – Officer Meetings
- 1. An Officer Meeting shall occur Monthly, on the first Thursday of each Month, and shall last for a minimum of 30 minutes
- 2. Each Officer must virtually attend the entire duration of a minimum of ten Officer Meetings annually
- 3. Officer Meetings will function like a direct democracy, where any Officer may propose debates, motions, amendments, or dissolution. All Officers can collectively vote on any issue. The majority of 50% shall always be decisive, unless specified elsewhere in this constitution
- 4. Any member of the XLP can observe any Officer Meeting, and may participate only in Member Questions
- 5. At any point during any Officer Meeting, any member can call for quorum. If there exists fewer than 75% of all Officers present, the meeting immediately terminates, and will be replaced with one the next Thursday at the same time. An inquorate meeting does not count towards an Officer’s minimum attendance of at least ten Officer Meetings annually
- 6. In the event that quorum is not reached for three continuous Thursdays in one Month, the fourth Thursday shall have compulsory attendance for all Officers: any Officer failing to attend with adequate reasoning shall have their position immediately withdrawn
- 7. There exists no leader in an Officer Meeting; the meeting shall be governed collectively by all Officers present
- 8. The order of every Officer Meeting shall proceed as follows:
- 1. Welcoming. Any new Officer shall be briefly welcomed
- 2. Updates. Any Officer with significant updates, that cannot be distributed in text format at a different time, will update and discuss with the other Officers
- 3. Complaints and Appeals. Any formed complaints and appeals shall be debated and voted on
- 4. Miscellaneous items. Any items that do not fall into any of the above categories will be discussed, and, where necessary, voted on
- 5. Member Questions. Members, selected by ballot, will have the opportunity to ask unseen questions to any or all Officers, for an immediate public response. This section shall last for no fewer than twenty minutes. Each question, including appropriate time for answers and responses, is limited to a maximum of two minutes in total
Article XII – Complaints
- 1. Should a member have cause for complaint about the administration of their team or the XLP, the provision of services thereby, or the conduct of Officers, and register that complaint in the form of a letter to their Officer, that Officer shall constitute a tribunal to investigate the complaint with all deliberate speed
- 2. If the complaint is directed at the behaviour or actions of a team’s Officer, then the complaint should be made known to the team’s Treasurer, who shall constitute a tribunal with all expediency
- 3. A tribunal shall consist of ten XLP members selected by sortation. Any member selected has the right to decline if they so wish. The Tribunal shall investigate the veracity and accuracy of the complaint, and shall present a report at the next Officer Meeting. Should the tribunal uphold the complaint, the next Officer Meeting must ensure that action is taken to resolve it
- 4. If the Tribunal concludes that a member has breached this Constitution in any way, a vote of no confidence in that member must be held at the next Officer Meeting
- 5. Should either party to the complaint wish to appeal, they may have recourse to their team’s Secretary, who will investigate and report on the complaint at an Officer Meeting as soon as practicable.
Article XIII – Extenuating Circumstances
- 1. In the event that there is significant and unexpected damage or loss to a crucial part of the operations of the XLP, there shall be called an Emergency Officer Meeting at the earliest opportunity
- 2. At any Emergency Officer Meeting quorum is reduced to 50% of all Officers present
- 3. An Emergency Officer Meeting may trigger the first of two consecutive meetings to amend or dissolve the Constitution. The second consecutive vote, however, may only occur in the ordinary monthly Officer Meetings as stated in Articles XI and XIV
- 4. The order of business in an Emergency Officer Meeting is restricted solely to the events and implications of the extenuating circumstances about which the meeting is formed
- 5. As each extenuating circumstance is unique, there is no fixed order of business. However, the following must be discussed, and where necessary, voted upon:
- 1. Immediate Actions. Any subsequent processes of high priority must be discussed and enacted
- 2. Long Term Actions. Processes of a direct or indirect result of the circumstance shall begin to be discussed. No formal vote is necessary until the next Officer Meeting
- 3. Disciplinary Actions (where appropriate). Any member intentionally contributing to the increase in likelihood of success of the extenuating circumstance shall receive appropriate penalisation
- 4. Honour (where appropriate). Any member intentionally contributing to the decrease in the likelihood of success of the extenuating circumstance shall receive appropriate reward
- 5. Future Precautions. Any necessary steps to eliminate the potential for another similar circumstance should be discussed and, where necessary, voted on
Article XIV – Disciplinary Procedure
- 1. If any member is found to be breaching the rules in any article of this constitution or their binding smart contract, disciplinary action shall occur
- 2. If a resolve of any smart contract breach is written into the smart contract, then the disciplinary procedure is automatic and machine-generated
- 3. If a member is found to be breaching their smart contract, and if no resolve is encoded within the smart contract, the Officer shall take appropriate action. This does not affect the member’s right to make a formal complaint on the Officer’s decision
- 4. If an Officer is found to be breaching their team smart contract, and if no resolve is encoded, a vote of no confidence within the Officer’s team shall be held within seven days
- 5. If an Officer is found to be breaching their Officer smart contract, and if no resolve is encoded, the Officer shall defend their actions at the next Officer Meeting. All other Officers shall vote on appropriate disciplinary action in a secret ballot, to have immediate effect
- 6. If any team member except the Officer is found to be breaching the rules of this constitution, the Officer shall suspend such a member for a minimum of seven days. A second constitution breach shall result in immediate XLP expulsion. Any breach of rights to any other member in the XLP at any point will result in immediate expulsion
- 7. If an Officer is found to be breaching the rules of this constitution, they must defend their case in the next Officer Meeting, whereby a secret ballot of all Officer members will decide the appropriate disciplinary action. If an Officer infringed on the rights of any other member, they face immediate expulsion, and a replacement shall be found in a team byelection
Article XV - Amendments & Dissolution
- 1. Amendments to the Constitution shall be made in Officer Meetings only. An amendment can be proposed by any Officer, and all members, not only Officers, may vote on and amend an amendment. The vote shall be held by secret ballot with the Single Transferable Vote electoral system. Any amendment requires a majority vote in two consecutive Officer Meetings reaching quorum to be changed into the Constitution, and will apply immediately once the second vote has a majority in proposition
- 2. Members shall leave the XLP at any point as set out in Article V
- 3. If a situation arises where the XLP must or wishes to dissolve, it requires two majority votes of at least 80% in two consecutive Officer Meetings reaching quorum. The vote will be held by secret ballot with the Single Transferable Vote electoral system. Any member virtually present may vote on the notion to dissolve the XLP. A proposition to dissolve the XLP may be proposed by any Officer in any Officer Meeting
How to: Use MediaWiki
You will use the wiki to group edit your report and other documents.
A wiki is a website on which users collaboratively modify content and structure directly from the web browser. In a typical wiki, text is written using a simplified markup language.
Wikipedia is by far the most popular wiki-based website, and is one of the most widely viewed sites of any kind in the world, having been ranked in the top ten since 2007. There are tens of thousands of other wikis in use, both public and private, including wikis functioning as knowledge management resources, notetaking tools, community websites, and intranets. The English-language Wikipedia has the largest collection of articles; as of September 2016, it had over five million articles.
We use Mediawiki, the same software that runs Wikipedia, to allow participants to collaboratively create reports and other documents.
Log In
Click on OAuth2Login on the top right of your MediaWiki install. Your coordinator should have given you the address.
Create a NewPage
- 1. Go to http://yourwebsite.com/index.php/page_title where page_title is the name of the page you want to create.
- 2. Click Create
- 3. Write in your text as needed. Don’t worry about adding a title, since the title will be the name of your page.
- 4. Write a one sentence summary in the Summary box, and then click Save changes.
Edit a Page
You can edit any page on the wiki, including the front page:
- 1. Go to the page you want to edit.
- 2. Click Edit at the top of the page.
- 3. After making changes, write a one sentence summary in the Summary box, and then click Save changes.
Format Text and Insert Images
Mediawiki uses wikitext to format text, create lists, insert images, and so on. Instead of a graphical editor like Microsoft Word, you use a plain text box with special wikitext codes to turn text into headers or lists, and insert images:
Bold and Italic
’’’Bold’’’
’’Italic’’
Headings
= Heading Level 1 =
= Heading Level 2 =
== Heading Level 3 ==
And so on...
Lists
* Bullet 1
* Bullet 2
** Sub bullet
*** Sub sub bullet
# Numbered list item 1
# Numbered list item 2
## Numbered list item 2.1
### Numbered list item 2.1.1
Links
External links:
[http://www.link.com Link Title]
For example:
[https://news.wisc.edu/curiosities-what-determines-the-colors-of-the-
sky-at-sunrise-and-sunset/ Curiosities: What determines the colors
of the sky at sunrise and sunset?]
Links on your own wiki
[[Page title]]
For example:
[[Digital Wallet]]
Renaming a link on your own wiki:
[[Page name | Text you want]]
Citing a source:
The sky is blue<ref>Steven Ackerman, professor of meteorology at UW ‒ Madison</ref>
You can also embed links into citations (see above for link syntax)
Insert Images
- 1. Click Upload File on the left sidebar
- 2. Browse for your file and click the Upload file button.
- 3. When you’re editing a page and want to insert the image, type: [[File:filename.png]] If the image is too big, you can use
[[File:filename.png|500px]]
- to make it 500 pixels wide, for example.
How to: Use WordPress and Elementor
A blog (short for ”weblog”) is a discussion or informational website consisting of posts (diary- style updates, displayed newest-first) and pages (more permanent information)<ref name="multiple">Adapted from Wikipedia, July 30, 2018</ref>.
Our blogging software is WordPress: a free and open-source content management system. It is most associated with blogging, but supports other types of web content including more traditional mailing lists and forums, media galleries, and online stores. Used by more than 60 million websites, including 30.6% of the top 10 million websites as of April 2018, WordPress is the most popular website management system in the world<ref name="multiple"></ref>. Our WordPress installation includes several plugins to make editing easier, most notably Elementor.
Log In
Your coordinator should have given you a URL, username, and password for your WordPress installation. Use this to log in.
Create a New Report Page
One from person from each group should create the report page, based on what your group wrote in MediaWiki:
- 1. On the left-hand sidebar, you should see a link to Pages. Hover over the link and click Add New:
- 2. Enter a page title, then click Edit with Elementor to enable a richer editing experience:
- 3. Click the folder icon to select a template:
- 4. Select one of the first two (free) templates:
- 5. Preview your template. If you’re happy with the overall look, click Insert:
- 6. Start editing the ”widgets” (i.e. components) of your template by clicking a widget and editing on the left sidebar:
- 7. Insert new widgets by dragging and dropping from the left sidebar:
- 8. When you’re happy with the result, click Publish:
If you need to go back to the widget menu, you can click the grid icon:
Create a New Landing Page
All the groups should get together and nominate one person out of everyone to create a landing page. This page gives an overview of the whole experience and links to each team’s report.
- 1. Follow the steps above to create a new page, but don’t publish yet
- 2. You will need to create a link to each report page. This isn’t a simple process unfortunately. For each report you need to create a link to:
- 1. Hover over the Pages link on the left sidebar, then right-click All Pages and click Open in New Tab then switch to that tab (this means we don’t lose our editing work on our landing page)
- 2. Hover over the report page you want to create a link to. Below the title you should see a link to view the page. Right-click this, and select Copy Link Location (or whatever the menu item is called in your browser):
- 3. Go back to the tab you are using for editing your landing page
- 4. Drag and drop a button into the page, and paste the address you just copied into the Link box:
- Note: If you want to create a link another way, feel free. Buttons are provided as an example
- 3. Repeat this process for each report you need to link to
- 4. Click Publish:
Edit a Page
- 1. Hover over the Pages link on the left sidebar, then click All Pages
- 2. Hover over the page you want to edit, then click Edit’ with Elementor
Back Up Your Work
Remember Murphy’s Law? Anything that can go wrong will go wrong. So backup your files! On the WordPress sidebar, click Tools then Export:
Then click Download Export File:
In case of data loss or some other catastrophe, you can import this data into a fresh WordPress installation and get your data back.
For Participants Coming to China
- Download and register on WeChat. WeChat is THE chat app for China, and everyone you meet will have it installed.
- Download and install a VPN if you want access to Google, Facebook, Twitter, Youtube, WhatsApp, Line Messenger, and lots of other online services that are blocked in China
- Install Google Translate for iPhone or Android and the offline language pack for Chinese
- Install Pleco for Chinese character recognition
As mentioned above, many overseas resources can only be reached via a VPN. While using a VPN for your research is fine, we suggest you assume your industry report, presentation anything else you create will be accessed by users without a VPN. That means:
- No hosting your work on Google Drive, Dropbox, or other online services (OneDrive works
- No embedded YouTube videos for now, but don’t assume it’ll always be the case)
- Disable Google Fonts in your WordPress theme (if you installed a theme yourself)
Also, wifi and network connections may be unreliable, so make sure everything will run offline when you are presenting. Assume Murphy’s Law: ”Anything that can go wrong will go wrong.”
How to: Install WordPress and MediaWiki
You will need
- A computer running Docker
- Access to your command line
- Internet access for the initial container pull
Optional First Step
Creating a Docker container requires first downloading the ”image” that the container is based on. A Docker image isn’t a picture or photograph but rather a template containing all of the files, code, settings, and libraries required to build a container. You can make as many Docker containers as you would like from one Docker image; any container is just one instance of its corresponding image.
The code in the following sections automatically download the required images, but if you have limited access to internet and would like to download all of the images before trying to set up containers, you can run the following lines in your command line.
docker pull tuitu/dind-wordpress
docker pull tuitu/dind-mediawiki
docker pull tuitu/dind-piwik
”pull” tells Docker that you want to download an image, ”tuitu” is the name of the repository where the image is stored, and ”dind-wordpress”, ”dind-mediawiki”, and ”dind-piwik” are the names of the images.
MediaWiki
MediaWiki requires MariaDB database. From your command line:
docker run --name my_wiki -e DOCKER_DAEMON_ARGS=”-D” -e PORT=4444 -- privileged -d -p 80:4444 tuitu/dind-mediawiki
Docker run creates a new container. The ”--name” flag sets the name of the container. The first ”-e” flag sets the environment variable ”DOCKER_DAEMON_ARGS” to ”-D”. The 2nd ”-e” flag sets the environment variable ”PORT” = 4444. The ”--privileged” flag gives the container administrative rights. The ”-d” flag is short for ”--detached”, this means that the container can run without being directly controlled by a user. The ”-p” is short for ”--publish”, which sets the port for the container and exposes the host port; the first number after the ”-p” flag -- 80 -- can be changed to any available port or it can be left as the default. The last phrase specifies which image to use for the container.
docker exec -it my_wiki bash /TensorCloud/DockerInDocker/mariadb_mediawiki_4444.sh
Docker exec runs a command on an already started container. The ”-it” flag is a combination of ”--interactive” (allows for input) and ”--tty” (pseudo-terminal). The next phrase is where you specify which container you are dealing with. In our case, this is ”my_wiki”. The last two phrases say to use bash (a programming language) to run a script at the specified location. This is necessary for setting up the internal containers.
Wordpress
The steps for Wordpress and Piwik are similar to those of Mediawiki.
From your command line:
docker run --name my_wordpress -e DOCKER_DAEMON_ARGS=”-D” -e PORT=4445--privileged -d -p 81:4445 tuitu/dind-wordpress
docker exec -it my_wordpress bash /TensorCloud/DockerInDocker/mariadb_wordpress_4445.sh
Piwik
docker run --name my_piwik -e DOCKER_DAEMON_ARGS=”-D” -e PORT=4446 -- privileged -d -p 82:4446 tuitu/dind-piwik
docker exec -it my_piwik bash /TensorCloud/DockerInDocker/mariadb_piwik_4446.sh
And more, http://toyhouse.cc/wiki/index.php/Get_Started_with_Remix#Using_Remix
Accessing on your local machine
In your web browser, open:
Jenkins CI/CD Tools 127.0.0.1:87 admin 123456 OpenModelica 3D Modeling 127.0.0.1:84 N/A -->
How to: Crowd Learn with remote participants
While individual and group learning typically take place in just one location at a time, large- scale crowd-learning involves participants from all around the world. This introduces several challenges that need to be addressed to achieve worthwhile learning outcomes. This is espe- cially the case when dealing with China, where many online services are blocked<ref> Censored: Distraction and Diversion Inside China‘s Great Firewall, Margaret E. Roberts, Princeton University Press</ref>.
Why Crowd Learning?
- New Perspectives: People from different countries and backgrounds bring new perspectives to the table
- Clearer Documentation: Because all communication is electronic, your group learning consciousness is stored in MediaWiki, WordPress, and other tools
Advice
For Remote/Local Teams
- Video chat by default: so no one feels less valued or left out
- Video team-building activities: play into the strengths of remote work, like sharing your classroom view
- Assume good intent: Remember that the kinds of nuanced communication you get in a physical classroom setting don’t necessarily translate online.
- Make rules: Establish communication rules in the constitution that includes teams and their wishes directly in the creation. When to use chats? Why to write emails? At what point to pick up the phone? Over time these will becomes social norms for your crowd learning group.
- Build structure: When having meetings or giving updates, have clear structure, process and agendas so everyone can follow along, no matter where they are. Assign a meeting lead and a note-taker to ensure key points are captured in writing.
- Understand each others’ contexts: If Bob doesn’t get an instant reply from Alice, it doesn’t mean that Alice doesn’t care - she may be running for a taxi in Rio!
- Asynchronous over synchronous: Being in different timezones makes it difficult to sync up, so plan ahead and make no decisions last minute
For Remote Participants
Many remote participants feel the need to be ”visible” in their digital workspaces to ”prove” that they are working<ref>Trello: How to Embrace Remote Work</ref>. With this mind, remote participants can:
- Indicate ”deep work” times on their NextCloud (or other) shared calendar
- Update your status in RocketChat or other chat tool to show they’re working
Contribute to the XLP Manual
Thanks for your interest in contributing to the XLP manual. Here are a few key points:
- Every two weeks we release a new stable version, at http://toyhouse.cc:81/wiki/index.php/XLP_manual_1.x, where 1.x refers to the version number.
- – Typically we increment the number after the decimal point, for example 1.1, 1.2, 1.3, etc
- – For a big release, we can change the main version number. For example 1.0, 2.0, 3.0, etc
- We don’t usually edit the stable versions directly. All edits are performed on our development version, then copied to the new stable version. This ensures there’s no half-finished stable versions out there
- We stick to American spelling by convention
- Not sure where to put something yet? Stick it in the Appendix section until you find a good place
Converting to a Book
We use mediawiki2book, a custom Python script to convert our wiki manual to a good-looking PDF book.
In your working directory, you should have:
- The resources folder
- The images folder, containing all images referenced in your mediawiki file
In your MediaWiki file:
- Ensure all images are formatted to be under 600 pixels wide, otherwise they’ll run off the page
- Page embeds like {{: Page}}
- don’t work with the script
In resources/header.yaml
- Update version number and authorship information. The mediawiki2book script will change the date automatically.
- If you don’t understand a certain line in header.yaml, leave it the heck alone. It likely modifies the template or layout in some important way
Bear in mind: Like most other tools on Unix, by default the script will overwrite any existing file with the same name. So if you already have xlp.pdf and run mediawiki2book xlp.mediawiki it will convert the mediawiki file to PDF and overwrite xlp.pdf with a new copy.
- Footnotes
<references />