It seems to me that most of the comments in this thread show the need for better ways to organize and communicate budget requests and others. The EGG framework already helps to standarize the content within funding requests, but to be honest following up with things on the forum is a bit hard sometimes. Here’s a few notes on that:
First, the name of the funding requests change frequently, and they’re not intuitive. In this case, calling it a continuation of st2024 like @SEEDOrg suggested would’ve probably made more sense.
Given this funding request comes from one of the main contributors group, it’d be easier to find a more standard naming convention that included the name of the entity/group, year/period and other relevant information. I always thought the name st2024, even if not perfect, was a good start to improve the information asymmetry within the community.
Not only that, but reporting/keeping track is also complicated. Some proposals such as Community Staking Module, contain multiple sub-proposals and associated Snapshot/Aragon votes on a single thread (which imo makes it harder for less-involved community members to search and find that info on the forum) whereas these for example, even if continuations, are separated (and with, again, different names).
If I see the norm is clearly separating proposals, it’d hardly cross my mind to check a single thread for all proposals related to one initiative, and vice versa.
On another hand, funding requests for Pool Maintenance Labs, Argo Technology Consulting and RCC have previously been under the name Lido Contributors Group. I understand the name may not be appropriate anymore with contributions now being made from others such as the Lido BORG Alliance, or Community Lifeguards ourselves. But given that PML, ATC and RCC are often together on funding requests, finding another name would help create a better mental model for issues like @Lanski’s, regardless of how that group of contributors decides to organize internally.
Contributors have already all the information and understanding, but these small details can make a huge difference now that the community is growing quite fast with both governance and NO improvements (e.g. delegation and SDVT/CSM). This should, in part, solve itself as the community matures and finds its own culture to propose–but I think it makes sense to spend some time to think about this.