jsr372-experts@javaserverfaces-spec-public.java.net

[jsr372-experts] Re: Some concerns about EG activity

From: Bauke Scholtz <balusc_at_gmail.com>
Date: Thu, 10 Dec 2015 15:06:47 +0100

Hi,

Before the SVN-to-Git migration and the JavaOne freeze I did got some
issues assigned on me and I finished the following:
- https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1113 remove
invalid "onselect" attribute from select components
- https://java.net/jira/browse/JAVASERVERFACES-4005 character encoding bug
in URL attribute writers
- https://java.net/jira/browse/JAVASERVERFACES-4024 improved deprecated
approach of loading scripts embedded in ajax response

All of them are however still "unresolved". Unsure how to continue.
@Manfred?

I've also a PORT issue assigned:
- https://java.net/jira/browse/JAVASERVERFACES-4049 port of 4024 to 2.2
branch

I actually have no idea what's the correct way to do that on SVN. @Manfred?

I'm currently busy with:
- https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1396 new f:socket

Then I've other open issues:
- https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-613 basically, a
new <h:commandScript> component
- https://java.net/jira/browse/JAVASERVERFACES-3981 h:outputText
escape="false" unescpaing bug in ajax responses
- https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790 fix view
state bug on ajax updates

I will pickup them in this order after <f:socket> is finished.


Cheers, B





On Thu, Dec 10, 2015 at 12:21 PM, arjan tijms <arjan.tijms_at_gmail.com> wrote:

> Hi,
>
> On Wed, Dec 9, 2015 at 11:26 PM, Josh Juneau <juneau001_at_gmail.com> wrote:
>
>> I was working on the Java 8 date time converter, but last I knew Ed was
>> going to finish it up (prior to JavaOne, I believe). If my assistance is
>> still needed on that issue then I would certainly help out. If nothing
>> else, I'd love to test and write about it.
>>
>
> It looks like both the spec issue and the implementation issue are
> complete done, as both
> https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1370 and
> https://java.net/jira/browse/JAVASERVERFACES-4070
>
> Testing and writing about it will always help, of course. I'll include
> this feature on my JSF 2.3 page soon.
>
>
>> As for other issues, I should take a look through the tracker and see if
>> there are any items that I feel I may be able to help with.
>>
>
> Great, thanks! :)
>
> Kind regards,
> Arjan Tijms
>
>
>
>>
>> Best
>>
>>
>> Josh Juneau
>> http://jj-blogger.blogspot.com
>> https://www.apress.com/index.php/author/author/view/id/1866
>>
>>
>> On Dec 9, 2015, at 8:53 AM, arjan tijms <arjan.tijms_at_gmail.com> wrote:
>>
>> He everyone,
>>
>> I'd like to share some concerns about the level of activity of this EG.
>>
>> I'm very happy with the recent proposal by Bauke, but apart from that,
>> activity currently doesn't seem to be at the same level as it once was.
>>
>> If you look at the commits in the RI, then it's quite clear that activity
>> is a little down, even after the master branch was opened again. See
>> https://github.com/javaserverfaces/mojarra/commits/master
>>
>> Looking at the amount of actual features being developed for JSF 2.3
>> (e.g. actual code), then when JSF 2.3 just started Manfred was doing an
>> amount of commits for the initial CDI alignment feature, but after
>> approximately early 2015 I didn't see JSF 2.3 feature commits from him
>> anymore (please correct me if I'm wrong, I may have missed something).
>>
>> As for Ed, there were some clarifications during 2015 and one bigger
>> feature just before JavaOne (validateWholeBean). I'm not entirely sure if
>> that feature is deemed fully ready wrt to the implementation (the spec
>> issue is closed though), but after JavaOne no more commits were being done
>> for it.
>>
>> As for the various EG members, a variety of issues were assigned to
>> different people, but I've not yet seen many patches or code commits for
>> those. The only one that comes to mind is the Java 8 JSR 310 from Josh and
>> Ed (again, correct me if I missed something).
>>
>> Now my own activity is down too, so I know I'm to blame as well, but that
>> still doesn't take away that IMHO activity could improve a little. It's now
>> almost 2016, so perhaps a good time to reflect on what we have accomplished
>> last year and what we plan to accomplish next year ;)
>>
>> Something that may help here is a scheduled bi-weekly IRC chat, just to
>> see where we stand and were we're heading.
>>
>> Thoughts?
>>
>> Kind regards,
>> Arjan Tijms
>>
>>
>>
>