Author Topic: [Worker Proposal] Bitshares UI Renewal  (Read 2101 times)

0 Members and 1 Guest are viewing this topic.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12793
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: [Worker Proposal] Bitshares UI Renewal
« Reply #15 on: August 16, 2018, 01:38:15 pm »
It may be worthwhile adding a "code of conduct" to the bitshares-ui repo just to have something there that you can argue *with*
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline startail

Re: [Worker Proposal] Bitshares UI Renewal
« Reply #16 on: August 18, 2018, 10:52:14 am »
Adding a code of conduct to the repo would be a good thing. I will make sure we apply one soon.

Offline startail

Re: [Worker Proposal] Bitshares UI Renewal
« Reply #17 on: September 05, 2018, 04:40:04 pm »
Bitshares UI supports Beet in long-term development


A recent addition to the family of Bitshares applications is the Bitshares Companion application, now called Beet. The app was initially drafted and by clockwork, which handed over the source for the Beet application to the community.

The goal of Beet is to make it easier for third party applications to work on the bitshares network, without having to worry about handling the private keys on these applications. Beet will be the handler for signing the transactions, while the application using it can focus on usability and functionality.

The bitshares teams believes that Beet fits nicely under the current UI worker in long-term development. Beet development will for the moment be supported by the UI worker and agreed to compensate for the initial development as source was released to the community. The project manager of the UI worker will handle issues, assignments, compensations in the same way as the current UI repo works today.

We see great potential of development for Bitshares applications with the addition of Beet. While Beet is still in very early alpha, having it compensated under the current UI worker will make development speed up, improving the ecosystem.

Beet Gihub Repo, https://github.com/bitshares/beet

The UI team also wants to inform that it will receive some extra support by Stefan Schießl during the month of August as Sigve is on a well-earned holiday.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12793
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: [Worker Proposal] Bitshares UI Renewal
« Reply #18 on: September 05, 2018, 04:45:40 pm »
+5%
This is excellent news!! Looking forward to using beet more actively!
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Online sschiessl

Re: [Worker Proposal] Bitshares UI Renewal
« Reply #19 on: December 21, 2018, 03:27:37 pm »
A quick summary of the ongoings in the BitShares UI worker

https://whaleshares.io/bitshares/@sschiessl/the-bitshares-ui-worker

The worker is currently inactive, which effectively means the development is stopped due to lack of funds. Please have a read, and if you like the latest progress please consider voting for it!

Offline iamredbar

Re: [Worker Proposal] Bitshares UI Renewal
« Reply #20 on: December 21, 2018, 10:36:21 pm »
I have made sure that I am currently voting for this proposal and urge others to do so as well.

This has been a crazy year and I am not deterred by not having a “weekly” update or something of the sort.

If you observe Github, you can see that this team has been hard at work. They have earned my trust to continue to improve and expand on the BitShares UI.

Offline startail

Re: [Worker Proposal] Bitshares UI Renewal
« Reply #21 on: December 22, 2018, 09:36:05 am »
@iamredbar thank you for your continued trust.

It has been a crazy few months, and we've had MUCH work to do on the UI. Thanks to the funding from the community we've been able to have plenty of community support by react developers in various stages of exprience. The main team have had plenty to do and learned alot along the way. Remember that we've all started in the middle of the project at some time or another, none of us was in the start of this.

Just during the last month of the year we had plenty to do to add functionallity for globally settled assets that was added to the core a while ago. Since bitUSD, and plenty of other assets, suffered this from the fall of BTS price. The whole team enganged in added new functions and test them to make sure they worked as intended.

Despite comprehensive testing tries, we do sometimes have issues coming up afterwards. One of the biggest changes we did was also to change the release schedule to also have a 'Release Candidate' before the actual release. We do our best to catch issues before they get out to the main release, but since the team is still not a large one, we rely heavily on othes to help us test. Once an issue is identified in a release candidate that is major we will make a fix for it before we do another standard release. This has been a big change, and something we've had to grow into and find good ways to work with.

To visualize how much issues that have been created, addressed and closed by the team since the community started funding the worker of Bitshares-UI.
We appreciate the support from the community to be able to do this work, and to continue enhancing the UI.



Repository activity for the last month.




Sources:
- https://github.com/bitshares/bitshares-ui/pulse/monthly
- https://repohealth.info/report/bitshares/bitshares-ui


Offline Digital Lucifer

  • Global Moderator
  • Full Member
  • *****
  • Posts: 179
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 2.0
  • BitShares: steem-not
  • GitHub: dls-cipher
Re: [Worker Proposal] Bitshares UI Renewal
« Reply #22 on: December 23, 2018, 03:02:21 am »
Thanks to few individuals going around and promoting this worker, believe that since this early AM, BitShares UI Worker is Active and just ~2M votes above refund400k.



Please keep giving in Your votes.

Chee®s
« Last Edit: December 23, 2018, 03:06:10 am by Digital Lucifer »
Milos (Mike) Preocanin - General Manager @ Syntek Solutions
TOANDI Co., LTD. (BOI Approved) - TAX ID: 0205549016913 - 95/5 Moo 4 Siam Country Club Rd.
Nong Prue, Bang Lamung, Chonburi 20250, Thailand.

Offline iamredbar

Re: [Worker Proposal] Bitshares UI Renewal
« Reply #23 on: December 23, 2018, 03:38:17 am »
Thanks to few individuals going around and promoting this worker, believe that since this early AM, BitShares UI Worker is Active and just ~2M votes above refund400k.

Please keep giving in Your votes.

Chee®s

This is great news right before the new year. Here's to a great 2019!

Offline startail

Re: [Worker Proposal] Bitshares UI Renewal
« Reply #24 on: December 23, 2018, 02:28:24 pm »
Thanks to few individuals going around and promoting this worker, believe that since this early AM, BitShares UI Worker is Active and just ~2M votes above refund400k.

Please keep giving in Your votes. [/center]

Chee®s

Indeed appreciate these that help us promote this worker. At the moment the worker have passed the refund100k worker as well.
Looking forward to a great 2019 with great progress and development for Bitshares!

Happy holidays everyone.

Offline iamredbar

Re: [Worker Proposal] Bitshares UI Renewal
« Reply #25 on: December 25, 2018, 08:04:07 pm »
How could you not want to vote for this worker? Look at this easter egg:

I found this Easter egg in the UI. While being a cool feature, this was not implemented by the UI team but by the underlying software. I found it interesting, but after reading about the Easter egg the situation is a little more serious than that.

This is all addressed below by @startail

« Last Edit: December 25, 2018, 10:05:44 pm by iamredbar »

Offline startail

Re: [Worker Proposal] Bitshares UI Renewal
« Reply #26 on: December 25, 2018, 08:35:33 pm »
I'd like to address the Easter egg that was visible in the application today.

The UI decided a few months ago to start implementing a style guide framework. We decided to go for ANT Design.

One of the coders at ANT Design decided that it would be a great idea to implement an Easter egg feature, without notifying this in the change log. To include a thing like this in production build on a framework that is used in a wide range of applications is a very bad judgement on their part. There was a hard coded feature in ANT Design that made this "feature" activate on the 25th of December. They have since the appearance of this "feature" released an official apology and removed the code responsible for it.

Their reputation did drop with this, as quite a large amount of repositories relying on this started reporting issues with this.

Let me be very clear, we take this most seriously.
We will have their work looked at before merging for now.
In the future, as we've finished implementing the new framework (the bitshares-styleguide), we would have the possibility to change freely on what dependency framework we would rely on.