New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub Admin #16

Open
cbeams opened this Issue Sep 4, 2017 · 13 comments

Comments

Projects
None yet
4 participants
@cbeams
Member

cbeams commented Sep 4, 2017

Docs: WIP at bisq-network/bisq-docs#64
Team: @bisq-network/github-admins
Primary owner: @ManfredKarrer

Note: @cbeams and @ManfredKarrer use Owner-privileged service accounts @bisq-github-admin-1 and @bisq-github-admin-2 respectively to perform GitHub administration duties.

@cbeams cbeams added the role:op label Sep 4, 2017

cbeams added a commit that referenced this issue Jan 2, 2018

cbeams added a commit that referenced this issue Jan 2, 2018

cbeams added a commit that referenced this issue Jan 2, 2018

@cbeams cbeams changed the title from GitHub organization operator to GitHub Admin Jan 2, 2018

@cbeams cbeams added role and removed role:op labels Jan 3, 2018

@cbeams

This comment has been minimized.

Member

cbeams commented Jan 4, 2018

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 cbeams referenced this issue Jan 4, 2018

Closed

For December 2017 #26

@cbeams

This comment has been minimized.

Member

cbeams commented Feb 1, 2018

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 cbeams referenced this issue Feb 1, 2018

Closed

For January 2018 #35

@cbeams

This comment has been minimized.

Member

cbeams commented Mar 1, 2018

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 cbeams referenced this issue Mar 1, 2018

Closed

For February 2018 #40

1 of 1 task complete
@cbeams

This comment has been minimized.

Member

cbeams commented Apr 4, 2018

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 cbeams referenced this issue Apr 4, 2018

Closed

For March 2018 #57

1 of 1 task complete
@cbeams

This comment has been minimized.

Member

cbeams commented May 3, 2018

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 cbeams referenced this issue May 3, 2018

Closed

For April 2018 #68

1 of 6 tasks complete

@cbeams cbeams removed the a:role label May 4, 2018

@cbeams

This comment has been minimized.

Member

cbeams commented Jun 1, 2018

2018.05 report

/cc bisq-network/compensation#74

@cbeams

This comment has been minimized.

Member

cbeams commented Jun 1, 2018

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.

@cbeams cbeams referenced this issue Jun 1, 2018

Closed

For May 2018 #74

0 of 5 tasks complete
@cbeams

This comment has been minimized.

Member

cbeams commented Jul 31, 2018

2018.07 report

  • I realized well after the fact of last month's voting that I forgot to leave a 2018.06 report. Oops.
  • Serviced requests to invite several members to the @bisq-network org
  • Monitored the #github channel, kept up on GitHub news and features

BSQ requested: 50

/cc bisq-network/compensation#101

@cbeams

This comment has been minimized.

Member

cbeams commented Aug 31, 2018

2018.08 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#114

@cbeams

This comment has been minimized.

Member

cbeams commented Sep 30, 2018

2018.09 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#139

@cbeams

This comment has been minimized.

Member

cbeams commented Oct 31, 2018

2018.10 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#160

@cbeams cbeams referenced this issue Oct 31, 2018

Closed

For October 2018 #160

@cbeams

This comment has been minimized.

Member

cbeams commented Nov 30, 2018

2018.11 report

Installed and authorized TestQuality GitHub integration at @devinbileck's request.

BSQ requested: 25

/cc bisq-network/compensation#179

@cbeams

This comment has been minimized.

Member

cbeams commented Dec 6, 2018

Per #1 (comment), I'll be away for the next ~2 months. I've made @ManfredKarrer the primary owner of this role in the meantime; please direct any GitHub administration requests to him.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment