Wasta Language Scientist
Some changes and additions to Wasta Linux for the language and linguistic Scientist.
This script attempts to document some changes (additions) to Wasta for the linguistic data scientist.
The reasons we want to use Wasta (and Linux are the following): We feel that there is great value in being on the same operating system with the indigenous language speaking (and using) members of our team. This equality could happen with any operating system. However, with Linux the cost of outfitting an entire team or part of a community with tools to make tools for their language is much lower than with OS X, or Windows. Wasta gives us the power of Ubuntu with the ease of access connect with SIL software systems.
Wasta is at its core the minimum toolset needed by the minority language user who is just starting with computing in their language. This script endeavors to bring the rest of what was forgotten (or intentionally left out). The new focus for this derivative of Wasta is on the modern interdisciplinary, digital humanities sensitive, anthropologically aware linguist, who is looking to enrich the lives and communities of minority language users (and digitally under-resourced) creatives.
Rather than providing a lean machine (as Wasta core does), we are looking at providing a grab and go solution with a health variety of tools pre-baked in.
We might want to change somethings about the look and feel of our Wasta machine (this is more or less to bring over some features from OS X). Many researchers use OS X or macOS in their work. Making the jump to Wasta is easier when there are some familiar behaviors in the way the computer responds.
We might want some fonts and text processing tools.
We might want to use some apache server (web) based tools for sharing our work globally or to work as a team on a local network. So, we will install some web development tools.
We might want some access to iOS devices. These are really popular and we want to be able to connect them (and their sensors) as seamlessly as possible into our work-flows.
We might want some SIL tools for doing some things "The SIL Way"... if there is one. (Basically, SIL makes some awesome tools, but these are not all installed by default on Wasta.)
We might want some other tools to do linguistics. There are lots of tools for linguistics which are, sometimes not known about, and sometimes known about. We want to put them in the machine for ease of access to the end user.
We might want some data wrangling tools for our data. As a data scientist we are really keen to be able to collect good data, to detect patterns, in that data, and then also present that data in (often visual) compelling ways to our colleagues, funders, and the communities we work with.
We might want some fun things to do... Because basically, the folks at Ubuntu don't have great tastes for intelligent games.
We might want some quality reference resources on literacy, linguistics, language documentation, language development, and language program management.
Included Software (over standard Wasta)
(all via apt)
- gloobus preview :: Install review - Spacebar previews a file.
- MacBuntu theme elements Various elements including:
- window shading
- plank - An OS X like dock.
- Plank theme files
- slingcold :: Install review - a launchpad like application which sits in the dock.
- Instructions on getting the icon for slingcold to appear in plank.
- Albert :: Install Review - a spotlight like tool.
(all via apt)
- kcharselect :: A tool from the KDE project which allows the user to find and select specific characters in Unicode.
- Open Fonts
- SIL Fonts
(all via as indicated)
Make a directory for websites
WordPress -via wget.
Linuxbrew - This is a package manager.
Why linux brew?
- Can install software to a home directory and so does not require sudo.
- Install software not packaged by the native distribution.
- Install up-to-date versions of software when the native distribution is old.
- Use the same package manager to manage both your Mac and Linux machines. When should we use apt-get when should we use linuxbrew? This is Linux, so if a tool exists via apt-get then we should try and get it from there first. However, sometimes it is better to not mess with the OS's version of something and leave that in place and use a different version of things, also sometimes homebrew repos get updated faster than apt-get repos do.
linuxbrew wrapper A couple of libraries of tools. Some of these are going to have already been installed, and won't install again. But this is a "just to make sure".
Some taps (like a ppa in Linux) for linuxbrew (via brew):
Via wget download
- atom - a markdown editor and code writer with syntax highlighting. Lots of plugins are available. Those listed here are installed via atom. If you know a computer language search for a syntax or auto complete plugin to fit your style.
(via apt) - we are updating the libimobiledevice libraries to make sure we have the latest even because this functionality gets a lot of tweaking and updating.
Make a directory for those projects we get from github. (~/github-tools)
We are getting the following two libs from github because they are even newer than what is in the apt repos. Then we use
make to install them.
- Old Java
- Fieldworks - via apt.
- WeSay - via apt.
- TECkit :: on github
- characterCount -via wget.
These sections will follow the musings of the following five lists:
- Pioneers - A Settlers of Catan like game. - via apt.
- JCloisterZone - A Carcassonne like game. - via git.
- yetris - A Tetris like game. - via brew
- Ninvaders - A Space Invaders like game. - via brew
This section has various potential installs not yet scripted or tested, but they look like they belong in the eco-system of tools we are using.