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: Feature request: More detailed upgrade notes  (Read 580 times)

0 Members and 1 Guest are viewing this topic.

Offline theoretical

Feature request: More detailed upgrade notes
« on: September 22, 2014, 12:41:21 AM »


Users are frustrated by the lack of communication surrounding the new v0.4.16 shorting mechanics:

yea it would be nice to know things like this BEFORE or at least once they are implemented......idk maybe under some kind changes to this version or something like that.

I realize developer time is at a premium, but there should be some official announcement channel to tell us about the changes in upcoming Mandatory Upgrades [1], such as the new shorting mechanics.

I am aware of two existing channels for this purpose, but one of them does not mention short issues at all [2], and the other merely says "Revised consensus market engine shorting mechanics" [3].

If we want traders and investors to take our markets seriously and make investments in our ecosystem, we need to provide a channel to tell them about major changes like this one.  Without requiring them to wade through many pages of irrelevant forum discussion, of which only a small handful of posts will contain accurate, up-to-date information.

IMHO such a channel should have an RSS feed and anyone should be able to submit improvements to the descriptions, but the description should be approved by the developers for accuracy, brevity and clarity before it can be posted.  I like the idea of using a Github repo with version-controlled Markdown files and accepting pull requests.  But a wiki, forum thread, or documentation file(s) in the main BitShares repo would also be reasonable choices.

My post in the pre-change discussion [4] or the help that I gave to the above frustrated user [5] contains the sort of description of the mechanics I'm thinking about.  But before the project adopts content from either of those posts as an official or semi-official description of how the system works, I would want the description to be reviewed for accuracy by bytemaster, vikram or another developer who's actually written or reviewed the patches which implement the new mechanics.

[1] The term "Mandatory Upgrade" is preferred to "Hardfork" for marketing reasons.

[2] https://bitsharestalk.org/index.php?topic=7067.30

[3] https://github.com/dacsunlimited/bitsharesx/releases

[4] https://bitsharestalk.org/index.php?topic=9029.msg117125#msg117125

[5] https://bitsharestalk.org/index.php?topic=9159.msg118819#msg118819
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk

Offline oco101

  • Hero Member
  • *****
  • Posts: 568
    • View Profile
Re: Feature request: More detailed upgrade notes
« Reply #1 on: September 22, 2014, 03:07:25 AM »
+1 +1  +1 +1 +1  +1+1 +1  +1

Offline James212

  • Sr. Member
  • ****
  • Posts: 312
    • View Profile
Re: Feature request: More detailed upgrade notes
« Reply #2 on: September 22, 2014, 03:59:42 AM »

Users are frustrated by the lack of communication surrounding the new v0.4.16 shorting mechanics:

yea it would be nice to know things like this BEFORE or at least once they are implemented......idk maybe under some kind changes to this version or something like that.

I realize developer time is at a premium, but there should be some official announcement channel to tell us about the changes in upcoming Mandatory Upgrades [1], such as the new shorting mechanics.

I am aware of two existing channels for this purpose, but one of them does not mention short issues at all [2], and the other merely says "Revised consensus market engine shorting mechanics" [3].

If we want traders and investors to take our markets seriously and make investments in our ecosystem, we need to provide a channel to tell them about major changes like this one.  Without requiring them to wade through many pages of irrelevant forum discussion, of which only a small handful of posts will contain accurate, up-to-date information.

IMHO such a channel should have an RSS feed and anyone should be able to submit improvements to the descriptions, but the description should be approved by the developers for accuracy, brevity and clarity before it can be posted.  I like the idea of using a Github repo with version-controlled Markdown files and accepting pull requests.  But a wiki, forum thread, or documentation file(s) in the main BitShares repo would also be reasonable choices.

My post in the pre-change discussion [4] or the help that I gave to the above frustrated user [5] contains the sort of description of the mechanics I'm thinking about.  But before the project adopts content from either of those posts as an official or semi-official description of how the system works, I would want the description to be reviewed for accuracy by bytemaster, vikram or another developer who's actually written or reviewed the patches which implement the new mechanics.

