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 <din...@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, <n...@apache.org> wrote: >> >>> >>>> On 5 Mar 2020, at 09:39, TB Dinesh <din...@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 >>>
