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/03/05 09:16:54 UTC

Re: Weekly calls/chats?

For the weekly rhythm, let’s check in again today? Same time (5 March,
21:00GMT), same place: <https://meet.jit.si/apache-annotator>.

For people wanting but unable to join the call this time, please suggest
a time slot for (a) next week.


On 21/02/2020 05:05, Jake Hartnell wrote:
> +1
>
> Sent from my iPhone
>
>> On Feb 20, 2020, at 6:04 PM, Nick Kew <ni...@apache.org> wrote:
>>
>> 
>>
>>> On 20 Feb 2020, at 22:34, Gerben <ge...@treora.com.INVALID> wrote:
>>>
>>> Hi all, I just talked with Randall; to get things rolling our idea was
>>> to simply call again next week (Thursday 27th, 21:00 GMT, assuming
>>> Benjamin is available) and invite you all to join.
>> I'd join, but my Thursday evenings are otherwise occupied between 
>> about 18:00 and 23:00.
>>
>> Don't let that stop you (it's not critical), but it would be good to join
>> from time to time.  Maybe a time slot that isn't the same every
>> week would help open it more widely?
>>
>> One note of caution.  This list has to be the project's primary forum.
>> That's for reasons of openness: what gets posted here is public,
>> and archived for posterity where anyone interested in the project
>> can find it.  If anything important or useful happens in IRC,
>> please report back to the list!
>>
>> -- 
>> Nick Kew

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>

Re: Weekly calls/chats?

Posted by Benjamin Young <by...@bigbluehat.com>.
Sorry I missed this one folks! The new time (starting next week) will be a better fit for me, so hopefully I'll miss less often. :-/

Also, looks like y'all got good stuff done! Thank you!!

And...in case you've missed it, Apache turned 21 today!
https://twitter.com/bigbluehat/status/1243203375988191232?s=20

Cheers!
Benjamin


--

http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung

________________________________
From: Gerben <ge...@treora.com.INVALID>
Sent: Thursday, March 26, 2020 1:10 PM
To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
Subject: Re: Weekly calls/chats?

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>

