Skip to content

Instantly share code, notes, and snippets.

View emmairwin's full-sized avatar
🏠
Working from home

Emma emmairwin

🏠
Working from home
View GitHub Profile
@emmairwin
emmairwin / gist:5208680
Last active December 15, 2015 05:20 — forked from GenOpen/gist:5207927
<!DOCTYPE html><html><head>
<title>My Music - Credits</title>
</head>
<body>
<p>Credits Page</p>
</body></html>
<!DOCTYPE html>
<html lang="en">
<head>
<base href="https://popcorn.webmaker.org/templates/basic/">
<title>Popcorn Maker</title>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="style.css">
@emmairwin
emmairwin / gist:9201099
Created February 25, 2014 01:50
Testing
<?php
//
// This module, taxonomy_menu_patch, should have a dependency of `tm_custom_paths`
function taxonomy_menu_patch_module_implements_alter(&$implementations, $hook) {
if ('form_taxonomy_form_vocabulary_alter' == $hook) {
// We need to ensure that taxonomy_menu_patch is that last one to be called
// as this way we can ensure that 'tm_custom_paths_vocabulary_validate'
// callback is removed from the $form's #validate callback stack.
$group = $implementations['taxonomy_menu_patch'];
function MYMOD_drush_command(){
$items = array();
$items['loc-update'] = array(
'description' => dt('Run Location update'),
'arguments' => array(
'arg1' => dt('Optional User ID'),
),
'examples' => array(
'Standard example' => 'drush loc-update',
'Argument example' => 'drush loc-update 5',
## Introduction
If I you can see this from inside a coursein the box, then remote include of a github file works.
FX OS - As BuddyUp is an on device help app, users will be able to quickly get device specific answers to their questions
SUMO - BuddyUp leverages the SUMO community, but will also add additional interest in SUMO and possibly result in onboarding more SUMO contributors to answer questions
As far as how it provides strategic advantage:
FX OS - We can more quickly identify device specific issues and rectify them. The app is now readily available in the Marketplace and can be leveraged by anyone that has a FX OS device.
SUMO - Enhances our overall support story by building a good story on the FX OS support side.
An overall strategic advantage of the whole BuddyUp pilot is:
Darwin 14.5.0
npm ERR! argv "node" "/usr/local/bin/npm" "run" "only-once"
npm ERR! node v0.12.7
npm ERR! npm v2.14.4
npm ERR! code ELIFECYCLE
npm ERR! freecodecamp@0.1.0 only-once: `npm run create-rev && echo '
npm ERR!
npm ERR! seeding database
npm ERR!
npm ERR! ' && node seed && node seed/nonprofits && echo`
Traceback (most recent call last):
File "manage.py", line 8, in <module>
from django.core.management import execute_from_command_line
File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 10, in <module>
from django.apps import apps
File "/usr/local/lib/python2.7/site-packages/django/apps/__init__.py", line 1, in <module>
from .config import AppConfig
File "/usr/local/lib/python2.7/site-packages/django/apps/config.py", line 5, in <module>
from django.utils._os import upath
File "/usr/local/lib/python2.7/site-packages/django/utils/_os.py", line 5, in <module>
Right now what is most important is agreeing on what we are building, how we'll measure it, with standards that
helps set and manage expectations.
There are currently 2 ways to self-select into contribution in the toolkit
1) Github tasks (link: https://github.com/emmairwin/leadership_toolkit/issues/3#boards?repos=70379420) - If there is a task with pipeline 'Review Requested', then I am hoping you will review the document and give feedback(in the document).
2) Self-select / 'Co-own a Task'. If any tasks speaks to you specifically ie: I want to invest on Measurement & Data, or I want to help
help a robust set of criteria by which we measure the quality of resources, and help implement it.
Ping me directly, and we can go through the possiblities. T=
@emmairwin
emmairwin / gist:ee9eddc9fd992685f2928cf92403cce6
Created August 20, 2019 17:49
Brian Proffitt: Open Sourcing for a Living: Determining Organizational Affiliations
"I often ask people at Red Hat is the piece of data you are most interested in?
90% of the time, the answer is, who is working for who, and where people are coming from. This is the #1 thing people want to know.
We have a problem with organisational diversity at Red Hat. We have found historically, this is not a good thing. 1) no one will want to come in and be part of our organisation. Perception is that people not part of Red Hat are not welcome (which is not true)
2)The second is the most successful projects are those who had a lot of diversity. For example when we were part of the larger openstack community, and we are just one part of that. We were also part of Kubernetes community, and we see huge innovation there.
To give you an example of what we do right - everything is upstream. I.e. Fedora, because of the way we work, that is one of our most important upstream projects.
What most people don’t realise, only 22% of active contributors in Fedora, are working for Red Hat. We loved when we h