Thank you for your prompt response and for taking the time to review my code.
With regard to point #1, I believe you may have a missunderstanding. I would like to draw your attention to the documentation and the code for triggerSplit(). It is already designed to request the current Nouns treasury to transfer funds to a newly created vanilla rage quit DAO. The whole treasury will of course never be held in the split contract.
Moving on to point #2, I understand that the new DAO is designed to have a vanilla ragequit feature in place by default based on your spec on github: “New DAOs are deployed with vanilla ragequit in place; otherwise it’s possible for a New DAO majority to collude to hurt a minority”. Has this design changed where there is now voting capabilities?
Lastly, I appreciate your transparency in informing me about yours and the team’s focus on coding at the moment. While I understand that the work may be conducted in a private repository, I would like to emphasize the benefits of leveraging community contributions through an open-source approach. As a long-time developer involved in various projects, I believe in the power of crowdsourcing and collaboration.
Please do not interpret my inquiry as confrontational; rather, I have been actively posting everywhere I can trying to find Nouns-related solidity needs to contribute to for over a month, and the lack of responses has been somewhat discouraging. It would be disheartening to learn that the core Nouns team is working on the Solidity in an exclusive repository, as I am eager to support the project in any way I can and I am also sure many devs have come and sadly gone because the lack of opportunity to help or even discuss.
Thank you for your understanding, and I look forward to your response.