You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@annotator.apache.org by Gerben <ge...@treora.com.INVALID> on 2020/04/02 08:04:00 UTC
Re: Weekly calls/chats?
Call reminder; this is 7 hours from now.
<https://meet.jit.si/apache-annotator>
On 26/03/2020 18:10, Gerben wrote:
> From next week, *one hour earlier* as the proposal was to jump along
> with summertime / daylight saving time starting in (most of?) Europe.
> So Thursday 2 April, 15:00 GMT <https://everytimezone.com/s/218bf97e>
> <https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
After a few weeks of confusion as our usual call participants switched
to winter time, we moved the weekly call time from 15:00 UTC to 16:00 UTC.
So for any people interested in getting involved with Annotator in one
way or another, be welcome to join our community call: every Thursday,
16:00 UTC, in <https://meet.jit.si/apache-annotator>.
— Gerben
On 2020-09-03 18:47, Gerben wrote:
> In case anyone wonders: weekly calls are still happening, I just stopped
> sending reminders over this list. Every Thursday, 15:00 UTC, in
> <https://meet.jit.si/apache-annotator>. The usual turn-up is somewhere
> between 1 and 3 of the current three core committers, and every now and
> then an Apache mentor, or (potential) users/contributors. Please do all
> feel welcome to pop some day, or let know if you’d like to join but this
> time slot does not work for you.
>
> We just had a call today, here a rough sketch of the state of play:
>
> - We’d like to get a second release out soon, incorporating the
> conversion to TypeScript and several small improvements and bugfixes we
> have made recently.
> - This time we will be documenting how to use it. :) Benjamin will start
> with a documentation section on website, to house both API reference and
> introduction.
> - Randall and I are reviewing the types (see PR #87), and will make the
> end-user API easier to use (hopefully to be included in the next release).
> - And not discussed today, but still in the works are some abstractions
> and improvements for text selection; in particular issue #85, which may
> go well together with supporting TextPositionSelector (issue #75).
>
> — Gerben
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
In case anyone wonders: weekly calls are still happening, I just stopped
sending reminders over this list. Every Thursday, 15:00 UTC, in
<https://meet.jit.si/apache-annotator>. The usual turn-up is somewhere
between 1 and 3 of the current three core committers, and every now and
then an Apache mentor, or (potential) users/contributors. Please do all
feel welcome to pop some day, or let know if you’d like to join but this
time slot does not work for you.
We just had a call today, here a rough sketch of the state of play:
- We’d like to get a second release out soon, incorporating the
conversion to TypeScript and several small improvements and bugfixes we
have made recently.
- This time we will be documenting how to use it. :) Benjamin will start
with a documentation section on website, to house both API reference and
introduction.
- Randall and I are reviewing the types (see PR #87), and will make the
end-user API easier to use (hopefully to be included in the next release).
- And not discussed today, but still in the works are some abstractions
and improvements for text selection; in particular issue #85, which may
go well together with supporting TextPositionSelector (issue #75).
— Gerben
On 2020-07-30 17:13, Gerben wrote:
> Hi, I lost track of the days and forgot about this, but I am available;
> let’s do a quick check-in at *:30 then (i.e. 15:30 UTC).
>
> On 2020-07-30 16:51, Benjamin Young wrote:
>> Hi folks. Not sure if there's a call today, but I'll try and pop in around the half-hour--conflict prior to that. :-/
>>
>> Cheers,
>> Benjamin
>>
>> -----Original Message-----
>> From: Gerben <ge...@treora.com.INVALID>
>> Sent: Thursday, July 16, 2020 9:02 AM
>> To: dev@annotator.incubator.apache.org
>> Subject: Re: Weekly calls/chats?
>>
>> Reminder: Next call in two hours, 15:00 UTC, in <https://meet.jit.si/apache-annotator>
>>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Hi, I lost track of the days and forgot about this, but I am available;
let’s do a quick check-in at *:30 then (i.e. 15:30 UTC).
On 2020-07-30 16:51, Benjamin Young wrote:
> Hi folks. Not sure if there's a call today, but I'll try and pop in around the half-hour--conflict prior to that. :-/
>
> Cheers,
> Benjamin
>
> -----Original Message-----
> From: Gerben <ge...@treora.com.INVALID>
> Sent: Thursday, July 16, 2020 9:02 AM
> To: dev@annotator.incubator.apache.org
> Subject: Re: Weekly calls/chats?
>
> Reminder: Next call in two hours, 15:00 UTC, in <https://meet.jit.si/apache-annotator>
>
RE: Weekly calls/chats?
Posted by Benjamin Young <by...@bigbluehat.com>.
Hi folks. Not sure if there's a call today, but I'll try and pop in around the half-hour--conflict prior to that. :-/
Cheers,
Benjamin
-----Original Message-----
From: Gerben <ge...@treora.com.INVALID>
Sent: Thursday, July 16, 2020 9:02 AM
To: dev@annotator.incubator.apache.org
Subject: Re: Weekly calls/chats?
Reminder: Next call in two hours, 15:00 UTC, in <https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Reminder: Next call in two hours, 15:00 UTC, in
<https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Reminder: Next call in one hour; 15:00 UTC, in
<https://meet.jit.si/apache-annotator>
Should we bring drinks for small release party? :)
And we should discuss updating website content, documentation, etcetera.
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Reminder: Next call in two hours; 15:00 UTC, in <https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Reminder: Next call in two hours; 15:00 UTC, in
<https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Notes of tasks discussed in today’s call (which lacked a reminder, but
the rhythm is unchanged):
- propose the release to the incubator mailing list
- create more welcoming documentation to help people understand what
Annotator does, what it does not (or not yet), and how to use it.
- make an example code showing how to use it; perhaps the current demo
would work for this, but we should add a link to its source code on the
website
- look into approaches for documentation going forward; perhaps use
tsdoc and publish its output on the website
- organise and label our open issues, use the issue tracker more
{in|ex}tensively
- try to provide more clarification about the relations and statuses of
related projects, especially AnnotatorJs.
- finish current PRs (typescript & dom-tests), keep on coding
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Next call is in an hour (15:00 UTC), in
<https://meet.jit.si/apache-annotator>
Besides status updates and any other topics that come up, I would be
glad to discuss the work around tests that I did this week (see pull
request #79 that I just opened); and what to focus on now/next.
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
No problem. We mainly discussed releasing (Randall is on it), creating
tests (I am on it), why are APIs are async and if we may want to provide
a synchronous API too/instead.
On 21/05/2020 17:40, Benjamin Young wrote:
> Sorry I missed y'all today! It's been pretty non-stop here...
>
> Hoping it was productive regardless! 🙂
>
>
> --
>
> http://bigbluehat.com/
>
> http://linkedin.com/in/benjaminyoung
>
> ________________________________
> From: Gerben <ge...@treora.com.INVALID>
> Sent: Thursday, May 21, 2020 9:11 AM
> To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
> Subject: Re: Weekly calls/chats?
>
> Next call is in less than two hours (15:00 UTC), in <https://meet.jit.si/apache-annotator>
>
Re: Weekly calls/chats?
Posted by Benjamin Young <by...@bigbluehat.com>.
Sorry I missed y'all today! It's been pretty non-stop here...
Hoping it was productive regardless! 🙂
--
http://bigbluehat.com/
http://linkedin.com/in/benjaminyoung
________________________________
From: Gerben <ge...@treora.com.INVALID>
Sent: Thursday, May 21, 2020 9:11 AM
To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
Subject: Re: Weekly calls/chats?
Next call is in less than two hours (15:00 UTC), in <https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Next call is in less than two hours (15:00 UTC), in <https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Next call is in three hours (15:00 UTC), in
<https://meet.jit.si/apache-annotator>
Possible topics to discuss:
- Oliver asked for feedback on his grant proposals around annotation interop
- I started to set up testing for anchoring in the DOM, and could use
some more brains on how to approach this.
- whatever comes up.
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Next call is in two hours (15:00 UTC), in
<https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Notes of some things discussed today (feel free to supplement):
– supporting WorldBrain’s Memex use case (see relevant thread); a good
start may be to have a corpus of documents and annotations for those to
create a test suite with.
– relatedly, the idea came up to help our users anchor annotations
created by Hypothesis[0] or H-derived applications. This could make it
easier for such applications to start using Apache Annotator, without
worrying that their existing annotations will no longer anchor as
before. We could approach this either in usage examples, or in our code
base itself (perhaps we accept an ‘H compatibility mode’ flag?);
possibly by wrapping the actual Hypothesis anchoring code with our
asynchronous API.
– generally, we lack an easy way to describe a target selection in
multiple ways, and conversely an easy way to resolve (anchor) a bunch of
alternative selectors (using some strategy of e.g. the order in which to
try apply them).
– for approximate text quote anchoring, we may want to look into Robert
Knight’s work again[1].
– we could easily add support for anchoring an XPathSelector[2] using
modern browsers’ built-in XPathEvaluator[3]. Conversely, i.e. describing
selections as XPaths, is not as obvious to solve as there are many ways
to describe the same target.
[0] https://hypothes.is/
[1] https://github.com/robertknight/approx-string-match-js/
[2] https://www.w3.org/TR/2017/REC-annotation-model-20170223/#xpath-selector
[3] https://developer.mozilla.org/en-US/docs/Web/API/XPathEvaluator
On 30/04/2020 15:51, Benjamin Young wrote:
> Woot! Should be there today. And hopefully in time. ;-P
> ________________________________
> From: Gerben <ge...@treora.com.INVALID>
> Sent: Thursday, April 30, 2020 9:08:54 AM
> To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
> Subject: Re: Weekly calls/chats?
>
> Reminder: next call is in two hours, 15:00 UTC in
> <https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Benjamin Young <by...@bigbluehat.com>.
Woot! Should be there today. And hopefully in time. ;-P
________________________________
From: Gerben <ge...@treora.com.INVALID>
Sent: Thursday, April 30, 2020 9:08:54 AM
To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
Subject: Re: Weekly calls/chats?
Reminder: next call is in two hours, 15:00 UTC in
<https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Reminder: next call is in two hours, 15:00 UTC in
<https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Benjamin Young <by...@bigbluehat.com>.
Running late again. But am planning to join.
________________________________
From: Gerben <ge...@treora.com.INVALID>
Sent: Thursday, April 23, 2020 10:11:41 AM
To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
Subject: Re: Weekly calls/chats?
Let’s call again in 50 minutes? <https://meet.jit.si/apache-annotator>
I’d be glad to chat about the conversion to Typescript (see my PR 74).
Also the questions raised in Oliver’s email may be good to discuss; it
seems a good use case indeed. And whatever anyone else may bring up. :)
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Let’s call again in 50 minutes? <https://meet.jit.si/apache-annotator>
I’d be glad to chat about the conversion to Typescript (see my PR 74).
Also the questions raised in Oliver’s email may be good to discuss; it
seems a good use case indeed. And whatever anyone else may bring up. :)
Re: Weekly calls/chats?
Posted by Benjamin Young <by...@bigbluehat.com>.
Planning to join, but will be a few minutes late. Talk soon!
________________________________
From: Gerben <ge...@treora.com.INVALID>
Sent: Thursday, April 16, 2020 9:33:48 AM
To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
Subject: Re: Weekly calls/chats?
Reminder: Call today again, in 1.5 hours. As usual in
<https://meet.jit.si/apache-annotator>.
Last week’s conversation went off into personal projects; no note-worthy
output.
On 09/04/2020 19:34, Randall Leeds wrote:
> Apologies, I was sleep deprived and slept through an alarm this morning.
>
> On Thu, Apr 9, 2020, 04:57 Gerben <ge...@treora.com.invalid> wrote:
>
>> Reminder: this call is in 3 hours.
>>
>> On 03/04/2020 01:25, Gerben wrote:
>>> Next week, same time same place: Thursday 9 April, 15:00 UTC
>>> <https://everytimezone.com/s/06252e96> in
>>> <https://meet.jit.si/apache-annotator>
>>>
>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Reminder: Call today again, in 1.5 hours. As usual in
<https://meet.jit.si/apache-annotator>.
Last week’s conversation went off into personal projects; no note-worthy
output.
On 09/04/2020 19:34, Randall Leeds wrote:
> Apologies, I was sleep deprived and slept through an alarm this morning.
>
> On Thu, Apr 9, 2020, 04:57 Gerben <ge...@treora.com.invalid> wrote:
>
>> Reminder: this call is in 3 hours.
>>
>> On 03/04/2020 01:25, Gerben wrote:
>>> Next week, same time same place: Thursday 9 April, 15:00 UTC
>>> <https://everytimezone.com/s/06252e96> in
>>> <https://meet.jit.si/apache-annotator>
>>>
>
Re: Weekly calls/chats?
Posted by Randall Leeds <ra...@gmail.com>.
Apologies, I was sleep deprived and slept through an alarm this morning.
On Thu, Apr 9, 2020, 04:57 Gerben <ge...@treora.com.invalid> wrote:
> Reminder: this call is in 3 hours.
>
> On 03/04/2020 01:25, Gerben wrote:
> > Next week, same time same place: Thursday 9 April, 15:00 UTC
> > <https://everytimezone.com/s/06252e96> in
> > <https://meet.jit.si/apache-annotator>
> >
> > == Today’s call notes ==
> >
> > Present: Nick, Gerben, Benjamin, Randall, (and Dinesh & Emery, but just
> > when we finished.. sorry about the timezone jump!)
> >
> > Past week:
> > - Benjamin&Randall sent a board report out
> > - Randall worked this week on related projects: dom-seek[1],
> > dom-node-iterator[2], dom-anchor-text-position[3]. Some may end up being
> > incorporated into Annotator.
> > - Gerben has deduplicated the demo code between website repo and code
> repo.
> >
> > Now/soon:
> > - new idea: also publish the in-browser test suite on the website, so
> > the tests can easily be run in anybody’s browser.
> > - the wiki is mostly outdated, let’s prune content to not confuse people
> > → Gerben
> > - …and add the promised release instructions to the wiki (or in the
> > repo itself?) → Randall
> > - let’s write a better documentation; pick a tool to generate docs from
> > inline comments?
> > - Jake had started on documenting functions’ APIs; we could start
> > from there?
> > - do we switch to Typescript? Yes (after releasing v0.1).
> > - fragment identifiers: Gerben tried to add tests today for
> > @annotator/fragment-identifier, but bumped into issues with URL
> > encoding. Turns out that the relevant spec (the W3C Selectors&States
> > note) may itself need some clarifications/modifications (see filed
> > issue[4]). Also, we may want/have to rewrite the parser, to replace the
> > curent (borrowed) PEG.js code, creating something with e.g.
> > Parsimmon[5]. Both tasks seem a significant effort, probably not what we
> > should focus on now. Does anyone even (want to) use it besides ourselves?
> > - intention: **remove** the fragment-identifier module, release
> > without it. Possibly get back to it in the future. → Gerben
> > - still tempted to implement Chrome’s ScrollToTextFragment spec[6]
> > as a polyfill.
> >
> > Other:
> > - Re: Pondering getting docs into HTML for annotation (see Benjamin’s
> > email of 27 March): too far off, let’s do one thing at a time; but it
> > would be cool to collaborate with (if) other projects doing such a thing.
> >
> > [1]: https://github.com/tilgovi/dom-seek/
> > [2]: https://github.com/tilgovi/dom-anchor-text-position
> > [3]: https://github.com/tilgovi/dom-anchor-text-position
> > [4]: https://github.com/w3c/web-annotation/issues/443
> > [5]: https://github.com/jneen/parsimmon/
> > [6]: https://wicg.github.io/ScrollToTextFragment/
> >
> >
> > On 02/04/2020 10:04, Gerben wrote:
> >> Call reminder; this is 7 hours from now.
> >> <https://meet.jit.si/apache-annotator>
> >>
> >> On 26/03/2020 18:10, Gerben wrote:
> >>> From next week, *one hour earlier* as the proposal was to jump along
> >>> with summertime / daylight saving time starting in (most of?) Europe.
> >>> So Thursday 2 April, 15:00 GMT <https://everytimezone.com/s/218bf97e>
> >>> <https://meet.jit.si/apache-annotator>
>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Reminder: this call is in 3 hours.
On 03/04/2020 01:25, Gerben wrote:
> Next week, same time same place: Thursday 9 April, 15:00 UTC
> <https://everytimezone.com/s/06252e96> in
> <https://meet.jit.si/apache-annotator>
>
> == Today’s call notes ==
>
> Present: Nick, Gerben, Benjamin, Randall, (and Dinesh & Emery, but just
> when we finished.. sorry about the timezone jump!)
>
> Past week:
> - Benjamin&Randall sent a board report out
> - Randall worked this week on related projects: dom-seek[1],
> dom-node-iterator[2], dom-anchor-text-position[3]. Some may end up being
> incorporated into Annotator.
> - Gerben has deduplicated the demo code between website repo and code repo.
>
> Now/soon:
> - new idea: also publish the in-browser test suite on the website, so
> the tests can easily be run in anybody’s browser.
> - the wiki is mostly outdated, let’s prune content to not confuse people
> → Gerben
> - …and add the promised release instructions to the wiki (or in the
> repo itself?) → Randall
> - let’s write a better documentation; pick a tool to generate docs from
> inline comments?
> - Jake had started on documenting functions’ APIs; we could start
> from there?
> - do we switch to Typescript? Yes (after releasing v0.1).
> - fragment identifiers: Gerben tried to add tests today for
> @annotator/fragment-identifier, but bumped into issues with URL
> encoding. Turns out that the relevant spec (the W3C Selectors&States
> note) may itself need some clarifications/modifications (see filed
> issue[4]). Also, we may want/have to rewrite the parser, to replace the
> curent (borrowed) PEG.js code, creating something with e.g.
> Parsimmon[5]. Both tasks seem a significant effort, probably not what we
> should focus on now. Does anyone even (want to) use it besides ourselves?
> - intention: **remove** the fragment-identifier module, release
> without it. Possibly get back to it in the future. → Gerben
> - still tempted to implement Chrome’s ScrollToTextFragment spec[6]
> as a polyfill.
>
> Other:
> - Re: Pondering getting docs into HTML for annotation (see Benjamin’s
> email of 27 March): too far off, let’s do one thing at a time; but it
> would be cool to collaborate with (if) other projects doing such a thing.
>
> [1]: https://github.com/tilgovi/dom-seek/
> [2]: https://github.com/tilgovi/dom-anchor-text-position
> [3]: https://github.com/tilgovi/dom-anchor-text-position
> [4]: https://github.com/w3c/web-annotation/issues/443
> [5]: https://github.com/jneen/parsimmon/
> [6]: https://wicg.github.io/ScrollToTextFragment/
>
>
> On 02/04/2020 10:04, Gerben wrote:
>> Call reminder; this is 7 hours from now.
>> <https://meet.jit.si/apache-annotator>
>>
>> On 26/03/2020 18:10, Gerben wrote:
>>> From next week, *one hour earlier* as the proposal was to jump along
>>> with summertime / daylight saving time starting in (most of?) Europe.
>>> So Thursday 2 April, 15:00 GMT <https://everytimezone.com/s/218bf97e>
>>> <https://meet.jit.si/apache-annotator>
Re: Weekly calls/chats?
Posted by Gerben <ge...@treora.com.INVALID>.
Next week, same time same place: Thursday 9 April, 15:00 UTC
<https://everytimezone.com/s/06252e96> in
<https://meet.jit.si/apache-annotator>
== Today’s call notes ==
Present: Nick, Gerben, Benjamin, Randall, (and Dinesh & Emery, but just
when we finished.. sorry about the timezone jump!)
Past week:
- Benjamin&Randall sent a board report out
- Randall worked this week on related projects: dom-seek[1],
dom-node-iterator[2], dom-anchor-text-position[3]. Some may end up being
incorporated into Annotator.
- Gerben has deduplicated the demo code between website repo and code repo.
Now/soon:
- new idea: also publish the in-browser test suite on the website, so
the tests can easily be run in anybody’s browser.
- the wiki is mostly outdated, let’s prune content to not confuse people
→ Gerben
- …and add the promised release instructions to the wiki (or in the
repo itself?) → Randall
- let’s write a better documentation; pick a tool to generate docs from
inline comments?
- Jake had started on documenting functions’ APIs; we could start
from there?
- do we switch to Typescript? Yes (after releasing v0.1).
- fragment identifiers: Gerben tried to add tests today for
@annotator/fragment-identifier, but bumped into issues with URL
encoding. Turns out that the relevant spec (the W3C Selectors&States
note) may itself need some clarifications/modifications (see filed
issue[4]). Also, we may want/have to rewrite the parser, to replace the
curent (borrowed) PEG.js code, creating something with e.g.
Parsimmon[5]. Both tasks seem a significant effort, probably not what we
should focus on now. Does anyone even (want to) use it besides ourselves?
- intention: **remove** the fragment-identifier module, release
without it. Possibly get back to it in the future. → Gerben
- still tempted to implement Chrome’s ScrollToTextFragment spec[6]
as a polyfill.
Other:
- Re: Pondering getting docs into HTML for annotation (see Benjamin’s
email of 27 March): too far off, let’s do one thing at a time; but it
would be cool to collaborate with (if) other projects doing such a thing.
[1]: https://github.com/tilgovi/dom-seek/
[2]: https://github.com/tilgovi/dom-anchor-text-position
[3]: https://github.com/tilgovi/dom-anchor-text-position
[4]: https://github.com/w3c/web-annotation/issues/443
[5]: https://github.com/jneen/parsimmon/
[6]: https://wicg.github.io/ScrollToTextFragment/
On 02/04/2020 10:04, Gerben wrote:
> Call reminder; this is 7 hours from now.
> <https://meet.jit.si/apache-annotator>
>
> On 26/03/2020 18:10, Gerben wrote:
>> From next week, *one hour earlier* as the proposal was to jump along
>> with summertime / daylight saving time starting in (most of?) Europe.
>> So Thursday 2 April, 15:00 GMT <https://everytimezone.com/s/218bf97e>
>> <https://meet.jit.si/apache-annotator>