Ferenc Erki ferki

Aspect	Open Source	Enterprise
Governance	Maintainers, community consensus, meritocracy-based influence	Empowered teams, lightweight oversight, guardrails over gates
Code Review	Public PRs, async reviews from global contributors, emphasis on transparency	Small PRs, fast feedback loops, pair/mob programming as alternative
Documentation	README-driven, contributor guides essential, public wikis	Living documentation, lightweight ADRs, docs as code
Branching Strategy	Fork-and-PR model, contributors work in personal forks	Trunk-based development, short-lived feature branches (< 1 day)
Communication	Public channels (GitHub issues, Discord, mailing lists)	Co-located teams (in space /and or time), minimal ceremony
Release Cadence	Varies widely, often semver-based, maintainer-driven	Continuous delivery, deploy on merge, feature flags for controlled rollout
Testing	CI on PRs, community-contributed

title	A Blog Post
published	2021-03-21

This will appear in the blog because it has a published field in the frontmatter.

Mutt + isync multiple accounts Unfinished

This is the setup that I use for mutt, I have two google domain account (read as gmail) and an institution where I work and study account. This means I have two gmail accounts and one outlook 365 account that i want to sync and read via mutt.

I want to store all my email locally as I travel a lot and will be in countries without easy internet access. For this I use mbsync (iSync). As it can handle multiple account types easily and efficently.

The setup works this way

[Remote Mail Servers] <= mbsync => [Local Mail Folders]

Bash Shortcuts

Moving

command	description
ctrl + a	Goto BEGINNING of command line

Next Steps

Measure time spend on index, flush, refresh, merge, query, etc. (TD - done)
Take hot threads snapshots under read+write, read-only, write-only (TD - done)
Adjust refresh time to 10s (from 1s) and see how load changes (TD)
Measure time of a rolling restart doing disable_flush and disable_recovery (TD)
Specify routing on query -- make it choose same node for each shard each time (MD)
GC new generation size (TD)
Warmers

measure before/after of client query time with and without warmers (MD)

Tiny Content Framework

About the project

This is a tiny content strategy framework focused on goals, messages, and branding. This is not a checklist. Use what you need and scrap the rest. Rewrite it or add to it. These topics should help you get to the bottom of things with clients and other people you work with.

Give me feedback on Twitter (@nicoleslaw) or by email (nicole@nicolefenton.com).

	Here are a few questions that will tee us up for a good conversation:

	- Can you tell me about your project in a few sentences?
	- What’s the timeframe? Does a certain event depend on this project launching?
	- What are you looking for from us? Do you want us to design, build, and launch the whole site? Or do you have developers or other partners lined up and only need us for design?
	- Have you already started on any part of the project? Do you have existing work? A new logo? Some rough designs or ideas for the site?
	- How large is your team? What are the roles you envision on your end?
	- How did you hear about our work? What specifically interests you about it? Any projects that you’re keen on?
	- How much money have you set aside for this project?
	- Are you talking to others about this project? Might we ask how many? What do you like about their work?

	#!/bin/bash

	# Runs the specified command (provided by the first argument) in all tmux panes
	# in every window. If an application is currently running in a given pane
	# (e.g., vim), it is suspended and then resumed so the command can be run.
	all-panes()
	{
	all-panes-bg_ "$1" &
	}