The below is based on #41 with some updates about growing (re)interest in the Web Annotation specs via the EPUB work at the W3C and the Readium foundation.
Annotator
Annotator provides annotation enabling code for browsers, servers, and
humans.
Annotator has been incubating since 2016-08-30.
Three most important unfinished issues to address before graduating:
Apache Annotator is unable to produce releases due to low activity
PMC is largely inactive
Motivation to contribute is low due to inability of producing enough release votes
Are there any issues that the IPMC or ASF Board need to be aware of?
See above. Unless there is interest by new people to join the project and help getting out releases, IMHO it would make more sense to retire the podling, fork it and release it without the three-vote hurdle. We continue to seek advice on this topic.
How has the community developed since the last report?
The community has not grown.
How has the project developed since the last report?
Yarn has been dropped from the project in favor of npm. Since then, a number of dependabot issues have piled up.
There have been a few mails regarding potentially adding support for the Highlight API instead of using mark elements (while keeking the elements as a fallback).
There is wider community interest growing around the Web Annotation specifications again driven by new W3C Web Publishing work rechartering and the Readium groups "profiling down" of the Web Annotation Data Model specification for reading platforms (many of which are DOM based and could benefit from Apache Annotator code):
https://github.com/readium/annotations
One key thing the community could work toward is building the code to ingest a full Web Annotation, AnnotationCollection, and/or AnnotationPage and use the existing selection code to anchor these annotations. The demo we have now gets pretty close, but developers seem to not be finding their way there.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Initial setup
[x] Working towards first release
[ ] Community building - we missed several golden opportunities for community growth due to the timing of joining the incubator after the "hype cycle" at the W3C and I Annotate conference hay days. We may have a new opportunity here with the rechartering and new exploration around DOM-based EPUB readers...but we'll need more active contributors to take advantage of the opportunity.
[ ] Nearing graduation
Date of last release:
2021-07-14 (0.2.0)
We tried to get out a 0.3.0 in May 2022, but it got stuck in the vote.
When were the last committers or PPMC members elected?
@reckart was the last one to join in August 2022 (waving the flag).
Have your mentors been helpful and responsive?
@BigBlueHat has prepared the last incubator report for this project and has provided some guidance.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?
reckart
commented
1 month ago
⏱️ Deadline: 02 Oct 2024 (only first notified on the 7th...)
The below is based on #41 with some updates about growing (re)interest in the Web Annotation specs via the EPUB work at the W3C and the Readium foundation.
Annotator
Annotator provides annotation enabling code for browsers, servers, and humans.
Annotator has been incubating since 2016-08-30.
Three most important unfinished issues to address before graduating:
Are there any issues that the IPMC or ASF Board need to be aware of?
See above. Unless there is interest by new people to join the project and help getting out releases, IMHO it would make more sense to retire the podling, fork it and release it without the three-vote hurdle. We continue to seek advice on this topic.
How has the community developed since the last report?
The community has not grown.
How has the project developed since the last report?
Yarn has been dropped from the project in favor of npm. Since then, a number of dependabot issues have piled up.
There have been a few mails regarding potentially adding support for the Highlight API instead of using
markelements (while keeking the elements as a fallback).There is wider community interest growing around the Web Annotation specifications again driven by new W3C Web Publishing work rechartering and the Readium groups "profiling down" of the Web Annotation Data Model specification for reading platforms (many of which are DOM based and could benefit from Apache Annotator code): https://github.com/readium/annotations
One key thing the community could work toward is building the code to ingest a full Web Annotation, AnnotationCollection, and/or AnnotationPage and use the existing selection code to anchor these annotations. The demo we have now gets pretty close, but developers seem to not be finding their way there.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
Date of last release:
2021-07-14 (0.2.0)
We tried to get out a 0.3.0 in May 2022, but it got stuck in the vote.
When were the last committers or PPMC members elected?
@reckart was the last one to join in August 2022 (waving the flag).
Have your mentors been helpful and responsive?
@BigBlueHat has prepared the last incubator report for this project and has provided some guidance.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
I don't know.
Signed-off-by:
Comments:
Comments:
Comments:
IPMC/Shepherd notes: