jelmer kuperus 13 Years Ago Ok sign me up in-depth investigation and non-trivial changes sounds more interesting than a relatively easy challenge though. Want me to take a stab at LPS-12988? Please sign in to reply. Reply as... Cancel James Falkner jelmer kuperus 13 Years Ago Awesome Jelmer! I'll add you to the team. Sure, please take a crack at LPS-12988. I looked at this morning, it looks like for the Activities portlet, it is implemented in a taglib and rendered as part of the render phase of that portlet, whereas with other feeds (e.g. blog feeds), it's implemented as a portlet resource request. For some reason, in the taglib code, even though setContentType() is called to set the content type to text/xml, it's not taking effect (possibly because the response writer has already been established by the time the taglib's jsp code is called). That's about as far as I got. Please sign in to reply. Reply as... Cancel
James Falkner jelmer kuperus 13 Years Ago Awesome Jelmer! I'll add you to the team. Sure, please take a crack at LPS-12988. I looked at this morning, it looks like for the Activities portlet, it is implemented in a taglib and rendered as part of the render phase of that portlet, whereas with other feeds (e.g. blog feeds), it's implemented as a portlet resource request. For some reason, in the taglib code, even though setContentType() is called to set the content type to text/xml, it's not taking effect (possibly because the response writer has already been established by the time the taglib's jsp code is called). That's about as far as I got. Please sign in to reply. Reply as... Cancel
Jaromir Hamala 13 Years Ago Hello James, I would like to participate. Please sign in to reply. Reply as... Cancel
Tomas Polesovsky 13 Years Ago Hey, that's very very nice work for first try, team!I think we can have some more challenging tasks in a backlog (like LPS-12988). Maybe it takes more effort to fix it but if community really want it, we shouldn't be afraid and at least try to know our limits (because reward can be sweet ) In the worst case we don't solve it ;)Btw. James, is it possible to ping Jenny to accept LPS-14351? Thank you. Please sign in to reply. Reply as... Cancel James Falkner Tomas Polesovsky 13 Years Ago I'm fine with it if everyone else is.. just so long as you all don't get fired for spending all your days fixing our bugs I'll ping Jenny via email, but our fallback that I just discovered is that I can change the bug so that *you* are the submitter, then you can "accept" your own solution If the original submitter of a bug doesn't respond within a week, I'll just do that. Please sign in to reply. Reply as... Cancel Tomas Polesovsky James Falkner 13 Years Ago All my days fixing bugs? Challenge accepted! No, I'm just kidding I think it's everyone's responsibility which ticket to choose and to do it in the free time.Thank you, I'll just wait what happen to LPS-14351 Please sign in to reply. Reply as... Cancel Juan Fernández Tomas Polesovsky 13 Years Ago Amazing job, 100ers!! You're the sugar in our community! Please sign in to reply. Reply as... Cancel
James Falkner Tomas Polesovsky 13 Years Ago I'm fine with it if everyone else is.. just so long as you all don't get fired for spending all your days fixing our bugs I'll ping Jenny via email, but our fallback that I just discovered is that I can change the bug so that *you* are the submitter, then you can "accept" your own solution If the original submitter of a bug doesn't respond within a week, I'll just do that. Please sign in to reply. Reply as... Cancel Tomas Polesovsky James Falkner 13 Years Ago All my days fixing bugs? Challenge accepted! No, I'm just kidding I think it's everyone's responsibility which ticket to choose and to do it in the free time.Thank you, I'll just wait what happen to LPS-14351 Please sign in to reply. Reply as... Cancel Juan Fernández Tomas Polesovsky 13 Years Ago Amazing job, 100ers!! You're the sugar in our community! Please sign in to reply. Reply as... Cancel
Tomas Polesovsky James Falkner 13 Years Ago All my days fixing bugs? Challenge accepted! No, I'm just kidding I think it's everyone's responsibility which ticket to choose and to do it in the free time.Thank you, I'll just wait what happen to LPS-14351 Please sign in to reply. Reply as... Cancel Juan Fernández Tomas Polesovsky 13 Years Ago Amazing job, 100ers!! You're the sugar in our community! Please sign in to reply. Reply as... Cancel
Juan Fernández Tomas Polesovsky 13 Years Ago Amazing job, 100ers!! You're the sugar in our community! Please sign in to reply. Reply as... Cancel
Boubker TAGNAOUTI 13 Years Ago Nice job everybody...I added some JIRA tickets to the 100PC backlog to prepare the next sprint!We can choose from now the issue we want to deal with ;-) Please sign in to reply. Reply as... Cancel Deb Troxel Boubker TAGNAOUTI 13 Years Ago Is there a JIRA filter to see only the available (pre-screened as not too major) backlog bugs to choose from?The "100PC Papercuts" filter includes those that have been worked on, so it's not easy to tell which to pick from, and "100 PC Candidates" is pretty much every open bug.Maybe we could add the Sprint # to the comment when a bug is claimed and then exclude those with 'Sprint' in the comment field to create a 100 PC Available filter? Please sign in to reply. Reply as... Cancel James Falkner Deb Troxel 13 Years Ago - Edited Yeah, the "100PC Papercuts" filter are those we've already selected to work on (our backlog).The "100 PC Candidates" are basically all unresolved bugs, but filters out those that are already in the Liferay engineering pipeline (associated with a specific sprint). Deb, I like your idea of separating the "backlog" bugs from the ones that have been selected for a specific sprint. If only we had the JIRA upgrade completed, this could all be solved with tags. But the interim, yeah, how about this:For bugs we consider potential papercuts (but aren't associated with a specific 100PC sprint), we use this phrase: "This issue is a backlog candidate for the 100 PaperCuts program. Please consider participating! See http://liferay.com/community/100-papercuts".For bugs that we select for a specific sprint, we put this:"This issue is currently being addressed in Sprint X of the 100 PaperCuts program. Please see http://liferay.com/community/100-papercuts"That way, the first phrase doesn't imply that the original submitter or person currently assigned should ignore it or that it will *definitely* be fixed. The second one does. Please sign in to reply. Reply as... Cancel James Falkner Deb Troxel 13 Years Ago BTW, our JIRA upgrade was completed over the weekend, so we can have arbitrary tags on tickets now.. yay!!!!!! I'll work on using the tagging system going forward (and converting the existing tickets we have identified). Please sign in to reply. Reply as... Cancel
Deb Troxel Boubker TAGNAOUTI 13 Years Ago Is there a JIRA filter to see only the available (pre-screened as not too major) backlog bugs to choose from?The "100PC Papercuts" filter includes those that have been worked on, so it's not easy to tell which to pick from, and "100 PC Candidates" is pretty much every open bug.Maybe we could add the Sprint # to the comment when a bug is claimed and then exclude those with 'Sprint' in the comment field to create a 100 PC Available filter? Please sign in to reply. Reply as... Cancel James Falkner Deb Troxel 13 Years Ago - Edited Yeah, the "100PC Papercuts" filter are those we've already selected to work on (our backlog).The "100 PC Candidates" are basically all unresolved bugs, but filters out those that are already in the Liferay engineering pipeline (associated with a specific sprint). Deb, I like your idea of separating the "backlog" bugs from the ones that have been selected for a specific sprint. If only we had the JIRA upgrade completed, this could all be solved with tags. But the interim, yeah, how about this:For bugs we consider potential papercuts (but aren't associated with a specific 100PC sprint), we use this phrase: "This issue is a backlog candidate for the 100 PaperCuts program. Please consider participating! See http://liferay.com/community/100-papercuts".For bugs that we select for a specific sprint, we put this:"This issue is currently being addressed in Sprint X of the 100 PaperCuts program. Please see http://liferay.com/community/100-papercuts"That way, the first phrase doesn't imply that the original submitter or person currently assigned should ignore it or that it will *definitely* be fixed. The second one does. Please sign in to reply. Reply as... Cancel James Falkner Deb Troxel 13 Years Ago BTW, our JIRA upgrade was completed over the weekend, so we can have arbitrary tags on tickets now.. yay!!!!!! I'll work on using the tagging system going forward (and converting the existing tickets we have identified). Please sign in to reply. Reply as... Cancel
James Falkner Deb Troxel 13 Years Ago - Edited Yeah, the "100PC Papercuts" filter are those we've already selected to work on (our backlog).The "100 PC Candidates" are basically all unresolved bugs, but filters out those that are already in the Liferay engineering pipeline (associated with a specific sprint). Deb, I like your idea of separating the "backlog" bugs from the ones that have been selected for a specific sprint. If only we had the JIRA upgrade completed, this could all be solved with tags. But the interim, yeah, how about this:For bugs we consider potential papercuts (but aren't associated with a specific 100PC sprint), we use this phrase: "This issue is a backlog candidate for the 100 PaperCuts program. Please consider participating! See http://liferay.com/community/100-papercuts".For bugs that we select for a specific sprint, we put this:"This issue is currently being addressed in Sprint X of the 100 PaperCuts program. Please see http://liferay.com/community/100-papercuts"That way, the first phrase doesn't imply that the original submitter or person currently assigned should ignore it or that it will *definitely* be fixed. The second one does. Please sign in to reply. Reply as... Cancel
James Falkner Deb Troxel 13 Years Ago BTW, our JIRA upgrade was completed over the weekend, so we can have arbitrary tags on tickets now.. yay!!!!!! I'll work on using the tagging system going forward (and converting the existing tickets we have identified). Please sign in to reply. Reply as... Cancel
jelmer kuperus 13 Years Ago Hey James, I added a possible fix for LPS-12988 Please sign in to reply. Reply as... Cancel