voting for the subsequent UI worker proposal

Thank you for your support @xeroc.
I've also posted here, https://bitsharestalk.org/index.php?topic=26858.0, about the renewal of the UI.

Dear Bitshares Community,

The previous worker for the UI team, 2018-02-bitsharesui, have come to its end and the team have submitted a new worker for a continuation of the work. During the last worker we've completed many things, including the addition of TradingView and a unified style guide based on Ant. We also had some great talents helping us with UX work.

We will keep the existing bounty program, including the requirements for UX work.

The biggest change for the new worker is that we will be three people with a fixed work hour, where I will take over most of the GitHub issue coordination and bounty program assignments. Bill Butler will continue with issue coordination and managing the funds and Sigve Kvalsvik takes care of code review as previously.

Let me present myself
My name is Magnus Anderson, and is known as 'startail' ('sc-steemit' on Steemit)

I have a long background in webpage and server management and maintaining. Most of my previous work is dynamic webpages with database backends, which involves languages like PHP, JS, CSS, jQuery and MySQL databases. I'm also well versed in Linux and server management, and I run both a Steem and a BitShares witness as well as a Bitshares public node.

Since the end of last summer I've worked together with the UI team, and made much work and some of the large changes to the UI. My involvement so far have given me great knowledge of the code, something that will greatly assist me when managing the GitHub issue planning.

I've come to learn a very good team of people and think we've found a good way to work together.
I feel we have a good group that can work together to bring great updates to the application. 

I look forward to continue working for adding great enhancements for the Bitshares UI and hope for great support from the community.

New worker

This worker proposal will continue to enhance this effort by:

- Creating a more modular exchange experience.
- Migrate to ANT components complete with a style guide.
- Further refine the navigation moving away from the sub-tab model.
- Create an easy way for exchanges to brand their own wallet from the reference wallet.
- Establish a more methodical QA and testing phase before releasing each version.
- Create a series of automated front and backend tests to reduce resurfacing bugs.

New worker: https://www.bitshares.foundation/workers/2018-08-bitshares-ui
Previous closed issues so far can be found on https://github.com/bitshares/bitshares-ui/milestones?state=closed

voting for witness @startail - seems very active and participating.

I thank you for your vote in confidence. I will do my best and stay as active as possible. As I mentioned in my post, I think a witness should stay active and visible in the crowd, and that's what I intend to do. I do some coding as well, making smaller help scripts here and there. But just being out there is what I try to do more.

I'd appreciate any and all votes on my witness 'sc-ol', http://cryptofresh.com/u/sc-ol.

Quote from: startail on September 16, 2017, 08:38:52 am

The testnet network is still running, so I assume the trial on the fork was successful.

let's ask our 25 active witnesses how the test goes

I'm one of the testnet witnesses running, and have so far not seen any issues on my end. This is why I put the question out here to see how everything was going for the other ones.

Seeing the many things fixed in this version I'm unsure if it's enough to just run a witness to see the effects. I assume some tests have to be performed to see that they are actually working as expected.

I miss an actual schedule or plan on doing this, but maybe I'm not in the right place?

Quote from: startail on September 14, 2017, 04:59:30 pm

So, in less than 24 hours we will activate the new hard fork on BitShares.

...on BitShares *testnet*.

Obviously

The test is schedule till tomorrow, just 24 hrs left, and so far we only have 3 witnesses joining. I'm also not a voted in witness on the main net, so just 2 regular witnesses so far. I think this is worrisome if witnesses aren't active in the community development.

Next task, that I think I should look at, is to look at price feeds.

Are there any assets that needs extra witnesses running price feeds?
As a non-block producing witness so far it doesn't make any sense for me to start publishing price feeds for anything, if I've understood this correct.
I might start to publish some feeds, just for the sake of it, but I need to set up a good price-feed script for that.

Anyhow, if anyone thinks I should post any specific price feeds, just give me a shout out here or on the Whaleshares Discord or Team Gridcoin Slack channels as I'm always in either of them.

As @sahkan posted before, there has been a need for FULL Nodes.
Today I've officially started up my full node.

Full Node Specs:
- 10-core Intel® Xeon® E5-2620v3 or E5-2630v4 processor
- 52GB RAM
- 1Gigabit unmetered traffic

It can be accessed trough wss://bitshares.crypto.fans/ws
I've also started to work on a forked modification of @roelandp's Python monitoring script to keep track of the witness status.
I will add a few more functions with the support that the Python libraries for Bitshares, Steem and PeerPlays gives to make it a one-stop witness monitoring script.