juneau-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Bognar <jamesbog...@apache.org>
Subject Re: August Juneau board report.
Date Tue, 20 Aug 2019 12:45:16 GMT
Hi Ayesh,

Go for it.  I can try to assist but my time is likely to be limited
over the next couple of months.

On Mon, Aug 19, 2019 at 6:10 PM Ayeshmantha Perera
<akayeshmantha@gmail.com> wrote:
>
> Hi @James Bognar
>
> The ASF has successfully been accepted as a participating FOSS
> community in the Outreachy Program [1] to work with Outreachy organizers
> to offer remote internships to applicants around the world.  With this
> program, we are looking forward to improving inclusion in our
> communities by understanding what are the barriers that underrepresented
> groups in the tech industry have while trying to start their journey.
>
> https://cwiki.apache.org/confluence/display/EDI/2019/08/19/Seeking+volunteer+mentors+from+all+Apache+projects+to+help+mentor+under-represented+contributors
> has the full post.
>
> I think this will be a great opportunity for get the potential developers who willing
to work on the project.
> This programme is also similar to GSoC.If we are moving forward would like to work as
a mentor or backup mentor on the programme
>
> Thank you
> Regards
> Ayesh
>
>
> On Thu, Aug 15, 2019 at 8:14 PM James Bognar <jamesbognar@apache.org> wrote:
>>
>> > Perhaps what does not come as easily across is an overall "when to use
>> > Juneau". I would think as part of a larger application doing RESTful
>> > services with potentially many formats - but for instance should a
>> > Juneau application be doing Web UI or is that done "outside"?
>>
>> > For instance could Juneau work in conjunction with or in competition
>> > with Spring Boot? (which does a couple of these things well, but lots of
>> > things badly)
>>
>> It's my personal opinion that Juneau should NOT be in the Web UI
>> business and should stick to REST.  We've started down the path of
>> providing UI-ish functionality by introducing thinks such as
>> HtmlRenders that allow you to customize how POJOs get rendered in the
>> HTML content type.  That may have been a mistake.  There are so many
>> existing UI frameworks out there that work with REST.  It doesn't make
>> sense to invent yet another.  Instead I'd prefer to provide examples
>> of how to use technologies like Datatables and Bootstrap on top of
>> Juneau.
>>
>> There was thought of providing Freemarker integration support for UI,
>> but that didn't get too far off the ground.
>>
>> I agree that Spring Boot does some things good and lots of things
>> badly (it's a bit too 'unstructured' for my taste).  But it's where
>> the cool kids are these days.  Since top-level resource classes are
>> just servlets, they can be provided as Spring Boot beans as-is without
>> any modifications.  Marcelo added the very useful
>> JuneauRestInitializer class that allows the resource classes
>> themselves to be injectable beans.  There are existing ways to create
>> REST interfaces in Spring Boot, but what I've seen they pale to the
>> capabilities that Juneau can provide.  And Juneau works naturally at
>> marshalling of Spring Data beans out-of-the-box and works well with
>> Spring Security annotations.
>>
>> So I agree that more integration support with Spring is a good idea
>> and probably should be our focus.  And we should be moving away from
>> UI support.
>>
>>
>>
>> On Thu, Aug 15, 2019 at 10:46 AM Stian Soiland-Reyes <stain@apache.org> wrote:
>> >
>> > On Wed, 14 Aug 2019 09:16:12 -0400, James Bognar <jamesbognar@apache.org>
wrote:
>> > > Here's the board report being submitted for August:
>> > >
>> > > https://whimsy.apache.org/board/agenda/2019-08-21/Juneau
>> >
>> > As that site is only accessible for ASF members, see below:
>> >
>> > ## Description:
>> > The mission of Apache Juneau is the creation and maintenance of software
>> > related to a toolkit for marshalling POJOs to a wide variety of content types
>> > using a common framework, and for creating sophisticated self-documenting REST
>> > interfaces and microservices using VERY little code
>> >
>> > ## Issues:
>> > No issues to report.
>> >
>> > ## Membership Data:
>> > Apache Juneau was founded 2017-10-17 (2 years ago) There are currently 12
>> > committers and 12 PMC members in this project. The Committer-to-PMC ratio is
>> > 1:1.
>> >
>> > Community changes, past quarter:
>> > - No new PMC members. Last addition was Ayeshmantha Perera on 2019-01-02.
>> > - No new committers. Last addition was Ayeshmantha Perera on 2019-01-02.
>> >
>> > ## Project Activity:
>> > Version 8.0.0 was released on 2018-12-13.  The community is currently voting
>> > on version 8.1.0 which includes significant new functionality for use in
>> > Spring Boot applications.  We hope to have this released within the next 1-2
>> > weeks.
>> >
>> > One of our newer members is working on a new component for a configuration
>> > server.
>> >
>> > ## Community Health:
>> > dev@juneau.apache.org had a 95% increase in traffic in the past quarter (92
>> > emails compared to 47) 20 issues opened in JIRA, past quarter (66% increase)
>> > 21 issues closed in JIRA, past quarter (320% increase) 120 commits in the past
>> > quarter (15% increase)
>> >
>> > Our active community continues to be small and we have struggled to attract
>> > new developers willing to make code contributions.  Our code base is rather
>> > mature/complex and can be daunting for new developers to pick up.  Most of the
>> > current JIRA issues are rather complex feature requests.  Low-hanging fruit
>> > for new developers is not always available.  All code commits within the past
>> > 6 months have come from 2 developers.
>> >
>> > The PMC Chair believes the project needs more exposure through external
>> > articles which current members have not had time to devote.

Mime
View raw message