Hi, yesterway was bi-weekly meeting #5, so I figured I would link it along with #4 and provide a tl;dr for both of them. # dev meeting 4: agenda and tl;dr: - Dev sync it's better if you listen to this one, there is a lot of stuff - Allow users to change the proposal title https://gitlab.syncad.com/hive/hive/-/issues/45 - Consider increasing proposal creation cost by 1HBD for each day it "lasts" over 10 days https://gitlab.syncad.com/hive/hive/-/issues/44 Basically it's on that meeting that we decided that it would be a good idea to have the update_proposal operation along with a new fee structure. - Referral system at the chain level https://gitlab.syncad.com/hive/hive/-/issues/43 Regarding the referral system, we thought it could be a cool idea to implement at the chain level similar to bitshares, but need more discussion on how exactly we should do it, add a buyback etc. - Allow linking more than one permlink per proposal https://gitlab.syncad.com/hive/hive/-/issues/41 We didn't think it was that necessary, it adds a burden to the chain when we could just have the main post have a list of posts at the top - Hard fork 24 and convert steemit stake to hdf We figured it would be a good idea - Node status page on hive.io ? Technically status page is already implemented on a few services already, we should try to get a list of them on hive.io - No longer remove expired proposals and instead allow filtering at the api level https://gitlab.syncad.com/hive/hive/-/issues/48 Better solved via hivemind instead of hive. https://youtu.be/-0x7uBfLYak # dev meeting 5: agenda and tl;dr: * Dev sync same, listen in. But basically, I've been working on update_proposal and the new fee structure and blocktrade's team has been working on optimizing the chain and prepping the testnet. * Consider increasing proposal creation cost by 1HBD for each day it "lasts" over 60 days feedback discussion https://peakd.com/hive-139531/@howo/some-extra-changes-are-being-bundled-into-hf24-regarding-the-proposal-system-we-want-your-opinion-on-it We discussed a bit other solutions proposed in this post, and in the end thought that it was best to ship as is and update in a later fork if necessary. * Discuss how to do "controversial" changes, and how to poll the community Basically, we post on chain ideas, mostly in the [Hive Improvement Community](https://peakd.com/c/hive-102930/created) or post it on [gitlab](https://gitlab.syncad.com/hive/hive/-/issues) to discuss more technical things. And if the change is controversial, we'll make two proposals to poll the community. * Proposal object permlink issue fix https://gitlab.syncad.com/hive/hive/-/issues/53 In the end, we figured that edge case was fine to be as it is, because it's super rare that it'll happen, and worst case it's more of a front end thing rather than a blockchain issue. * Should we add support for "custom keys"? https://gitlab.syncad.com/hive/hive/-/issues/49 This one was interesting, we were mostly throwing ideas around, I think having custom keys is a bit too much of a burden on apps and on chain to manage. And I think that idea should be done via changing the give authority operation where you don't have to use your active key for it, if you want to give voting authority you should be able to do it with a posting key, but if you want to give witness voting authority, then you should be using an active key. * downvote mana delegation Same, mostly a discussion, I suggest you just listen in as there wasn't really a conclusion. * increase max vote changes https://gitlab.syncad.com/hive/hive/-/issues/40 Why not, but we need to find out why this limit was put there in the first place before acting. * @imwatsi was asking "I'm interested to know how I can get involved with hivemind, jussi or hive-python. Are there any priority issues I can tackle?" The issue was that for this fork a lot of stuff changed, so any work would probably cause code conflicts (all the names have changed from steem to hive for instance), so we were kind of preventing outside help for a bit. After hf24 we will be much more open and have a lots of tasks that can be tackled by volunteers. Also we had some discussion on leaving some easy tasks open (not work on them) tag them as "good for new contributors" so that new people can learn how to work on core subject with easy tasks. https://youtu.be/uAXQb5swLys FYI, those are streamed on the hiveio youtube account, and the next one is on the 22th of june at 5pm CET. Tune in to ask questions :) Finally, please consider voting on my core development proposal here https://hivedao.com/proposals/97 and for the witness I co-manage @steempress

See: Hive developpers bi-weekly meetings #4 and #5 with a tl;dr ! by @howo