Harold Dost hdost

## scribing.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                hdost
                / scribing.md
            
            
              Created
              June 19, 2023 10:08
                — forked from Manishearth/scribing.md
            
              
                Tips for effective scribing from the W3C
              
          
    W3C teams have a tendency of scribing everytihng they do, and they're pretty effective at it.
This is not due to individuals being great at scribing: the system is set up such that even new group members will be able to scribe reasonably effectively. It's also set up such that new group members will get that opportunity soon enough.
The main thing is that "anyone can scribe": most teams avoid a designated scribe and instead designate a scribe per meeting and discussion. This works with some of the following additional structure:

Nobody is expected to scribe and take minutes simultaneously. if the scribe wants to say something, someone else will take over. You pre-agree to who that person will be before the scribe actually says something

Before the discussion starts, scribe asks for an alternate


During the discussion, scribe may use chat to say "anyone want to scribe for me when I talk in a bit" and then call out that person before speaking.


## .gitmessage
# <type>(<scope>): <subject>
#
# <body>
#
# <footer>
#
# ** TYPES **
# feat (new feature)
# fix (bug fix)
# docs (changes to documentation)

## .gitconfig
[push]
	default = current
[pull]
	rebase = true
[branch]
	autosetuprebase = always
[commit]
	template = ~/.gitmessage
[color]
	ui = true

## keybase.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                hdost
                / keybase.md
            
            
              Created
              December 5, 2014 16:29
            
          
    Keybase proof

I hereby claim:

I am hdost on github.
I am hd3 (https://keybase.io/hd3) on keybase.
I have a public key whose fingerprint is 9914 1F76 82DF 41D9 2BBA  B3B4 7AEA AACF 46BE E1CB

To claim this, I am signing this object:

  
## String+Hashing.swift
import Foundation

enum HMACAlgorithm {
    case MD5, SHA1, SHA224, SHA256, SHA384, SHA512

    func toCCEnum() -> CCHmacAlgorithm {
        var result: Int = 0
        switch self {
        case .MD5:
            result = kCCHmacAlgMD5

## gist:03a41173613cd4b6fc10
"""
This script starts an edit session, creates two different JMS Servers,
targets the jms servers to the server WLST is connected to and creates
jms topics, jms queues and jms templates in a JMS System module. The
jms queues and topics are targeted using sub-deployments.
"""

import sys
from java.lang import System
	# <type>(<scope>): <subject>
	#
	# <body>
	#
	# <footer>
	#
	# TYPES
	# feat (new feature)
	# fix (bug fix)
	# docs (changes to documentation)
	[push]
	default = current
	[pull]
	rebase = true
	[branch]
	autosetuprebase = always
	[commit]
	template = ~/.gitmessage
	[color]
	ui = true
	import Foundation

	enum HMACAlgorithm {
	case MD5, SHA1, SHA224, SHA256, SHA384, SHA512

	func toCCEnum() -> CCHmacAlgorithm {
	var result: Int = 0
	switch self {
	case .MD5:
	result = kCCHmacAlgMD5
	"""
	This script starts an edit session, creates two different JMS Servers,
	targets the jms servers to the server WLST is connected to and creates
	jms topics, jms queues and jms templates in a JMS System module. The
	jms queues and topics are targeted using sub-deployments.
	"""

	import sys
	from java.lang import System