text:
# CS 2053: Final Report for RUBIK ESCAPE!

#### Winter 2020

#### Current & Original Group Members:

#### Conor Hennessy

#### Caleb Reath

#### Adalgisa Ferrer

#### Moses Cruz

## 1. Game Design Requirements

_Describe in the following sections how your game meets/supports each of the following project_

#### requirements:

#### 1.1. Story Telling. The game should contain storytelling with audio or text narration.

```
Our game primarily uses text-based storytelling. It involves dialogue of the
antagonist directed at you, the player. The story elements added by the antagonist will be
```
#### tutorials for new elements added in future levels.

#### The synopsis of the story is as follows:

- _The Cube King has taken you (the top Spherical General of the Revolutionary_
    _Army) captive after a long and fierce battle in the war of shapes. To ensure he is_
    _able to maintain his “edge” in the war the King knows he must squeeze every bit_
    _of information out of you. To accomplish this task the Cube King employs his top_
    _cube scientist Rubi K... Rubi K. has developed a rigorous set of “impossible”_
    _puzzles with the help of the top_ **_edgechelon_** _of cube interrogators. These puzzles_
    _will break any sphere that rolls in. Will they break you? Or will you escape and_
    _finish the war once and for all?_

```
The game begins with a short introduction to the interrogation torture chambers.
These chambers are cubic and edge filled rooms which would leave any normal sphere
wallowing in their pointless existence offering everything they know to get out. Then the
player must progress through increasingly difficult levels. Where different levels offer
different challenges. Eventually, when they reach the end of the last level a short outro
can be scripted to show the player’s sphere escaping and defeating the Cube King once
```
#### and for all.

#### The player will be represented by the wellbeing of their spheroid character.

#### Characters:

#### Cube King // Dark Red

#### Rubi K. // rubik cube

#### Player // vibrant blue

```
1.2. The number of levels. The game should be a multi-level/scene game with 2N scenes
(where N is the number of teammates). How many levels do you have and what do they
```
#### represent?

#### 8 Scenes/Levels

#### What the following levels represent

1. _Introduction_ : setting out how the player got stuck in the puzzle
2. _A basic tutorial level_ :
3. _Level 1_ : Another tutorial maze with a new game element, bouncy walls.
4. _Level 2_ : Continuation of bouncy walls but harder
5. _Level 3_ : Continuation of the story where a new game element is introduced
    - A laser emitter that tries to hit players
6. _Level 4_ : Continuation of emitter level but harder
7. _Level 5_ : New game element introduced: Gravity. Also, this is the final Level
    with Boss. Gravity affects how the player can control their ball.
8. _Outro_ : Finally an outro animation and credits level.

## 2. Game Programming Requirements

_Describe in the following sections how your game meets/supports each of the following project_

#### requirements (what parts of the game and how it was provided):

#### The project and resulting game must include the following game programming technologies:

```
2.1. Sound (note that if your game did not contain sound because of limitations in the lab
```
#### computers, please comment on this here).

Voice for characters, sounds for ball such as rolling sound for ball, falling sound for ball,

#### hitting sounds against walls, hitting sounds against bouncy walls and Ambient music.

#### 2.2. Physics

```
The ball itself has physics to roll and move around the board. The board has physics to move
and tilt with the user’s keypresses, the board tilts down the direction pressed and then
```
#### returns to the neutral position when no keys are pressed.

```
Additional game components of bouncy walls, emitters, the boss character and other
```
#### objects all have respected physics technology for their own functions.

#### 2.3. Cameras: should have dynamic (or multiple)

#### The camera follows the player as they wobble around the maze.

```
The camera moves dynamically as the camera follows the ball to transition through an
```
#### obstacle or goal holes.

#### 2.4. User Interface (menu).

#### Dialogue is shown throughout the game at the start of every scene and level.

#### The user interacts with this to remove a piece of dialogue with each level.

```
2.5. AI: AI game objects must have state-based behaviours and involve pathfinding. Note that
for this point, you can use those provided by the game engine/platform which you will use
for the project development and/or write your own. We removed the requirement for AI,
```
#### but if you have some AI in your project, you may describe it here.

#### We do not have a UI component to our game.

### 3. Describe what parts of the game you attempted to build or

### wanted to build, but were unable to

_Distinguish between the parts you were unable to implement, but would have satisfied a project
requirement, from parts that you wanted to add additionally to improve gameplay or play_

#### experience.

#### Parts that would have satisfied project requirements:

#### N/A

#### Parts for additional functionality:

#### Split gravity level and boss (level 5) into two separate levels

## 4. How successful were you?

#### Provide a description of how successful you were in creating a 'good' game with this project.

## There are no right or wrong answers, this is to help you reflect on your experience.

We were very successful, we got a lot done, and we were able to implement all the features we

#### wanted to. We worked as a team and were able to pull of a working game.

### 5. Describe how you were able to work remotely with

## your team or individually.

_Did you have any challenges? What worked well? Would you do something differently in the_

#### future?

We encountered major issues with working remotely. With two of our group members being
international students, they both had to organise, move and relocate back to their home countries
with limited support. Then expected to settle down and continue all projects and assignments with

#### minimal changes, other than a change of deadlines.

With this development for all courses, including CS2053, was affected and slowed and so the

#### expected level of input may not have been achieved.

We also experienced problems due to all group members having additional new commitments,
may it be work to support themselves or supporting family. Additionally, we now had a 4-hour time

#### difference where we would normally be able to meet up and complete tasks.

With all this, we were able to complete something that meets our original project proposal and is

#### overall fun to play.

With regards to doing something differently in the future, not much can be changed with regards
to logistics in light of the current situation. But I would change the course requirements if possible.
As assuming the learning objectives of the course have been achieved, some components could
be dropped, this would have been the easiest way to reduce workload, expectations and stress

#### on the team.

### 6. Describe what external/third-party resources (or asset

## packs) you used

_Please describe what third-party resources/scripts/objects/music/sprites/etc. you used, what
functionality/features they provide and how you used them? You can provide URLs for important_

#### libraries/assets, but leave out simple sprites.

 Creator: Jazz Create Games
    o https://assetstore.unity.com/packages/2d/fonts/bubble-font-free-version- 24987
The sound was used every time the ball was moving to create a better user experience when
playing. The font was just used for the aesthetic of the game and the 3D models were used for

#### the intro and outro of the game, just to put some ‘faces’ to our characters.

branch_name: refs/heads/dev-primary


text:
# linter-spell-pretext

