#Lute_RetroactiveGrant_20250328
midnight quail
zealous skiff
the submission is overly concise. I will be spreading the proposal writing work over last week and the coming 2 weeks.
steady prairie
Added a little bit here for the voiapedia ; )
I often use Lute as a light wallet and to use high forge. A few times my wallets have been erased. Its okay because I have a backup.
steady prairie
I love Lute but just want to put it out there to not undersell the contributions by Kibisis that came with being open source as part of the deliverables.
I understand how we can't really lean on support for open source development in the case of Nodely. However, this is not the case. The proposal should explicitly be clear even if it states stating that it is for the dev time and webservers. Lute is no exception how much we love it.
zealous skiff
I have asked clarifying questions about opensource development.
steady prairie
- We should never put ourself in a position to cover a persons dev time.
- We are too early to be closed source and should not start. Granted there are exceptions. Not going to name any names.
zealous skiff
1. We should never put ourself in a position to cover a persons dev time.
2. We...
Input: Dev time + Hardware to code and test
Output: Deliverables
We are paying for Deliverables.
steady prairie
Maybe someone should go submit a proposal to bang rocks. Dev time to bang rocks + Hardware rocks. Deliverables make fire. We are paying for the developer to make fire.
That makes sense though. We are paying for those deliverables which comes in the form of code and impact qualitative and quantitative but ideals quantitative by means of KPIs ; )
zealous skiff
It will remain closed source for now. Funk doesn't want to rush it.
Ask is reduced to 5M. @torn lance
When open-sourced another proposal will be submitted.
zealous skiff
Ready for an eval @torn lance ?
torn lance
Ready for an eval <@409034572970328076> ?
working on it right now!
torn lance
Evaluation has finally been submitted