Szymon Gołębiewski 13 Years Ago I think you should also sort new tickets. For example look at this: http://issues.liferay.com/browse/LPS-14009Juan wrote that this is moved to backlog but maybe it would be better point this user to alternative solution and close this ticket like this "For such functionality we recommend to use other workflow engine (Intalio, jBPML) and integrate them with liferay through API". It's nice to have a backlog with "what can we develop for new release" but IMHO it is better to have something like this http://getsatisfaction.com/worksmartlabs/products/worksmartlabs_cardiotrainer?sort=most_me_toos&style=topics Please sign in to reply. Reply as... Cancel James Falkner Szymon Gołębiewski 13 Years Ago We're not as much worried about closing improvement or new feature tickets as we are with resolving the major and critical bugs because we want to make sure the issues reported against old versions are no longer issues (either they are fixed or are not really issues).Your idea for a "leaderboard" for new features is a good one, and I'm working on something like that. Currently we have the "Suggestions and Improvements" Wiki which we routinely convert into tickets, but the interface could be streamlined into a linear list. Another good example (thanks to Juan) is http://brainstorm.ubuntu.com Please sign in to reply. Reply as... Cancel
James Falkner Szymon Gołębiewski 13 Years Ago We're not as much worried about closing improvement or new feature tickets as we are with resolving the major and critical bugs because we want to make sure the issues reported against old versions are no longer issues (either they are fixed or are not really issues).Your idea for a "leaderboard" for new features is a good one, and I'm working on something like that. Currently we have the "Suggestions and Improvements" Wiki which we routinely convert into tickets, but the interface could be streamlined into a linear list. Another good example (thanks to Juan) is http://brainstorm.ubuntu.com Please sign in to reply. Reply as... Cancel
jelmer kuperus 13 Years Ago That's probably a good first step. But what think is essential is that bugs are looked at more quickly. People typically file bugs while working on a project. if 6 months later somebody finally gets around to look at the bug. This person will have moved on to other things and will no longer care about the issue.As it stands now the situation is pretty dire with critical issues going unresolved for months and community patches sitting idle in jira. Even when a fix is trivial and obvious like AUI-267 Please sign in to reply. Reply as... Cancel James Falkner jelmer kuperus 13 Years Ago I agree the faster issues are looked at the better chance they have of getting resolved, since the submitter is still interested in getting it fixed.I hope that we can get community members to start pushing these fixes themselves (following the process of course) instead of relying on Liferay, Inc. employees to do it. This is already happening on a smaller scale, but I hope to widen it in the next 3-4 months. Please sign in to reply. Reply as... Cancel jelmer kuperus James Falkner 13 Years Ago If you want to encourage community members to start pushing fixes then again being responsive is key.There is nothing more frustrating than going the extra mile to submit a patch and seeing it ignored release after releaseFor example LPS-12203 is an example of an obvious problem that is solved by an obvious 1 line fix. Yet it lingered in jira for a very long timeI know that the people at liferay are doing what they can but if you want to grow community participation. This has to improve Please sign in to reply. Reply as... Cancel James Falkner jelmer kuperus 13 Years Ago "I know that the people at liferay are doing what they can but if you want to grow community participation. This has to improve."Agreed. Please sign in to reply. Reply as... Cancel
James Falkner jelmer kuperus 13 Years Ago I agree the faster issues are looked at the better chance they have of getting resolved, since the submitter is still interested in getting it fixed.I hope that we can get community members to start pushing these fixes themselves (following the process of course) instead of relying on Liferay, Inc. employees to do it. This is already happening on a smaller scale, but I hope to widen it in the next 3-4 months. Please sign in to reply. Reply as... Cancel jelmer kuperus James Falkner 13 Years Ago If you want to encourage community members to start pushing fixes then again being responsive is key.There is nothing more frustrating than going the extra mile to submit a patch and seeing it ignored release after releaseFor example LPS-12203 is an example of an obvious problem that is solved by an obvious 1 line fix. Yet it lingered in jira for a very long timeI know that the people at liferay are doing what they can but if you want to grow community participation. This has to improve Please sign in to reply. Reply as... Cancel James Falkner jelmer kuperus 13 Years Ago "I know that the people at liferay are doing what they can but if you want to grow community participation. This has to improve."Agreed. Please sign in to reply. Reply as... Cancel
jelmer kuperus James Falkner 13 Years Ago If you want to encourage community members to start pushing fixes then again being responsive is key.There is nothing more frustrating than going the extra mile to submit a patch and seeing it ignored release after releaseFor example LPS-12203 is an example of an obvious problem that is solved by an obvious 1 line fix. Yet it lingered in jira for a very long timeI know that the people at liferay are doing what they can but if you want to grow community participation. This has to improve Please sign in to reply. Reply as... Cancel James Falkner jelmer kuperus 13 Years Ago "I know that the people at liferay are doing what they can but if you want to grow community participation. This has to improve."Agreed. Please sign in to reply. Reply as... Cancel
James Falkner jelmer kuperus 13 Years Ago "I know that the people at liferay are doing what they can but if you want to grow community participation. This has to improve."Agreed. Please sign in to reply. Reply as... Cancel
Szymon Gołębiewski 13 Years Ago And another question: how can we help you with "I-forgot-that-there-is-a-forum-for-questions" bugs such as LPS-14052? Please sign in to reply. Reply as... Cancel James Falkner Szymon Gołębiewski 13 Years Ago We need to add some Liferay-specific content to the JIRA workflow for creating new bugs and such, to remind folks to search first. For extra credit, before submitting a new issue, we could show a list of "possibly related issues" (based on the info entered so far in the workflow). Hmm. There is an upcoming upgrade of JIRA planned, I'll ask if this is possible. Please sign in to reply. Reply as... Cancel
James Falkner Szymon Gołębiewski 13 Years Ago We need to add some Liferay-specific content to the JIRA workflow for creating new bugs and such, to remind folks to search first. For extra credit, before submitting a new issue, we could show a list of "possibly related issues" (based on the info entered so far in the workflow). Hmm. There is an upcoming upgrade of JIRA planned, I'll ask if this is possible. Please sign in to reply. Reply as... Cancel
jelmer kuperus 13 Years Ago I'd like to point out that currently it's not possible for the reporter of an issue to close a bug when he determines that an issue has been resolved Please sign in to reply. Reply as... Cancel James Falkner jelmer kuperus 13 Years Ago "I'd like to point out that currently it's not possible for the reporter of an issue to close a bug when he determines that an issue has been resolved "I think this is a bug that needs to be fixed! Please sign in to reply. Reply as... Cancel
James Falkner jelmer kuperus 13 Years Ago "I'd like to point out that currently it's not possible for the reporter of an issue to close a bug when he determines that an issue has been resolved "I think this is a bug that needs to be fixed! Please sign in to reply. Reply as... Cancel