Provider for Atom [linter-spell](https://atom.io/packages/linter-spell) package
to enable PreTeXt spell checking.  Based on [linter-spell-html](https://atom.io/packages/linter-spell-html) and [linter-spell-latex](https://atom.io/packages/linter-spell-latex)

## Installing

 Use the Atom package manager and search for "linter-spell-pretext", or run `apm install linter-spell-pretext` from the command line.

## Prerequisites

This package relies upon [linter-spell](https://atom.io/packages/linter-spell)
and it must therefore be installed.

## Language Tags

The package scans the file for language tags like `lang="fr"` or `lang="en-US"`
to determine the appropriate dictionary.

## Status

Please note that this package is in an **alpha** state.

license: MIT

repository: oscarlevin/linter-spell-pretext

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: oscarlevin/linter-spell-pretext


text:
---
title: Theme Configuration
taxonomy:
    category: docs
---

In Grav you can easily access theme configuration and blueprint information from your Twig and PHP files.

## Accessing Theme Blueprint Information

Information from the currently active theme's `blueprints.yaml` file can be had from the `theme` object. Let's use the following `blueprints.yaml` file as an example:

[prism classes="language-yaml line-numbers"]
name: Antimatter
slug: antimatter
type: theme
version: 1.7.0
description: "Antimatter is the default theme included with **Grav**"
icon: empire
author:
  name: Team Grav
  email<EMAIL_ADDRESS>  url: https://getgrav.org
homepage: https://github.com/getgrav/grav-theme-antimatter
demo: http://demo.getgrav.org/blog-skeleton
keywords: antimatter, theme, core, modern, fast, responsive, html5, css3
bugs: https://github.com/getgrav/grav-theme-antimatter/issues
license: MIT
[/prism]

You can reach any of these items via `theme` by using the standard **dot-syntax**:

[prism classes="language-twig line-numbers"]
Author Email: {{ theme.author.email }}
Theme License: {{ theme.license }}
[/prism]

You can also reach these same values from a Grav plugin with PHP syntax:

[prism classes="language-php line-numbers"]
$theme_author_email = $this->grav['theme']['author']['email'];
$theme_license = $this->grav['theme']['license'];
[/prism]

## Accessing Theme Configuration

Themes have configuration files, too. A theme's configuration file is named `<themename>.yaml`. The default file lives in the theme's root folder (`user/themes/<themename>`).

It is **strongly** recommended not to actually change the theme's default YAML file but to override the settings in the `user/config/themes` folder. This will ensure that the theme's original settings remain intact, allowing you to quickly access the changes and/or revert back whenever necessary.

For example, let us consider the Antimatter theme.  By default, there is a file called `antimatter.yaml` in the theme's root folder. The contents of this configuration file look like this:

[prism classes="language-yaml line-numbers"]
enabled: true
color: blue
[/prism]

This is a simple file, but it provides you an idea of what you can do with theme configuration settings. Let us override these settings and add a new one.

So, create a file in the following location: `user/config/themes/antimatter.yaml`.  In this file put the following contents:

> *I note that `enabled` is not repeated here. If the config files are merged and not simply replaced, then that should be explicitly stated.*

[prism classes="language-yaml line-numbers"]
color: red
info: Grav is awesome!
[/prism]

Then in your theme templates you can access these variables using the `grav.theme.config` object:

```
<h1 style="color:{{ grav.theme.config.color|e }}">{{ grav.theme.config.info|e }}</h1>
```

This should render out as:

Grav is awesome!

In PHP you can access the current theme's configuration with:

[prism classes="language-php line-numbers"]
$color = $this->grav['theme']->config()['color'];
$info = $this->grav['theme']->config()['info'];
[/prism]

Simple! The sky is the limit regarding the configuration of your themes.  You can use them for whatever you like! :)

### Alternative Notation

The following aliases also work:

[prism classes="language-twig line-numbers"]
Theme Color Option: {{ config.theme.color_option|e }}
   or
Theme Color Option: {{ theme_var(color_option)|e }}
   or
Theme Color Option: {{ grav.themes.antimatter.color_option|e }} [AVOID!]
[/prism]

**Even though `grav.themes.<themename>` is supported, it should be avoided because it makes it impossible to inherit the theme properly.**

repository: getgrav/grav-learn

branch_name: refs/heads/develop

gha_language: SCSS

gha_license_id: MIT

repo_name: getgrav/grav-learn


text:
# LocalLibrary
Local Library website written in Express(node).

This web application creates an online catalog for a small local library, where users can browse available books and manage their accounts.

![Library Website - Mongoose_Express](https://user-images.githubusercontent.com/40798328/92680123-be59b880-f347-11ea-8d8c-e0cab2a3627c.png)

repository: shivamsahni/LocalLibrary

repo_name: shivamsahni/LocalLibrary


text:
# 2048

Recreation of the popular 2048 game created by Gabriele Cirulli (found [here](https://play2048.co/ "Original 2048 Game")) made in python using pygame

### Controls

use the arrow keys to move the board. press C to restart the game. press X to close the game

### Requirements

- Python 3+

```bash
# install required dependancies
$ pip install  -r requirements.txt
```


text:
# 815. Bus Routes

Difficulty: Hard

https://leetcode.com/problems/bus-routes/

We have a list of bus routes. Each routes[i] is a bus route that the i-th bus repeats forever. For example if routes[0] = [1, 5, 7], this means that the first bus (0-th indexed) travels in the sequence 1->5->7->1->5->7->1->... forever.

We start at bus stop S (initially not on a bus), and we want to go to bus stop T. Travelling by buses only, what is the least number of buses we must take to reach our destination? Return -1 if it is not possible.
```
Example:
Input:
routes = [[1, 2, 7], [3, 6, 7]]
S = 1
T = 6
Output: 2
Explanation:
The best strategy is take the first bus to the bus stop 7, then take the second bus to the bus stop 6.
```

**Note:**

* 1 <= routes.length <= 500.
* 1 <= routes[i].length <= 500.
* 0 <= routes[i][j] < 10 ^ 6.

Companies: Google

Related Topics: Breadth-first Search

repository: jiadaizhao/LeetCode

repo_name: jiadaizhao/LeetCode


text:
# Object Detection in Raspberry Pi
This is the code repository of Object Detection module for running on Edge device of Raspberry Pi. To get started, you will have to download the pretrained model along with its label file. We recommend making use of the quantized SSD MobileNet V1 model trained on COCO capable of classifying around 80 different common object categories. To download and extract it, run the following:
```
wget http://storage.googleapis.com/download.tensorflow.org/models/tflite/coco_ssd_mobilenet_v1_1.0_quant_2018_06_29.zip
unzip coco_ssd_mobilenet_v1_1.0_quant_2018_06_29.zip
```

## Prerequisites
* PiCamera
* matplotlib (with tkinter as backend)
* python-tk
* Pillow
* numpy

To install the Python dependencies, run:
```
pip install -r requirements.txt
```

Next, to run the code on Raspberry Pi, use `classify.py` as follows:

```
python3 main.py --model_path detect.tflite --label_path labelmap.txt
```

We encourage you to look through all the available options in the code.

For more information, go [here](https://www.tensorflow.org/lite/models/object_detection/overview).

url: https://raw.githubusercontent.com/foochane/TensorFlow-in-Practice-Notes/6bf36749026fa21147a3bd34accb8fc9fa9a7df5/dlaicourse/TensorFlow Deployment/Module 1 - TF Lite/Week 4/object_detection/README.md

repository: foochane/TensorFlow-in-Practice-Notes

gha_language: Jupyter Notebook

repo_name: foochane/TensorFlow-in-Practice-Notes


text:
# OneDrive Configuration Scripts

Scripts for configuring the OneDrive client via PowerShell scripts deployed to Windows 10 with Microsoft Intune.

* _Install-OneDrivePerMachine.ps1_ - downloads and installs the OneDrive sync client in per-machine mode. Currently downloads and installs the preview version of the OneDrive client.
* _OneDrive-EnableADAL.ps1_ - must be deployed in the user's context by selecting 'Run this script using the logged on credentails'.
* _OneDrive-SilentAccountConfig.ps1_ - must run in the system context

For more information on configuring the OneDrive client see this article: [Use Group Policy to control OneDrive sync client settings](https://support.office.com/en-us/article/Use-Group-Policy-to-control-OneDrive-sync-client-settings-0ecb2cf5-8882-42b3-a6e9-be6bda30899c)

repository: paulwetter/Intune-Scripts

repo_name: paulwetter/Intune-Scripts


text:
# redux-saga-demo
Companion Repo for [Redux/Redux-saga beginner tutorial](https://github.com/redux-saga/redux-saga/blob/master/docs/introduction/BeginnerTutorial.md)

# Instructions

Setup

```
cd redux-saga-beginner-tutorial

npm install
```

Run the demo

```
npm start
```


text:
# rbenv4ci-container

This is a set of Dockerfiles including
[rbenv4ci](https://github.com/unleashed/rbenv4ci).

## License

Licensed under the [Apache 2.0 license](https://www.apache.org/licenses/LICENSE-2.0.html).


text:
# GamenChanger
the UI Component implementation & UI interaction tuning tool for Unity.
Synchronize the UI running on the UnityEditor and the actual device without build.

![corner](./Images/image.png)

*this product is in early stage of its implementation. do not use in production yet.

## 1. Corner
"Corner" is the component which can retrieve every Unity component which extends UIComponent.

the Corner component automatically captures all child UI components and
then you can
* swap all contents to another Corner's all contents.
* borrow all contents from other Corner's all contents. other become empty.
* back all contents to it's owner. become empty.

* exposure contents with Type.
* exclude specific contents.

![corner](./Images/corner.png)

ICornerContentHandler interface receives the events of Corner.
this is convenient for control contents itself when the Corner is changed by other Corner functions.

## 2. FlickableCorner, OneOfNCorner, DraggableCorner and OverlayCorner(WIP)

![corner](./Images/corners.png)

### 2-1. FlickableCorer
FlickableCorner can have 4 additional Corners on the Top/Bottom/Left/Right of it.
when player touches FlickableCorner which has one or more Corners, FlickableCorner can be flicked to the direction of connected Corners.

IFlickableCorner interface receives "Flick" events from FlickableCorner.

### 2-2. OneOfNCorner
OneOfNCorner can have N contents and is able to choice the 1 from there.
when you tap the UI which is contained in OneOfNCorner, you can update the status of choosed 1 object and others.

IOneOfNCorner interface receives "choose" events from OneOfN.

### 2-3. DraggableCorner
DraggableCorner can have 1 or more contents and add draggable feature, limit it's move to inside of the region of the DraggableCorner attached object.

### 2-4. OverlayCorner(WIP)
OverlayCorner can have one additional Corner and set it to back of this OverlayCorner when active.

 ## todo
 * implement OverlayCorner.
 * add accelelation parameter to the touch of flick gesture.
 * editor/device sync feature
 * bug fix

## furure(WIP)

![corner](./Images/overview_reflect.png)

## license
see below.
[LICENSE](./LICENSE)

repository: sassembla/GamenChanger

branch_name: refs/heads/main

repo_name: sassembla/GamenChanger


text:
# StructuredOptimization.jl

StructuredOptimization.jl is a high-level modeling language
that utilizes a syntax that is very close to
the mathematical formulation of an optimization problem.

This user-friendly interface
acts as a parser to utilize
three different packages:

* [ProximalOperators.jl](https://github.com/kul-forbes/ProximalOperators.jl) provides proximal mappings of functions that are frequently used in signal processing and optimization.

* [AbstractOperators.jl](https://github.com/kul-forbes/AbstractOperators.jl) provides algorithms for the evaluation and combination of forward and (Jacobian) adjoint of linear and nonlinear mappings.

* [ProximalAlgorithms.jl](https://github.com/kul-forbes/ProximalAlgorithms.jl) is a library of proximal algorithms (aka splitting algorithms) solvers.

StructuredOptimization.jl can handle large-scale convex and nonconvex problems with nonsmooth cost functions. It supports complex variables as well. See the [Quick tutorial guide](@ref) and the [Demos](@ref).

## Installation

To install the package, hit `]` from the Julia command line to enter the package manager, then

```julia
pkg> add StructuredOptimization
```

## Citing

If you use StructuredOptimization.jl for published work, we encourage you to cite:

* N. Antonello, L. Stella, P. Patrinos, T. van Waterschoot, “Proximal Gradient Algorithms: Applications in Signal Processing,” [arXiv:1803.01621](https://arxiv.org/abs/1803.01621) (2018).

## Credits

StructuredOptimization.jl is developed by
[Lorenzo Stella](https://lostella.github.io) and
[Niccolò Antonello](https://nantonel.github.io)
at [KU Leuven, ESAT/Stadius](https://www.esat.kuleuven.be/stadius/).

gha_license_id: NOASSERTION


text:
# Contributing to Atom

:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:

The following is a set of guidelines for contributing to Atom and its packages, which are hosted in the [Atom Organization](https://github.com/atom) on GitHub.
These are just guidelines, not rules, use your best judgment and feel free to propose changes to this document in a pull request.

#### Table Of Contents

[What should I know before I get started?](#what-should-i-know-before-i-get-started)
  * [Code of Conduct](#code-of-conduct)
  * [Atom and Packages](#atom-and-packages)

[How Can I Contribute?](#how-can-i-contribute)
  * [Submitting Issues](#submitting-issues)
  * [Your First Code Contribution](#your-first-code-contribution)
  * [Pull Requests](#pull-requests)

[Styleguides](#styleguides)
  * [Git Commit Messages](#git-commit-messages)
  * [CoffeeScript Styleguide](#coffeescript-styleguide)
  * [Specs Styleguide](#specs-styleguide)
  * [Documentation Styleguide](#documentation-styleguide)

[Additional Notes](#additional-notes)
  * [Issue and Pull Request Labels](#issue-and-pull-request-labels)

## What should I know before I get started?

### Code of Conduct

This project adheres to the [Contributor Covenant 1.2](http://contributor-covenant.org/version/1/2/0).
By participating, you are expected to uphold this code.
Please report unacceptable behavior to [atom@github.com](mailto:atom@github.com).

### Atom and Packages

Atom is a large open source project—it's made up of over [200 repositories](https://github.com/atom).
When you initially consider contributing to Atom, you might be unsure about which of those 200 repositories implements the functionality you want to change or report a bug for.
This section should help you with that.

Atom is intentionally very modular.

These packages are packages in the same way that packages in the [package store](https://atom.io/packages) are packages, with one difference: they are bundled into the [default distribution](https://github.com/atom/atom/blob/10b8de6fc499a7def9b072739486e68530d67ab4/package.json#L58).

![atom-packages](https://cloud.githubusercontent.com/assets/69169/10472281/84fc9792-71d3-11e5-9fd1-19da717df079.png)

To get a sense for the packages that are bundled with Atom, you can go to Settings > Packages within Atom and take a look at the Core Packages section.

Here's a list of the big ones:

* [atom/atom](https://github.com/atom/atom) - Atom Core! The core editor component is responsible for basic text editing (e.g. cursors, selections, scrolling), text indentation, wrapping, and folding, text rendering, editor rendering, file system operations (e.g. saving), and installation and auto-updating. You should also use this repository for feedback related to the [core API](https://atom.io/docs/api/latest/Notification) and for large, overarching design proposals.
* [tree-view](https://github.com/atom/tree-view) - file and directory listing on the left of the UI.
* [fuzzy-finder](https://github.com/atom/fuzzy-finder) - the quick file opener.
* [find-and-replace](https://github.com/atom/find-and-replace) - all search and replace functionality.
* [tabs](https://github.com/atom/tabs) - the tabs for open editors at the top of the UI.
* [status-bar](https://github.com/atom/status-bar) - the status bar at the bottom of the UI.
* [markdown-preview](https://github.com/atom/markdown-preview) - the rendered markdown pane item.
* [settings-view](https://github.com/atom/settings-view) - the settings UI pane item.
* [autocomplete-plus](https://github.com/atom/autocomplete-plus) - autocompletions shown while typing. Some languages have additional packages for autocompletion functionality, such as [autocomplete-html](https://github.com/atom/autocomplete-html).
* [git-diff](https://github.com/atom/git-diff) - Git change indicators shown in the editor's gutter.
* [language-javascript](https://github.com/atom/language-javascript) - all bundled languages are packages too, and each one has a separate package `language-[name]`. Use these for feedback on syntax highlighting issues that only appear for a specific language.
* [one-dark-ui](https://github.com/atom/one-dark-ui) - the default UI styling for anything but the text editor. UI theme packages (i.e. packages with a `-ui` suffix) provide only styling and it's possible that a bundled package is responsible for a UI issue. There are other other bundled UI themes, such as [one-light-ui](https://github.com/atom/one-light-ui).
* [one-dark-syntax](https://github.com/atom/one-dark-syntax) - the default syntax highlighting styles applied for all languages. There are other other bundled syntax themes, such as [solarized-dark](https://github.com/atom/solarized-dark). You should use these packages for reporting issues that appear in many languages, but disappear if you change to another syntax theme.
* [apm](https://github.com/atom/apm) - the `apm` command line tool (Atom Package Manager). You should use this repository for any contributions related to the `apm` tool and to publishing packages.
* [atom.io](https://github.com/atom/atom.io) - the repository for feedback on the [Atom.io website](https://atom.io) and the [Atom.io package API](https://github.com/atom/atom/blob/master/docs/apm-rest-api.md) used by [apm](https://github.com/atom/apm).

There are many more, but this list should be a good starting point.
For more information on how to work with Atom's official packages, see [Contributing to Atom Packages](https://github.com/atom/atom/blob/master/docs/contributing-to-packages.md).

Also, because Atom is so extensible, it's possible that a feature you've become accustomed to in Atom or an issue you're encountering aren't coming from a bundled package at all, but rather a [community package](https://atom.io/packages) you've installed.
Each community package has its own repository too, and you should be able to find it in Settings > Packages for the packages you installed and contribute there.

## How can I contribute?

### Submitting Issues

* You can create an issue [here](https://github.com/atom/atom/issues/new), but
  before doing that please read the notes below on debugging and submitting issues,
  and include as many details as possible with your report.
* Check the [debugging guide](https://atom.io/docs/latest/hacking-atom-debugging) for tips
  on debugging. You might be able to find the cause of the problem and fix
  things yourself.
* Include the version of Atom you are using and the OS.
* Include screenshots and animated GIFs whenever possible; they are immensely
  helpful.
* Include the behavior you expected and other places you've seen that behavior
  such as Emacs, vi, Xcode, etc.
* Check the dev tools (`alt-cmd-i`) for errors to include. If the dev tools
  are open _before_ the error is triggered, a full stack trace for the error
  will be logged. If you can reproduce the error, use this approach to get the
  full stack trace and include it in the issue.
* On Mac, check Console.app for stack traces to include if reporting a crash.
* Perform a [cursory search](https://github.com/issues?q=+is%3Aissue+user%3Aatom)
  to see if a similar issue has already been submitted.
* Please setup a [profile picture](https://help.github.com/articles/how-do-i-set-up-my-profile-picture)
  to make yourself recognizable and so we can all get to know each other better.

### Your First Code Contribution

Unsure where to begin contributing to Atom? You can start by looking through these `beginner` and `help-wanted` issues:

* [Beginner issues][beginner] - issues which should only require a few lines of code, and a test or two.
* [Help wanted issues][help-wanted] - issues which should be a bit more involved than `beginner` issues.

Both issue lists are sorted by total number of comments. While not perfect, number of comments is a reasonable proxy for impact a given change will have.

### Pull Requests

* Include screenshots and animated GIFs in your pull request whenever possible.
* Follow the [CoffeeScript](#coffeescript-styleguide),
  [JavaScript](https://github.com/styleguide/javascript),
  and [CSS](https://github.com/styleguide/css) styleguides.
* Include thoughtfully-worded, well-structured
  [Jasmine](http://jasmine.github.io/) specs in the `./spec` folder. Run them using `apm test`. See the [Specs Styleguide](#specs-styleguide) below.
* Document new code based on the
  [Documentation Styleguide](#documentation-styleguide)
* End files with a newline.
* Place requires in the following order:
    * Built in Node Modules (such as `path`)
    * Built in Atom and Atom Shell Modules (such as `atom`, `shell`)
    * Local Modules (using relative paths)
* Place class properties in the following order:
    * Class methods and properties (methods starting with a `@`)
    * Instance methods and properties
* Avoid platform-dependent code:
    * Use `require('fs-plus').getHomeDirectory()` to get the home directory.
    * Use `path.join()` to concatenate filenames.
    * Use `os.tmpdir()` rather than `/tmp` when you need to reference the
      temporary directory.
* Using a plain `return` when returning explicitly at the end of a function.
    * Not `return null`, `return undefined`, `null`, or `undefined`

## Styleguides

### Git Commit Messages

* Use the present tense ("Add feature" not "Added feature")
* Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
* Limit the first line to 72 characters or less
* Reference issues and pull requests liberally
* Consider starting the commit message with an applicable emoji:
    * :art: `:art:` when improving the format/structure of the code
    * :racehorse: `:racehorse:` when improving performance
    * :non-potable_water: `:non-potable_water:` when plugging memory leaks
    * :memo: `:memo:` when writing docs
    * :penguin: `:penguin:` when fixing something on Linux
    * :apple: `:apple:` when fixing something on Mac OS
    * :checkered_flag: `:checkered_flag:` when fixing something on Windows
    * :bug: `:bug:` when fixing a bug
    * :fire: `:fire:` when removing code or files
    * :green_heart: `:green_heart:` when fixing the CI build
    * :white_check_mark: `:white_check_mark:` when adding tests
    * :lock: `:lock:` when dealing with security
    * :arrow_up: `:arrow_up:` when upgrading dependencies
    * :arrow_down: `:arrow_down:` when downgrading dependencies
    * :shirt: `:shirt:` when removing linter warnings

### CoffeeScript Styleguide

* Set parameter defaults without spaces around the equal sign
    * `clear = (count=1) ->` instead of `clear = (count = 1) ->`
* Use spaces around operators
    * `count + 1` instead of `count+1`
* Use spaces after commas (unless separated by newlines)
* Use parentheses if it improves code clarity.
* Prefer alphabetic keywords to symbolic keywords:
    * `a is b` instead of `a == b`
* Avoid spaces inside the curly-braces of hash literals:
    * `{a: 1, b: 2}` instead of `{ a: 1, b: 2 }`
* Include a single line of whitespace between methods.
* Capitalize initialisms and acronyms in names, except for the first word, which
  should be lower-case:
  * `getURI` instead of `getUri`
  * `uriToOpen` instead of `URIToOpen`
* Use `slice()` to copy an array
* Add an explicit `return` when your function ends with a `for`/`while` loop and
  you don't want it to return a collected array.
* Use `this` instead of a standalone `@`
  * `return this` instead of `return @`

### Specs Styleguide

- Include thoughtfully-worded, well-structured
  [Jasmine](http://jasmine.github.io/) specs in the `./spec` folder.
- treat `describe` as a noun or situation.
- treat `it` as a statement about state or how an operation changes state.

#### Example

```coffee
describe 'a dog', ->
 it 'barks', ->
 # spec here
 describe 'when the dog is happy', ->
  it 'wags its tail', ->
  # spec here
```

### Documentation Styleguide

* Use [AtomDoc](https://github.com/atom/atomdoc).
* Use [Markdown](https://daringfireball.net/projects/markdown).
* Reference methods and classes in markdown with the custom `{}` notation:
    * Reference classes with `{ClassName}`
    * Reference instance methods with `{ClassName::methodName}`
    * Reference class methods with `{ClassName.methodName}`

#### Example

```coffee
# Public: Disable the package with the given name.
#
# * `name`    The {String} name of the package to disable.
# * `options` (optional) The {Object} with disable options (default: {}):
#   * `trackTime`     A {Boolean}, `true` to track the amount of time taken.
#   * `ignoreErrors`  A {Boolean}, `true` to catch and ignore errors thrown.
# * `callback` The {Function} to call after the package has been disabled.
#
# Returns `undefined`.
disablePackage: (name, options, callback) ->
```

## Additional Notes

### Issue and Pull Request Labels

This section lists the labels we use to help us track and manage issues and pull requests. Most labels are used across all Atom repositories, but some are specific to `atom/atom`.

[GitHub search](https://help.github.com/articles/searching-issues/) makes it easy to use labels for finding groups of issues or pull requests you're interested in. For example, you might be interested in [open issues across `atom/atom` and all Atom-owned packages which are labeled as bugs, but still need to be reliably reproduced](https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Abug+label%3Aneeds-reproduction) or perhaps [open pull requests in `atom/atom` which haven't been reviewed yet](https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+repo%3Aatom%2Fatom+comments%3A0). To help you find issues and pull requests, each label is listed with search links for finding open items with that label in `atom/atom` only and also across all Atom repositories. We  encourage you to read about [other search filters](https://help.github.com/articles/searching-issues/) which will help you write more focused queries.

The labels are loosely grouped by their purpose, but it's not required that every issue have a label from every group or that an issue can't have more than one label from the same group.

Please open an issue on `atom/atom` if you have suggestions for new labels, and if you notice some labels are missing on some repositories, then please open an issue on that repository.

#### Type of Issue and Issue State

| Label name | `atom/atom` :mag_right: | `atom`‑org :mag_right: | Description |
| --- | --- | --- | --- |
| `enhancement` | [search][search-atom-repo-label-enhancement] | [search][search-atom-org-label-enhancement] | Feature requests. |
| `bug` | [search][search-atom-repo-label-bug] | [search][search-atom-org-label-bug] | Confirmed bugs or reports that are very likely to be bugs. |
| `question` | [search][search-atom-repo-label-question] | [search][search-atom-org-label-question] | Questions more than bug reports or feature requests (e.g. how do I do X). |
| `feedback` | [search][search-atom-repo-label-feedback] | [search][search-atom-org-label-feedback] | General feedback more than bug reports or feature requests. |
| `help-wanted` | [search][search-atom-repo-label-help-wanted] | [search][search-atom-org-label-help-wanted] | The Atom core team would appreciate help from the community in resolving these issues. |
| `beginner` | [search][search-atom-repo-label-beginner] | [search][search-atom-org-label-beginner] | Less complex issues which would be good first issues to work on for users who want to contribute to Atom. |
| `more-information-needed` | [search][search-atom-repo-label-more-information-needed] | [search][search-atom-org-label-more-information-needed] | More information needs to be collected about these problems or feature requests (e.g. steps to reproduce). |
| `needs-reproduction` | [search][search-atom-repo-label-needs-reproduction] | [search][search-atom-org-label-needs-reproduction] | Likely bugs, but haven't been reliably reproduced. |
| `blocked` | [search][search-atom-repo-label-blocked] | [search][search-atom-org-label-blocked] | Issues blocked on other issues. |
| `duplicate` | [search][search-atom-repo-label-duplicate] | [search][search-atom-org-label-duplicate] | Issues which are duplicates of other issues, i.e. they have been reported before. |
| `wontfix` | [search][search-atom-repo-label-wontfix] | [search][search-atom-org-label-wontfix] | The Atom core team has decided not to fix these issues for now, either because they're working as intended or for some other reason. |
| `invalid` | [search][search-atom-repo-label-invalid] | [search][search-atom-org-label-invalid] | Issues which are't valid (e.g. user errors). |
| `package-idea` | [search][search-atom-repo-label-package-idea] | [search][search-atom-org-label-package-idea] | Feature request which might be good candidates for new packages, instead of extending Atom or core Atom packages. |
| `wrong-repo` | [search][search-atom-repo-label-wrong-repo] | [search][search-atom-org-label-wrong-repo] | Issues reported on the wrong repository (e.g. a bug related to the [Settings View package](https://github.com/atom/settings-view) was reported on [Atom core](https://github.com/atom/atom)). |

#### Topic Categories

| Label name | `atom/atom` :mag_right: | `atom`‑org :mag_right: | Description |
| --- | --- | --- | --- |
| `windows` | [search][search-atom-repo-label-windows] | [search][search-atom-org-label-windows] | Related to Atom running on Windows. |
| `linux` | [search][search-atom-repo-label-linux] | [search][search-atom-org-label-linux] | Related to Atom running on Linux. |
| `mac` | [search][search-atom-repo-label-mac] | [search][search-atom-org-label-mac] | Related to Atom running on OSX. |
| `documentation` | [search][search-atom-repo-label-documentation] | [search][search-atom-org-label-documentation] | Related to any type of documentation (e.g. [API documentation](https://atom.io/docs/api/latest/Atom) and the [flight manual](https://atom.io/docs/latest/)). |
| `performance` | [search][search-atom-repo-label-performance] | [search][search-atom-org-label-performance] | Related to performance. |
| `security` | [search][search-atom-repo-label-security] | [search][search-atom-org-label-security] | Related to security. |
| `ui` | [search][search-atom-repo-label-ui] | [search][search-atom-org-label-ui] | Related to visual design. |
| `api` | [search][search-atom-repo-label-api] | [search][search-atom-org-label-api] | Related to Atom's public APIs. |
| `uncaught-exception` | [search][search-atom-repo-label-uncaught-exception] | [search][search-atom-org-label-uncaught-exception] | Issues about uncaught exceptions, normally created from the [Notifications package](https://github.com/atom/notifications). |
| `crash` | [search][search-atom-repo-label-crash] | [search][search-atom-org-label-crash] | Reports of Atom completely crashing. |
| `auto-indent` | [search][search-atom-repo-label-auto-indent] | [search][search-atom-org-label-auto-indent] | Related to auto-indenting text. |
| `encoding` | [search][search-atom-repo-label-encoding] | [search][search-atom-org-label-encoding] | Related to character encoding. |
| `network` | [search][search-atom-repo-label-network] | [search][search-atom-org-label-network] | Related to network problems or working with remote files (e.g. on network drives). |
| `git` | [search][search-atom-repo-label-git] | [search][search-atom-org-label-git] | Related to Git functionality (e.g. problems with gitignore files or with showing the correct file status). |

#### `atom/atom` Topic Categories

| Label name | `atom/atom` :mag_right: | `atom`‑org :mag_right: | Description |
| --- | --- | --- | --- |
| `editor-rendering` | [search][search-atom-repo-label-editor-rendering] | [search][search-atom-org-label-editor-rendering] | Related to language-independent aspects of rendering text (e.g. scrolling, soft wrap, and font rendering). |
| `build-error` | [search][search-atom-repo-label-build-error] | [search][search-atom-org-label-build-error] | Related to problems with building Atom from source. |
| `error-from-pathwatcher` | [search][search-atom-repo-label-error-from-pathwatcher] | [search][search-atom-org-label-error-from-pathwatcher] | Related to errors thrown by the [pathwatcher library](https://github.com/atom/node-pathwatcher). |
| `error-from-save` | [search][search-atom-repo-label-error-from-save] | [search][search-atom-org-label-error-from-save] | Related to errors thrown when saving files. |
| `error-from-open` | [search][search-atom-repo-label-error-from-open] | [search][search-atom-org-label-error-from-open] | Related to errors thrown when opening files. |
| `installer` | [search][search-atom-repo-label-installer] | [search][search-atom-org-label-installer] | Related to the Atom installers for different OSes. |
| `auto-updater` | [search][search-atom-repo-label-auto-updater] | [search][search-atom-org-label-auto-updater] | Related to the auto-updater for different OSes. |
| `deprecation-help` | [search][search-atom-repo-label-deprecation-help] | [search][search-atom-org-label-deprecation-help] | Issues for helping package authors remove usage of deprecated APIs in packages. |
| `electron` | [search][search-atom-repo-label-electron] | [search][search-atom-org-label-electron] | Issues that require changes to [Electron](https://electron.atom.io) to fix or implement. |

#### Core Team Project Management

| Label name | `atom/atom` :mag_right: | `atom`‑org :mag_right: | Description |
| --- | --- | --- | --- |
| `in-progress` | [search][search-atom-repo-label-in-progress] | [search][search-atom-org-label-in-progress] | Tasks which the Atom core team is working on currently. |
| `on-deck` | [search][search-atom-repo-label-on-deck] | [search][search-atom-org-label-on-deck] | Tasks which the Atom core team plans to work on next. |
| `shipping` | [search][search-atom-repo-label-shipping] | [search][search-atom-org-label-shipping] | Tasks which the Atom core team completed and will be released in one of the next releases. |
| `post-1.0-roadmap` | [search][search-atom-repo-label-post-1.0-roadmap] | [search][search-atom-org-label-post-1.0-roadmap] | The Atom core team's roadmap post version 1.0.0. |
| `atom` | [search][search-atom-repo-label-atom] | [search][search-atom-org-label-atom] | Topics discussed for prioritization at the next meeting of Atom core team members. |

#### Pull Request Labels

| Label name | `atom/atom` :mag_right: | `atom`‑org :mag_right: | Description
| --- | --- | --- | --- |
| `work-in-progress` | [search][search-atom-repo-label-work-in-progress] | [search][search-atom-org-label-work-in-progress] | Pull requests which are still being worked on, more changes will follow. |
| `needs-review` | [search][search-atom-repo-label-needs-review] | [search][search-atom-org-label-needs-review] | Pull requests which need code review, and approval from maintainers or Atom core team. |
| `under-review` | [search][search-atom-repo-label-under-review] | [search][search-atom-org-label-under-review] | Pull requests being reviewed by maintainers or Atom core team. |
| `requires-changes` | [search][search-atom-repo-label-requires-changes] | [search][search-atom-org-label-requires-changes] | Pull requests which need to be updated based on review comments and then reviewed again. |
| `needs-testing` | [search][search-atom-repo-label-needs-testing] | [search][search-atom-org-label-needs-testing] | Pull requests which need manual testing. |

[search-atom-repo-label-enhancement]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aenhancement
[search-atom-org-label-enhancement]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aenhancement
[search-atom-repo-label-bug]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Abug
[search-atom-org-label-bug]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Abug
[search-atom-repo-label-question]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aquestion
[search-atom-org-label-question]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aquestion
[search-atom-repo-label-feedback]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Afeedback
[search-atom-org-label-feedback]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Afeedback
[search-atom-repo-label-help-wanted]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Ahelp-wanted
[search-atom-org-label-help-wanted]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Ahelp-wanted
[search-atom-repo-label-beginner]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Abeginner
[search-atom-org-label-beginner]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Abeginner
[search-atom-repo-label-more-information-needed]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Amore-information-needed
[search-atom-org-label-more-information-needed]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Amore-information-needed
[search-atom-repo-label-needs-reproduction]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aneeds-reproduction
[search-atom-org-label-needs-reproduction]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aneeds-reproduction
[search-atom-repo-label-triage-help-needed]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Atriage-help-needed
[search-atom-org-label-triage-help-needed]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Atriage-help-needed
[search-atom-repo-label-windows]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Awindows
[search-atom-org-label-windows]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Awindows
[search-atom-repo-label-linux]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Alinux
[search-atom-org-label-linux]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Alinux
[search-atom-repo-label-mac]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Amac
[search-atom-org-label-mac]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Amac
[search-atom-repo-label-documentation]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Adocumentation
[search-atom-org-label-documentation]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Adocumentation
[search-atom-repo-label-performance]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aperformance
[search-atom-org-label-performance]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aperformance
[search-atom-repo-label-security]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Asecurity
[search-atom-org-label-security]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Asecurity
[search-atom-repo-label-ui]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aui
[search-atom-org-label-ui]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aui
[search-atom-repo-label-api]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aapi
[search-atom-org-label-api]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aapi
[search-atom-repo-label-crash]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Acrash
[search-atom-org-label-crash]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Acrash
[search-atom-repo-label-auto-indent]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aauto-indent
[search-atom-org-label-auto-indent]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aauto-indent
[search-atom-repo-label-encoding]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aencoding
[search-atom-org-label-encoding]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aencoding
[search-atom-repo-label-network]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Anetwork
[search-atom-org-label-network]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Anetwork
[search-atom-repo-label-uncaught-exception]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Auncaught-exception
[search-atom-org-label-uncaught-exception]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Auncaught-exception
[search-atom-repo-label-git]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Agit
[search-atom-org-label-git]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Agit
[search-atom-repo-label-blocked]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Ablocked
[search-atom-org-label-blocked]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Ablocked
[search-atom-repo-label-duplicate]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aduplicate
[search-atom-org-label-duplicate]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aduplicate
[search-atom-repo-label-wontfix]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Awontfix
[search-atom-org-label-wontfix]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Awontfix
[search-atom-repo-label-invalid]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Ainvalid
[search-atom-org-label-invalid]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Ainvalid
[search-atom-repo-label-package-idea]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Apackage-idea
[search-atom-org-label-package-idea]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Apackage-idea
[search-atom-repo-label-wrong-repo]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Awrong-repo
[search-atom-org-label-wrong-repo]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Awrong-repo
[search-atom-repo-label-editor-rendering]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aeditor-rendering
[search-atom-org-label-editor-rendering]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aeditor-rendering
[search-atom-repo-label-build-error]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Abuild-error
[search-atom-org-label-build-error]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Abuild-error
[search-atom-repo-label-error-from-pathwatcher]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aerror-from-pathwatcher
[search-atom-org-label-error-from-pathwatcher]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aerror-from-pathwatcher
[search-atom-repo-label-error-from-save]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aerror-from-save
[search-atom-org-label-error-from-save]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aerror-from-save
[search-atom-repo-label-error-from-open]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aerror-from-open
[search-atom-org-label-error-from-open]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aerror-from-open
[search-atom-repo-label-installer]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Ainstaller
[search-atom-org-label-installer]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Ainstaller
[search-atom-repo-label-auto-updater]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aauto-updater
[search-atom-org-label-auto-updater]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aauto-updater
[search-atom-repo-label-deprecation-help]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Adeprecation-help
[search-atom-org-label-deprecation-help]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Adeprecation-help
[search-atom-repo-label-electron]: https://github.com/issues?q=is%3Aissue+repo%3Aatom%2Fatom+is%3Aopen+label%3Aelectron
[search-atom-org-label-electron]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aelectron
[search-atom-repo-label-on-deck]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aon-deck
[search-atom-org-label-on-deck]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aon-deck
[search-atom-repo-label-in-progress]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Ain-progress
[search-atom-org-label-in-progress]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Ain-progress
[search-atom-repo-label-shipping]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Ashipping
[search-atom-org-label-shipping]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Ashipping
[search-atom-repo-label-post-1.0-roadmap]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Apost-1.0-roadmap
[search-atom-org-label-post-1.0-roadmap]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Apost-1.0-roadmap
[search-atom-repo-label-atom]: https://github.com/issues?q=is%3Aopen+is%3Aissue+repo%3Aatom%2Fatom+label%3Aatom
[search-atom-org-label-atom]: https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aatom+label%3Aatom
[search-atom-repo-label-work-in-progress]: https://github.com/pulls?q=is%3Aopen+is%3Apr+repo%3Aatom%2Fatom+label%3Awork-in-progress
[search-atom-org-label-work-in-progress]: https://github.com/pulls?q=is%3Aopen+is%3Apr+user%3Aatom+label%3Awork-in-progress
[search-atom-repo-label-needs-review]: https://github.com/pulls?q=is%3Aopen+is%3Apr+repo%3Aatom%2Fatom+label%3Aneeds-review
[search-atom-org-label-needs-review]: https://github.com/pulls?q=is%3Aopen+is%3Apr+user%3Aatom+label%3Aneeds-review
[search-atom-repo-label-under-review]: https://github.com/pulls?q=is%3Aopen+is%3Apr+repo%3Aatom%2Fatom+label%3Aunder-review
[search-atom-org-label-under-review]: https://github.com/pulls?q=is%3Aopen+is%3Apr+user%3Aatom+label%3Aunder-review
[search-atom-repo-label-requires-changes]: https://github.com/pulls?q=is%3Aopen+is%3Apr+repo%3Aatom%2Fatom+label%3Arequires-changes
[search-atom-org-label-requires-changes]: https://github.com/pulls?q=is%3Aopen+is%3Apr+user%3Aatom+label%3Arequires-changes
[search-atom-repo-label-needs-testing]: https://github.com/pulls?q=is%3Aopen+is%3Apr+repo%3Aatom%2Fatom+label%3Aneeds-testing
[search-atom-org-label-needs-testing]: https://github.com/pulls?q=is%3Aopen+is%3Apr+user%3Aatom+label%3Aneeds-testing

[beginner]:https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Abeginner+label%3Ahelp-wanted+user%3Aatom+sort%3Acomments-desc
[help-wanted]:https://github.com/issues?q=is%3Aopen+is%3Aissue+label%3Ahelp-wanted+user%3Aatom+sort%3Acomments-desc

repository: vacom/atom

gha_language: CoffeeScript

repo_name: vacom/atom


text:
# joshandjames.github.io

Our website for computer science. This website entails the various soccer positions and some details on them as well as other training information.

---

When creating a page, make sure that your page meets these requirements:

- Navigation bar included
- Background Color/Image
- Cited Image
- Link to a relevant video
- At least one header and paragraph
  - Each `<h1>` tag needs to have same class name. Insert `class="standard"` into each tag like so: `<h1 class="standard">`
- External CSS
- JavaScript feature

---

### Feature Guide

When we created this project, we created a variety of different features to make the website stand out.

| Feature | Why | Pages It Is On |
| --- | --- | --- |
| JavaScript NavBar | We created a [JavaScript navbar script](https://github.com/joshandjames/joshandjames.github.io/blob/master/script/navigation.js) that fills in the navigation bar on page load. Having a single file do the work makes it easy to change the navbar's contents. Rather than updating every page's navbar, we can just add a link object to the link array in the script. | This feature can be seen on every page. |
| Consistent Look | You might notice that all of our pages look similar. This is because, we used the same page layout for each page. We first made the homepage beautiful and then used the same code again and again for each page while adjusting the page content and format when needed. | This feature can be seen on every page. |

repository: joshandjames/soccerstuff

repo_name: joshandjames/soccerstuff


text:
# Note-Taker

## Description
This is an application that can be used to write, save, and delete notes. This application uses an express backend, saves and retrieve note data from a JSON file.

### Link for the project
https://github.com/seebell/Note-Taker

## Table of Contents
* [License](#license)
* [Installation](#installation)
* [Usage](#usage)

## License

ISC

### Installation

Npm i first; also express will need to be installed

## Usage

Run the command 'node server.js on the terminal; port will be listening on local host 3000. When you open the page you will be able write, save and delete notes on the Note Taker

### User story
AS A user, I want to be able to write and save notes

I WANT to be able to delete notes I've written before

SO THAT I can organize my thoughts and keep track of tasks I need to complete

## Business Context

For users that need to keep track of a lot of information, it's easy to forget or be unable to recall something important. Being able to take persistent notes allows users to have written information available when needed.

## Link for working app via Heroku

https://enigmatic-bastion-04411.herokuapp.com/notes

license: ISC

repository: seebell/Note-Taker

gha_language: JavaScript

repo_name: seebell/Note-Taker


text:
# Project Builder
___

* [About The Project](#1)
* [Getting Started](#2)
* [Prerequisites](#3)
* [Installation](#4)
* [Contributing](#5)
* [License](#6)
* [Acknowledgements](#7)

---

### About the Project
ProjectBuilder is a app where you can create, projects and details that do with it.

Backend is created with Ruby on Rails. Click to see the [backend](https://github.com/myildiz17/Mod3ProjectBackend).

[Frontend](https://github.com/myildiz17/Mod3ProjectFrontend-) is designed in Vanilla JavaScipt.

Watch the [demo](https://youtu.be/-gECARO9lUU).

---

### Getting Started
Make sure you have the following tools installed on your system:

* Github
* Ruby 2.6.1
* Rails <IP_ADDRESS>
* React 17.10.4

---

### Prerequisites
Make sure to install all necessary programs and create the database

bundle install

rails console

rails db:create

rails db:migrate

---

### Installation

Create a folder and clone forntend and backend repos into it:

git clone https://github.com/myildiz17/Mod4FrontEnd

git clone https://github.com/myildiz17/Mod4BackEnd

cd into the frontend

Install the gemfile packages

bundle install

Set up the Database

rails db:create

rails db:migrate

rails db:seed

rails s

cd into school-app

npm install

open index.html

---

### Contributing
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

---

### License

Distributed under the MIT License. https://opensource.org/licenses/MIT

---

### Acknowledgements
Flatiron School

---
### Available Scripts
In the project directory, you can run:

npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

---

### Learn More
You can learn more in the [Create React App documentation](https://create-react-app.dev/docs/getting-started/).

To learn React, check out the [React documentation](https://reactjs.org/).


text:
# SMX template for JSDoc 3

- [SMX](https://github.com/canvasplay/SMX)
- [SMX API Documentation](http://canvasplay.github.io/SMX/)

## Installation

Install the template using NPM:

```bash
npm install smx-jsdoc-template --save-dev
```

## Usage

If you already have JSDoc system, you can use this project as JSDoc template. More information about JSDoc command-line arguments can be found [here](http://usejsdoc.org/about-commandline.html).

```bash
jsdoc -c conf.json -R README.md
```

### conf.json

Customize your docs output under the `templates` object in your jsdoc `conf.json`. Notice the `"template"` field for setting the path to **smx-jsdoc-template**.

There are also two additional objects for customizing the content on the sidebar navigation menu.
`NavSections` determines wich section the menu will show, and `navRecursion` resolve tree item contents by kind. Only first level items are initially visible, but using the serach form will reveal them if the search matches the items' names.

Bonus tip. The template has some keyboard shortcuts, the `s` key will focus the search input and `ESC` will clear the search.

```json
"templates": {
    "applicationName": "Demo",
    "disqus": "",
    "googleAnalytics": "",
    "openGraph": {
        "title": "",
        "type": "website",
        "image": "",
        "site_name": "",
        "url": ""
    },
    "meta": {
        "title": "",
        "description": "",
        "keyword": ""
    },
    "linenums": true,
    "source": {
        "include": [
            "./src/"
        ],
        "includePattern": ".+\\.js(doc)?$",
        "excludePattern": "(^|\\/|\\\\)_"
    },
    "opts": {
        "encoding": "utf8",
        "recurse": true,
        "private": false,
        "lenient": true,
        "destination": "./docs",
        "template": "./node_modules/smx-jsdoc-template"
    },
    "navRecursion": {
      "global": ["module", "class", "mixin", "member", "function", "event", "typedef"],
      "namespace": ["member", "function", "event", "typedef"],
      "module": ["module", "class", "mixin", "member", "function", "event", "typedef"],
      "class": ["member", "function", "event", "typedef"],
      "mixin": ["member", "function", "event", "typedef"]
    },
    "navSections":[
      {
        "id": "index",
        "title": "Home"
      },
      {
        "id": "tutorials",
        "title": "Tutorials"
      },
      {
        "id": "namespaces",
        "title": "Namespaces"
      },
      {
        "id": "classes",
        "title": "Classes"
      },
      {
        "id": "modules",
        "title": "Modules"
      },
      {
        "id": "globals",
        "title": "Global"
      }
    ]

}
```

## License

This project is under the MIT License. And this project was inspired by by default template for JSDoc 3 and docdash.

repository: clairestreb/smx-jsdoc-template

repo_name: clairestreb/smx-jsdoc-template


text:
# Exposing Cluster DNS

## Replace Systemd-resolved With Dnsmasq

Sometimes systemd-resolved, default stub resolver for many linux systems, needs to be replaced with dnsmasq. This dnsmasq systemd drop-in is useful to ensure that systemd-resolved is not running when the dnsmasq service is started:

```
# /etc/systemd/system/dnsmasq.service.d/10-resolved-fix.conf
[Unit]
After=systemd-resolved.service

[Service]
ExecStartPre=/bin/systemctl stop systemd-resolved.service
ExecStartPost=/bin/systemctl start systemd-resolved.service
```

It works by allowing systemd-resolved to start, but stopping it once the dnsmasq service is started. This is helpful because it doesn't require changing any of the systemd-resolved specific settings but allows the dnsmasq service to be enabled/disabled when desired.

## Forwarding Cluster-bound DNS on the Host

A reason why one might want to use something like dnsmasq, instead of systemd-resolved, is to expose the cluster DNS to the host. This would allow resolution of DNS for [service and pod subnets](configuring-control-plane-components.md#configuring-podservice-subnets) from the host that is running the Kubernetes components. It only requires adding this dnsmasq configuration drop-in:

```
# /etc/dnsmasq.d/kube.conf
server=/cluster.local/<IP_ADDRESS>
```

This tells dnsmasq to forward any DNS queries it receives that end in the cluster domain, to the Kubernetes cluster dns, CoreDNS. In this case, it is presuming that the default cluster domain (`cluster.local`) and services subnet, have been configured. The address of CoreDNS is chosen automatically based upon the services subnet, so if the services subnet is `<IP_ADDRESS>/16` (the default), CoreDNS will be listening at `<IP_ADDRESS>`.

## Specifying the resolv.conf

The default resolv.conf from the host is used, `/etc/resolv.conf` or a different conf file can be set in the Kubelet:

```yaml
apiVersion: crit.sh/v1alpha2
kind: ControlPlaneConfiguration
node:
  kubelet:
    resolvConf: /other/resolv.conf
```

Crit attempts to determine if systemd-resolved is running, and dynamically sets `resolvConf` to be `/run/systemd/resolve/resolv.conf`.

repository: criticalstack/crit

gha_language: Go

repo_name: criticalstack/crit


text:
# Task 2 - Blobber
---
Call your files task2.py, blobber.py, and plan2.txt.

 A Blobber is an imaginary being who is shaped like a cylinder. Your program will allow a user to create a Virtual Blobber they can take care of, similar to virtual pet like a Tamagotchi. Taking care of a Blobber is not an easy task. It takes constant vigilance and dedication. By the time you’re done testing your program you will never want to own an actual Blobber.

---
### Starter Code
---
[task2_starter.zip](https://github.com/drewriker/USU-CS-1400/files/6283298/task2_starter.zip)

Change the name of this file to task2.py. Only change the file where marked `<Fill-In>`. If `<Fill-In>` is only a line by itself, then you must complete the entire line. If it is part of a line, then you just add code to replace the `<Fill-In>` marker.

---
### How a Blobber works
---
A Blobber is a funny kind of being. It known by a combination of a name and color. It is shaped like a cylinder and likes to maintain a certain level of happiness. Its happiness is determined solely by how close its current volume is compared to its volume at birth. Immediately following birth, its radius begins to decrease. The Blobber caretaker can feed the Blobber regularly in order to maintain its volume. If the volume is ever too high or too low, the Blobber turns to dust.

Create a class called Blobber inside of a file called blobber.py. Your Blobber class should have the following properties:

* A private float data field called radius
* A private float data field called height
* A private string data field called color. The color should always be lowercase.
* A private string data field called name. The name should always be capitalized.
* A constructor is called with a name, color, radius, and height.
* Accessor (getter) and mutator (setter) methods for name and color
* A method called feedBlobber()
    * Takes a float value and increases the radius by the given amount
    * This method takes some thought!
* A method called blobberSpeak() that returns a string that can be printed.
    * The string should be a complete two line statement that includes the name, color, and happiness level of the Blobber.
    * Ex:
        * My name is Alice, and I am green.
        * My current happiness level is 93.25%
    * The happiness level should be shown as a percentage with two decimal places
    * Note: this method returns a string, it does not print a string
* A method called vitalsOK().
    * See the Blobber Vitality section for more details
    * Returns two values:
        * The current happiness level
        * A Boolean value
            * True if the Blobber is alive.
            * False if the Blobber has turned to dust.
* Any other private data or methods you need.

---
### Blobber Vitality
---
A Blobber’s happiness level is a measure of how close its current volume is compared to its original volume. It is 100% when the volumes are exactly the same. It cannot survive when the current volume is +/- 10% of its original volume. This means a Blobber can only exist if its happiness is from 90% to 110%.

A Blobber loses 0.2% of its ***original*** radius every second. If its volume is ever greater or less than 10% of its ***original*** volume, then it turns to dust.  The vitality should be checked and displayed right after the menu. It should also be checked right after a menu selection is made. In either case, if the Blobber has turned to dust, an appropriate message should be displayed and the program should end. See the starter code for details.

---
### Main Menu
---

    (1): Display Name
    (2): Change Name
    (3): Display Color
    (4): Change Color
    (5): Feed Blobber
    (6): Blobber Speak
    (7): Exit

You will need to decide on some submenus for some of the choices. Use blank lines in your output so it's easy for the user to see what is happening.

---
### Video Demo
---

Sorry, there is a bug in my demo. The calculation of the happiness level is off. I believe I had the radius and height variables backwards. Double check your formula and go with your calculation.

---
### Timer Help
---

This is not really part of the assignment, but may help you figure out how to manage the changing of the Blobber's vitality.

[FakeTimer.zip](https://github.com/drewriker/USU-CS-1400/files/6283341/FakeTimer.zip)

---
### Design Plan
---

Your Software Design is getting more and more complicated. Make your plan for blobber.py, including UML. Within the plan create a design for each function/method. As you break down the problem into individual pieces, calling a function/method you design counts as an individual piece since it will be designed as well.  This means the design of one function/method can include a function call to another function/method. Make sure to include UML for the Blobber class.

---
### Common Errors
---

This is the most difficult task to this point of this semester. It is meant to be very challenging. The most common error is not breaking the program down into small pieces. Complete one menu item at a time.

url: https://raw.githubusercontent.com/drewriker/USU-CS-1400/c364e8591120c7f4b6c91ca8612615295134f19d/Assignment 9/Task 2 - Blobber.md

path: /Assignment 9/Task 2 - Blobber.md

filename: Task 2 - Blobber.md

gha_language: Python


text:
# Employee Directory

   Deployed website:  https://jamiekim87.github.io/employee/

   GitHub Repo:  https://github.com/jamiekim87/employee_directory.git

   ![image2](https://user-images.githubusercontent.com/64169844/94744429-d52f7180-032d-11eb-8fd5-be5013c129d2.png)

   ## Table of Contents

   - [Description](#description)
   - [Installation](#installation)
   - [Usage](#usage)
   - [License](#license)
   - [Contributing](#contributing)
   - [Tests](#tests)
   - [Questions](#questions)

   ## Description
   For this assignment, you'll creat a employee directory with React. This assignment will require you to break up your application's UI       into components, manage component      state, and respond to user events.

   ## Installation
   For installation, install npx creat-react-app <foldername>

   ## Usage
   As a user, I want to be able to view my entire employee directory at once so that I have quick access to their information.

   ## License
   https://img.shields.io/badge/license-<LICENSE_NAME>-blue.svg
   APACHE 2.0

   ## Contributing
   Jamie

   ## Tests
   run test

   ## Questions
   undefined


text:
# Lumin
A test project for Lumin attempting to recreate the products list page.

## Project Setup
You'll need to have Node installed to run this project locally.
* Clone the project.
* run `yarn` from the project root directory.
* run `yarn start` to start the project
* Go to `localhost:3000` on your browser to access the project

## Project stack
This is built with:
* React
* Apollo Client
* React testing library

repository: CodyGbengz/Lumin

repo_name: CodyGbengz/Lumin


text:
# React-Native-Pure-Icon

This is a simple implementation of having custom icons in React-Native.
There are a lot of implementations but most of them use native code. You can even just copy the content into your project.

In this repo, I have introduced a simple way to incorporate your custom fonts in your
React-Native by just using Text Component and some unicode helper.

# Create Custom Fonts

For creating custom fonts, you can use a free tools [icomoon.io](https://icomoon.io). You can import
all of your custom shapes as SVG and it transforms them into `ttf` file. It also
exports a css file which contains a unique unicode assign to each shape, which you
can use it with this module.

# Usage

- install the module from npm, `npm install react-native-pure-icon --save`
- in Android copy font file to `android/app/src/main/assets/fonts`
- in iOS
  - right click on your project in xCode and select `Add files to` and add the font file
  - edit `Info.plist` and add a property `Fonts provided by application` and add the font file
- recompile and build the project
- create a file called `font_types.js` and add the unicode representation of each shape.

```js
export default {
  "Home": "e900",
  "PAINT": "e901",
  "CLUBS": "e902",
  "FILE": "e903"
}
```

> if you are using `icomoon.io`, when you generate font, it will also generate a style.css which contains all of the unicode numbers.

- Using `glypyMapMaker` utility, convert font_types into actual values which can be used by Text component.

```js
import { Icon, glypyMapMaker } from 'react-native-pure-icon';
import fontTypes from './font_types';

const glypy = glypyMapMaker(fontTypes);

//inside your component
<Icon type={glypy.HOME} font="custom_font" style={{ fontSize: 14 }}/>
```

repository: alinz/react-native-pure-icon

gha_language: Objective-C

repo_name: alinz/react-native-pure-icon


text:
---
layout: default
---

# 1998-10-05 - RE: I thought of an initialy regulated industry!... (fwd)

## Header Data

From: me<EMAIL_ADDRESS>To: "Blanc"<EMAIL_ADDRESS>Message Hash: 3daa26e7b08287aa477a9fcd673ded452b890ceeef844c8f4ae901b12daeffe7

Message ID<EMAIL_ADDRESS>Reply To: \<000c01bdf045$4c5b3f60$7e8195cf@blanc\>

UTC Datetime: 1998-10-05 03:43:24 UTC

Raw Date: Mon, 5 Oct 1998 11:43:24 +0800

## Raw message

```
{% raw  %}From: me<EMAIL_ADDRESS>Date: Mon, 5 Oct 1998 11:43:24 +0800
To: "Blanc"<EMAIL_ADDRESS>Subject: RE: I thought of an initialy regulated industry!... (fwd)
In-Reply-To: <000c01bdf045$4c5b3f60$7e8195cf@blanc>
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

At 02:48 AM 10/5/98 -0700, Blanc wrote:
>
>They never have to worry about who has more or less, who is better or
worse, or
>who knows better than anyone what is best for everyone.  It's all been
>pre-established and exists incontrovertibly in their national consumer
database.
>   ..
>Blanc

The above concept is embraced by a vast number of the planets population
and illustrates the ability of rationality to control perception.

----------------------------
"That's entertainment."  - Vlad the Impaler

{% endraw %}
```

## Thread

+ Return to [October 1998](/archive/1998/10)

+ Return to "["Blanc" <blancw@cnw.com>](/authors/blanc_blancw_at_cnw_com_)"
+ Return to "[Mac Norton <mnorton@cavern.uark.edu>](/authors/mac_norton_mnorton_at_cavern_uark_edu_)"
+ Return to "[me <me@myplace.to>](/authors/me_me_at_myplace_to_)"

+ 1998-10-04 (Mon, 5 Oct 1998 04:40:44 +0800) - [RE: I thought of an initialy regulated industry!... (fwd)](/archive/1998/10/9e5b51df92e507edc380318fe00673d0f9053304d124fae9bea0e159b1a57140) - _"Blanc"<EMAIL_ADDRESS>  + 1998-10-05 (Mon, 5 Oct 1998 11:43:24 +0800) - RE: I thought of an initialy regulated industry!... (fwd) - _me<EMAIL_ADDRESS>    + 1998-10-06 (Tue, 6 Oct 1998 10:26:59 +0800) - [RE: I thought of an initialy regulated industry!... (fwd)](/archive/1998/10/256d7c0eb1025d306380c992113ddf1e7336a16e4a931a548f7148190451731b) - _Mac Norton<EMAIL_ADDRESS>


text:
# Ruby on Rails Hello World Sample

This application demonstrates a simple, reusable Ruby web application based on the Rails framework.

The command `rails new <app name>` is used to create the files and folders that make up the structure of a Rails application. They are described in the [Getting Started with Rails][] guide.

## Run the app locally

1. [Install Ruby][]
1. cd into this project's root directory
1. Run `gem install bundler` to install bundler
1. Run `bundle install` to install app dependencies
1. Run `rails server`
1. Access the running app in a browser at <http://localhost:3000>

[Install Ruby]: https://www.ruby-lang.org/en/documentation/installation
[Getting Started with Rails]: http://guides.rubyonrails.org/v3.2.8/getting_started.html#creating-the-blog-application

repository: starterapps-metadata/rubyHelloWorld

gha_language: Ruby

repo_name: starterapps-metadata/rubyHelloWorld


text:
# Write a shell script which counts the number of consonants and vowels in a given sentence
```shell
#!/bin/sh

echo "Enter a sentence: "
read string

vow=$(echo $string | grep -o -i "[aeiou]" | wc --lines)
cons=$(echo $string | grep -o -i "[bcdfghjklmnpqrstvwxyz]" | wc --lines)

echo "The given sentence has $vow vowels, $cons consonants."
```

url: https://raw.githubusercontent.com/nikki-priyaHIT/Shell-Scripting-Programs.md/216f9315b281c35dd83e42894139b6bbac5c1723/6.Write a shell script which counts the number of consonants and vowels in a given sentence.md


text:
<properties
	pageTitle="Azure App Service, Cloud Services and Virtual Machines comparison"
	description="Learn when to use Azure App Service, Cloud Services, and Virtual Machines for hosting web applications."
	services="app-service\web, virtual-machines, cloud-services"
	documentationCenter=""
	authors="tdykstra"
	manager="wpickett"
	editor="jimbe"/>

<tags
	ms.service="app-service-web"
	ms.workload="web"
	ms.tgt_pltfrm="na"
	ms.devlang="na"
	ms.topic="article"
	ms.date="11/19/2015"
	ms.author="tdykstra"/>

# Azure App Service, Cloud Services, and Virtual Machines comparison

## Overview

Azure offers several ways to host web sites: [Azure App Service][], [Cloud Services][], and [Virtual Machines][]. This article helps you understand the options and make the right choice for your web application.

Azure App Service is the best choice for most web apps. Deployment and management are integrated into the platform, sites can scale quickly to handle high traffic loads, and the built-in load balancing and traffic manager provide high availability. You can move existing sites to Azure App Service easily with an [online migration tool](https://www.migratetoazure.net/), use an open-source app from the Web Application Gallery, or create a new site using the framework and tools of your choice. The [WebJobs][] feature makes it easy to add background job processing to your App Service web app.

If you need more control over the web server environment, such as the ability to remote into your server or configure server startup tasks, Azure Cloud Services is typically the best option.

If you have an existing application that would require substantial modifications to run in Azure App Service or Azure Cloud Services, you could choose Azure Virtual Machines in order to simplify migrating to the cloud. However, correctly configuring, securing, and maintaining VMs requires much more time and IT expertise compared to Azure App Service and Cloud Services. If you are considering Azure Virtual Machines, make sure you take into account the ongoing maintenance effort required to patch, update, and manage your VM environment.

The following diagram illustrates the relative degree of control versus ease of use for each of these web hosting options on Azure.

![ChoicesDiagram][ChoicesDiagram]

##Scenarios and recommendations

Here are some common application scenarios with recommendations as to which Azure web hosting option might be most appropriate for each.

- [I need a web front end with background processing and database backend to run business applications integrated with on premise assets.](#onprem)
- [I need a reliable way to host my corporate website that scales well and offers global reach.](#corp)
- [I have an IIS6 application running on Windows Server 2003.](#iis6)
- [I'm a small business owner, and I need an inexpensive way to host my site but with future growth in mind.](#smallbusiness)
- [I'm a web or graphic designer, and I want to design and build web sites for my customers.](#designer)
- [I'm migrating my multi-tier application with a web front-end to the Cloud.](#multitier)
- [My application depends on highly customized Windows or Linux environments and I want to move it to the cloud.](#custom)
- [My site uses open source software, and I want to host it in Azure.](#oss)
- [I have a line-of-business application that needs to connect to the corporate network.](#lob)
- [I want to host a REST API or web service for mobile clients.](#mobile)

###  I need a web front end with background processing and database backend to run business applications integrated with on premise assets.

Azure App Service is a great solution for complex business applications. It lets you develop apps that scale automatically on a load balanced platform, are secured with Active Directory, and connect to your on-premises resources. It makes managing those apps easy through a world-class portal and APIs, and allows you to gain insight into how customers are using them with app insight tools. The [Webjobs][] feature lets you run background processes and tasks as part of your web tier, while hybrid connectivity and [VNET features](../fundamentals-introduction-to-azure.md#networking/) make it easy to connect back to on-premises resources. Azure App Service provides three 9's SLA for web apps and enables you to:

* Run your applications reliably on a self-healing, auto-patching cloud platform.
* Scale automatically across a global network of datacenters.
* Back up and restore for disaster recovery.
* Be ISO, SOC2, and PCI compliant.
* Integrate with Active Directory

###  I need a reliable way to host my corporate website that scales well and offers global reach.

Azure App Service is a great solution for hosting corporate websites. It enables web apps to scale quickly and easily to meet demand across a global network of datacenters. It offers local reach, fault tolerance, and intelligent traffic management. All on a platform that provides world-class management tools, allowing you to gain insight into site health and site traffic quickly and easily. Azure App Service provides three 9's SLA for web apps and enables you to:

* Run your websites reliably on a self-healing, auto-patching cloud platform.
* Scale automatically across a global network of datacenters.
* Back up and restore for disaster recovery.
* Manage logs and traffic with integrated tools.
* Be ISO, SOC2, and PCI compliant.
* Integrate with Active Directory

###  I have an IIS6 application running on Windows Server 2003.

Azure App Service makes it easy to avoid the infrastructure costs associated with migrating older IIS6 applications. Microsoft has created [easy to use migration tools and detailed migration guidance](https://www.movemetowebsites.net/) that enable you to check compatibility and identify any changes that need to be made. Integration with Visual Studio, TFS, and common CMS tools makes it easy to deploy IIS6 applications directly to the cloud. Once deployed, the Azur Portal provides robust management tools that enable you to scale down to manage costs and up to meet demand as necessary. With the migration tool you can:

* Quickly and easily migrate your legacy Windows Server 2003 web application to the cloud.
* Opt to leave your attached SQL database on-premise to create a hybrid application.
* Automatically move your SQL database along with your legacy application.

### I'm a small business owner, and I need an inexpensive way to host my site but with future growth in mind.

Azure App Service is a great solution for this scenario, because you can start using it for free and then add more capabilities when you need them. Each free web app comes with a domain provided by Azure (*your_company*.azurewebsites.net), and the platform includes integrated deployment and management tools as well as an application gallery that make it easy to get started. There are many other services and scaling options that allow the site to evolve with increased user demand. With Azure App Service, you can:

- Begin with the free tier and then scale up as needed.
- Use the Application Gallery to quickly set up popular web applications, such as WordPress.
- Add additional Azure services and features to your application as needed.
- Secure your web app with HTTPS.

###  I'm a web or graphic designer, and I want to design and build websites for my customers

For web developers and designers, Azure App Service integrates easily with a variety of frameworks and tools, includes deployment support for Git and FTP, and offers tight integration with tools and services such as Visual Studio and SQL Database. With App Service, you can:

- Use command-line tools for [automated tasks][scripting].
- Work with popular languages such as [.Net][dotnet], [PHP][], [Node.js][nodejs], and [Python][].
- Select three different scaling levels for scaling up to very high capacities.
- Integrate with other Azure services, such as [SQL Database][sqldatabase], [Service Bus][servicebus] and [Storage][], or partner offerings from the [Azure Store][azurestore], such as MySQL and MongoDB.
- Integrate with tools such as Visual Studio, Git, WebMatrix, WebDeploy, TFS, and FTP.

### I'm migrating my multi-tier application with a web front-end to the Cloud

If you’re running a multi-tier application, such as a web server that connects to a database, Azure App Service is a good option that offers tight integration with Azure SQL Database. And you can use the WebJobs feature for running backend processes.

Choose Cloud Service for one or more of your tiers if you need more control over the server environment, such as the ability to remote into your server or configure server startup tasks.

Choose Virtual Machines for one or more of your tiers if you want to use your own machine image or run server software or services that you can't configure on Cloud Services.

### My application depends on highly customized Windows or Linux environments and I want to move it to the cloud.

If your application requires complex installation or configuration of software and the operating system, Virtual Machines is probably the best solution. With Virtual Machines, you can:

- Use the Virtual Machine gallery to start with an operating system, such as Windows or Linux, and then customize it for your application requirements.
- Create and upload a custom image of an existing on-premises server to run on a virtual machine in Azure.

### My site uses open source software, and I want to host it in Azure

If your open source framework is supported on App Service, the languages and frameworks needed by your application are configured for you automatically. App Service enables you to:

- Use many popular open source languages, such as [.NET][dotnet], [PHP][], [Node.js][nodejs], and [Python][].
- Set up WordPress, Drupal, Umbraco, DNN, and many other third-party web applications.
- Migrate an existing application or create a new one from the Application Gallery.

If your open source framework is not supported on App Service, you can run it on either of the other two Azure web hosting options. With Cloud Services, you use startup tasks to install and configure any required open source software that runs on Windows. With Virtual Machines, you install and configure the software on the machine image, which can be Windows or Linux-based.

### I have a line-of-business application that needs to connect to the corporate network

If you want to create a line-of-business application, your website might require direct access to services or data on the corporate network. This is possible on App Service, Cloud Services, and Virtual Machines using the [Azure Virtual Network service](/services/virtual-network/). On App Service you can use the [VNET integration feature](http://azure.microsoft.com/blog/2014/09/15/azure-websites-virtual-network-integration/), which allows your Azure applications to run as if they were on your corporate network.

### I want to host a REST API or web service for mobile clients

HTTP-based web services enable you to support a wide variety of clients, including mobile clients. Frameworks like ASP.NET Web API integrate with Visual Studio to make it easier to create and consume REST services.  These services are exposed from a web endpoint, so it is possible to use any web hosting technique on Azure to support this scenario. However, App Service is a great choice for hosting REST APIs. With App Service, you can:

- Quickly create a web app to host the HTTP web service in one of Azure’s globally distributed datacenters.
- Migrate existing services or create new ones.
- Achieve SLA for availability with a single instance, or scale out to multiple dedicated machines.
- Use the published site to provide REST APIs to any HTTP clients, including mobile clients.

In addition, Azure App Service has a new preview feature for REST APIs:  API apps.  For more information about API apps, see [What are API apps](../app-service-api/app-service-api-apps-why-best-platform.md).

##Feature Comparison

The following table compares the capabilities of App Service, Cloud Services, and Virtual Machines to help you make the best choice. For current information about the SLA for each option, see [Azure Service Level Agreements](/support/legal/sla/).

Feature|App Service (web apps)|Cloud Services (web roles)|Virtual Machines|Notes
---|---|---|---|---
Near-instant deployment|X|||Deploying an application or an application update to a Cloud Service, or creating a VM, takes several minutes at least; deploying an application to a web app takes seconds.
Scale up to larger machines without redeploy|X|||
Web server instances share content and configuration, which means you don't have to redeploy or reconfigure as you scale.|X|||
Multiple deployment environments (production and staging)|X|X||
Automatic OS update management|X|X||
Seamless platform switching (easily move between 32 bit and 64 bit)|X|X||
Deploy code with GIT, FTP|X||X|
Deploy code with Web Deploy|X||X|Cloud Services supports the use of Web Deploy to deploy updates to individual role instances. However, you can't use it for initial deployment of a role, and if you use Web Deploy for an update you have to deploy separately to each instance of a role. Multiple instances are required in order to qualify for the Cloud Service SLA for production environments.
WebMatrix support|X||X|
Access to services like Service Bus, Storage, SQL Database|X|X|X|
Host web or web services tier of a multi-tier architecture|X|X|X|
Host middle tier of a multi-tier architecture|X|X|X|App Service web apps can easily host a REST API middle tier, and the [WebJobs](http://go.microsoft.com/fwlink/?linkid=390226) feature can host background processing jobs. You can run WebJobs in a dedicated website to achieve independent scalability for the tier. The preview [API apps](../app-service-api/app-service-api-apps-why-best-platform.md) feature provides even more features for hosting REST services.
Integrated MySQL-as-a-service support|X|X|X|Cloud Services can integrate MySQL-as-a-service through ClearDB's offerings, but not as part of the Azure Portal workflow.
Support for ASP.NET, classic ASP, Node.js, PHP, Python|X|X|X|
Scale out to multiple instances without redeploy|X|X|X|Virtual Machines can scale out to multiple instances, but the services running on them must be written to handle this scale-out. You have to configure a load balancer to route requests across the machines, and create an Affinity Group to prevent simultaneous restarts of all instances due to maintenance or hardware failures.
Support for SSL|X|X|X|For App Service web apps, SSL for custom domain names is only supported for Basic and Standard mode. For information about using SSL with web apps, see [Configuring an SSL certificate for an Azure Website](../app-service-web/web-sites-configure-ssl-certificate.md).
Visual Studio integration|X|X|X|
Remote Debugging|X|X|X|
Deploy code with TFS|X|X|X|
Network isolation with [Azure Virtual Network](/services/virtual-network/)|X|X|X|See also [Azure Websites Virtual Network Integration](/blog/2014/09/15/azure-websites-virtual-network-integration/)
Support for [Azure Traffic Manager](/services/traffic-manager/)|X|X|X|
Integrated Endpoint Monitoring|X|X|X|
Remote desktop access to servers||X|X|
Install any custom MSI||X|X|
Ability to define/execute start-up tasks||X|X|
Can listen to ETW events||X|X|

> [AZURE.NOTE]
> If you want to get started with Azure App Service before signing up for an account, go to https://trywebsites.azurewebsites.net, where you can immediately create a short-lived starter app in Azure App Service for free. No credit card required, no commitments.

##  Next Steps

For more information about the three web hosting options, see the following resources:

* [Introducing Azure](../fundamentals-introduction-to-azure.md)
* [Compute Hosting Options Provided by Azure](../fundamentals-application-models.md)

To get started with the option(s) you choose for your application, see the following resources:

* [Azure App Service](/documentation/services/app-service/)
* [Azure Cloud Services](/documentation/services/cloud-services/)
* [Azure Virtual Machines](/documentation/services/virtual-machines/)

  [ChoicesDiagram]: ./media/choose-web-site-cloud-service-vm/Websites_CloudServices_VMs_3.png
  [Azure App Service]: /services/app-service/
  [Cloud Services]: http://go.microsoft.com/fwlink/?LinkId=306052
  [Virtual Machines]: http://go.microsoft.com/fwlink/?LinkID=306053
  [ClearDB]: http://www.cleardb.com/
  [WebJobs]: http://go.microsoft.com/fwlink/?linkid=390226&clcid=0x409
  [Configuring an SSL certificate for an Azure Website]: http://www.windowsazure.com/develop/net/common-tasks/enable-ssl-web-site/
  [azurestore]: http://www.windowsazure.com/gallery/store/
  [scripting]: http://www.windowsazure.com/documentation/scripts/?services=web-sites
  [dotnet]: http://www.windowsazure.com/develop/net/
  [nodejs]: http://www.windowsazure.com/develop/nodejs/
  [PHP]: http://www.windowsazure.com/develop/php/
  [Python]: http://www.windowsazure.com/develop/python/
  [servicebus]: http://www.windowsazure.com/documentation/services/service-bus/
  [sqldatabase]: http://www.windowsazure.com/documentation/services/sql-database/
  [Storage]: http://www.windowsazure.com/documentation/services/storage/

repository: wacncontent/MooncakePortal

repo_name: wacncontent/MooncakePortal


text:
# xrt
Package xrt (XRayTracer) is a python software library for ray tracing and wave propagation in x-ray regime.
It is primarily meant for modeling synchrotron sources, beamlines and beamline elements.

xrt is available as source distribution from https://pypi.python.org/pypi/xrt

See the documentation at http://pythonhosted.org/xrt.

repository: yxrmz/xrt

repo_name: yxrmz/xrt


text:
# Mu.S.I.C.A.
The Musical Speech Isolation and Conversion Automation Project

## Motivation
This project is inspired by my personal interests in language, the topic of translation and my desire to improve my engineering skills. The motivation for this project is to explore speech recognition techniques that are relevant to translation technology and to become familiar with topics including linguistics, feature extraction, and machine learning. This project is structured as part of the Applied Leadership / Learning Experience (ALE) in the Presidents Leadership Class at the University of Colorado in Boulder. For this project, I chose to use musical context for speech recognition because it is less common and introduces unique speech patterns and additional auditory features.

My learning goals for this project can be categorized as broad topic goals, technical skills goals, and experience goals. As mentioned above, my topic goals are to become familiar and gain a base understanding of linguistics, feature extraction and machine learning. I will also explore concepts within the topics of vocal isolation, developing language models, and speech recognition. My technical skills goals are to become proficient in C++ programming, the linux operating system, and to develop skills in signal processing for extracting information from audio data. My experience goals include embracing active learning, pushing my comfort zone, and developing strong reflection habits.

## Phase I
Develop C++ code to read, write, and play audio .wav file

* Libraries/Packages Used:
  * SDL
  * FFmpeg

Develop C++ code to display audio in time domain (waveform) and frequency domain (Spetrogram)

* Libraries/Packages Used:
  * Matplotlib (C++ wrapper)
  * OpenCV

## Phase II (in progress...)
Tested mlpack machine learning library with its dependencies and cmake

* Libraries/Packages Used
  * mlpack
  * Armadillo

CNN to perform vocal isolation

* Libraries/Packages Used:
  * Opencv
  * mlpack
    * armadillo


text:
# Pararchidendron pruinosum (Benth.) I.C.Nielsen SPECIES

#### Status
ACCEPTED

#### According to
The Catalogue of Life, 3rd January 2011

#### Published in
Bull. Mus. Natl. Hist. Nat. , B, Adansonia 5:328. 1984 ("1983")

#### Original name
null

### Remarks
null

repository: mdoering/backbone

repo_name: mdoering/backbone