You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2022/04/03 11:19:33 UTC
[Draft] Apache Jena report - 2022-04
## Description:
The mission of Jena is the creation and maintenance of software related
to Java framework for building Semantic Web applications
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Jena was founded 2012-04-18 (10 years ago)
There are currently 18 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 9:7.
Community changes, past quarter:
- No new PMC members. Last addition was Aaron Coburn on 2019-01-22.
- No new committers. Last addition was Greg Albiston on 2019-07-08.
## Project Activity:
Jena 4.4.0 was released 2022-02-02.
Key features of this release:
* New triplestore (Apache Jena Fuseki) UI. The UI has been rewritten for
improved maintenance and style. We now have much better management of
dependencies, as witnessed by security advisories on the github
repository.
* Improved bulk loader. The database bulk loader has fixes and
performance refinements. It has been used to load the full WikiData
dataset. This has been a community effort to test and load large scale
data in different hardware environments.
## Community Health:
The development community has decided to enable some github features
(issues and discussions areas) and reorganise the mailing lists. The
dev@ mailing list was primarily JIRA messages; these have been rerouted
to a specific jira@.
We hope that having the github features will make it easier for external
feedback and contributions. The existing channels of feedback and
contribution continue - nothing has been closed down.
The level of email on the dev@ list will fall dramatically. This will
show up in next quarter's report.
We hope this makes it easier for people to observe the project and also
have project-wide discussions without the JIRA emails dominating the list.
Re: [Draft] Apache Jena report - 2022-04
Posted by Bruno Kinoshita <br...@gmail.com>.
+1! Thanks!!
On Mon, 4 Apr 2022 at 02:57, <aj...@apache.org> wrote:
> +1, thanks Andy!
>
> Adam
>
> On Sun, Apr 3, 2022, 7:19 AM Andy Seaborne <an...@apache.org> wrote:
>
> >
> > ## Description:
> > The mission of Jena is the creation and maintenance of software related
> > to Java framework for building Semantic Web applications
> >
> > ## Issues:
> > There are no issues requiring board attention.
> >
> > ## Membership Data:
> > Apache Jena was founded 2012-04-18 (10 years ago)
> >
> > There are currently 18 committers and 14 PMC members in this project.
> > The Committer-to-PMC ratio is 9:7.
> >
> > Community changes, past quarter:
> > - No new PMC members. Last addition was Aaron Coburn on 2019-01-22.
> > - No new committers. Last addition was Greg Albiston on 2019-07-08.
> >
> > ## Project Activity:
> > Jena 4.4.0 was released 2022-02-02.
> >
> > Key features of this release:
> >
> > * New triplestore (Apache Jena Fuseki) UI. The UI has been rewritten for
> > improved maintenance and style. We now have much better management of
> > dependencies, as witnessed by security advisories on the github
> > repository.
> >
> > * Improved bulk loader. The database bulk loader has fixes and
> > performance refinements. It has been used to load the full WikiData
> > dataset. This has been a community effort to test and load large scale
> > data in different hardware environments.
> >
> > ## Community Health:
> > The development community has decided to enable some github features
> > (issues and discussions areas) and reorganise the mailing lists. The
> > dev@ mailing list was primarily JIRA messages; these have been rerouted
> > to a specific jira@.
> >
> > We hope that having the github features will make it easier for external
> > feedback and contributions. The existing channels of feedback and
> > contribution continue - nothing has been closed down.
> >
> > The level of email on the dev@ list will fall dramatically. This will
> > show up in next quarter's report.
> >
> > We hope this makes it easier for people to observe the project and also
> > have project-wide discussions without the JIRA emails dominating the
> list.
> >
>
Re: [Draft] Apache Jena report - 2022-04
Posted by aj...@apache.org.
+1, thanks Andy!
Adam
On Sun, Apr 3, 2022, 7:19 AM Andy Seaborne <an...@apache.org> wrote:
>
> ## Description:
> The mission of Jena is the creation and maintenance of software related
> to Java framework for building Semantic Web applications
>
> ## Issues:
> There are no issues requiring board attention.
>
> ## Membership Data:
> Apache Jena was founded 2012-04-18 (10 years ago)
>
> There are currently 18 committers and 14 PMC members in this project.
> The Committer-to-PMC ratio is 9:7.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Aaron Coburn on 2019-01-22.
> - No new committers. Last addition was Greg Albiston on 2019-07-08.
>
> ## Project Activity:
> Jena 4.4.0 was released 2022-02-02.
>
> Key features of this release:
>
> * New triplestore (Apache Jena Fuseki) UI. The UI has been rewritten for
> improved maintenance and style. We now have much better management of
> dependencies, as witnessed by security advisories on the github
> repository.
>
> * Improved bulk loader. The database bulk loader has fixes and
> performance refinements. It has been used to load the full WikiData
> dataset. This has been a community effort to test and load large scale
> data in different hardware environments.
>
> ## Community Health:
> The development community has decided to enable some github features
> (issues and discussions areas) and reorganise the mailing lists. The
> dev@ mailing list was primarily JIRA messages; these have been rerouted
> to a specific jira@.
>
> We hope that having the github features will make it easier for external
> feedback and contributions. The existing channels of feedback and
> contribution continue - nothing has been closed down.
>
> The level of email on the dev@ list will fall dramatically. This will
> show up in next quarter's report.
>
> We hope this makes it easier for people to observe the project and also
> have project-wide discussions without the JIRA emails dominating the list.
>