Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: [Worker Proposal] Project administration & essential maintenance  (Read 1060 times)

Offline vikram

[Worker Proposal] Project administration & essential maintenance
« on: November 06, 2016, 12:13:42 AM »

This proposal is based on my original thread here: https://bitsharestalk.org/index.php/topic,23474.msg300044.html#msg300044

Soledger Inc. (myself and @Agent86) is proposing a BitShares worker for handling administrative and maintenance tasks including--but not limited to--the following:
  • Emergency security patches
  • Emergency network stability patches
  • Merge upstream Graphene, fc, other library updates
  • Fix important compilation and compatibility issues
  • Tag core releases
  • Manage GitHub issue tracker
  • Manage GitHub pull requests
  • Consolidate high-quality community projects into BitShares GitHub organization
  • Consolidate and maintain other important documentation to help ease contributing and integrating
I have prior experience with all of these tasks from when I was project manager of BitShares 1.

We think it's important that a specific party maintains responsibility for addressing any emergency issues that disrupt the ongoing stability and operations of the network. In addition, it is my experience that it is helpful to have an unambiguous project administrator to act as a clear point of contact to help coordinate community contributions, avoid fragmentation of community efforts, and generally help keep things organized so that important information is readily accessible.

Taking into account that the BitShares codebase is reasonably stable at present, we have chosen a pay rate of 10,000 BTS/day for this worker. At a conservative exchange rate of $0.004/BTS, this is roughly $1200/month or $14,500/year. $0.004/BTS currently corresponds roughly to a market cap of $10.3 million. At the time of posting, the current price is around $0.0045/BTS and market cap $11.6 million.

For comparison, here are the most recent expired workers:




This Soledger worker has been defined to last until 2017-12-31. For those who want to approve this worker, please choose the correct version that expires in 2017, instead of my first attempt that was mistakenly set to expire in 2016:






