GitHub Admin

[cbeams]

Docs: WIP at bisq-network/bisq-docs#64 (should move to https://bisq.wiki/GitHub_Admin)
Team: @bisq-network/github-admins

Note: @ripcurlx uses the Owner-privileged service account @bisq-github-admin-3 to perform GitHub administration duties.

[cbeams]

2017.12 report

• Experimented with GitHub's new 'team discussions' feature, and discovered that it's not ready for primetime / suitable for our uses under the Bisq DAO. Perhaps that will change.
• Performed usual admin activities related to creating new repositories, assigning access rights, etc.
• Migrated from having bisq-network/github act as the 'root node' for our org and all its repositories (i.e. where our .mrconfig is stored) to having this managed under bisq-network/dao.

There were no major changes or incidents otherwise.

/cc bisq-network/compensation#26

[cbeams]

2018.01 report

We started using Atomist this month as a replacement for Slack's built-in GitHub integration. You've probably seen the @atomist bot in most of our channels reporting commits and comments on GitHub issues and pull requests, etc. This is just the beginning of what Atomist can do, though. It's really all about automating the process of development itself (or automating everything about development that can be automated anyway). People can read up about it elsewhere, but I'm excited about how Atomist can take our already pretty serious GitHub-fu to the next level and make a lot of the stuff I do manually happen automatically.

Note that Atomist is also built by a lot of my old friends and colleagues from the Spring team, so I'm extra excited about it, as they have a tendency to build excellent, useful things. I've already had some initial chats with them about what we're up to with the Bisq DAO and how Atomist might be able to help. We'll see where it goes.

Otherwise, there's not much to report. Just basic day-to-day GitHub admin activities like inviting new contributors to the @bisq-network org, managing team memberships, creating repositories, etc.

/cc bisq-network/compensation#35

[cbeams]

2018.02 report

Not much to report this month.

GitHub published a new /github Slack app that looks promising. I'll be replacing our old Slack GitHub integration over the next month, and possibly swapping out Atomist for the new native GitHub app if the latter seems like a complete replacement for what we're using Atomist for now.

/cc bisq-network/compensation#40

[cbeams]

2018.03 report

As discussed in last month's report, I did swap out all Atomist integrations with the new /github Slack app, and while it has some rough edges, it's basically meeting our needs.

I created the new https://github.com/bisq-network/bisq repository this month, as a new "root level" repository for managing all other repositories in the @bisq-network organization. See the readme in that repository for details. Previously, the bisq-network/dao repository had been playing this role, but that arrangement was a bit awkward. Now the dao repository is responsible for managing only non-code (i.e. dao-specific) repositories like bisq-network/roles, bisq-network/dns, etc.

I've also just updated the assignees and description of this role issue to reflect that I'm the 'primary' GitHub Admin, and that @ManfredKarrer is the 'secondary'. Both of us have Owner rights, and can technically service any request, but I am the one who is on point; Manfred plays a passive, "backup" role.

/cc bisq-network/compensation#57

[cbeams]

2018.04 report

@cbeams and @Emzy began logging @bisq-network GitHub organization notifications to github@lists.bisq.network. See bisq-network/lists#5.

/cc bisq-network/compensation#68

[cbeams]

2018.05 report

• @alfsbs created the https://github.com/bisq-network/payment-methods repository, and has migrated existing issues from bisq-desktop.
• @cbeams created the @bisq-network/design-contributors team
• @cbeams created the @bisq-network/docs-contributors team
• 2 members were added to the @bisq-network org and 2 members left
• @cbeams has begun drafting a GitHub doc at [WIP] Produce 'GitHub' doc bisq-docs#64

/cc bisq-network/compensation#74

[cbeams]

2018.05 report (cont)

I forgot to mention above that GitHub released a new, long-awaited feature this month, that allows users to see the revision history of issue descriptions and comments. As I wrote in this tweet, this is important for the Bisq DAO, where certain kinds of issues, like those in https://github.com/bisq-network/proposals are quite important, and where changes to them can really matter.

See https://blog.github.com/changelog/2018-05-24-comment-edit-history/ for details.

[ripcurlx]

Cycle 34 report

• Had to increase the Git LFS account plan again,again to 3,000 GB to match our consumed bandwidth (2,600 GB consumed already) > 300 USD/year ATM.
• Forked https://github.com/bisq-network/slate for Bisq API documentation
• Gave @pazza83 permissions to manage project repository

