₿atch₡oin
🦡

NFTs

Users who produce batch specs can mint their own NFTs protecting their property.
Users with valuable batch specs get ₿atch₡oin, a proof of stake based cryptocurrency that can be used to purchase a Team plan.

Things Cornelius Snarlington, Business Deer wants

Blood
The ability to track multiple PRs and issues without spreadsheets
Cufflinks with built in laser cutters
Integration between batch changes and the evilest tool in existence: JIRA
Bigger antlers

Changeset tracking

We have some of this already
What we don't have is a good onboarding path
Cornelius gets stabby when he has to write YAML


importChangesets:
	- repository: github.com/sourcegraph/sourcegraph
	  externalIDs: [11075, "12139", 16686, 16685, 16682]

Discussion and activity tracking

As a Sourcegraph user
Cornelius wants to determine which PRs aren't being actioned
so that
he can determine who to defenestrate

Finally, you may remember that Cornelius, being a psychopathic business deer, uses JIRA. In order to keep JIRA tickets up to date with the state of batch changes, preferably without having to build out the full workflow of how we might interact with issue trackers. Therefore we should build out the minimal webhooks required to be able to build external syncing tools that can update on the fly: initially, I'd argue we should scope this to just global webhooks configured by a site admin, but eventually we could extend this to allow users to like and subscribe to batch changes that operate on specific repos. I haven't put a lot of effort into defining the webhooks, but I think a reasonable starting point would be for us to think through any time we mutate a batch change or changeset.

features

Browser extension support for creating import-only batch changes
Last activity tracking on changesets
Webhooks for batch changes and changesets
BLOOD FOR THE BLOOD GOD