by Jim » Sun Mar 27, 2005 10:55 pm
Chris wrote:I don't even understand what he said.
Jim wrote:How about letting people vote on bugs? If every post in this forum automatically included a poll "great idea", "good idea", "OK idea", "bad idea", and "terrible idea", maybe the controversial (and sometimes just plain bad or dumb) requests would be voted down.
Vote on bugs? If you mean feature requests, we can.. just setup a poll with the request. Can anonymous guest users answer the poll, though? If they can, it wouldn't be worth it. I'd also be wary of people who'd vote immediately "no", then when the idea evolves into something more practical they couldn't change the vote.
I mis-typed. I meant feature requests, although voting is also done more generally for any bugs with many larger projects to let developers know what is bothering users the most. The way that is usually done is that you can only vote that you agree (or want it fixed), with no allowance for voting against bugs or feature requests.
Chris wrote:
Whatever, I just wish that ZDoom's development were more transparent.
Wouldn't that mean fewer people to help, then?
Chris, since you are not a native speaker of English, I understand your confusion somewhat. However, one of the meanings for transparent is
Chris wrote:
There are two reasons that everyone forks ZDoom
I don't even know what this is supposed to mean.
Some example of forks of ZDoom are ZDaemon, Skulltag, CSDoom, etc. In general, a fork is when someone takes a snapshot of the code and modifies it to suit their own tastes without having those changes merged back into the original project.
Chris wrote:it is difficult to contribute to the project when you cannot see the current state of source code, or even frequent snapshots. Remember,
SourceForge.net is a free host, with automatic bug management/feature request areas, web-browseable cvs, and many other things.
Which is exactly why being more transparent/invisible wouldn't be a good thing. Why would you wish for ZDoom development to be more transparent, then turn around and say you wish it was more open and visible? It would have to be one or the other..
See my earlier comment on your misunderstanding.
[quote="Chris"]I don't even understand what he said.
[quote="Jim"]How about letting people vote on bugs? If every post in this forum automatically included a poll "great idea", "good idea", "OK idea", "bad idea", and "terrible idea", maybe the controversial (and sometimes just plain bad or dumb) requests would be voted down.[/quote]
Vote on bugs? If you mean feature requests, we can.. just setup a poll with the request. Can anonymous guest users answer the poll, though? If they can, it wouldn't be worth it. I'd also be wary of people who'd vote immediately "no", then when the idea evolves into something more practical they couldn't change the vote.
[/quote]
I mis-typed. I meant feature requests, although voting is also done more generally for any bugs with many larger projects to let developers know what is bothering users the most. The way that is usually done is that you can only vote that you agree (or want it fixed), with no allowance for voting against bugs or feature requests.
[quote="Chris"]
[quote]Whatever, I just wish that ZDoom's development were more transparent.[/quote]
Wouldn't that mean fewer people to help, then?
[/quote]
Chris, since you are not a native speaker of English, I understand your confusion somewhat. However, one of the meanings for transparent is
[quote="[url]http://dictionary.reference.com/search?q=transparent[/url]"]
4.
a. Easily seen through or detected; obvious: transparent lies.
b. Free from guile; candid or [b]open[/b]: transparent sincerity.
[/quote]
[quote="Chris"]
[quote]There are two reasons that every[i][b]one[/b][/i] forks ZDoom[/quote]
I don't even know what this is supposed to mean.[/quote]
Some example of forks of ZDoom are ZDaemon, Skulltag, CSDoom, etc. In general, a fork is when someone takes a snapshot of the code and modifies it to suit their own tastes without having those changes merged back into the original project.
[quote="Chris"][quote]it is difficult to contribute to the project when you cannot see the current state of source code, or even frequent snapshots. Remember, [url=http://www.sourceforge.net]SourceForge.net[/url] is a free host, with automatic bug management/feature request areas, web-browseable cvs, and many other things.[/quote]
Which is exactly why being more transparent/invisible wouldn't be a good thing. Why would you wish for ZDoom development to be more transparent, then turn around and say you wish it was more open and visible? It would have to be one or the other..[/quote]
See my earlier comment on your misunderstanding.