30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
|
---
|
||
|
|
title: "Pixelfed team member"
|
||
|
|
summary: "Turning a one-person project into an organized effort."
|
||
|
|
date: "2019-01-01"
|
||
|
|
tags: ["pixelfed", "project management", "product management", "github issues", "documentation"]
|
||
|
|
---
|
||
|
|
|
||
|
|
## Overview
|
||
|
|
|
||
|
|
## Being invited to the team
|
||
|
|
|
||
|
|
I made that masterpost issue with every bug and missing feature from the initial beta release, with a big checklist and organized into areas of interest.
|
||
|
|
|
||
|
|
dansup saw that and decided to invite me to join the pixelfed organization on github.
|
||
|
|
|
||
|
|
## Responsibilities
|
||
|
|
|
||
|
|
### Issue triage
|
||
|
|
|
||
|
|
I implemented the current issue tagging system.
|
||
|
|
|
||
|
|
Issues have tags by area, Milestone by rough version target, Project by which feature they pertain to
|
||
|
|
|
||
|
|
### Design consultancy
|
||
|
|
|
||
|
|
dansup does a lot of experimenting with building out mock features, and I'm there to tell him which ones are good ideas and which ones are bad ideas.
|
||
|
|
|
||
|
|
### Release planning
|
||
|
|
|
||
|
|
0.x betas each usually focus on one feature and related development around it. When the focus changes, a new 0.x beta will be tagged. We have a few more betas left, for circles, and for polish. If it weren't for me, dansup would have tagged 1.0 already and media attention would have been lackluster.
|