pmbaumgartner

#cloud-config
package_upgrade: true

ssh_authorized_keys:
  - <your key>

packages:
  - apt-transport-https
  - ca-certificates
  - curl

Morendil

The citations game: Pressman Ratios

Rubric: Software Engineering : Factual Claims : Defect Cost Increase : Pressman Ratios

Context

See previous note on the IBM Systems Sciences Institute

Origins

broglep-work

AWSTemplateFormatVersion: 2010-09-09
Description: 'Registers ecs tasks to a second target group'
Parameters:
  ClusterArn:
    Description: 'ANR of cluster the service resides in'
    Type: String
  ServiceName:
    Description: 'Name of the service to register'
    Type: String
  ContainerName:

caseywatts

short url: caseywatts.com/graphviz

Graphviz is like markdown, for diagrams.

It's a tool that can transform text input into a "directed graph" output, which is nodes pointing to other nodes. You can use it for architecture diagrams, DB diagrams, documentation for users, etc.

You'll want to use a tool with a two-pane layout - the left side is the source text, the right side is the image output.

• For just you working on it, use (shown above; it has more features)

sators

<?php

/********* CONFIG ********/
$clusterEndpoint = "";
$clusterPort = 3306;
$clusterRegion = "us-east-1";
$dbUsername = "";
$dbDatabase = "";
/*************************/

johnscancella

# new 4.0 format.
vcl 4.0;

import directors;

backend app1 {
    .host = "ndnpappvlp01.loc.gov";
    .probe = {
        .url = "/";
        .interval = 60s;

azaroth42

Discovery Support Technical Specifications Group Charter

Introduction

Interoperable resources are only useful if they can be found. This has been well-recognized since the early days of the IIIF community, and more recently it has become clear that a concerted effort to standardize patterns that will facilitate discovery, harvesting and synchronization, indexing, and importing of IIIF resources is required.

This group will create specifications that improve the discovery process for IIIF resources, with a focus on leveraging existing techniques and tools, and promoting widespread adoption within the community. It will assist with and steer the implementation of community infrastructure, such as a registry of adopters, validators for the implementations, and transformation tools to generate the required data from existing systems and APIs.

If successful, the work will enable the collaborative development of global or thematic registries, search engines and portal applications that allow developers a

acdha

Traceback (most recent call last):
  File "/Users/cadams/.virtualenvs/wdl/bin/django-admin", line 11, in <module>
    sys.exit(execute_from_command_line())
  File "/Users/cadams/.virtualenvs/wdl/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line
    utility.execute()
  File "/Users/cadams/.virtualenvs/wdl/lib/python2.7/site-packages/django/core/management/__init__.py", line 328, in execute
    django.setup()
  File "/Users/cadams/.virtualenvs/wdl/lib/python2.7/site-packages/django/__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/Users/cadams/.virtualenvs/wdl/lib/python2.7/site-packages/django/apps/registry.py", line 85, in populate

phill-tornroth

"""
 This is the basis for an elasticsearch 1.x backend I've cobbled together and am continuing 
 to refine and test for use. It's based on haystack master's version as of:
    - https://github.com/toastdriven/django-haystack/blob/cbb72b3253404ba21e20860f620774f7b7b691d0/haystack/backends/elasticsearch_backend.py
 But with @HonzaKral and @davedash's work to make the backend behave more like an ES user would expect with regard to doc types:
    - https://github.com/toastdriven/django-haystack/pull/921

 I also made a number of changes:
    - I fixed bugs that I found in #921 (mostly related to mapping synchronization issues), 
      all of which I wrote up as comments on #921

jmcnamara

##############################################################################
#
# Simple Python program to benchmark several Python Excel writing modules.
#
# python bench_excel_writers.py [num_rows] [num_cols]
#
#

import sys
from time import clock