Skip to content
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

Closed
cbeams opened this issue Sep 4, 2017 · 74 comments
Closed

GitHub Admin #16

cbeams opened this issue Sep 4, 2017 · 74 comments
Assignees
Labels
team:admin https://bisq.wiki/Admin_Team

Comments

@cbeams
Copy link
Member

cbeams commented Sep 4, 2017

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 cbeams added the role:op label Sep 4, 2017
cbeams added a commit that referenced this issue Jan 2, 2018
@cbeams cbeams changed the title GitHub organization operator GitHub Admin Jan 2, 2018
@cbeams cbeams added role and removed role:op labels Jan 3, 2018
@cbeams
Copy link
Member Author

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
Copy link
Member Author

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
Copy link
Member Author

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
Copy link
Member Author

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
Copy link
Member Author

cbeams commented May 3, 2018

2018.04 report

@cbeams and @Emzy began logging @bisq-network GitHub organization notifications to [email protected]. See bisq-network/lists#5.

/cc bisq-network/compensation#68

@cbeams
Copy link
Member Author

cbeams commented Jun 1, 2018

2018.05 report

/cc bisq-network/compensation#74

@cbeams
Copy link
Member Author

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.

@ripcurlx
Copy link
Contributor

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
Copy link
Contributor

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
Copy link
Contributor

ripcurlx commented Jun 1, 2022

Cycle 36 report

/cc bisq-network/compensation#1088

@ripcurlx
Copy link
Contributor

@ripcurlx
Copy link
Contributor

ripcurlx commented Sep 9, 2022

@ripcurlx
Copy link
Contributor

ripcurlx commented Sep 9, 2022

Cycle 39 report

/cc bisq-network/compensation#1154

@ripcurlx
Copy link
Contributor

ripcurlx commented Oct 4, 2022

Cycle 40 report

Nothing to report.

/cc bisq-network/compensation#1154

@ripcurlx
Copy link
Contributor

ripcurlx commented Nov 4, 2022

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 cbeams assigned gabernard and unassigned cbeams Nov 8, 2022
@cbeams
Copy link
Member Author

cbeams commented Nov 8, 2022

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
Copy link
Contributor

ripcurlx commented Dec 5, 2022

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
Copy link
Contributor

ripcurlx commented Feb 8, 2023

Cycle 43 report

Added @w0000000t to the Bisq organization.

/cc bisq-network/compensation#1237

@ripcurlx
Copy link
Contributor

ripcurlx commented Feb 8, 2023

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
Copy link

Cycle 41 report

Nothing to report.

/cc bisq-network/compensation#1274

@gabernard
Copy link

Cycle 42 report

Nothing to report.

/cc bisq-network/compensation#1274

@gabernard
Copy link

@gabernard
Copy link

Cycle 44 report

Removed @ripcurlx as Github Owner

/cc bisq-network/compensation#1274

@gabernard
Copy link

@gabernard
Copy link

gabernard commented Apr 10, 2023

Cycle 46 report

/cc bisq-network/compensation#1274

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team:admin https://bisq.wiki/Admin_Team
Projects
None yet
Development

No branches or pull requests

8 participants