[1] The term "Mandatory Upgrade" is preferred to "Hardfork" for marketing reasons.

[2] https://bitsharestalk.org/index.php?topic=7067.30

[3] https://github.com/dacsunlimited/bitsharesx/releases

[4] https://bitsharestalk.org/index.php?topic=9029.msg117125#msg117125

[5] https://bitsharestalk.org/index.php?topic=9159.msg118819#msg118819

 +5% +5%
BTS: theangelwaveproject

Offline Gentso1

Re: Feature request: More detailed upgrade notes
« Reply #3 on: September 22, 2014, 03:27:10 PM »
They could have put it up in github or under the important announcements thread, either of those are easy to follow and would allow us to see the changes.

Offline iHashFury

Re: Feature request: More detailed upgrade notes
« Reply #4 on: September 22, 2014, 04:33:48 PM »
 +5%
http://j.mp/ALTCAP - http://bit.ly/BitShares-Exchange - https://t.me/BitSharesDEX - http://bit.ly/ihashfury

"If you owe a bank thousands, you have a problem; owe a bank millions, the bank has a problem" ;)

Offline vikram

Re: Feature request: More detailed upgrade notes
« Reply #5 on: September 22, 2014, 04:46:32 PM »
I agree this needs to be addressed. It has been ignored thus far due to all the devs being so busy combined with how rapidly all the rules have been changing.

I think in the short-term, it may suffice to provide a link in the changelog to any threads explaining the changes, e.g.:
- "Revised consensus market engine shorting mechanics (see https://bitsharestalk.org/index.php?topic=9029.msg116902#msg116902 for details)"

A more proper solution might be a blog with an RSS feed as you mentioned. What do you think about a GitHub website (https://pages.github.com/) for BTSX? There could be a post for each new version. People can submit pull requests and it appears that you should be able to add an rss feed (https://github.com/snaptortoise/jekyll-rss-feeds).

Offline theoretical

Re: Feature request: More detailed upgrade notes
« Reply #6 on: September 22, 2014, 05:08:12 PM »
A more proper solution might be a blog with an RSS feed as you mentioned. What do you think about a GitHub website (https://pages.github.com/) for BTSX? There could be a post for each new version. People can submit pull requests and it appears that you should be able to add an rss feed (https://github.com/snaptortoise/jekyll-rss-feeds).

Depends on how easy it is to get the RSS feed working.

The good part of a blog:  The marketing guys can make it look pretty, and you can point your own domain to it (e.g. blog.bitshares.org).

The good part of version-controlled Markdown:  It requires less effort to get it running right away.

The project already has a blog at http://bitshares.org/blog/ but I don't know how easy it is for people to contribute posts to that, or whether that blog is targeted to a different audience.
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk

Offline bitsapphire

Re: Feature request: More detailed upgrade notes
« Reply #7 on: September 22, 2014, 05:37:05 PM »
I agree this needs to be addressed. It has been ignored thus far due to all the devs being so busy combined with how rapidly all the rules have been changing.

I think in the short-term, it may suffice to provide a link in the changelog to any threads explaining the changes, e.g.:
- "Revised consensus market engine shorting mechanics (see https://bitsharestalk.org/index.php?topic=9029.msg116902#msg116902 for details)"

A more proper solution might be a blog with an RSS feed as you mentioned. What do you think about a GitHub website (https://pages.github.com/) for BTSX? There could be a post for each new version. People can submit pull requests and it appears that you should be able to add an rss feed (https://github.com/snaptortoise/jekyll-rss-feeds).

We could also send an email newsletter subscription request to all bitsharestalk.org subscribers. That way very important announcements get to everybody.
Register and get your personal Moonstone Wallet Beta here: https://moonstone.io/login-register.html

Offline theoretical

Re: Feature request: More detailed upgrade notes
« Reply #8 on: September 22, 2014, 05:48:46 PM »
We could also send an email newsletter subscription request to all bitsharestalk.org subscribers. That way very important announcements get to everybody.

Please don't rely on this.  I used a throwaway email to register, so I never check it.  Something publicly accessible like a forum thread would be better.
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk

 

Google+