== Today’s call notes ==
Present: Randall, Nick, Gerben
- Licensing nitty-gritty, Randall may follow up about this.
- Whether to import Randall’s dom-seek code into Annotator
<https://github.com/tilgovi/dom-seek/>; and whether then want to publish
it as a module (as people might have use for it), or just consider it
internal code we need for dom/text-quote.js (to keep a coherent set of
high-level packages, reduce maintenance&documentation effort). Probably
we will include and publish it for now, but we could decide to drop it
in the future.
- Using the highlighter package in the demo (= merge PR #62), then use
the demo in the website — but how best to depend on a lerna package
across the two repositories?


On 26/03/2020 16:36, TB Dinesh wrote:
> Thanks. We are skipping today's call. Looking forward to minutes
>
> On Thu, 26 Mar, 2020, 20:36 Gerben, <ge...@treora.com.invalid> wrote:
>
>> Reminder: this call is in (less than) an hour.
>>
>> On 19/03/2020 18:16, Gerben wrote:
>>> Notes from today’s call below.
>>>
>>> Next call, same time and place: Thursday 26 March 16:00 UTC
>>> <https://everytimezone.com/s/18066379>, in
>>> <https://meet.jit.si/apache-annotator>
>>>
>>> ===
>>>
>>> Present: Benjamin, Juan, Randall, Gerben, Nick
>>>
>>> Despite successful vote in the dev-list, the release failed because we
>>> forgot to add the Apache licence header to some source files. We will
>>> (l)earn it, some day.
>>>
>>> Discussed tasks:
>>> - add missing licence header and open a new vote — Randall
>>> - figure out what exactly to put in Licence and Notice file — Benjamin
>>> - document our processes in the repo: how to use Rat to check Apache’s
>>> requirements, how to create a release, and how to verify the
>>> contents/hashes the release objects — Randall
>>> - test & merge PR #62 to use highlighter in demo — (unassigned?)
>>> - Deduplicate the separate demos in the code repo and website repo —
>> Gerben
>>> - add the logo to the website — anyone in a good mood
>>>
>>> On 19/03/2020 17:03, Benjamin Young wrote:
>>>> Ready when y'all are. ;)
>>>>
>>>> Also, there's an (old) #annotator channel on irc.freenode.net that
>> several of us have hung out in (for years). Feel free to join there also!
>>>> Talk soon,
>>>> Benjamin
>>>>
>>>>
>>>> --
>>>>
>>>> http://bigbluehat.com/
>>>>
>>>> http://linkedin.com/in/benjaminyoung
>>>>
>>>> ________________________________
>>>> From: Gerben <ge...@treora.com.INVALID>
>>>> Sent: Wednesday, March 18, 2020 6:22 PM
>>>> To: dev@annotator.incubator.apache.org <
>> dev@annotator.incubator.apache.org>
>>>> Subject: Re: Weekly calls/chats?
>>>>
>>>> Reminder for tomorrow’s call.
>>>>
>>>> These days there is a risk that Jitsi is overloaded, let’s see if it
>>>> works and try find another instance/solution if necessary (and if so,
>>>> announce it on this list).
>>>>
>>>> 19 March 16:00 UTC: https://everytimezone.com/s/a02b29d3
>>>> Room: https://meet.jit.si/apache-annotator
>>>>
>>>> To join by phone dial one of these numbers and then enter the pin.
>>>>
>>>> PIN: 2527 1718 26
>>>>
>>>> Phone numbers:
>>>> US +1.512.402.2718
>>>> UK +44.121.468.3154
>>>> France +33.1.84.88.6478
>>>> Germany +49.89.380.38719
>>>> Spain +34.932.205.409
>>>> Canada +1.647.243.6108
>>>> Australia +61.8.7150.1136
>>>> Brazil +55.21.3500.0112
>>>> Japan +81.3.4510.2372
>>>> Switzerland +41.61.588.0496
>>>>
>>>>

Re: Weekly calls/chats?

Posted by Gerben <ge...@treora.com.INVALID>.
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>.
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>

== Today’s call notes ==
Present: Randall, Nick, Gerben
- Licensing nitty-gritty, Randall may follow up about this.
- Whether to import Randall’s dom-seek code into Annotator
<https://github.com/tilgovi/dom-seek/>; and whether then want to publish
it as a module (as people might have use for it), or just consider it
internal code we need for dom/text-quote.js (to keep a coherent set of
high-level packages, reduce maintenance&documentation effort). Probably
we will include and publish it for now, but we could decide to drop it
in the future.
- Using the highlighter package in the demo (= merge PR #62), then use
the demo in the website — but how best to depend on a lerna package
across the two repositories?


On 26/03/2020 16:36, TB Dinesh wrote:
> Thanks. We are skipping today's call. Looking forward to minutes
>
> On Thu, 26 Mar, 2020, 20:36 Gerben, <ge...@treora.com.invalid> wrote:
>
>> Reminder: this call is in (less than) an hour.
>>
>> On 19/03/2020 18:16, Gerben wrote:
>>> Notes from today’s call below.
>>>
>>> Next call, same time and place: Thursday 26 March 16:00 UTC
>>> <https://everytimezone.com/s/18066379>, in
>>> <https://meet.jit.si/apache-annotator>
>>>
>>> ===
>>>
>>> Present: Benjamin, Juan, Randall, Gerben, Nick
>>>
>>> Despite successful vote in the dev-list, the release failed because we
>>> forgot to add the Apache licence header to some source files. We will
>>> (l)earn it, some day.
>>>
>>> Discussed tasks:
>>> - add missing licence header and open a new vote — Randall
>>> - figure out what exactly to put in Licence and Notice file — Benjamin
>>> - document our processes in the repo: how to use Rat to check Apache’s
>>> requirements, how to create a release, and how to verify the
>>> contents/hashes the release objects — Randall
>>> - test & merge PR #62 to use highlighter in demo — (unassigned?)
>>> - Deduplicate the separate demos in the code repo and website repo —
>> Gerben
>>> - add the logo to the website — anyone in a good mood
>>>
>>> On 19/03/2020 17:03, Benjamin Young wrote:
>>>> Ready when y'all are. ;)
>>>>
>>>> Also, there's an (old) #annotator channel on irc.freenode.net that
>> several of us have hung out in (for years). Feel free to join there also!
>>>> Talk soon,
>>>> Benjamin
>>>>
>>>>
>>>> --
>>>>
>>>> http://bigbluehat.com/
>>>>
>>>> http://linkedin.com/in/benjaminyoung
>>>>
>>>> ________________________________
>>>> From: Gerben <ge...@treora.com.INVALID>
>>>> Sent: Wednesday, March 18, 2020 6:22 PM
>>>> To: dev@annotator.incubator.apache.org <
>> dev@annotator.incubator.apache.org>
>>>> Subject: Re: Weekly calls/chats?
>>>>
>>>> Reminder for tomorrow’s call.
>>>>
>>>> These days there is a risk that Jitsi is overloaded, let’s see if it
>>>> works and try find another instance/solution if necessary (and if so,
>>>> announce it on this list).
>>>>
>>>> 19 March 16:00 UTC: https://everytimezone.com/s/a02b29d3
>>>> Room: https://meet.jit.si/apache-annotator
>>>>
>>>> To join by phone dial one of these numbers and then enter the pin.
>>>>
>>>> PIN: 2527 1718 26
>>>>
>>>> Phone numbers:
>>>> US +1.512.402.2718
>>>> UK +44.121.468.3154
>>>> France +33.1.84.88.6478
>>>> Germany +49.89.380.38719
>>>> Spain +34.932.205.409
>>>> Canada +1.647.243.6108
>>>> Australia +61.8.7150.1136
>>>> Brazil +55.21.3500.0112
>>>> Japan +81.3.4510.2372
>>>> Switzerland +41.61.588.0496
>>>>
>>>>

Re: Weekly calls/chats?

Posted by TB Dinesh <di...@servelots.com>.
Thanks. We are skipping today's call. Looking forward to minutes

On Thu, 26 Mar, 2020, 20:36 Gerben, <ge...@treora.com.invalid> wrote:

> Reminder: this call is in (less than) an hour.
>
> On 19/03/2020 18:16, Gerben wrote:
> > Notes from today’s call below.
> >
> > Next call, same time and place: Thursday 26 March 16:00 UTC
> > <https://everytimezone.com/s/18066379>, in
> > <https://meet.jit.si/apache-annotator>
> >
> > ===
> >
> > Present: Benjamin, Juan, Randall, Gerben, Nick
> >
> > Despite successful vote in the dev-list, the release failed because we
> > forgot to add the Apache licence header to some source files. We will
> > (l)earn it, some day.
> >
> > Discussed tasks:
> > - add missing licence header and open a new vote — Randall
> > - figure out what exactly to put in Licence and Notice file — Benjamin
> > - document our processes in the repo: how to use Rat to check Apache’s
> > requirements, how to create a release, and how to verify the
> > contents/hashes the release objects — Randall
> > - test & merge PR #62 to use highlighter in demo — (unassigned?)
> > - Deduplicate the separate demos in the code repo and website repo —
> Gerben
> > - add the logo to the website — anyone in a good mood
> >
> > On 19/03/2020 17:03, Benjamin Young wrote:
> >> Ready when y'all are. ;)
> >>
> >> Also, there's an (old) #annotator channel on irc.freenode.net that
> several of us have hung out in (for years). Feel free to join there also!
> >>
> >> Talk soon,
> >> Benjamin
> >>
> >>
> >> --
> >>
> >> http://bigbluehat.com/
> >>
> >> http://linkedin.com/in/benjaminyoung
> >>
> >> ________________________________
> >> From: Gerben <ge...@treora.com.INVALID>
> >> Sent: Wednesday, March 18, 2020 6:22 PM
> >> To: dev@annotator.incubator.apache.org <
> dev@annotator.incubator.apache.org>
> >> Subject: Re: Weekly calls/chats?
> >>
> >> Reminder for tomorrow’s call.
> >>
> >> These days there is a risk that Jitsi is overloaded, let’s see if it
> >> works and try find another instance/solution if necessary (and if so,
> >> announce it on this list).
> >>
> >> 19 March 16:00 UTC: https://everytimezone.com/s/a02b29d3
> >> Room: https://meet.jit.si/apache-annotator
> >>
> >> To join by phone dial one of these numbers and then enter the pin.
> >>
> >> PIN: 2527 1718 26
> >>
> >> Phone numbers:
> >> US +1.512.402.2718
> >> UK +44.121.468.3154
> >> France +33.1.84.88.6478
> >> Germany +49.89.380.38719
> >> Spain +34.932.205.409
> >> Canada +1.647.243.6108
> >> Australia +61.8.7150.1136
> >> Brazil +55.21.3500.0112
> >> Japan +81.3.4510.2372
> >> Switzerland +41.61.588.0496
> >>
> >>
>

Re: Weekly calls/chats?

Posted by Gerben <ge...@treora.com.INVALID>.
Reminder: this call is in (less than) an hour.

On 19/03/2020 18:16, Gerben wrote:
> Notes from today’s call below.
>
> Next call, same time and place: Thursday 26 March 16:00 UTC
> <https://everytimezone.com/s/18066379>, in
> <https://meet.jit.si/apache-annotator>
>
> ===
>
> Present: Benjamin, Juan, Randall, Gerben, Nick
>
> Despite successful vote in the dev-list, the release failed because we
> forgot to add the Apache licence header to some source files. We will
> (l)earn it, some day.
>
> Discussed tasks:
> - add missing licence header and open a new vote — Randall
> - figure out what exactly to put in Licence and Notice file — Benjamin
> - document our processes in the repo: how to use Rat to check Apache’s
> requirements, how to create a release, and how to verify the
> contents/hashes the release objects — Randall
> - test & merge PR #62 to use highlighter in demo — (unassigned?)
> - Deduplicate the separate demos in the code repo and website repo — Gerben
> - add the logo to the website — anyone in a good mood
>
> On 19/03/2020 17:03, Benjamin Young wrote:
>> Ready when y'all are. ;)
>>
>> Also, there's an (old) #annotator channel on irc.freenode.net that several of us have hung out in (for years). Feel free to join there also!
>>
>> Talk soon,
>> Benjamin
>>
>>
>> --
>>
>> http://bigbluehat.com/
>>
>> http://linkedin.com/in/benjaminyoung
>>
>> ________________________________
>> From: Gerben <ge...@treora.com.INVALID>
>> Sent: Wednesday, March 18, 2020 6:22 PM
>> To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
>> Subject: Re: Weekly calls/chats?
>>
>> Reminder for tomorrow’s call.
>>
>> These days there is a risk that Jitsi is overloaded, let’s see if it
>> works and try find another instance/solution if necessary (and if so,
>> announce it on this list).
>>
>> 19 March 16:00 UTC: https://everytimezone.com/s/a02b29d3
>> Room: https://meet.jit.si/apache-annotator
>>
>> To join by phone dial one of these numbers and then enter the pin.
>>
>> PIN: 2527 1718 26
>>
>> Phone numbers:
>> US +1.512.402.2718
>> UK +44.121.468.3154
>> France +33.1.84.88.6478
>> Germany +49.89.380.38719
>> Spain +34.932.205.409
>> Canada +1.647.243.6108
>> Australia +61.8.7150.1136
>> Brazil +55.21.3500.0112
>> Japan +81.3.4510.2372
>> Switzerland +41.61.588.0496
>>
>>

Re: Weekly calls/chats?

Posted by Gerben <ge...@treora.com.INVALID>.
Notes from today’s call below.

Next call, same time and place: Thursday 26 March 16:00 UTC
<https://everytimezone.com/s/18066379>, in
<https://meet.jit.si/apache-annotator>

===

Present: Benjamin, Juan, Randall, Gerben, Nick

Despite successful vote in the dev-list, the release failed because we
forgot to add the Apache licence header to some source files. We will
(l)earn it, some day.

Discussed tasks:
- add missing licence header and open a new vote — Randall
- figure out what exactly to put in Licence and Notice file — Benjamin
- document our processes in the repo: how to use Rat to check Apache’s
requirements, how to create a release, and how to verify the
contents/hashes the release objects — Randall
- test & merge PR #62 to use highlighter in demo — (unassigned?)
- Deduplicate the separate demos in the code repo and website repo — Gerben
- add the logo to the website — anyone in a good mood

On 19/03/2020 17:03, Benjamin Young wrote:
> Ready when y'all are. ;)
>
> Also, there's an (old) #annotator channel on irc.freenode.net that several of us have hung out in (for years). Feel free to join there also!
>
> Talk soon,
> Benjamin
>
>
> --
>
> http://bigbluehat.com/
>
> http://linkedin.com/in/benjaminyoung
>
> ________________________________
> From: Gerben <ge...@treora.com.INVALID>
> Sent: Wednesday, March 18, 2020 6:22 PM
> To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
> Subject: Re: Weekly calls/chats?
>
> Reminder for tomorrow’s call.
>
> These days there is a risk that Jitsi is overloaded, let’s see if it
> works and try find another instance/solution if necessary (and if so,
> announce it on this list).
>
> 19 March 16:00 UTC: https://everytimezone.com/s/a02b29d3
> Room: https://meet.jit.si/apache-annotator
>
> To join by phone dial one of these numbers and then enter the pin.
>
> PIN: 2527 1718 26
>
> Phone numbers:
> US +1.512.402.2718
> UK +44.121.468.3154
> France +33.1.84.88.6478
> Germany +49.89.380.38719
> Spain +34.932.205.409
> Canada +1.647.243.6108
> Australia +61.8.7150.1136
> Brazil +55.21.3500.0112
> Japan +81.3.4510.2372
> Switzerland +41.61.588.0496
>
>

Re: Weekly calls/chats?

Posted by Benjamin Young <by...@bigbluehat.com>.
Ready when y'all are. ;)

Also, there's an (old) #annotator channel on irc.freenode.net that several of us have hung out in (for years). Feel free to join there also!

Talk soon,
Benjamin


--

http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung

________________________________
From: Gerben <ge...@treora.com.INVALID>
Sent: Wednesday, March 18, 2020 6:22 PM
To: dev@annotator.incubator.apache.org <de...@annotator.incubator.apache.org>
Subject: Re: Weekly calls/chats?

Reminder for tomorrow’s call.

These days there is a risk that Jitsi is overloaded, let’s see if it
works and try find another instance/solution if necessary (and if so,
announce it on this list).

19 March 16:00 UTC: https://everytimezone.com/s/a02b29d3
Room: https://meet.jit.si/apache-annotator

To join by phone dial one of these numbers and then enter the pin.

PIN: 2527 1718 26

Phone numbers:
US +1.512.402.2718
UK +44.121.468.3154
France +33.1.84.88.6478
Germany +49.89.380.38719
Spain +34.932.205.409
Canada +1.647.243.6108
Australia +61.8.7150.1136
Brazil +55.21.3500.0112
Japan +81.3.4510.2372
Switzerland +41.61.588.0496


Re: Weekly calls/chats?

Posted by Gerben <ge...@treora.com.INVALID>.
Reminder for tomorrow’s call.

These days there is a risk that Jitsi is overloaded, let’s see if it
works and try find another instance/solution if necessary (and if so,
announce it on this list).

19 March 16:00 UTC: https://everytimezone.com/s/a02b29d3
Room: https://meet.jit.si/apache-annotator

To join by phone dial one of these numbers and then enter the pin.

PIN: 2527 1718 26

Phone numbers:
US +1.512.402.2718
UK +44.121.468.3154
France +33.1.84.88.6478
Germany +49.89.380.38719
Spain +34.932.205.409
Canada +1.647.243.6108
Australia +61.8.7150.1136
Brazil +55.21.3500.0112
Japan +81.3.4510.2372
Switzerland +41.61.588.0496


Re: Weekly calls/chats?

Posted by Christian von Uffel <ch...@cvonu.com>.
I seem to keep missing these meeting notifications. 

Hope to catch the next meeting.

On 2020/03/12 16:25:25, Gerben <ge...@treora.com.INVALID> wrote: 
> Sorry to hear; if it helps, these phone numbers should also let you call in:
> 
>     To join your meeting, dial one of these numbers and then enter the pin.
>     PIN: 2527 1718 26
> 
>     Country 	Dial-in Numbers 	
>     US 	
> 
>       * +1.512.402.2718
> 
>     	
> 
>       *
> 
> 
>     UK 	
> 
>       * +44.121.468.3154
> 
>     	
> 
>       *
> 
> 
>     France 	
> 
>       * +33.1.84.88.6478
> 
>     	
> 
>       *
> 
> 
>     Germany 	
> 
>       * +49.89.380.38719
> 
>     	
> 
>       *
> 
> 
>     Spain 	
> 
>       * +34.932.205.409
> 
>     	
> 
>       *
> 
> 
>     Canada 	
> 
>       * +1.647.243.6108
> 
>     	
> 
>       *
> 
> 
>     Australia 	
> 
>       * +61.8.7150.1136
> 
>     	
> 
>       *
> 
> 
>     Brazil 	
> 
>       * +55.21.3500.0112
> 
>     	
> 
>       *
> 
> 
>     Japan 	
> 
>       * +81.3.4510.2372
> 
>     	
> 
>       *
> 
> 
>     Switzerland 	
> 
>       * +41.61.588.0496
> 
> On 12/03/2020 17:21, Nick Kew wrote:
> > On Wed, 11 Mar 2020 16:35:50 -0700
> > Randall Leeds <ra...@gmail.com> wrote:
> >
> >> Reminder for the upcoming call:
> >>
> >> 12 March 16:00 UTC: https://everytimezone.com/s/a80c98c6
> >> Video link: https://meet.jit.si/apache-annotator
> > I can't see or hear anything beyond a line of aliases
> > (a "tbd" and a "bhanu" and a couple of anons).
> >
> > That's on the laptop.  I first tried the desktop, which
> > wouldn't play at all, then the phone, which wanted me to
> > download a separate app.  That's mac, linux, and android.
> >
> > I expect I can figure that out, but it'll need a bit of time.
> > I was under the misapprehension it was something simple
> > like IRC!
> >
> 

Re: Weekly calls/chats?

Posted by Gerben <ge...@treora.com.INVALID>.
Sorry to hear; if it helps, these phone numbers should also let you call in:

    To join your meeting, dial one of these numbers and then enter the pin.
    PIN: 2527 1718 26

    Country 	Dial-in Numbers 	
    US 	

      * +1.512.402.2718

    	

      *


    UK 	

      * +44.121.468.3154

    	

      *


    France 	

      * +33.1.84.88.6478

    	

      *


    Germany 	

      * +49.89.380.38719

    	

      *


    Spain 	

      * +34.932.205.409

    	

      *


    Canada 	

      * +1.647.243.6108

    	

      *


    Australia 	

      * +61.8.7150.1136

    	

      *


    Brazil 	

      * +55.21.3500.0112

    	

      *


    Japan 	

      * +81.3.4510.2372

    	

      *


    Switzerland 	

      * +41.61.588.0496

On 12/03/2020 17:21, Nick Kew wrote:
> On Wed, 11 Mar 2020 16:35:50 -0700
> Randall Leeds <ra...@gmail.com> wrote:
>
>> Reminder for the upcoming call:
>>
>> 12 March 16:00 UTC: https://everytimezone.com/s/a80c98c6
>> Video link: https://meet.jit.si/apache-annotator
> I can't see or hear anything beyond a line of aliases
> (a "tbd" and a "bhanu" and a couple of anons).
>
> That's on the laptop.  I first tried the desktop, which
> wouldn't play at all, then the phone, which wanted me to
> download a separate app.  That's mac, linux, and android.
>
> I expect I can figure that out, but it'll need a bit of time.
> I was under the misapprehension it was something simple
> like IRC!
>

Re: Weekly calls/chats?

Posted by Nick Kew <ni...@apache.org>.
On Wed, 11 Mar 2020 16:35:50 -0700
Randall Leeds <ra...@gmail.com> wrote:

> Reminder for the upcoming call:
> 
> 12 March 16:00 UTC: https://everytimezone.com/s/a80c98c6
> Video link: https://meet.jit.si/apache-annotator

I can't see or hear anything beyond a line of aliases
(a "tbd" and a "bhanu" and a couple of anons).

That's on the laptop.  I first tried the desktop, which
wouldn't play at all, then the phone, which wanted me to
download a separate app.  That's mac, linux, and android.

I expect I can figure that out, but it'll need a bit of time.
I was under the misapprehension it was something simple
like IRC!

-- 
Nick Kew

Re: Weekly calls/chats?

Posted by Randall Leeds <ra...@gmail.com>.
Reminder for the upcoming call:

12 March 16:00 UTC: https://everytimezone.com/s/a80c98c6
Video link: https://meet.jit.si/apache-annotator

On Thu, Mar 5, 2020 at 2:41 PM Gerben <ge...@treora.com.invalid> wrote:

> If it indeed works for everyone, we could follow Nick’s suggestion and
> default to run regularly on Thursdays 16:00 London time (= 16:00 UTC
> this month, 17:00 UTC from April onwards).
>
> So unless there are requests for an alternative, the next meeting would
> be 12 March 16:00 UTC. <https://everytimezone.com/s/a80c98c6>
>
> Note that in at least the USA, clocks jump this weekend already, so e.g.
> in California it will be at 9am this month, then 8am. In India, no clock
> jumps (great idea), so it will be 21:30 this month, then 20:30. If I am
> not making errors, that is — check with your local clockarian.
>
> Below are a few notes from last week’s call (apologies for the delay)
> and today’s call.
>
> ======
>
> Notes of last week’s call, 27 Feb 2020 21:00 UTC
>
> Present: Jake, Randall, Christoph, Gerben
>
> - Jake started writing API documentation for the project’s current code
> (for exported functions), plans to submit a pull request soon.
>
> - Randall intends to open a vote tonight for the initial release.
>
> - Christoph is interested in contributing to project aspects like its
> documentation and website.
>
> - Gerben made a pull request to add a text highlighter package to the repo
>
> - The Chrome browser just shipped a feature to scroll to and highlight a
> text fragment given in the address bar:
> <https://github.com/WICG/ScrollToTextFragment>. It could be worthwile to
> implement this spec as a polyfill (see issue #60
> <https://github.com/apache/incubator-annotator/issues/60>), create a
> test suite around it, and/or create a browser extension that adds
> support in other browsers (which could be based on Gerben’s Precise
> Links extension: <https://github.com/Treora/precise-links>).
>
> - Question: How far is annotator from being ready for outside developer
> implementation?
>   Responses: Some modules can already be used, but notably this system
> is not a complete package such as Annotator.js. The current approach is
> rather to build small modules for converting between JSON annotation
> objects/‘descriptors’ and Range objects in a DOM (in both directions:
> ‘anchoring’ & ‘describing’).
>     - Downsides for using it right now: the feature set is limited (the
> focus is only on TextQuoteSelectors, and it does not do fuzzy matching),
> the quality is still mediocre (it may fail to anchor in various
> situations), and the API may well change in the future.
>     - Upsides that may already make it valuable: it returns multiple
> matches and its design is asynchronous, which could be important when
> dealing with large documents.
>
> =======
>
> Notes of today’s call,  5 March 2020 21:00 UTC
>
> Present: Gerben, Randall
>
> - The vote process was started but done incorrectly (it should first
> have been only on the dev-list); moreover due to bad timing less than
> three PPMC members managed to respond their required +1s.
>
> - Randall will open a new vote today.
>
> - Two PRs were merged; as we will run a vote again anyway these can
> directly be included in the release.
>
> - Gerben will tweak the demo code to use the newly added highlighter
> package.
>
> ======
>
>
> On 05/03/2020 16:42, Randall Leeds wrote:
> > 4pm London right now is 8am here in California, 11am on the east coast of
> > the US.
> >
> > That would work well for me in the future!
> >
> > On Thu, Mar 5, 2020, 04:38 TB Dinesh <di...@servelots.com> wrote:
> >
> >> That's 3am or 5am in the dev hots in the valley. Benjamin is likely up
> and
> >> wide eyed by 7am.
> >>
> >> On Thu, 5 Mar, 2020, 17:40 Nick Kew, <ni...@apache.org> wrote:
> >>
> >>>
> >>>> On 5 Mar 2020, at 09:39, TB Dinesh <di...@servelots.com> wrote:
> >>>>
> >>>> If we do weekly calls, we can alternate week time that suits
> india/east
> >>> and
> >>>> other the west.
> >>> When I worked in a team that spanned Silicon Valley and Bangalore,
> >>> we had weekly meetings mostly at 4pm UK time - which is either
> >>> 15:00 or 16:00 GMT according to Daylight Saving Time.
> >>> Nice for us in Europe, and also worked for the US and India.
> >>>
> >>> Maybe that would fix things for you and me, if not for any prospective
> >>> participants in Far East timezones?
> >>>
> >>> --
> >>> Nick Kew
> >>>
>

Re: Weekly calls/chats?

Posted by Gerben <ge...@treora.com.INVALID>.
If it indeed works for everyone, we could follow Nick’s suggestion and
default to run regularly on Thursdays 16:00 London time (= 16:00 UTC
this month, 17:00 UTC from April onwards).

So unless there are requests for an alternative, the next meeting would
be 12 March 16:00 UTC. <https://everytimezone.com/s/a80c98c6>

Note that in at least the USA, clocks jump this weekend already, so e.g.
in California it will be at 9am this month, then 8am. In India, no clock
jumps (great idea), so it will be 21:30 this month, then 20:30. If I am
not making errors, that is — check with your local clockarian.

Below are a few notes from last week’s call (apologies for the delay)
and today’s call.

======

Notes of last week’s call, 27 Feb 2020 21:00 UTC

Present: Jake, Randall, Christoph, Gerben

- Jake started writing API documentation for the project’s current code
(for exported functions), plans to submit a pull request soon.

- Randall intends to open a vote tonight for the initial release.

- Christoph is interested in contributing to project aspects like its
documentation and website.

- Gerben made a pull request to add a text highlighter package to the repo

- The Chrome browser just shipped a feature to scroll to and highlight a
text fragment given in the address bar:
<https://github.com/WICG/ScrollToTextFragment>. It could be worthwile to
implement this spec as a polyfill (see issue #60
<https://github.com/apache/incubator-annotator/issues/60>), create a
test suite around it, and/or create a browser extension that adds
support in other browsers (which could be based on Gerben’s Precise
Links extension: <https://github.com/Treora/precise-links>).

- Question: How far is annotator from being ready for outside developer
implementation?
  Responses: Some modules can already be used, but notably this system
is not a complete package such as Annotator.js. The current approach is
rather to build small modules for converting between JSON annotation
objects/‘descriptors’ and Range objects in a DOM (in both directions:
‘anchoring’ & ‘describing’).
    - Downsides for using it right now: the feature set is limited (the
focus is only on TextQuoteSelectors, and it does not do fuzzy matching),
the quality is still mediocre (it may fail to anchor in various
situations), and the API may well change in the future.
    - Upsides that may already make it valuable: it returns multiple
matches and its design is asynchronous, which could be important when
dealing with large documents.

=======

Notes of today’s call,  5 March 2020 21:00 UTC

Present: Gerben, Randall

- The vote process was started but done incorrectly (it should first
have been only on the dev-list); moreover due to bad timing less than
three PPMC members managed to respond their required +1s.

- Randall will open a new vote today.

- Two PRs were merged; as we will run a vote again anyway these can
directly be included in the release.

- Gerben will tweak the demo code to use the newly added highlighter
package.

======


On 05/03/2020 16:42, Randall Leeds wrote:
> 4pm London right now is 8am here in California, 11am on the east coast of
> the US.
>
> That would work well for me in the future!
>
> On Thu, Mar 5, 2020, 04:38 TB Dinesh <di...@servelots.com> wrote:
>
>> That's 3am or 5am in the dev hots in the valley. Benjamin is likely up and
>> wide eyed by 7am.
>>
>> On Thu, 5 Mar, 2020, 17:40 Nick Kew, <ni...@apache.org> wrote:
>>
>>>
>>>> On 5 Mar 2020, at 09:39, TB Dinesh <di...@servelots.com> wrote:
>>>>
>>>> If we do weekly calls, we can alternate week time that suits india/east
>>> and
>>>> other the west.
>>> When I worked in a team that spanned Silicon Valley and Bangalore,
>>> we had weekly meetings mostly at 4pm UK time - which is either
>>> 15:00 or 16:00 GMT according to Daylight Saving Time.
>>> Nice for us in Europe, and also worked for the US and India.
>>>
>>> Maybe that would fix things for you and me, if not for any prospective
>>> participants in Far East timezones?
>>>
>>> --
>>> Nick Kew
>>>

Re: Weekly calls/chats?

Posted by Randall Leeds <ra...@apache.org>.
4pm London right now is 8am here in California, 11am on the east coast of
the US.

That would work well for me in the future!

On Thu, Mar 5, 2020, 04:38 TB Dinesh <di...@servelots.com> wrote:

> That's 3am or 5am in the dev hots in the valley. Benjamin is likely up and
> wide eyed by 7am.
>
> On Thu, 5 Mar, 2020, 17:40 Nick Kew, <ni...@apache.org> wrote:
>
> >
> >
> > > On 5 Mar 2020, at 09:39, TB Dinesh <di...@servelots.com> wrote:
> > >
> > > If we do weekly calls, we can alternate week time that suits india/east
> > and
> > > other the west.
> >
> > When I worked in a team that spanned Silicon Valley and Bangalore,
> > we had weekly meetings mostly at 4pm UK time - which is either
> > 15:00 or 16:00 GMT according to Daylight Saving Time.
> > Nice for us in Europe, and also worked for the US and India.
> >
> > Maybe that would fix things for you and me, if not for any prospective
> > participants in Far East timezones?
> >
> > --
> > Nick Kew
> >
>

Re: Weekly calls/chats?

Posted by TB Dinesh <di...@servelots.com>.
That's 3am or 5am in the dev hots in the valley. Benjamin is likely up and
wide eyed by 7am.

On Thu, 5 Mar, 2020, 17:40 Nick Kew, <ni...@apache.org> wrote:

>
>
> > On 5 Mar 2020, at 09:39, TB Dinesh <di...@servelots.com> wrote:
> >
> > If we do weekly calls, we can alternate week time that suits india/east
> and
> > other the west.
>
> When I worked in a team that spanned Silicon Valley and Bangalore,
> we had weekly meetings mostly at 4pm UK time - which is either
> 15:00 or 16:00 GMT according to Daylight Saving Time.
> Nice for us in Europe, and also worked for the US and India.
>
> Maybe that would fix things for you and me, if not for any prospective
> participants in Far East timezones?
>
> --
> Nick Kew
>

Re: Weekly calls/chats?

Posted by Nick Kew <ni...@apache.org>.

> On 5 Mar 2020, at 09:39, TB Dinesh <di...@servelots.com> wrote:
> 
> If we do weekly calls, we can alternate week time that suits india/east and
> other the west.

When I worked in a team that spanned Silicon Valley and Bangalore,
we had weekly meetings mostly at 4pm UK time - which is either 
15:00 or 16:00 GMT according to Daylight Saving Time.
Nice for us in Europe, and also worked for the US and India.

Maybe that would fix things for you and me, if not for any prospective
participants in Far East timezones?

-- 
Nick Kew

Re: Weekly calls/chats?

Posted by TB Dinesh <di...@servelots.com>.
If we do weekly calls, we can alternate week time that suits india/east and
other the west.


21 GMT will be 2.30am here.
But you all should go ahead for now


On Thu, 5 Mar, 2020, 14:47 Gerben, <ge...@treora.com.invalid> wrote:

> For the weekly rhythm, let’s check in again today? Same time (5 March,
> 21:00GMT), same place: <https://meet.jit.si/apache-annotator>.
>
> For people wanting but unable to join the call this time, please suggest
> a time slot for (a) next week.
>
>
> On 21/02/2020 05:05, Jake Hartnell wrote:
> > +1
> >
> > Sent from my iPhone
> >
> >> On Feb 20, 2020, at 6:04 PM, Nick Kew <ni...@apache.org> wrote:
> >>
> >> 
> >>
> >>> On 20 Feb 2020, at 22:34, Gerben <ge...@treora.com.INVALID> wrote:
> >>>
> >>> Hi all, I just talked with Randall; to get things rolling our idea was
> >>> to simply call again next week (Thursday 27th, 21:00 GMT, assuming
> >>> Benjamin is available) and invite you all to join.
> >> I'd join, but my Thursday evenings are otherwise occupied between
> >> about 18:00 and 23:00.
> >>
> >> Don't let that stop you (it's not critical), but it would be good to
> join
> >> from time to time.  Maybe a time slot that isn't the same every
> >> week would help open it more widely?
> >>
> >> One note of caution.  This list has to be the project's primary forum.
> >> That's for reasons of openness: what gets posted here is public,
> >> and archived for posterity where anyone interested in the project
> >> can find it.  If anything important or useful happens in IRC,
> >> please report back to the list!
> >>
> >> --
> >> Nick Kew
>