Yes, that's for sharing details, e.g. stack trace on failure (from the TCK). That doesn't mean you can't submit a "descriptive" jira ticket ;-)
-Matthias On Sun, Mar 1, 2009 at 8:09 PM, Michael Concini <[email protected]> wrote: > I got a response back from our legal, and any usage of the TCK must be > appropriately related to IBM products. So you're right that we can't share > results. Sorry for any misunderstanding on that. > > Matthias Wessendorf wrote: > > On Thu, Feb 26, 2009 at 6:10 PM, Michael Concini <[email protected]> wrote: > > > I'll have to check on what the deal is with the tck results. I'm not sure > what our current license conditions are with Sun (not my area of > expertise). I'll let you know what I find out from our legal team. > > > cool. There is an "jcp-open" ([email protected]) list on Apache, > which you may want > to ping as well, to inform them about your conditions on that TCK thing. > > -Matthias > > > > Matthias Wessendorf wrote: > > Not sure what you mean by "combing a committer". As far as the TCK is > > > whoops. Typo... becoming :-) > > > > concerned though, we will have immediate access to the TCK at IBM once Sun > releases it. We'd be happy to run any alpha, beta and eventually final > releases of MyFaces 2.0 through the tck and work on fixing those bugs. > > > IMO that's fine, but you can't share the results if I remember correctly > > > > I also think it would be a good idea to come up with a more formal way > of > keeping track of who is working on which items. As more folks become > involved, its going to become more and more likely that we'll step on > each > other's toes. > > > I agree, but JIRA only allows to assign ticket to commiters and I don't > have > anything better than adding a comment to the ticket for now. If you have > a > better idea it would be welcome. > > > Perhaps we could use the wiki ? Like creating an umbrella MyFaces 2.0 > items wiki > page, which "links" the all the subtasks / issues . > > > > Using the wiki may not be a bad idea. If we were to do that though, one > thing that would be of great help to my team at least would be to have the > work items mapped back to the changes in the spec where possible. Even > something as simple as an which section/subsection the change comes from. > I'd be happy to help out with that work, but I would guess Simon or someone > from his team could do it more efficiently since they did the initial > breakdown of the work into the JIRA issues. > > > I think so too. We can add that info to the wiki. something like: > > ISSUE NAME MYFACES JIRA SPEC ISSUE > implement blah MYFACES-1234 SPEC-789 (all are linked to > the real resources) > > -M > > > > > Does anyone have thoughts on any of the above? I'd be glad to work > with > someone from the PMC to assist in any of the required planning. > > > Michael, the right channel to communicate on the development of Apache > MyFaces > is this mailing list. If you/your team has questions, the best is to > use something > like [myfaces 2.0] in the beginning of the subject, so a mail can be > filtered easily. > We usually use other resources, like JIRA or the MyFaces wiki ([2]) to > "organize" > the work. You can create an account on those services and contribute some > work > there as well. > > If you have more questions, please ask them here, as the community is more > than > willing to answer them. > > -Matthias > > [1] http://www.apache.org/jcp/sunopenletter.html > [2] http://wiki.apache.org/myfaces/ > > > > Thanks, > Mike Concini > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > > > > > > > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
