|
|
| (39 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | {{#css: | | {{#css: |
| | | | |
| − | .toc {
| + | h1{ |
| − | display: block;
| + | display: none; |
| | } | | } |
| | | | |
| − | }}
| + | .mw-body-content p:nth-of-type(1){ |
| | + | margin-top: 0; |
| | + | } |
| | | | |
| − | ==Introduction==
| + | .mw-body-content p, .mw-body-content ul{ |
| | + | max-width: 70%; |
| | + | } |
| | | | |
| − | This project will guide us into the possibilities of Codes of Conduct, user guidelines, and other informal documents to manage online hate. Community rules are not only written files but labour intensive routines that imply human effort and affection. This project shares the experience of users and custodians, it comments on existing documents and celebrates the networks of care generated together.
| + | img { |
| | + | width: 29vw; |
| | + | height: auto; |
| | + | } |
| | + | }} |
| | | | |
| | + | <div style="width: 30vw; float: left;"> [[File:About.jpg|frameless|left]] </div> |
| | | | |
| − | ==Technical Documentation== | + | <div style="margin-left: 30vw; width: 70vw;"> |
| | + | ==Networks== |
| | | | |
| − | In the forefront of the fight against hate, there are users committed to creating better social media experiences for them and for others. These users offer support with their work on moderation, technical knowledge, emotional labour, and many others.
| + | Managing an online community is difficult. It requires a collective understanding of how people want to be together and how to deal with conflict. These challenges motivated different groups to create and apply informal rules to their networks. They are published online as user guidelines, community rules, collaboration protocols, network etiquette, community covenants, a group pact, a collective agreement, a Code of Conduct. These guidelines aim for comfortable interactions between the members; they set expectations for users, put in evidence the values of a community, making explicit which behaviours are allowed or discouraged, possibly decreasing unwanted hate. They can help to deal with internal and exterior abuses, especially when the documents are upheld by a network of people who acknowledges the differences in privilege, power, experiences, money and time of different users. |
| | | | |
| | + | ==of Care== |
| | | | |
| − | Technical knowledge is relevant to:
| + | Discussing Codes of Conduct isn't only considering the potential of text, but recognising the labour intensive routines that imply human effort and involve the community. The caretakers are essential — to write the guidelines, to manage reports, to moderate, to document, to listen, to grant support. A Code of Conduct also needs visibility and a plan for distribution. Furthermore, the desire to share different guidelines from corporate-owned social platforms requires other competencies, such as moving to other platforms, or self-hosting our social groups. Care work is highly skilled, and it needs to be further discussed, recognised and cherished. |
| | | | |
| − | *use moderation tools
| + | == — a field guide == |
| − | *adapt, fork, customise moderation tools
| |
| − | *create new tools
| |
| − | *adapt, fork, customise social platforms
| |
| − | *create new platforms
| |
| − | *use software and hardware
| |
| − | *question autonomy
| |
| − | *experiment with protocols
| |
| − | *self-host
| |
| − | *understand tutorials
| |
| − | *write and send reports
| |
| | | | |
| | + | This field guide will lead you through the attempts, accomplishments and missteps of moderators, writers, users and custodians of social networks. It collects and comments on existing Codes of Conduct, listens to different experiences, and proposes other projects to explore. The field guide goes through the work of artists, designers, libre and open software enthusiasts, feminists and LGBTQ users, aiming to facilitate future work for other circles. It's exciting to consider which gestures may contribute to increasing autonomy and cooperation in digital platforms, whether Codes of Conduct can be useful to reduce hate and improve interactions, or even desirable. Let's explore the networks of care generated together. |
| | | | |
| − | These actions can be challenging, and they demand time, money and effort from a community. Networks of Care goes through some of these technical hurdles, it exposes processes and documents the experience of creating and maintaining this project.
| |
| | | | |
| − | Networks of Care is hosted on a Raspberry Pi and uses MediaWiki software to organise the content. It uses extensions such as Semantic MediaWiki and Page Forms. The main page shows a diagram that uses the API to get access to wiki features. It also uses Leaflet, a JavaScript library.
| + | ==Structure== |
| | | | |
| | + | Networks of Care is divided into three parts. |
| | | | |
| − | ===Setting up the Raspberry Pi=== | + | [https://hub.xpub.nl/networksofcare/mediawiki/index.php?title=Category:Archiving Archiving] — to collect and annotate Codes of Conduct, creating a collection that is possible to browse, dissect and analyse. |
| | | | |
| − | In my computer:
| + | [https://hub.xpub.nl/networksofcare/mediawiki/index.php?title=Category:Networking Networking] — to interview and document the work of moderators, writers of Codes of Conduct, facilitators, community members and networks' administrators. |
| | | | |
| − | '''SD card'''
| + | [https://hub.xpub.nl/networksofcare/mediawiki/index.php?title=Category:Linking Linking] — to point other ways forward, useful templates, resources, and experiments. |
| | | | |
| − | 1. Format for FAT32 (I used disk utility on mac. Format to MS_DOS). Use more than 8gb, mediawiki can become heavy.
| |
| | | | |
| | + | ==Images== |
| | | | |
| − | 2. Flash ISO to SD card (Raspbian Buster Light, https://www.raspberrypi.org/downloads/raspbian/ ) with a mounter (I've used etcher https://www.balena.io/etcher/ )
| + | The images that appear throughout this project are cyanographic prints. A guide to the printing and creation process is shown [[Images|in this page]]. |
| | | | |
| | | | |
| − | With raspi connected to power, internet, screen and keyboard:
| + | ==Technical Documentation== |
| | | | |
| − | '''01 Default login'''
| + | Technical knowledge is relevant to: |
| | | | |
| − | Login: pi
| + | *use moderation tools |
| − | | + | *adapt, fork, customise moderation tools |
| − | Password: raspberry
| + | *create new tools |
| − | | + | *adapt, fork, customise social platforms |
| − | | + | *create new platforms |
| − | '''02 SSH config'''
| + | *use software and hardware |
| − | | + | *question autonomy |
| − | $ cd /boot
| + | *experiment with protocols |
| − | | + | *self-host |
| − | $ sudo touch ssh
| + | *understand tutorials |
| − | | + | *write and send reports |
| − | $ sudo reboot
| |
| − | | |
| − | | |
| − | '''03 Check IP address'''
| |
| − | | |
| − | $ hostname -i
| |
| − | | |
| − | Response: 192.0.0.0
| |
| − | | |
| − | | |
| − | '''04 My keyboard wasn't working properly.'''
| |
| − | | |
| − | I had to change language of keyboard to US instead of UK.
| |
| − | | |
| − | $ sudo raspi-config
| |
| − | | |
| − | Localisation Options
| |
| − | | |
| − | Change Keyboard Layout
| |
| − | | |
| − | Choose US
| |
| − | | |
| − | After using the keyboard I changed back to UK to avoid errors.
| |
| − | | |
| − | | |
| − | '''05 Change hostname'''
| |
| − | | |
| − | $ ssh pi@192.0.0.0
| |
| − | | |
| − | $ sudo raspi-config
| |
| − | | |
| − | Choose item no. 2 on the menu: Network Options
| |
| − | | |
| − | Rename hostname to: newhostname
| |
| − | | |
| − | $ reboot
| |
| − | | |
| − | | |
| − | '''06 Add user'''
| |
| − | | |
| − | $ sudo adduser name
| |
| − | | |
| − | | |
| − | '''07 Add new user to sudo'''
| |
| − | | |
| − | $ sudo adduser name sudo
| |
| − | | |
| − | | |
| − | '''08 You should be able to login with:'''
| |
| − | | |
| − | $ ssh name@newhostname
| |
| − | | |
| − | | |
| − | '''09 I had an error with known hosts.'''
| |
| − | I removed cached key on my computer:
| |
| − | | |
| − | $ ssh-keygen -R 192.000.0.000
| |
| − | | |
| − | | |
| − | '''10 Remove default pi user'''
| |
| − | | |
| − | $ sudo deluser pi
| |
| − | | |
| − | | |
| − | '''10 Use key-based authentication:'''
| |
| − | | |
| − | | |
| − | '''10.1 Add .ssh keys to RPI'''
| |
| − | | |
| − | https://www.raspberrypi.org/documentation/remote-access/ssh/passwordless.md#copy-your-public-key-to-your-raspberry-pi
| |
| − | | |
| − | | |
| − | '''10.2 Edit file'''
| |
| − | $ sudo nano /etc/ssh/sshd_config
| |
| − | | |
| − | Uncomment PassowrdAuthentication and set it to no;
| |
| − | | |
| − | Uncomment PermitRootLogin prohibit-passowrd;
| |
| − | | |
| − | | |
| − | '''10.3 Reload SSH'''
| |
| − | | |
| − | $ sudo /etc/init.d/ssh restart
| |
| − | | |
| − | | |
| − | '''10.4 Reboot RPi'''
| |
| − | | |
| − | $ sudo reboot
| |
| − | | |
| − | | |
| − | '''10.5 In my computer:'''
| |
| − | | |
| − | $ cd ~/.ssh
| |
| − | | |
| − | $ sudo nano config
| |
| − | | |
| − | | |
| − | Add to the document:
| |
| − | | |
| − | Host newhostname
| |
| − | User name
| |
| − | Hostname 192.000.0.0
| |
| − | Port 22
| |
| − | Identityfile /Users/ritagraca/.ssh/id_rsa
| |
| − | Serveraliveinterval 30
| |
| − | | |
| − | | |
| − | '''10.6 To ssh to my pi now:'''
| |
| − | | |
| − | $ ssh newhostname
| |
| − | | |
| − | | |
| − | '''11. Set static ip address for LAN'''
| |
| − | | |
| − | $ sudo nano /etc/dhcpcd.conf
| |
| − | | |
| − | | |
| − | Edit this part:
| |
| − | | |
| − | #Static IP text block
| |
| − | interface eth0
| |
| − | static ip_address=192.000.0.00
| |
| − | static routers=192.000.0.0
| |
| − | static domain_name_servers=8.8.8.8 8.8.4.4
| |
| − | | |
| − | | |
| − | Note:
| |
| − | | |
| − | I shut down my pi, IP changed and couldn't ssh to it. If this happened already, connect pi again to screen, find new IP with $ config command, and put new IP in ~/.ssh, step 10.5.
| |
| − | | |
| − | | |
| − | ===Installing Mediawiki on the pi===
| |
| − | | |
| − | | |
| − | '''1. Install Apache'''
| |
| − | | |
| − | $ sudo apt update
| |
| − | | |
| − | $ sudo apt install apache2 -y
| |
| − | | |
| − | I will remove Apache and install Ngnix in the next steps, see ''Fixing my very slow MediaWiki''.
| |
| − | | |
| − | | |
| − | '''2. Download Mediawiki'''
| |
| − | | |
| − | $ mkdir Downloads
| |
| − | | |
| − | $ cd Downloads
| |
| − | | |
| − | $ wget https://releases.wikimedia.org/mediawiki/1.34/mediawiki-1.34.0.tar.gz (check the version)
| |
| − | | |
| − | $ tar -xvzf mediawiki-1.34.0.tar.gz
| |
| − | | |
| − | | |
| − | '''3. Move'''
| |
| − | | |
| − | $ sudo mkdir /var/lib/mediawiki
| |
| − | | |
| − | $ sudo mv mediawiki-*/* /var/lib/mediawiki
| |
| − | | |
| − | | |
| − | '''4. Linking'''
| |
| − | | |
| − | $ cd /var/www/html
| |
| − | | |
| − | $ sudo ln -s /var/lib/mediawiki mediawiki
| |
| − | | |
| − | | |
| − | '''5. Updating'''
| |
| − | | |
| − | $ sudo apt-get update
| |
| − | | |
| − | $ sudo apt-get install apache2 mysql-server php php-mysql libapache2-mod-php php-xml php-mbstring
| |
| − | | |
| − | | |
| − | '''5.1 Error: Package 'mysql-server' has no installation candidate'''
| |
| − | | |
| − | Fix with:
| |
| − | | |
| − | $ sudo apt install mariadb-server-10.3 php-mysql
| |
| − | | |
| − | | |
| − | '''5.2 Error: MySQL didn't ask for password so:'''
| |
| − | | |
| − | $ sudo mysql_secure_installation
| |
| − | | |
| − | It will ask for password now.
| |
| − | | |
| − | | |
| − | '''6. Database'''
| |
| − | | |
| − | $ sudo mysql -u root -p
| |
| − | | |
| − | Enter password.
| |
| − | Type:
| |
| − | | |
| − | mysql> CREATE DATABASE wiki;
| |
| − | mysql> USE wiki;
| |
| − | | |
| − | mysql> CREATE USER 'name'@'localhost' IDENTIFIED BY 'yourpassword';
| |
| − | mysql> GRANT ALL PRIVILEGES ON wiki.* TO 'name'@'localhost';
| |
| − | mysql> FLUSH PRIVILEGES;
| |
| − | mysql> quit
| |
| − | | |
| − | | |
| − | '''7. Open browser'''
| |
| − | | |
| − | http://ip_address_of_pi/mediawiki
| |
| − | | |
| − | On the website, it will ask for database connection settings:
| |
| − | | |
| − | localhost
| |
| − | database: wiki
| |
| − | user: name
| |
| − | password: yourpassword
| |
| − | | |
| − | Continue installation.
| |
| − | | |
| − | | |
| − | '''8. After setting up, it will ask to save LocalSettings.php. Download to your computer.'''
| |
| − | | |
| − | | |
| − | '''9. Move file from your computer to pi.'''
| |
| − | | |
| − | In your computer:
| |
| − | | |
| − | $ scp LocalSettings.php name@hostname:/home/name/Downloads
| |
| − | | |
| − | | |
| − | '''10. Move from pi to the right place.'''
| |
| − | | |
| − | In your pi:
| |
| − | | |
| − | $ sudo mv ~/Downloads/LocalSettings.php /var/lib/mediawiki/
| |
| − | | |
| − | | |
| − | some more help to setup mediawiki http://willbeone-techtips.co.za/2018/02/12/installing-mediawiki-raspberry-pi3/
| |
| − | | |
| − | | |
| − | === Fixing my very slow MediaWiki ===
| |
| − | | |
| − | My wiki is painfully slow. Things I'll try:
| |
| − | | |
| − | 1. Switch from Apache to Ngnix.
| |
| − | | |
| − | 2. Swap to SanDisk Ultra 64gb a2. ''Update — The sd card made the most difference. Amazing.''
| |
| − | | |
| − | | |
| − | '''0. Backing up my raspbery pi image'''
| |
| − | | |
| − | First, I backed up my raspbery pi image. Tutorial for mac:
| |
| − | https://medium.com/@ccarnino/backup-raspberry-pi-sd-card-on-macos-the-2019-simple-way-to-clone-1517af972ca5
| |
| − | | |
| − | | |
| − | '''1. Switching from Apache to Ngnix'''
| |
| − | | |
| − | '''1.1 Uninstalling Apache:'''
| |
| − | | |
| − | $ sudo apt-get --purge remove apache2
| |
| − | | |
| − | $ sudo apt-get autoremove
| |
| − | | |
| − | | |
| − | '''1.2 Installing Ngnix:'''
| |
| − | | |
| − | $ sudo apt update
| |
| − | | |
| − | $ sudo apt install nginx
| |
| − | | |
| − | $ sudo /etc/init.d/nginx start
| |
| − | | |
| − | | |
| − | Go to ip address and see the Ngnix starting message.
| |
| − | | |
| − | '''1.3 Additional — Install PHP:'''
| |
| − | | |
| − | https://www.raspberrypi.org/documentation/remote-access/web-server/nginx.md
| |
| − | | |
| − | | |
| − | '''1.4 I uninstalled mediawiki:'''
| |
| − | | |
| − | $ rm -rf /var/www/mediawiki
| |
| − | | |
| − | | |
| − | '''1.5 Started from step ''Installing Mediawiki'' '''
| |
| − | | |
| − | ===Extensions===
| |
| − | | |
| − | ==== Extension Semantic MediaWiki ====
| |
| − | | |
| − | '''1. Download composer'''
| |
| − | | |
| − | More here https://getcomposer.org/doc/00-intro.md#installation-nix
| |
| − | | |
| − | | |
| − | '''1.1 Download the installer to the current directory'''
| |
| − | | |
| − | $ php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
| |
| − | | |
| − | | |
| − | '''1.2 Verify the installer SHA-384'''
| |
| − | | |
| − | $ php -r "if (hash_file('sha384', 'composer-setup.php') === 'e0012edf3e80b6978849f5eff0d4b4e4c79ff1609dd1e613307e16318854d24ae64f26d17af3ef0bf7cfb710ca74755a') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
| |
| − | | |
| − | | |
| − | '''1.3 Run the installer'''
| |
| − | | |
| − | $ php composer-setup.php
| |
| − | | |
| − | | |
| − | '''1.4 Remove the installer'''
| |
| − | | |
| − | $ php -r "unlink('composer-setup.php');"
| |
| − | | |
| − | | |
| − | '''1.5 Global Access'''
| |
| − | | |
| − | Now that I have composer.phar, I will put it in /usr/local/bin to have global access.
| |
| − | | |
| − | $ sudo mv composer.phar /usr/local/bin/composer
| |
| − | | |
| − | This means that instead of starting with $ php composer.phar, I just write $ composer.
| |
| − | | |
| − | Some more help to install composer https://www.semantic-mediawiki.org/wiki/Help:Installation/Using_Composer_with_MediaWiki_1.25%2B
| |
| − | | |
| − | | |
| − | '''2. Create and edit the file composer.local.json in /var/www/html/mediawiki.'''
| |
| − | | |
| − | $ cd /var/www/html/mediawiki
| |
| − | | |
| − | $ sudo nano composer.local.json
| |
| − | | |
| − | | |
| − | paste this code:
| |
| − | | |
| − | {
| |
| − | "require": {
| |
| − | "mediawiki/semantic-media-wiki": "~3.1"
| |
| − | }
| |
| − | }
| |
| − | | |
| − | | |
| − | '''3. Run the update script'''
| |
| − | | |
| − | $ composer update --no-dev
| |
| − | | |
| − | | |
| − | '''3.1 Change permissions:'''
| |
| − | | |
| − | Gives error:
| |
| − | | |
| − | file_put_contents(./composer.lock): failed to open stream: Permission denied
| |
| − | | |
| − | Give permissions:
| |
| − | | |
| − | $ chmod -R 777 ./
| |
| − | | |
| − | | |
| − | '''4. Maintenance script'''
| |
| − | | |
| − | $ php maintenance/update.php
| |
| − | | |
| − | | |
| − | '''5. Enable Semantic MediaWiki on LocalSetting.php'''
| |
| − | | |
| − | Write in the end of the file:
| |
| − | | |
| − | enableSemantics( ' http://192.000.0.0/mediawiki/ ' );
| |
| − | | |
| − | | |
| − | '''6. Repeat step 4.'''
| |
| − | | |
| − | I had a error with database. I had to run the update script again.
| |
| − | If when running this script there's error with permissions, just change permissions, step 3.1
| |
| − | | |
| − | | |
| − | '''7. Uploading files to the server'''
| |
| − | | |
| − | Check first folder permissions, and change if necessary:
| |
| − | | |
| − | $ chmod -R 777 ./
| |
| − | | |
| − | | |
| − | To allow bigger files:
| |
| − | | |
| − | '''7.1. Edit this file'''
| |
| − | $ sudo nano /etc/nginx/nginx.conf
| |
| − | | |
| − | | |
| − | '''7.2 Add this in the bottom of the http part:'''
| |
| − | | |
| − | # set client body size to 2M
| |
| − | client_max_body_size 2M;
| |
| − | | |
| − | | |
| − | '''7.3 Reload the server'''
| |
| − | $ service nginx reload
| |
| − | | |
| − | | |
| − | ==== Extension Page Forms ====
| |
| − | | |
| − | This enables forms, useful to add semantic annotations to pages.
| |
| − | | |
| − | | |
| − | '''1. Download'''
| |
| − | | |
| − | https://github.com/wikimedia/mediawiki-extensions-PageForms/archive/4.8.zip
| |
| − | | |
| − | Put it in /var/www/html/mediawiki/extensions.
| |
| − | | |
| − | You shoud now have a directory called PageForms in your extensions folder.
| |
| − | | |
| − | | |
| − | '''2. Add the following line to your LocalSettings.php file:'''
| |
| − | | |
| − | wfLoadExtension( 'PageForms' );
| |
| − | | |
| − | | |
| − | ==== Extension WikiEditor ====
| |
| − | | |
| − | This enables the edit toolbar like Piet Zwart wiki has.
| |
| − | | |
| − | | |
| − | '''1. Download'''
| |
| − | | |
| − | https://www.mediawiki.org/wiki/Extension:WikiEditor
| |
| − | | |
| − | Put it in /var/www/html/mediawiki/extensions.
| |
| − | | |
| − | You should now have a directory called PageForms in your extensions folder.
| |
| − | | |
| − | | |
| − | '''2. Add the following line to your LocalSettings.php file:'''
| |
| − | wfLoadExtension( 'WikiEditor' );
| |
| − | | |
| − | | |
| − | ==== EmbedVideo ====
| |
| − | | |
| − | To allow video files, such as .mp4, on the wiki.
| |
| − | | |
| − | https://www.mediawiki.org/wiki/Extension:VideoPlayer
| |
| − | | |
| − | | |
| − | === Understanding and using Semantic MediaWiki ===
| |
| − | | |
| − | ====Understanding Properties====
| |
| − | | |
| − | Basic way of entering semantic data:
| |
| − | | |
| − | <nowiki>[[Property + name of property::datatype]</nowiki>
| |
| − | | |
| − | <nowiki>[[Has + name of property::datatype]]</nowiki>
| |
| − | | |
| − | The creator of this text is <nowiki>[[Has Author:Rita]]</nowiki>
| |
| − | | |
| − | | |
| − | There are special kinds of properties: Has, Media type, Creation date, Language code, etc.
| |
| − | | |
| − | See all here: https://www.semantic-mediawiki.org/wiki/Help:Special_properties
| |
| − | | |
| − | | |
| − | Possible datatypes: Number, page, temperature, date, text, page, URL, telephone number, etc.
| |
| − | | |
| − | See all of 15 here: https://www.semantic-mediawiki.org/wiki/Help:Property_declaration
| |
| − | | |
| − | | |
| − | Choose a fitting datatype for your property.
| |
| − | | |
| − | * For example, the datatype ''Telephone number'' only holds numbers, if you try to write something like ''Hello'', it will give an error. | |
| − | * For me, it will be useful the datatype ''Text''. (Used to store strings of arbitrary length, i.e. text.)
| |
| − | * Default datatype is ''Page''. (Holds names of wiki pages, and displays them as a link). | |
| − | | |
| − | | |
| − | '''Doing it — Creating semantic information from example'''
| |
| − | | |
| − | Some information I want to store for every page in Archiving:
| |
| − | | |
| − | Field — xxxx, xxxx, xxxx
| |
| − | | |
| − | Scope — online, offline
| |
| − | | |
| − | | |
| − | * Create property Field and Scope. (Create this in Special:SpecialPages > Page Forms > Create a property)
| |
| − | * Create template Archiving (Create this in Special:SpecialPages > Page Forms > Create a template). A template sets the display of the data on a page.
| |
| − | * Create form Archiving (Create this in Special:SpecialPages > Page Forms > Create a form) A form allow users to easily add and edit pages. | |
| − | | |
| − | Now go to forms. You can create a page. Every time you go to forms and select "Archiving" form you can create a new page using the form. The forms asks you to fill the properties.
| |
| − | | |
| − | (more here: https://www.mediawiki.org/wiki/Extension:Page_Forms/Quick_start_guide )
| |
| − | | |
| − | | |
| − | ====Edit with form====
| |
| − | | |
| − | To have the "edit with form" appear when you create a page without going to the forms page in Special Pages:
| |
| − | | |
| − | * Create a category (I created one called "Archiving") and select a default form <nowiki>{{#default_form:Archiving}}.</nowiki> | |
| − | * Everytime you create a page within the category, you'll have the option of "edit with form". | |
| − | | |
| − | | |
| − | ====Queries====
| |
| − | | |
| − | https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2017/Introduction_to_Semantic_MediaWiki
| |
| − | | |
| − | | |
| − | ====Templates====
| |
| − | | |
| − | In the category Archiving, I wanted to annotate the Codes of Conduct I was collecting. I saw some common patterns in the texts, and I wanted to make them visible. The main themes were:
| |
| − | | |
| − | | |
| − | '''Intentions'''
| |
| − | : This section sets the goals for the Code of Conducts, manages expectations for the document, explains who is the community.
| |
| − | '''Expected behaviour'''
| |
| − | : This section describes the actions welcomed in the community.
| |
| − | '''Unacceptable behaviour'''
| |
| − | : This section expresses the behaviours not tolerated in the community. Ignoring these guidelines may result in action from the community.
| |
| − | '''Behaviour to avoid'''
| |
| − | : This section lists the actions users should refrain to do, attitudes that weaken the community. It focuses on behaviours some people may think are acceptable.
| |
| − | '''Enforcement'''
| |
| − | : This section explains the consequences for the users who break the Code of Conducts. It also clarifies how reports should be done and how the community will act upon the information given. It sets responsibilities when incidents happen.
| |
| − | '''Support'''
| |
| − | : This section holds contacts of the people who are responsible for the Code of Conducts. They may respond to reports, inform the community of changes in the documents, be moderators.
| |
| − | '''Links'''
| |
| − | : This sections has other links for support, further explanation of some topics, it points to related content elsewhere.
| |
| − | | |
| − | | |
| − | First, I created properties. This allowed me to annotate the text in-line.
| |
| − | | |
| − | <nowiki>[[Intentions:: We want to provide a safe place.]]</nowiki>
| |
| − | | |
| − | But I wanted to make the annotations visible. So, I created templates which allowed me to add style.
| |
| − | | |
| − | | |
| − | Template example:
| |
| − | | |
| − | <nowiki>[[Intentions::{{{1}}}|<span style="border-bottom: 2px solid DarkGrey;">{{{1}}}</span>]]</nowiki>
| |
| − | | |
| − | | |
| − | Template usage in text:
| |
| − | | |
| − | <nowiki>{{Intentions | We want to provide a safe place.}}</nowiki>
| |
| − | | |
| − | | |
| − | Result:
| |
| − | | |
| − | The sentence will appear with a grey border, the style I wanted.
| |
| − | | |
| − | It will also be added the property Intentions.
| |
| − | | |
| − | === Creating a diagram for navigation/main page ===
| |
| − | | |
| − | As the project was developing it was important to show the connections between content, people and projects. For example, if I was archiving a Code of Conducts of a community and could then make questions to a moderator of that same group, I wanted to make visible that story line. In this way, I began experimenting with different ways of visualising information.
| |
| − | | |
| − | | |
| − | '''1. Playing with Mediawiki Extensions'''
| |
| − | | |
| − | '''1.1 Extension "Semantic Result Formats"'''
| |
| − | | |
| − | *Information here — https://www.semantic-mediawiki.org/wiki/Extension:Semantic_Result_Formats ) | |
| − | *Installation — https://github.com/SemanticMediaWiki/SemanticResultFormats/blob/master/docs/INSTALL.md | |
| − | *Tried to use result format graph. ( https://www.semantic-mediawiki.org/wiki/Help:Graph_format ) | |
| − | *It doesn't work, because it needs Extention GraphViz and GraphViz doesn't work on recent mediawiki installations.
| |
| − | *Uninstalling.
| |
| − | | |
| − | | |
| − | '''1.2 Extension "Maps" (using leaflet from Maps Extension)'''
| |
| − | | |
| − | *Some info — https://www.semantic-mediawiki.org/wiki/Extension:Maps
| |
| − | *Tried to use. It works for basic map / coordinate property. It doesn't have a lot of options like Leaflet alone has. For example, couldn't change map layout to an image.
| |
| − | *Uninstalling.
| |
| − | | |
| − | I couldn't find an extension that actually let me do what I wanted and have some creative freedom.
| |
| − | | |
| − | | |
| − | '''2. Alternative: doing the diagram outside the wiki but using Mediawiki API'''
| |
| − | | |
| − | Steps:
| |
| − | | |
| − | *Create my diagram on leaflet
| |
| − | *Link Mediawiki Semantic wiki API to leaflet
| |
| − | *Include diagram to wiki
| |
| − | *Populate, populate, populate
| |
| − | | |
| − | | |
| − | '''2.1 API'''
| |
| | | | |
| − | The web server is using HTTP requests to communicate to a publicly available URL endpoint containing JSON data. You need to use CORS or JSONP, I'll try to use JSONP for now. (note that JSONP is inherently read-only)
| |
| | | | |
| − | A request consists of an endpoint and a set of parameters. Example to list all pages in category Archiving:
| + | These actions can be challenging. Networks of Care goes through a few of these technical hurdles, documenting along the way the experience of creating and maintaining this project. |
| | | | |
| − | http://192.000.0.0/mediawiki/api.php?action=query&format=json&&cmtitle=Category:Archiving&list=categorymembers
| + | Networks of Care is hosted on a Raspberry Pi and uses MediaWiki software to organise the content. It uses extensions such as Semantic MediaWiki and Page Forms. The main page shows a diagram that uses the API to get access to wiki features. It also uses Leaflet, a JavaScript library. |
| | | | |
| − | Important things:
| + | [[Technical_documentation|Here is the detailed Technical Documentation]]. |
| − | *main endpoint — http://192.000.0.0/mediawiki/api.php
| |
| − | *action=query means fetch data from wiki.
| |
| − | *format=jsonfm indicates JSON output, which is the recommended output format.
| |
| | | | |
| | | | |
| − | Mediawiki API Sandbox:
| + | ==Contacts== |
| | | | |
| − | https://www.mediawiki.org/wiki/Special:ApiSandbox
| + | This work has been produced in the context of the graduation research of [http://www.ritagraca.com Rita Graça] from the Experimental Publishing (XPUB) Master course at the Piet Zwart Institute, Willem de Kooning Academy, Rotterdam, University of Applied Sciences. |
| | | | |
| | + | XPUB is a two year Master of Arts in Fine Art and Design that focuses on the intents, means and consequences of making things public and creating publics in the age of post-digital networks. |
| | | | |
| − | Semantic Wiki API Sandbox:
| + | https://xpub.nl |
| | | | |
| − | https://www.semantic-mediawiki.org/wiki/Special:ApiSandbox
| |
| | | | |
| − | Overall the sandbox is very useful to create queries with properties.
| + | </div> |
| | + | <div style="clear: both;"> </div> |
