BitShares Forum
Main => General Discussion => Topic started by: blockchainprojectsbv on January 11, 2018, 01:10:21 pm
-
We would like to let everyone know that our development team lead by @xeroc has
worked on a new feature that allows to claim BTS from the fee pool.
While we recognize that this can be seen as a minor contribution, we believe that
starting with baby steps first and establishing a reputation as a core development team
is the better approach and proposing significant changes right away.
The following contributions comes as a gift to the BitShares community and is released
under MIT:
https://github.com/bitshares/bitshares-core/pull/572/files
Whether the code is merged with bitshares-core to be released on a yet to be defined
hard fork date remains under the control of the core developers and the rest of the community.
-
hey there, i think you guys are taking the right steps, i don't consider the change so minor, it actually backed by a BSIP(even if it ended with a new operation) and it requires a hardfork. need to be tested on the public testnet and will probably became operational with other changes that require hardfork.
the plan we have for hardforks is 1 "big" change plus a few other small changes at the same time. this can be considered as one of the small changes.
i am getting out for vacations for a week tomorrow so i will not have time to review it but i will take a more detailed look at the code and start some tests when i came back.
keep the good work! welcome to the bitshares core.
-
I personally think it is about time for a hardfork schedule .. something along the lines of "be prepared for a hasrdfork every 9 months" .. then exchanges and business partners of BitShares can be prepared and expect hard forks right away ...
Also, I don't mind waiting 9+ months for this feature to be included .. not my decision to make
-
planned hardforks every 6-9 months ... sounds good to me so everyone can be ready and core devs can work on having enough stuff for a hardfork inside those period of times. i like the idea, we need to spread it starting with @pc and @abit.
-
If we plan for a fixed release schedule we need the resources to deliver. Which means mostly it's up to our paid developers. You decide, @abit @oxarbitrage . :-)
-
If we plan for a fixed release schedule we need the resources to deliver. Which means mostly it's up to our paid developers. You decide, @abit @oxarbitrage . :-)
i think a HF around every 6 months will be healthy but yes we need to have enough quality stuff to worth the effort.
the best to me will be as we made it last time that worked. this is:
- a dedicated worker proposal to work in a bsip or big feature with hardfork(will be great if we can have @pc again on it).
- worker will take care of the hardfork planning while a few satellite changes are added to the same hardfork(like the one on this thread).
- other devs contribute in this side changes and help the hardfork worker with the planning, testing, etc.
this should be done every X months resulting in more or less a planned hardfork release every X time.
-
So far so good. :)
I was thinking about 2 to 3 hard fork releases per year, besides emergency bug fixes. We don't need to make very big changes every time. For me, BSIP 26 + 27 is a big enough improvement for the system, so worth a hard fork release, I'm looking to release them in March or April. We do need to think about future plans, according to the BSIPs repository, there are already lots of jobs to be done, we do need more devs to work on them.
-
So far so good. :)
I was thinking about 2 to 3 hard fork releases per year, besides emergency bug fixes. We don't need to make very big changes every time. For me, BSIP 26 + 27 is a big enough improvement for the system, so worth a hard fork release, I'm looking to release them in March or April. We do need to think about future plans, according to the BSIPs repository, there are already lots of jobs to be done, we do need more devs to work on them.
How do we spread the word developers can be paid by the blockchain?! The money is there, we just need the talent.
-
How do we spread the word developers can be paid by the blockchain?! The money is there, we just need the talent.
A nice post like this could help:
- https://blog.decred.org/2017/07/25/Decred-Recruiting/
We should officially clarify:
- that bitshares is effectively hiring
- what positions are open / wanted.
- what contributions are wanted (BSIP, "help-wanted" tag in github, page with a list of ideas, documentation, ...)
- how you can already contribute (UI worker, witness, etc...)
- how works the hiring process (worker proposal, guidelines to get voted in, etc..)
It should be posted by the spokesperson and then we should share the word.
Incoming Graphene Conferences are also a good forum.
Another idea is a "Build Challenge" like this: https://www.stellar.org/blog/build-challenge/ + https://www.stellar.org/developers/guides/things-to-build.html
I also like this page which is more clear than most of the pages we have for bitshares: https://www.dash.org/governance/
-
How do we spread the word developers can be paid by the blockchain?! The money is there, we just need the talent.
A nice post like this could help:
- https://blog.decred.org/2017/07/25/Decred-Recruiting/
We should officially clarify:
- that bitshares is effectively hiring
- what positions are open / wanted.
- what contributions are wanted (BSIP, "help-wanted" tag in github, page with a list of ideas, documentation, ...)
- how you can already contribute (UI worker, witness, etc...)
- how works the hiring process (worker proposal, guidelines to get voted in, etc..)
It should be posted by the spokesperson and then we should share the word.
Incoming Graphene Conferences are also a good forum.
Another idea is a "Build Challenge" like this: https://www.stellar.org/blog/build-challenge/ + https://www.stellar.org/developers/guides/things-to-build.html
I also like this page which is more clear than most of the pages we have for bitshares: https://www.dash.org/governance/
It's a really good blog