HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ethereum
pm
Python2017–2022
ethereum / pm

pm

Project Management: Meeting notes and agenda items

7Distinct people
8Mentions
0Explicit recommenders
1.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Project Management: Meeting notes and agenda items

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year8 dated mentions

Observed mentions: 2017-10-12 14:18:41 UTC to 2022-09-15 04:06:31 UTC.

0123452017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC211
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC514

What Hacker News says

8 sources

Ask HN: Is Ethereum's Merge one of the biggest successes in Open Source?

It certainly seems it will be remembered as a major success story for open p2p protocols on the global Internet of our time. A great multitude of developers and enthusiasts belonging or contributing to diverse teams spread across the world: developing, debating, and collaborating for years to arrive at the big event. And it's all been done very much in the public view: https://weekinethereumnews.com/ https://hackmd.io/@benjaminion/eth2_news https://github.com/ethereum/pm https://www.youtube.com/c/EthereumFoundation/videos Consensus Clients: https://github.com/sigp/lighthouse#readme https://github.com/ChainSafe/lodestar#readme https://github.com/status-im/nimbus-eth2#readme https://github.com/prysmaticlabs/prysm#readme https://github.com/ConsenSys/teku#readme Execution Clients: https://github.com/akula-bft/akula#readme https://github.com/h
Read the rest
yperledger/besu#readme https://github.com/ledgerwatch/erigon#readme https://github.com/ethereum/go-ethereum#readme https://github.com/NethermindEth/nethermind#readme https://github.com/status-im/nimbus-eth1#readme And there are many Open Source specs and libraries underlying those clients that have also involved non-trivial development and collaboration, e.g. libp2p.
22 points · Open discussion
There is still no date but it's getting really close. You can track the progress here: https://github.com/ethereum/pm/blob/master/Merge/mainnet-rea... Notably, there is only 2 testnet merges left to do. Ethereum has 3 testnets to try things out. One testnet has already merge and is running on PoS (Ropsten testnet). The merge was a success although it allowed to uncover some minor issues. The next one, called Sepolia, is happening this week. After that, there is only one other testnet merge to occur, likely in August. If all that goes well a date will be set. Ethereum does have a way to force the death of PoW. The Ethereum protocol has always built-in the so-called "difficulty bomb". The difficulty bomb is simply a target date in the future when the mining difficulty starts rising exponentially. Making finding new blocks exponentially hard
Read the rest
er until the chain freezes to a halt. Its death is always coded-in, so to speak. The difficulty bomb needs to be delayed periodically so Ethereum can keep working. Last month the difficulty bomb was pushed a few months to occur in September. If all testing goes well, the merge will be triggered in September aligned with the difficulty bomb which will cause the death of PoW Ethereum. You could argue that you can always fork Ethereum, remove the difficulty bomb, and run that instead. Which is true. Except there won't be economic value in that chain, so there won't be fee revenues to capture which means it won't be profitable to point your hash-power to this forked chain.
In Ethereum Energy Consumption
What’s New in Eth2 is a biweekly newsletter that's a good resource for tracking progress toward PoS: https://hackmd.io/@benjaminion/eth2_news From the current edition: Go/no-go decision on doing the Merge or postponing the difficulty bomb to be discussed on the 29th of April [2022] ACD call. If it’s "go" then start merging the existing testnets at 2 week intervals with a view to doing the real thing in July [2022]. ACD call == AllCoreDevs meeting. Here's a summary of the most recent one (includes a link to a recording of the call): https://github.com/ethereum/pm/blob/master/AllCoreDevs-Meeti...
In Ethereum Has Issues
It's been slow, but progress is happening. There's already ~$28 billion worth of ETH staked on the beacon chain. Most of the engineering work for the merge has already happened. A post-merge testnet (Kintsugi) was launched a few weeks ago. If you look at the mainnet readiness checklist [1], the remaining work is largely testing and documentation. Hard to imagine how it could not happen at this point. [1] https://github.com/ethereum/pm/blob/master/Merge/mainnet-rea...
In Mozilla Foundation pausing cryptocurrency donations
I should also add two more important pieces to this: 1. In-person meetings and real-time calls have been a major part of the work. There is an agenda and very good notes are taken during these sessions (https://github.com/ethereum/pm). The calls have been essential for coordinating in a more formal setting and to get a feel for when consensus is achieved on a particular topic or proposal. What threaded forums later added was the ability for others to get involved in the discussion, particularly those who are not core developers or not able to attend. 2. Another important medium has been GitHub issues (e.g. https://github.com/ethereum/EIPs/issues/2315). Proposals are submitted as a PR and, earlier in the evolution of the governance process, many people would comment on them. These were not ideal due the flat nature of the format. What gene
Read the rest
rally changed on GitHub issues in recent years was the encouraging of commenters to go to an external forum thread (https://github.com/ethereum/EIPs/issues/2315#issuecomment-63...), leaving editors and authors to work out structural and other basic issues about a proposal in GitHub PR comments.
In If it will matter after today, don't talk about it in a chat room

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.