Wiki Topics

[Jonathan Giles]

Regarding a list of desired patches/work, I have been using the 
'openjfx-candidate' label up to this point (but this isn't something 
anyone else is using, afaik):

http://javafx-jira.kenai.com/secure/IssueNavigator.jspa?mode=hide&requestId=13558

On top of this, there is also the unassigned (ui controls) bugs that I 
want to get fixed for JavaFX 8.0:

http://javafx-jira.kenai.com/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+RT+AND+status+!%3D+New+AND+resolution+%3D+Unresolved+AND+fixVersion+in+%28Lombard%29+AND+component+in+%28Control%29+AND+assignee+is+EMPTY

If anyone can help with these it would be great - just leave a comment 
on the bug claiming a desire to own it. Of course, a signed / accepted 
OCA is required first, but a number of people are starting to get their 
OCAs submitted, which is great.

-- Jonathan

On 23/01/2013 9:16 a.m., Danno Ferrin wrote:
> These requests are more meta to the process than the platform itself
>
> 1)  A list of desired patches/work.  Maybe a tag in Jira 'patches-welcome'
> as well.  Rather than deciding what the potential contributor thinks is
> valuable this list would help them prioritize contributions that are more
> likely to be accepted.
>
> 2) The lifecycle of a patch/bug report.  What parts are gating, where it
> might get stalled, when to shake the tree, what to expect.  Right now I
> have two issues with patches that have been sitting for some time
> (RT-25559<http://javafx-jira.kenai.com/browse/RT-25559>
>   and RT-26719 <http://javafx-jira.kenai.com/browse/RT-26719>, which I
> consider a straight up bug).  I don't know if it is a time issue with the
> engineer, if they didn't like my patches, or if they have been rejected.  A
> prompt response that either adds the patch to the review queue for
> commitment or bounces it back to the developer is what I see as lacking.  A
> prompt rejection is better than neglect.
>
> --Danno
>
>
> On Tue, Jan 22, 2013 at 12:56 PM, Richard Bair <richard.bair at oracle.com>wrote:
>
>> Hi,
>>
>> I want to write a bunch of documentation on our wiki around working with
>> and contributing to openjfx. Some of this will be on-boarding documentation
>> (including building, testing, etc). Some of it will be architecture. Some
>> of it will be features.
>>
>> What are the things you'd like documented on there? What would have been
>> (or would still be) most useful in understanding the platform when
>> approaching it from the perspective of a contributor (whether contributing
>> patches or bug reports etc)?
>>
>> Thanks!
>> Richard
>
>
>