starred/tview

Fork 0

mirror of https://github.com/rivo/tview.git synced 2026-04-27 05:45:49 +03:00

*.md #638

New issue

Closed

opened 2026-03-04 01:06:40 +03:00 by kerem · 5 comments

kerem commented

2026-03-04 01:06:40 +03:00

Owner

Originally created by @verdverm on GitHub (Aug 30, 2023).
Original GitHub issue: https://github.com/rivo/tview/issues/876

Just wanted to float the idea by, it would make contributing words or examples easier and part of the pull request workflow.

Thoughts?

Originally created by @verdverm on GitHub (Aug 30, 2023). Original GitHub issue: https://github.com/rivo/tview/issues/876 Just wanted to float the idea by, it would make contributing words or examples easier and part of the pull request workflow. Thoughts?

kerem closed this issue

2026-03-04 01:06:40 +03:00

kerem commented

2026-03-04 01:06:41 +03:00

Author

Owner

@rivo commented on GitHub (Sep 16, 2023):

I don't want to add Wiki contents into this package so it would have to be a separate repo. But that means keeping track of another repo for me. So, to be honest, given the little changes that have been requested for the Wiki so far, it's probably easier to just open up an issue here. This has worked quite well in the past.

@rivo commented on GitHub (Sep 16, 2023): I don't want to add Wiki contents into this package so it would have to be a separate repo. But that means keeping track of another repo for me. So, to be honest, given the little changes that have been requested for the Wiki so far, it's probably easier to just open up an issue here. This has worked quite well in the past.

kerem commented

2026-03-04 01:06:41 +03:00

Author

Owner

@verdverm commented on GitHub (Sep 16, 2023):

given the little changes that have been requested

The wiki is the cause, the change rate is the symptom, that's why I'm asking

... and now remembering why I forked this repo 5 years ago and again this year, symptom of another cause...

@verdverm commented on GitHub (Sep 16, 2023): > given the little changes that have been requested The wiki is the cause, the change rate is the symptom, that's why I'm asking ... and now remembering why I forked this repo 5 years ago and again this year, symptom of another cause...

kerem commented

2026-03-04 01:06:41 +03:00

Author

Owner

@rivo commented on GitHub (Sep 16, 2023):

the change rate is the symptom

Do you think so? My experience is that people generally don't like to write documentation. Let's say, if you volunteer to be in charge of the Wiki and turn it into a major information resource for tview users, i.e. write a lot of the content yourself, I might actually think about it.

Btw, I'm also frequently getting a comment along the lines of, "I did not know there was a Wiki."

@rivo commented on GitHub (Sep 16, 2023): > the change rate is the symptom Do you think so? My experience is that people generally don't like to write documentation. Let's say, if you volunteer to be in charge of the Wiki and turn it into a major information resource for `tview` users, i.e. write a lot of the content yourself, I might actually think about it. Btw, I'm also frequently getting a comment along the lines of, "I did not know there was a Wiki."

kerem commented

2026-03-04 01:06:41 +03:00

Author

Owner

@verdverm commented on GitHub (Sep 17, 2023):

Have you seen how many tview forks are out there? People are making little fixes or changes and not thinking to contribute back. There are some really great improvements out there, even major overhauls, and people trying to bring them all together into one place. The community is more active around the forks from what I can tell.

Have you ever wondered why that is?

(I ask only to pose a question for reflection, this project has an unusual & interesting history, and as one of these people who have forked and not looked back, I certainly have a few opines on the matter)

@verdverm commented on GitHub (Sep 17, 2023): Have you seen how many `tview` forks are out there? People are making little fixes or changes and not thinking to contribute back. There are some really great improvements out there, even major overhauls, and people trying to bring them all together into one place. The community is more active around the forks from what I can tell. Have you ever wondered why that is? _(I ask only to pose a question for reflection, this project has an unusual & interesting history, and as one of these people who have forked and not looked back, I certainly have a few opines on the matter)_

kerem commented

2026-03-04 01:06:41 +03:00

Author

Owner

@rivo commented on GitHub (Sep 17, 2023):

I fail to see how any of this is related to putting the Wiki source in a repo. I haven't seen anyone put up an alternative documentation resource for tview. (If you know one, I'd be very interested in seeing it.)

Regarding the forks, which I assume is a separate topic you brought up, sure, that's what Open Source is all about, isn't it? If people don't like the direction this project is going, they can fork it and present their own opinion on the matter. If people find that one of these alternatives better suits their needs, they will use that instead. I don't have a problem with that.

As I can dedicate only my free time to this project (of which I have very little to begin with), I will always keep my workflow streamlined, while keeping the project stable, making improvements, and adding new features every now and then. All of this for the long run. I've seen forks on day 1 which nobody talks about anymore. Abandonware is rampant. Unless I get sick or something, that's not going to happen with tview.

@rivo commented on GitHub (Sep 17, 2023): I fail to see how any of this is related to putting the Wiki source in a repo. I haven't seen anyone put up an alternative documentation resource for `tview`. (If you know one, I'd be very interested in seeing it.) Regarding the forks, which I assume is a separate topic you brought up, sure, that's what Open Source is all about, isn't it? If people don't like the direction this project is going, they can fork it and present their own opinion on the matter. If people find that one of these alternatives better suits their needs, they will use that instead. I don't have a problem with that. As I can dedicate only my free time to this project (of which I have very little to begin with), I will always keep my workflow streamlined, while keeping the project stable, making improvements, and adding new features every now and then. All of this for the long run. I've seen forks on day 1 which nobody talks about anymore. Abandonware is rampant. Unless I get sick or something, that's not going to happen with `tview`.