-
Notifications
You must be signed in to change notification settings - Fork 16
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
Comments
2017.12 report
There were no major changes or incidents otherwise. |
2018.01 reportWe 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. |
2018.02 reportNot much to report this month. GitHub published a new |
2018.03 reportAs discussed in last month's report, I did swap out all Atomist integrations with the new 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 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. |
2018.04 report@cbeams and @Emzy began logging @bisq-network GitHub organization notifications to [email protected]. See bisq-network/lists#5. |
2018.05 report
|
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. |
Cycle 34 report
|
Cycle 35 report
|
Cycle 36 report
|
Cycle 37 report
|
Cycle 38 report
|
Cycle 39 report
|
Cycle 40 reportNothing to report. |
Cycle 41 reportAdded @gabernard to the Bisq organization making him GitHub Admin after bisq-network/proposals#382 was approved and Bond was locked successfully. |
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! |
Cycle 42 reportAdded @alejandrogarcia83 to the Bisq organization making him Bisq maintainer after bisq-network/proposals#394 was approved and Bond was locked successfully. |
Cycle 43 reportAdded @w0000000t to the Bisq organization. |
Cycle 44 reportNothing 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. |
Cycle 41 reportNothing to report. |
Cycle 42 reportNothing to report. |
Cycle 43 report
|
Cycle 44 reportRemoved @ripcurlx as Github Owner |
Cycle 45 report
|
Cycle 46 report
|
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.
The text was updated successfully, but these errors were encountered: