Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
There are status tags for bugs and feature requests to declare that the lifecycle of a bug and a feature request was completed, but apparently, there isn't something equivalent for discussions. Di...
#3: Post edited
by
Wicket
·
2023-06-30T14:50:52Z (over 1 year ago)
Added Progress Update section
- There are status tags for bugs and feature requests to declare that the lifecycle of a bug and a feature request was completed, but apparently, there isn't something equivalent for discussions.
- Discussions are usually used to propose something that might make sense when that discussion was started. When the circumstances change, some discussions do not make sense to continue open to getting comments and answers. I.E. 3-2 years ago,
- - It was suggested to migrate "office suite questions" from Software Development to Power Users.
- - I have not found a trace of the migration done; I have found multiple questions about spreadsheets, one of the basic apps of the most popular "office suite" in Software Development but not in Power Users.
- It's worth mentioning that spreadsheets are one of the apps most commonly used for end-user development / programming. Also, it's worth mentioning that since a few years ago, more software vendors have offered "low code / no code" platforms to develop software. Writing spreadsheet formulas and using "low code / no code" platforms might lead to extended discussions, i.e., about if they belong to Software Development, to Power Users or both; I usually participate in them. I have found that in these discussions "always", some people disagree and that people join the discussion years after the discussion started.
- So, I'm looking at how is the lifecycle of discussions handled in Codidact and if there is a way to identify when a question is not worthy of being "refloated" and when a discussion is perpetually open to having new answers and comments.
- There are status tags for bugs and feature requests to declare that the lifecycle of a bug and a feature request was completed, but apparently, there isn't something equivalent for discussions.
- Discussions are usually used to propose something that might make sense when that discussion was started. When the circumstances change, some discussions do not make sense to continue open to getting comments and answers. I.E. 3-2 years ago,
- - It was suggested to migrate "office suite questions" from Software Development to Power Users.
- - I have not found a trace of the migration done; I have found multiple questions about spreadsheets, one of the basic apps of the most popular "office suite" in Software Development but not in Power Users.
- It's worth mentioning that spreadsheets are one of the apps most commonly used for end-user development / programming. Also, it's worth mentioning that since a few years ago, more software vendors have offered "low code / no code" platforms to develop software. Writing spreadsheet formulas and using "low code / no code" platforms might lead to extended discussions, i.e., about if they belong to Software Development, to Power Users or both; I usually participate in them. I have found that in these discussions "always", some people disagree and that people join the discussion years after the discussion started.
- So, I'm looking at how is the lifecycle of discussions handled in Codidact and if there is a way to identify when a question is not worthy of being "refloated" and when a discussion is perpetually open to having new answers and comments.
- ---
- #### Progress Update
- I found here, in Codidact Meta, [Should there be a forum-like place for the Codidact network?](https://meta.codidact.com/posts/278036). It is a discussion that started 3 years ago, it hasn't been answered, but it has a comment thread. The last comment believes discussions are feasible only if they have a proper post type.
- I will refloat this question :)
#2: Post edited
by
Wicket
·
2023-06-22T15:58:08Z (over 1 year ago)
- There are status tags for bugs and feature requests to declare that the lifecycle of a bug and a feature request was completed, but apparently, there isn't something equivalent for discussions.
- Discussions are usually used to propose something that might make sense when that discussion was started. When the circumstances change, some discussions do not make sense to continue open to getting comments and answers. I.E. 3-2 years ago,
- - It was suggested to migrate "office suite questions" from Software Development to Power Users.
- - I have not found a trace of the migration done; I have found multiple questions about spreadsheets, one of the basic apps of the most popular "office suite" in Software Development but not in Power Users.
It's worth mentioning that spreadsheets are one of the apps most commonly used for end-user development / programming. Also, it's worth mentioning that since a few years ago, more software vendors have offered "low code / no code" platforms to develop software. Writing spreadsheet formulas and using "low code / no code" platforms might lead to extended discussions, and I usually participate in them. I have found that in these discussions always, some people disagree and that people join the discussion years after the discussion started.- So, I'm looking at how is the lifecycle of discussions handled in Codidact and if there is a way to identify when a question is not worthy of being "refloated" and when a discussion is perpetually open to having new answers and comments.
- There are status tags for bugs and feature requests to declare that the lifecycle of a bug and a feature request was completed, but apparently, there isn't something equivalent for discussions.
- Discussions are usually used to propose something that might make sense when that discussion was started. When the circumstances change, some discussions do not make sense to continue open to getting comments and answers. I.E. 3-2 years ago,
- - It was suggested to migrate "office suite questions" from Software Development to Power Users.
- - I have not found a trace of the migration done; I have found multiple questions about spreadsheets, one of the basic apps of the most popular "office suite" in Software Development but not in Power Users.
- It's worth mentioning that spreadsheets are one of the apps most commonly used for end-user development / programming. Also, it's worth mentioning that since a few years ago, more software vendors have offered "low code / no code" platforms to develop software. Writing spreadsheet formulas and using "low code / no code" platforms might lead to extended discussions, i.e., about if they belong to Software Development, to Power Users or both; I usually participate in them. I have found that in these discussions "always", some people disagree and that people join the discussion years after the discussion started.
- So, I'm looking at how is the lifecycle of discussions handled in Codidact and if there is a way to identify when a question is not worthy of being "refloated" and when a discussion is perpetually open to having new answers and comments.
#1: Initial revision
by
Wicket
·
2023-06-22T15:55:51Z (over 1 year ago)
How is the lifecycle of discussions handled in Codidact Meta?
There are status tags for bugs and feature requests to declare that the lifecycle of a bug and a feature request was completed, but apparently, there isn't something equivalent for discussions. Discussions are usually used to propose something that might make sense when that discussion was started. When the circumstances change, some discussions do not make sense to continue open to getting comments and answers. I.E. 3-2 years ago, - It was suggested to migrate "office suite questions" from Software Development to Power Users. - I have not found a trace of the migration done; I have found multiple questions about spreadsheets, one of the basic apps of the most popular "office suite" in Software Development but not in Power Users. It's worth mentioning that spreadsheets are one of the apps most commonly used for end-user development / programming. Also, it's worth mentioning that since a few years ago, more software vendors have offered "low code / no code" platforms to develop software. Writing spreadsheet formulas and using "low code / no code" platforms might lead to extended discussions, and I usually participate in them. I have found that in these discussions always, some people disagree and that people join the discussion years after the discussion started. So, I'm looking at how is the lifecycle of discussions handled in Codidact and if there is a way to identify when a question is not worthy of being "refloated" and when a discussion is perpetually open to having new answers and comments.