New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove FTT legacy, test comment #5

Merged
merged 1 commit into from Oct 2, 2017

Conversation

Projects
None yet
2 participants
@dvorkbod
Contributor

dvorkbod commented Sep 24, 2017

OK, let's see if this works.
I made a small change to "changing rules" sentence. It is still not grammatically very elegant, but content is most important now.

In the meantime, it seems some changes were made to the original text.

@nbabenko

Added comments directly on a changeset, please let me know if you cannot find it, you should be notified about it I guess.

Rest of changes are fine (thank you for fixes :) ), let me know if thats it, I'll merge this pull request.

In order to do this, community should be able to change also the rules how decisions are made in the community also.
In order to do this, the community should be able to change also the rules how decisions are made in the community.
> The sentence above seems out of place. Do you consider the AtomChange blockchain already such a change? If you want to ties this in to "forks are a way, but they are too divisive", I guess we can adapt this section.

This comment has been minimized.

@nbabenko

nbabenko Sep 24, 2017

Contributor

We can also discuss in comments to changes)
Like this) You can find necessary changeset to comment on opening file -> Blame -> going to specific line and its changeset.
Maybe you will find more convenient way.

Regarding this specific question - yes, the point was that ultimately in an open network you cannot force community to do something it does not want to do, because if somebody will force, community will fork away. Forks are not totally bad, but in order to avoid unnecessary forks, community should have effective governance, and here we are with our project - trying to implement effective governance.

@nbabenko

nbabenko Sep 24, 2017

Contributor

We can also discuss in comments to changes)
Like this) You can find necessary changeset to comment on opening file -> Blame -> going to specific line and its changeset.
Maybe you will find more convenient way.

Regarding this specific question - yes, the point was that ultimately in an open network you cannot force community to do something it does not want to do, because if somebody will force, community will fork away. Forks are not totally bad, but in order to avoid unnecessary forks, community should have effective governance, and here we are with our project - trying to implement effective governance.

@nbabenko

This comment has been minimized.

Show comment
Hide comment
@nbabenko

nbabenko Sep 24, 2017

Contributor

BTW, you can do pull requests not only from your personal copy of repo, but from just a branch of the same repo.

Contributor

nbabenko commented Sep 24, 2017

BTW, you can do pull requests not only from your personal copy of repo, but from just a branch of the same repo.

@nbabenko nbabenko merged commit 79a9222 into atomchange:master Oct 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment