BitShares administrative and maintenance tasks

[bobmaloney]

 

[testz]

Welcome back Vikram and Agent86!   

[CLains]

Vikram <3

Happy to see you back and working with The Agent

[vikram]

After discussion, we have decided to proceed with a worker proposal as described in this thread. Requesting that fellow stakeholders please review: https://bitsharestalk.org/index.php/topic,23495.msg300188.html#msg300188

[vikram]

Thank you everyone for the warm welcome! It's great to see so many familiar names and the enthusiasm among the community.

Lance and I have both mostly been out of the loop for some time and the feedback is very helpful.

You might want to also try posting on SteemIt and introducing your project there. Many of the old Bitshares community members reside there more often than here. Regards.

Yes we will look into getting set up on Steem.

fixing all the little warts, polishing edges, properly tagging and announcing releases, and more generally maintaining the administrative part of the project that makes it easier for the rest of the ecosystem to consume the software.

Yes this is what I was thinking. Although these tasks are relatively simple, having someone consistently handle them can help prevent friction for others to contribute or integrate.

Historically, it has been difficult to get workers approved.  It may be easier to break apart tasks into smaller, specific worker proposals instead of one general proposal.

However, as BlockTrades.us had a worker for the maintenance work but still left some fund unspent after months, I guess we don't have much high priority work here to be done (or perhaps not to be funded by worker proposals). Please be aware that your worker proposal will be evaluated by all stake holders, not only the ones who replied here (and don't be surprised if it didn't be voted in quickly).

Consider potentially looking at the current list of fixes and creating a roadmap for each one along with potentially some minor feature enhancements. This would go a long way towards providing a long term benefit of your worker and keeping it voted in in tandem with releases.

I agree with abit - we have little need for maintenance right now. The software has proven to be very stable.

What we need is people who are capable of tackling specific projects. There are several threads here in the forum where improvements are being discussed. Most of the stuff is frontend-related, but there's backend work to be done, too.

Thanks guys this is all good to know. The way I structured the tasks in the OP was just an initial idea; Lance and I will continue to discuss possible paths based on your thoughts. In particular I see that @abit, @pc, @svk, and @xeroc are amongst those who are still active on the GitHub repositories so I especially want to see what you guys are thinking. And I want to emphasize that we don't want to step on anyone's toes or do anything that is against stakeholder wishes or interest.

Since you've started a new company, I guess you have a real business plan, not only to work for BitShares, right? Could you share more info?

@Agent86 has started another thread here: https://bitsharestalk.org/index.php/topic,23478.msg300083.html#msg300083 to start a discussion a bit more focused on Soledger as a company. Keep in mind we are very young still and appreciate any and all feedback especially from this community.

[ebit]

I suggest soledger to do a VC's referrer .
If soledger got a VC,then we vote for a worker.Because ,I know the VC will need your "BitShares administrative and maintenance tasks".So,we will get win-win,So good Soledger.

A great video http://www.tudou.com/programs/view/y2pu_QuBSNE/

[iHashFury]

Welcome back!

Could I also suggest a maintenance schedule for hard forks:

every 1 year on a fixed date (if required) for bitshares
every 6 months for the test net

This should help structure further development and allow all shareholders and exchanges to know when major updates will happen.

[xeroc]

Welcome back Vikram and Agent86! Good to have you on board again! Looking forward to your worker proposal! + 5%!

[kenCode]

Welcome again! I want stealth features... stealth transactions.

