All ideas peoples writtes on bugs.kde.org, it creates a lot of unnecessary and not related to bugs. I suggest to creating - requests.kde.org There will be a separate site to Bugs report and site to requests of ideas. This will remove confusion In Get Involved page will need to create a new header - "Requesting of ideas".
Can you describe: - The problem resulting from handling requests and wishlist items on bugs.kde.org - The benefits to both bug reporters and developers from splitting it up like you're requesting
(In reply to Nate Graham from comment #1) > Can you describe: > - The problem resulting from handling requests and wishlist items on > bugs.kde.org > - The benefits to both bug reporters and developers from splitting it up > like you're requesting Need to make a new site, with a kool design to match https://phabricator.kde.org/T10827. Need to create different sections for ideas: Text Requests Mokups And for different projects: Plasma Desktop Plasma Mobile KDE Applications KDE neon
I'm not asking for implementation details, but rather for an explanation regarding why this is a good idea in the first place. :)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Bug Janitor Service from comment #4) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! Ok
You still need to provide the following information: > I'm not asking for implementation details, but rather for an explanation > regarding why this is a good idea in the first place. :)
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!