/cc bisq-network/compensation#1041

[ripcurlx]

Cycle 35 report

• Had to increase the Git LFS account plan again,again,again to 3,600 GB to match our consumed bandwidth (3,118 GB consumed already) > 360 USD/year ATM. Our data will reset in 21 days, so hopefully that will be our yearly plan from now on.
• Gave @UX-P permissions to manage the design repository
• Added @alvasw and @alkum as Triage maintainer for the bisq2 repository

/cc bisq-network/compensation#1060

[ripcurlx]

Cycle 36 report

• Luckily this time no new data package necessary as we started a new accounting year. So €360 were payed for GitHub.
• Gave @devinbileck temporary admin permissions for https://github.com/bisq-network/bisqremote_iOS and https://github.com/bisq-network/bisqremote_Android
• Added https://github.com/bisq-network/bisq-api-reference repository
• Added @ghubstan as maintainer to https://github.com/bisq-network/bisq-api-reference

/cc bisq-network/compensation#1088

[ripcurlx]

Cycle 37 report

• Forked https://github.com/bisq-network/jsocks and https://github.com/bisq-network/java-opentimestamps on request from @chimp1984

/cc bisq-network/compensation#1088

[ripcurlx]

Cycle 38 report

• Created https://github.com/bisq-network/bisq-pricenode based on request from @ghubstan
• Created https://github.com/bisq-network/bisq-monitor based on request from @ghubstan
• Created https://github.com/bisq-network/bisq-gradle based on request from @ghubstan
• Created https://github.com/bisq-network/bisq-inventory based on request from @ghubstan

/cc bisq-network/compensation#1154

[ripcurlx]

Cycle 39 report

• Created https://github.com/bisq-network/bisq-daonode based on request from @ghubstan
• Created https://github.com/bisq-network/bisq-relay based on request from @ghubstan

/cc bisq-network/compensation#1154

[ripcurlx]

Cycle 40 report

Nothing to report.

/cc bisq-network/compensation#1154

[ripcurlx]

Cycle 41 report

Added @gabernard to the Bisq organization making him GitHub Admin after bisq-network/proposals#382 was approved and Bond was locked successfully.

/cc bisq-network/compensation#1184

[cbeams]

I've assigned @gabernard to this role, and I've also removed myself from it. I've unlocked my associated bond, and have asked @ripcurlx to remove my Owner role from the GitHub org. This change has been planned for a while, and now's the time to do it with @gabernard taking it on. Welcome @gabernard!

[ripcurlx]

Cycle 42 report

Added @alejandrogarcia83 to the Bisq organization making him Bisq maintainer after bisq-network/proposals#394 was approved and Bond was locked successfully.
Removed @cbeams as Github Owner. I've also started to unlock my bond for GitHub admin and will request @gabernard to remove me from this role as soon as hand over is done.

/cc bisq-network/compensation#1197

[ripcurlx]

Cycle 43 report

Added @w0000000t to the Bisq organization.

/cc bisq-network/compensation#1237

[ripcurlx]

Cycle 44 report

Nothing to report. As it seems that @gabernard can take everything over from now on, I'll request him to remove my GitHub Admin account as GitHub owner.

/cc bisq-network/compensation#1237

[gabernard]

Cycle 41 report

Nothing to report.

/cc bisq-network/compensation#1274

[gabernard]

Cycle 42 report

Nothing to report.

/cc bisq-network/compensation#1274

[gabernard]

Cycle 43 report

• Added @alejandrogarcia83 as maintainer to https://github.com/bisq-network/bisq-website
• Added @alejandrogarcia83 as maintainer to https://github.com/bisq-network/bitcoinj

/cc bisq-network/compensation#1274

[gabernard]

Cycle 44 report

Removed @ripcurlx as Github Owner

/cc bisq-network/compensation#1274

[gabernard]

Cycle 45 report

• Added @alejandrogarcia83 as maintainer to https://github.com/bisq-network/netlayer

/cc bisq-network/compensation#1274

[gabernard]

Cycle 46 report

• Added https://github.com/bisq-network/bisq2-web-ui repository based on request from @salokiam
• Added @salokiam as maintainer to https://github.com/bisq-network/bisq2-web-ui

/cc bisq-network/compensation#1274