Me too! BitShares Munich should have most of Stealth ready for public tests around Christmas. I post weekly updates on telegram Bitshares channel, my steemit blog (https://steemit.com/@kenCode), my github (https://github.com/kenCode-de), and here on the forum:
https://bitsharestalk.org/index.php/topic,22576.0.html

[ag]

Welcome again! I want stealth features... stealth transactions.

[btswildpig]

I was going to +5 % , then I saw "Agent86"   

[pc]

Good to see you again, Vikram!

I agree with abit - we have little need for maintenance right now. The software has proven to be very stable.

What we need is people who are capable of tackling specific projects. There are several threads here in the forum where improvements are being discussed. Most of the stuff is frontend-related, but there's backend work to be done, too.

[BunkerChainLabs-DataSecurityNode]

holy s*** Vikram is back!

great to hear this! I have to say that as much as Dan was the brains behind the project, you were the engineer behind it, and you made witnesses' lives much easier by fixing all the little warts, polishing edges, properly tagging and announcing releases, and more generally maintaining the administrative part of the project that makes it easier for the rest of the ecosystem to consume the software.

Your presence in BitShares 2.0 was missed (by me at least, but I don't think I'm the only one) and for example the general feel of the cli_wallet in bts 2.0 is a lot less polished than what it was at the end of 0.9.x due to that.

So if you want to come back and fix all these little things to make a great product even greater and manage the project to that end, then I guess that you clearly have my support!

^^ This... So long as the proposal is well laid out you can expect bunkerchainlabs-com proxy support. Consider potentially looking at the current list of fixes and creating a roadmap for each one along with potentially some minor feature enhancements. This would go a long way towards providing a long term benefit of your worker and keeping it voted in in tandem with releases.

If there is anything we can do to help out feel free to contact us. I know how difficult it can be as a startup.

[abit]

Welcome back.

However, as BlockTrades.us had a worker for the maintenance work but still left some fund unspent after months, I guess we don't have much high priority work here to be done (or perhaps not to be funded by worker proposals). Please be aware that your worker proposal will be evaluated by all stake holders, not only the ones who replied here (and don't be surprised if it didn't be voted in quickly). Since you've started a new company, I guess you have a real business plan, not only to work for BitShares, right? Could you share more info?

The community need (1)more whale promotion（2）more public robot tools

I think @alt is working on the second one.

[ebit]

Welcome back.

However, as BlockTrades.us had a worker for the maintenance work but still left some fund unspent after months, I guess we don't have much high priority work here to be done (or perhaps not to be funded by worker proposals). Please be aware that your worker proposal will be evaluated by all stake holders, not only the ones who replied here (and don't be surprised if it didn't be voted in quickly). Since you've started a new company, I guess you have a real business plan, not only to work for BitShares, right? Could you share more info?

The community need (1)more whale promotion（2）more public robot tools

[ebit]

Welcome back.

Are you concerned about robots?Can you add them into light wallet?If you can ,there will be more people use robot.

[abit]

Welcome back.

However, as BlockTrades.us had a worker for the maintenance work but still left some fund unspent after months, I guess we don't have much high priority work here to be done (or perhaps not to be funded by worker proposals). Please be aware that your worker proposal will be evaluated by all stake holders, not only the ones who replied here (and don't be surprised if it didn't be voted in quickly). Since you've started a new company, I guess you have a real business plan, not only to work for BitShares, right? Could you share more info?

[kenCode]

I'm surprised this post alone has not caused a price spike! 

Me too! Welcome back Vikram!!

[fav]

I'd vote for you.

[santaclause102]

Great to see you back with this proposal! 

@xeroc

[ElMato]

Hi Vikram! Welcome back to the BTS community!! I'm glad to see you around here again!

Sent from my XT1063 using Tapatalk

[Thom]

Wow! Vikram!!!

Welcome to BitShares 2.0

I echo wackou's remarks about your noticeable absence as graphene was being tested and rolled out last year. Xeroc also has my proxy.

I'm also anxious to see what you & agent86 are cooking up. Sounds like the genesis of a great team.

[llildur]

This sounds like a great idea to me.

However, not being technically minded, I have proxied my vote to Xeroc. If you get his vote, you automatically have mine!

Same here and welcome back 

[merivercap]

Welcome back Vikram!!! 

Good to see you team up with @Agent86 !

Yes would be great to have you work on maintenance!

[Chronos]

It's great to have you back, Vikram. You are a true pillar of the community.

[Fox]

Vikram,
Warmest welcome back! Congratulations on forming a company in this space. Your prior contributions speak volumes for what it accomplish in the future. Will surely support your efforts toward a worker proposal.

Cheers!
Fox

[Brekyrself]

I'm surprised this post alone has not caused a price spike!  You could really jump start this community as of right now we only have BitShares Munich doing visible work.

Glad to see you are still around.  Historically, it has been difficult to get workers approved.  It may be easier to break apart tasks into smaller, specific worker proposals instead of one general proposal.

[wackou]

holy s*** Vikram is back!

great to hear this! I have to say that as much as Dan was the brains behind the project, you were the engineer behind it, and you made witnesses' lives much easier by fixing all the little warts, polishing edges, properly tagging and announcing releases, and more generally maintaining the administrative part of the project that makes it easier for the rest of the ecosystem to consume the software.

Your presence in BitShares 2.0 was missed (by me at least, but I don't think I'm the only one) and for example the general feel of the cli_wallet in bts 2.0 is a lot less polished than what it was at the end of 0.9.x due to that.

So if you want to come back and fix all these little things to make a great product even greater and manage the project to that end, then I guess that you clearly have my support!

[onceuponatime]

This sounds like a great idea to me.

However, not being technically minded, I have proxied my vote to Xeroc. If you get his vote, you automatically have mine!

[SolomonSollarsNSense]

  Upvote

Good to see you back Vikram!

Didn't know you were based in Chicago IL. We are too. Gold Coast area. Small world 
How about them Cubbies! Anyways good luck on your project. You might want to also try posting on SteemIt and introducing your project there. Many of the old Bitshares community members reside there more often than here. Regards.

[chryspano]

^ upvote

[vikram]

Edit: I have created a worker proposal based on this thread: https://bitsharestalk.org/index.php/topic,23495.msg300188.html#msg300188

Hello everyone,

It's been a long time! Some of you will remember me as a former BitShares developer and project manager (https://github.com/vikramrajkumar), particularly during the lifespan of BitShares 1. Since BitShares, I haven't been involved in any blockchain projects, but now I am changing that and want to start contributing to the industry again.

I've linked up with Lance Kasper, or Agent86 as he's known on this forum (https://bitsharestalk.org/index.php?action=profile;u=9289), who you may recall also previously worked as an active member of the BitShares community. The two of us decided to start a company together, as a vehicle for us to explore some of our own ideas around blockchain technology.

We are Soledger Inc. (https://www.soledger.com/), and are based in Chicago, IL, USA. We are completely independent and are not affiliated with Invictus, Cryptonomex, Steemit, or any other organization. At present, Soledger is focusing on exploring some of our own experimental ideas, which you will hear more about once we have something that we are ready to share. However, we have not forgotten the BitShares community and want to see it grow and succeed as much as possible.

Given the nature of our prior experience with BitShares, we think it could be mutually beneficial for Soledger to handle certain project maintenance/administrative functions for the project.

BitShares seems to have been running with reasonable stability for some time now and we want to help preserve that stability. We think it could be beneficial to have someone who is unambiguously responsible for certain maintenance tasks around the network and platform. In practice, this would mostly mean that someone is in charge of administrating the GitHub organization (https://github.com/bitshares) and repositories, and could include responsibilities such as:

- Emergency security patches
- Emergency network stability patches
- Merge upstream Graphene, fc, other library updates
- Fix important compilation and compatibility issues that may arise
- 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

Since the platform is already relatively stable, we would expect these responsibilities to be fairly straightforward to manage. Regardless, we think BitShares could benefit from help with maintaining the stability and ongoing operations of the network, as well an administrator to act as a clear point of contact to help coordinate community contributions, avoid fragmentation of community efforts, and keep things organized to help achieve consensus on decisions.

If there is support for Soledger to take on such a role, we are thinking that we will define it as a simple worker proposal, and thus only proceed if there is sufficient stakeholder agreement.

Let us know your thoughts and questions, and whether you think something like this makes sense for BitShares.