If and when this worker is approved, I will request full administrative permissions for the BitShares GitHub organization (https://github.com/bitshares/). Upon acquiring said permissions, I will begin to perform any reorganization/cleanup/updating that I see fit, in line with the tasks outlined in the initial bullet points.

Edit: Given the decentralized nature of the greater BitShares project, I think it is important that currently active community leaders hold some administrative authority, and so if I am given GitHub admin permissions, I will also look into adding other admins: @xeroc and @svk are two names that come to mind.

Thank you to all stakeholders for your consideration.
« Last Edit: November 06, 2016, 09:04:07 PM by vikram »

Offline BunkerChain Labs

Re: [Worker Proposal] Project administration & essential maintenance
« Reply #1 on: November 06, 2016, 04:26:54 AM »
Transaction confirmed
[email protected]

Bunkerchainlabs-com supported.
+-+-+-+-+-+-+-+-+-+-+
www.Peerplays.com | World's First Decentralized Tournament Platform Built Entirely on the Blockchain!
+-+-+-+-+-+-+-+-+-+-+

Offline Chronos

Re: [Worker Proposal] Project administration & essential maintenance
« Reply #2 on: November 06, 2016, 04:28:31 AM »
  • Emergency security patches
  • Emergency network stability patches

Would you be responsible for coding these patches, should the need arise?

We have chosen a pay rate of 10,000 BTS/day for this worker. At an exchange rate of $0.004/BTS, this is roughly $1200/month or $14,500/year.
This example is a bit misleading, since the current exchange rate is actually more than 12% higher than your example. Imagine if you were interviewing for a job, and you didn't bother to mention that you expected your pay to be 12% higher than discussed. :)

This Soledger worker has been defined to last until 2017-12-31.
A full year strikes me as a long time for a BTS-denominated worker. It's almost a guarantee that the pay will be eventually quite out-of-whack. Any thoughts on this?

Offline vikram

Re: [Worker Proposal] Project administration & essential maintenance
« Reply #3 on: November 06, 2016, 05:14:46 AM »
  • Emergency security patches
  • Emergency network stability patches

Would you be responsible for coding these patches, should the need arise?
Yes.

We have chosen a pay rate of 10,000 BTS/day for this worker. At an exchange rate of $0.004/BTS, this is roughly $1200/month or $14,500/year.
This example is a bit misleading, since the current exchange rate is actually more than 12% higher than your example. Imagine if you were interviewing for a job, and you didn't bother to mention that you expected your pay to be 12% higher than discussed. :)
Good point. I've edited that part to reflect the current price as well. We just picked $0.004 as a round number, and a bit more conservative than the current price.


This Soledger worker has been defined to last until 2017-12-31.
A full year strikes me as a long time for a BTS-denominated worker. It's almost a guarantee that the pay will be eventually quite out-of-whack. Any thoughts on this?

Wasn't totally sure about this either, but figured that if the price gets too low, we can always make another worker. Conversely, if the price gets too high, we should be voted out. Edit: I'm not sure that this is that much of an issue otherwise, as the BTS amount is still a fixed percentage of the daily fund.
« Last Edit: November 06, 2016, 05:31:19 AM by vikram »



Offline lil_jay890

  • Hero Member
  • *****
  • Posts: 1116
    • View Profile
Re: [Worker Proposal] Project administration & essential maintenance
« Reply #6 on: November 06, 2016, 01:09:58 PM »
I think this was brought up earlier, but isn't Dan Notenstein still in possession of several million bts that are to be used for bitshares maintenance issues as they pop up? Do consider those bts gone? How are patches going to be implemented and work delegated unless the two parties are working together?

Offline ripplexiaoshan

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 1947
    • View Profile
  • BTS: xiaoshan
Re: [Worker Proposal] Project administration & essential maintenance
« Reply #7 on: November 06, 2016, 02:16:53 PM »
Good to see that old BTS developers want to come back. 
BTS ID:xiaoshan                   www.btsabc.org

Offline Akado

  • Hero Member
  • *****
  • Posts: 2743
    • View Profile
  • BTS: akado
Re: [Worker Proposal] Project administration & essential maintenance
« Reply #8 on: November 06, 2016, 02:47:15 PM »
I think this was brought up earlier, but isn't Dan Notenstein still in possession of several million bts that are to be used for bitshares maintenance issues as they pop up? Do consider those bts gone? How are patches going to be implemented and work delegated unless the two parties are working together?

Wold like to know this as well.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline pc

  • Hero Member
  • *****
  • Posts: 1000
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BTS: cyrano
  • Witness: cyrano
  • Payrate: 100%
Re: [Worker Proposal] Project administration & essential maintenance
« Reply #9 on: November 06, 2016, 03:22:38 PM »
Soledger Inc. (myself and @Agent86) is proposing a BitShares worker for handling administrative and maintenance tasks including--but not limited to--the following:
  • Emergency security patches
  • Emergency network stability patches
  • Merge upstream Graphene, fc, other library updates
  • Fix important compilation and compatibility issues
  • Tag core releases
  • Manage GitHub issue tracker
  • Manage GitHub pull requests
  • Consolidate high-quality community projects into BitShares GitHub organization
  • Consolidate and maintain other important documentation to help ease contributing and integrating

Vikram - I don't mean to quench your enthusiam, but like others have already said, the software has been *very* stable, which means that there is no immediate need for any of the above. You've set up a worker that pays $1200 per month - for essentially nothing.

Also, I find it a little strange that someone with little knowledge of Graphene turns up after a year of absence, and the first (well, second actually) thing they do is request full access to the main GitHub repo.

I know you're a very capable person, but I would still prefer a more gentle approach to things. That would allow the community to evaluate your work, and give you a chance make yourself familiar with the new codebase. If we reach a point again where BitShares sees more or less regular updates, with your help, I will certainly approve your maintenance worker as proposed above. But not yet.
Please vote for my BitShares witness "cyrano" and for my STEEM witness "cyrano.witness"!
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline Brekyrself

  • Sr. Member
  • ****
  • Posts: 338
    • View Profile
Re: [Worker Proposal] Project administration & essential maintenance
« Reply #10 on: November 06, 2016, 06:02:14 PM »
Soledger Inc. (myself and @Agent86) is proposing a BitShares worker for handling administrative and maintenance tasks including--but not limited to--the following:
  • Emergency security patches
  • Emergency network stability patches
  • Merge upstream Graphene, fc, other library updates
  • Fix important compilation and compatibility issues
  • Tag core releases
  • Manage GitHub issue tracker
  • Manage GitHub pull requests
  • Consolidate high-quality community projects into BitShares GitHub organization
  • Consolidate and maintain other important documentation to help ease contributing and integrating

Vikram - I don't mean to quench your enthusiam, but like others have already said, the software has been *very* stable, which means that there is no immediate need for any of the above. You've set up a worker that pays $1200 per month - for essentially nothing.

Also, I find it a little strange that someone with little knowledge of Graphene turns up after a year of absence, and the first (well, second actually) thing they do is request full access to the main GitHub repo.

I know you're a very capable person, but I would still prefer a more gentle approach to things. That would allow the community to evaluate your work, and give you a chance make yourself familiar with the new codebase. If we reach a point again where BitShares sees more or less regular updates, with your help, I will certainly approve your maintenance worker as proposed above. But not yet.


@pc There may not be an immediate need however having someone like Vikram more involved can help tackle idea's found in this thread: https://bitsharestalk.org/index.php/topic,23355.0.html

We need someone technical to keep pushing the BTS codebase forward.

Offline vikram

Re: [Worker Proposal] Project administration & essential maintenance
« Reply #11 on: November 06, 2016, 08:58:32 PM »
Soledger Inc. (myself and @Agent86) is proposing a BitShares worker for handling administrative and maintenance tasks including--but not limited to--the following:
  • Emergency security patches
  • Emergency network stability patches
  • Merge upstream Graphene, fc, other library updates
  • Fix important compilation and compatibility issues
  • Tag core releases
  • Manage GitHub issue tracker
  • Manage GitHub pull requests
  • Consolidate high-quality community projects into BitShares GitHub organization
  • Consolidate and maintain other important documentation to help ease contributing and integrating

Vikram - I don't mean to quench your enthusiam, but like others have already said, the software has been *very* stable, which means that there is no immediate need for any of the above. You've set up a worker that pays $1200 per month - for essentially nothing.

Also, I find it a little strange that someone with little knowledge of Graphene turns up after a year of absence, and the first (well, second actually) thing they do is request full access to the main GitHub repo.

I know you're a very capable person, but I would still prefer a more gentle approach to things. That would allow the community to evaluate your work, and give you a chance make yourself familiar with the new codebase. If we reach a point again where BitShares sees more or less regular updates, with your help, I will certainly approve your maintenance worker as proposed above. But not yet.

I definitely hear your concerns and perhaps we should have reached out to you directly before attempting to finalize such a proposal. And perhaps I should have also been more descriptive in the OP:

- Emergency security patches
- Emergency network stability patches

Ideally these would never require any work. However, if such an issue were to arise--which may happen unexpectedly at any time--I think it is important that a specific party has responsibility for ensuring that the issue ultimately gets resolved.

- Merge upstream Graphene, fc, other library updates

This may be a combination of minor things, but something that I want to make sure is maintained well nonetheless. I note that bitshares/bitshares-2/bitshares has diverged from cryptonomex/graphene/master after commit 006d54863312c7daf1ccb73d5940ec658c860efb and has diverged from cryptonomex/graphene/develop after commit f049fce4e97154ce0d037ee2818a285ebffb944f. bitshares/fc has also diverged from steemit/fc after commit 0dca15c3954d38f2a8603aab316d214ca893930f. The updates themselves may not be particularly important but I think it points to a lack of organization in that these divergences persist.

I am also interested in backporting other base Graphene fixes from Steem when applicable and permissible. I also want to look into the feasibility of backporting an upgrade like ChainBase (https:[email protected]/announcing-steem-0-14-4-shared-db-preview-release) should it be successfully integrated into Steem.

- Fix important compilation and compatibility issues

Ideally this would never require any work. However, operating systems and environments continue to update and move forward, and it may become more difficult to contribute to or run BitShares as time goes on. As an example, I am unable to compile BitShares on my local machine running Arch Linux, presumably due to compilers or libraries which are too new. Perhaps nobody needs specific responsibility for issues like this, but it is something that I intend to keep track of and try to address when possible.

- Tag core releases

Perhaps I misunderstood this initially; although @svk has been tagging what are marked "GUI Release"s, they indeed incorporate all of the few changes to the core code that occurred as well. I do not want to interfere with his work. However, if in the future, there are non-trivial changes to the core code, I am willing to perform final reviews of all said changes before signing off on an official release tag, as I previously was responsible for with BitShares 1. Further, if there are significant updates in the future, someone should also be responsible for coordinating and notifying exchanges and other service providers, a step which has had oversights in the past.

- Manage GitHub issue tracker
- Manage GitHub pull requests
- Consolidate high-quality community projects into BitShares GitHub organization
- Consolidate and maintain other important documentation to help ease contributing and integrating

On second look, I am not yet sure on the best path for the issue tracker. If it seems that bitshares/bitshares-2 will continue to diverge from cryptonomex/graphene, perhaps it does make sense to open an independent issue tracker for bitshares/bitshares-2. This can also be used to collect BitShares-specific issues and should also be more discoverable for BitShares users who do not understand the Graphene heritage.

There are also outstanding pull requests in cryptonomex/graphene, cryptonomex/fc, and bitshares/bitshares-2. The commits may ultimately be inconsequential, but again I think it points to a lack of organization that these requests sometimes go unaddressed. I want to make sure that potentially valuable issues or contributions do not fall through the cracks.

I will have to do more of a survey of projects to get a better idea, but I was thinking that projects from community leaders such as https://github.com/xeroc/python-graphenelib, https://github.com/xeroc/graphene-paperwallet, https://github.com/svk31/graphenejs-lib, https://github.com/svk31/graphenejs-ws, https://github.com/kenCode-de/bitshares-wallet, https://github.com/kenCode-de/smartcoins-wallet as some examples, could potentially be moved into https://github.com/bitshares if said owners find it suitable, to consolidate pieces of the BitShares ecosystem more clearly under the "official" BitShares name.

I will also have to explore the state of documentation more, but I want to look into consolidating and updating info from places like https://bitshares.org/, http://docs.bitshares.eu/, https://bitshares.org/doxygen/, https://github.com/bitshares/bitshares-2/wiki, or at least try to help organize things so that relevant information is more discoverable.

In general, I will also do my best to address relatively clear issues that arise if and when possible. As an example, while syncing a new node yesterday my p2p logs ballooned to greater than 35GB. I can't say that fixing such an issue will be straightforward, but it is the kind of clear problem that I will look into.

Again, I hear your concerns but I hope I have clarified my thinking at least somewhat. The system has indeed been stable and hopefully will remain so, but I do not think these responsibilities amount to nothing. In a system as large and integrated as BitShares--still around a $10 million market cap--I think it is important that even the small details are taken care of. If BitShares were to rise dramatically in value, I think it is even more important to pay attention to the details.

I indeed have relatively little experience working with Graphene, especially after the time that has passed, but I am not wholly unfamiliar with its design--I was there when it was first built and made a number of commits (https://github.com/bitshares/bitshares-2/graphs/contributors) --and am confident in my ability to get back up to speed.

If I recall correctly from when I previously stepped down as GitHub admin, at the time the only other admins were Cryptonomex, BlockTrades, and maybe @cass. If no one else has been added since, it seems like there is room for additional active community leaders to be given administrative permissions, which I would want to grant to probably at least @xeroc and @svk--if there is no great objection to me adding more admins. I will edit the OP to mention this, but it's a natural extension of consolidating community project repos into the GitHub organization. Part of the intent of this worker proposal is for stakeholders to vote on assigning administrative authority to a new party. BitShares is a decentralized project and will continue to have different people in different roles as time goes on.

I hope I have made my thinking a bit more clear. Thank you for the honest thoughts and consideration.

Offline pc

  • Hero Member
  • *****
  • Posts: 1000
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BTS: cyrano
  • Witness: cyrano
  • Payrate: 100%
Re: [Worker Proposal] Project administration & essential maintenance
« Reply #12 on: November 07, 2016, 07:20:45 AM »
Thanks for spelling it our for me. That description looks a lot more convincing than the initial list of bullet points. You have my vote.
« Last Edit: November 07, 2016, 07:44:30 AM by pc »
Please vote for my BitShares witness "cyrano" and for my STEEM witness "cyrano.witness"!
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 11958
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: [Worker Proposal] Project administration & essential maintenance
« Reply #13 on: November 07, 2016, 07:46:15 AM »
Just voted for your worker!

If and when this worker is approved, I will request full administrative permissions for the BitShares GitHub organization (https://github.com/bitshares/). Upon acquiring said permissions, I will begin to perform any reorganization/cleanup/updating that I see fit, in line with the tasks outlined in the initial bullet points.
If I recall correctly, CNX as well as @cass are administrators for the bitshares organization.

Quote
Edit: Given the decentralized nature of the greater BitShares project, I think it is important that currently active community leaders hold some administrative authority, and so if I am given GitHub admin permissions, I will also look into adding other admins: @xeroc and @svk are two names that come to mind.
I already do have write permissions to some of the repos and don't see the need to become an administrator. Given that I am the biggest proxy, it could mean too much power in the hands of a single entity
« Last Edit: November 07, 2016, 07:48:49 AM by xeroc »
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline vikram

Re: [Worker Proposal] Project administration & essential maintenance
« Reply #14 on: November 17, 2016, 11:54:57 PM »
NOTE: 2 pages of posts disappeared from this thread (I asked about this here: https://bitsharestalk.org/index.php/topic,23506.0.html)

Again, I want to express sincere thanks to all stakeholders from myself and @Agent86 at Soledger. Our worker has been voted in and I've been given administrative privileges for the BitShares GitHub organization. I've merged some minor commits (https://github.com/bitshares/bitshares-2/compare/d7c51f26e3...4eaef390a3) and will continue to address tasks in line with what I've outlined in earlier posts.

Continued feedback and thoughts are always appreciated.

 

Google+