Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0 (-rc.2)

2020-03-11 Thread Randall Leeds 
On Wed, Mar 11, 2020 at 7:17 AM Benjamin Young 
wrote:

> Randall,
>
> Any thoughts on the fragment.js file situation? Otherwise this seems fine.
>

I believe Gerben correctly responded that fragment.js is built from
fragment.pegjs at build time and therefore it is purposely absent from the
source release.
Additionally, the advice to compare the tarball to a clean working
directory is good. There should be no differences in that case.

Re: Using Apache Annotator

2020-03-11 Thread Randall Leeds 
On Wed, Feb 19, 2020 at 11:03 AM Tal August 
wrote:

> Hi Annotator dev team,
>
> I'm a graduate student looking to build a lightweight annotation system for
> annotating science news articles with common writing strategies. The
> initial project is to crowdsource these annotations, but eventually my goal
> is to shift this to a volunteer-based system where people can log on to
> annotate articles as a way of improving their own writing.
>

Welcome, Tal! Sounds like a great project and exactly the sort of thing
we'd like to support.


> I have been talking with Jon Udell at Hypothes.is about using their stack
> for this project, but it sounds like it might be overkill since right now
> all I need is a way of embedding annotation into a webpages I will be
> serving and saving these annotations to my database. Annotator.js looked
> ideal for the project, but it seems like it's in maintenance mode now and
> Apache Annotator is its successor.
>

Annotator.js is indeed in maintenance mode. That project receives support
requests not infrequently, but I have little time to answer and my energy
is focused here.


> Would you recommend I use annotator.js or does Apache Annotator also
> provide this functionality?
>

The primary difference between the projects is that Apache Annotator is
focused on solving low level challenges facing developers rather than on
providing an drop-in application for publishers. By solving common
challenges we hope to enable developers to focus on higher level concerns
that are specific to their application domains.

We are in the process of making our first official release right now. The
initial focus is on reliably translating browser text selections to JSON
and vice versa.


> Happy to answer any questions you might have. Thank you also for building
> this amazing tool! I have spent the last week looking over annotation
> toolkits, and it's awesome what you are building.
>

Thank you, Tal! We've been getting Apache Annotator started slowly, and
welcome your involvement in any capacity. Several of us in the community
hang out in the #annotator channel on the Freenode IRC server if you want
to chat in realtime.

Hope to hear from you again soon. Watch this list for announcements about
the release and keep us informed of any of your successes and *especially*
failures to get started with the project.

Re: Weekly calls/chats?

2020-03-11 Thread Randall Leeds 
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  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. 
>
> 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:
> . It could be worthwile to
> implement this spec as a polyfill (see issue #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: ).
>
> - 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  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,  wrote:
> >>
> >>>
>  On 5 Mar 2020, at 09:39, TB Dinesh  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: [VOTE] Release Apache Annotator (incubating) version 0.1.0 (-rc.2)

2020-03-11 Thread Benjamin Young 
Randall,

Any thoughts on the fragment.js file situation? Otherwise this seems fine.


--

http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung


From: TB Dinesh 
Sent: Wednesday, March 11, 2020 5:22 AM
To: dev@annotator.incubator.apache.org 
Cc: Jack Park 
Subject: Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0 (-rc.2)

+1

+1 for Benjamin's remarks too :)

On Tue, Mar 10, 2020 at 8:39 PM Benjamin Young  wrote:
>
> +1 from me--with huge gratitude to Randall for making this all happen!! :D
>
> The signature and sha's all checked out fine. My local diff (on Windows) has 
> line ending differences (which I know about...per my git config). My diff 
> also shows the following files in the git checkout which are not in the 
> tarball--all of which I think are fine, but wanted to confirm and/or document 
> for future comparison/checks.
>
> Files in local git checkout which are not in the tarball include:
>  - .git/ (as for Randall)
>  - .nyc_output/ (probably due to a different reporter I used at some point)
>  - node_modules/ (we don't ship this in the tarball...nor should we afaik)
>  - packages/fragment-identifier/node_modules/ (same as above)
>  - packages/fragment-identifier/src/fragment.js (...not sure about this 
> one...)
>
> Everything else is identical (ignoring line endings--per platform 
> differences).
>
> Any thoughts (or explanations) about the fragment.js situation?
>
> Otherwise this looks fabulous. Thank you!
> Benjamin
>
> --
>
> http://bigbluehat.com/
>
> http://linkedin.com/in/benjaminyoung
>
> 
> From: Jack Park 
> Sent: Tuesday, March 10, 2020 10:23 AM
> To: dev@annotator.incubator.apache.org 
> Subject: Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0 
> (-rc.2)
>
> +1
>
> On Mon, Mar 9, 2020 at 10:20 PM Randall Leeds  wrote:
>
> > I'll kick it off.
> >
> > No differences between tarball and the git tag:
> >
> >   > diff -r apache-annotator-0.1.0-incubating annotator-git
> >   Only in annotator: .git
> >
> > Valid checksums:
> >
> >   > sha256sum -c apache-annotator-0.1.0-rc.2-incubating.tar.gz.sha256
> >   apache-annotator-0.1.0-rc.2-incubating.tar.gz: OK
> >
> >   > sha512sum -c apache-annotator-0.1.0-rc.2-incubating.tar.gz.sha512
> >   apache-annotator-0.1.0-rc.2-incubating.tar.gz: OK
> >
> > Valid signature (from me):
> >
> >   > gpg --verify apache-annotator-0.1.0-rc.2-incubating.tar.gz.asc
> >   gpg: assuming signed data in
> > 'apache-annotator-0.1.0-rc.2-incubating.tar.gz'
> >   gpg: Signature made Mon 09 Mar 2020 09:36:50 PM PDT
> >   gpg:using RSA key
> > 83CBD56B79A00C8693C0B919ED6455D90F33F0BB
> >   gpg: Good signature from "Randall Leeds "
> > [ultimate]
> >   gpg: aka "Randall Leeds "
> > [ultimate]
> >   gpg: aka "Randall Leeds " [ultimate]
> >
> > Running `make check` passes in the apache-annotator-0.1.0-incubating
> > directory unpacked from the tarball (Node.js v13.10.1, Yarn v1.22.0).
> >
> > +1 from me!
> >
> > On Mon, Mar 9, 2020 at 9:43 PM Randall Leeds  wrote:
> >
> > > Dear community,
> > >
> > > I would like to propose we release Apache Annotator (incubating) 0.1.0.
> > >
> > > This is the second release candidate. The first vote was aborted because
> > > it was not made on this list before being brought to the incubator PMC.
> > >
> > > This is the first release of Apache Annotator and represents a modest but
> > > exciting step for the community. We encourage everyone to help us verify
> > > that the release is proper and help identify and fix any critical issues
> > > with the project's packaging or the proper functioning of the build.
> > >
> > > The release artifacts are available here:
> > >
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/annotator/source/0.1.0/rc.2
> > >
> > > There you will find a tarball, a GPG signature, and SHA256/SHA512
> > > checksums.
> > >
> > > A KEYS file for checking the signatures can be found here:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/annotator/KEYS
> > >
> > > Please verify that the build is from commit
> > > 2eb484150c0fa86a144fa3f3f6811e856e761dd6, tagged as v0.1.0-rc.2, by
> > > checking out the source tree and comparing it to the contents of the
> > > tarball.
> > >
> > > Please validate the release by checking that the signature and checksums
> > > are valid for the uploaded tarball and then unpacking it and ensuring
> > that
> > > `make && make check` exits cleanly.
> > >
> > > If you would like to further validate the packaging, the repository is
> > set
> > > up for Apache Rat to check for proper license headers and notifications.
> > As
> > > this is our first release, it is important to us that we get these
> > > processes correctly in place.
> > >
> > > If the vote passes, these artifacts will be proposed to Apache Incubator
> > > for release as Apache Annotator (incubating) 0.1.0.
> > >
> > > Regards,
> > > Randall Leed

Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0 (-rc.2)

2020-03-11 Thread TB Dinesh 
+1

+1 for Benjamin's remarks too :)

On Tue, Mar 10, 2020 at 8:39 PM Benjamin Young  wrote:
>
> +1 from me--with huge gratitude to Randall for making this all happen!! :D
>
> The signature and sha's all checked out fine. My local diff (on Windows) has 
> line ending differences (which I know about...per my git config). My diff 
> also shows the following files in the git checkout which are not in the 
> tarball--all of which I think are fine, but wanted to confirm and/or document 
> for future comparison/checks.
>
> Files in local git checkout which are not in the tarball include:
>  - .git/ (as for Randall)
>  - .nyc_output/ (probably due to a different reporter I used at some point)
>  - node_modules/ (we don't ship this in the tarball...nor should we afaik)
>  - packages/fragment-identifier/node_modules/ (same as above)
>  - packages/fragment-identifier/src/fragment.js (...not sure about this 
> one...)
>
> Everything else is identical (ignoring line endings--per platform 
> differences).
>
> Any thoughts (or explanations) about the fragment.js situation?
>
> Otherwise this looks fabulous. Thank you!
> Benjamin
>
> --
>
> http://bigbluehat.com/
>
> http://linkedin.com/in/benjaminyoung
>
> 
> From: Jack Park 
> Sent: Tuesday, March 10, 2020 10:23 AM
> To: dev@annotator.incubator.apache.org 
> Subject: Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0 
> (-rc.2)
>
> +1
>
> On Mon, Mar 9, 2020 at 10:20 PM Randall Leeds  wrote:
>
> > I'll kick it off.
> >
> > No differences between tarball and the git tag:
> >
> >   > diff -r apache-annotator-0.1.0-incubating annotator-git
> >   Only in annotator: .git
> >
> > Valid checksums:
> >
> >   > sha256sum -c apache-annotator-0.1.0-rc.2-incubating.tar.gz.sha256
> >   apache-annotator-0.1.0-rc.2-incubating.tar.gz: OK
> >
> >   > sha512sum -c apache-annotator-0.1.0-rc.2-incubating.tar.gz.sha512
> >   apache-annotator-0.1.0-rc.2-incubating.tar.gz: OK
> >
> > Valid signature (from me):
> >
> >   > gpg --verify apache-annotator-0.1.0-rc.2-incubating.tar.gz.asc
> >   gpg: assuming signed data in
> > 'apache-annotator-0.1.0-rc.2-incubating.tar.gz'
> >   gpg: Signature made Mon 09 Mar 2020 09:36:50 PM PDT
> >   gpg:using RSA key
> > 83CBD56B79A00C8693C0B919ED6455D90F33F0BB
> >   gpg: Good signature from "Randall Leeds "
> > [ultimate]
> >   gpg: aka "Randall Leeds "
> > [ultimate]
> >   gpg: aka "Randall Leeds " [ultimate]
> >
> > Running `make check` passes in the apache-annotator-0.1.0-incubating
> > directory unpacked from the tarball (Node.js v13.10.1, Yarn v1.22.0).
> >
> > +1 from me!
> >
> > On Mon, Mar 9, 2020 at 9:43 PM Randall Leeds  wrote:
> >
> > > Dear community,
> > >
> > > I would like to propose we release Apache Annotator (incubating) 0.1.0.
> > >
> > > This is the second release candidate. The first vote was aborted because
> > > it was not made on this list before being brought to the incubator PMC.
> > >
> > > This is the first release of Apache Annotator and represents a modest but
> > > exciting step for the community. We encourage everyone to help us verify
> > > that the release is proper and help identify and fix any critical issues
> > > with the project's packaging or the proper functioning of the build.
> > >
> > > The release artifacts are available here:
> > >
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/annotator/source/0.1.0/rc.2
> > >
> > > There you will find a tarball, a GPG signature, and SHA256/SHA512
> > > checksums.
> > >
> > > A KEYS file for checking the signatures can be found here:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/annotator/KEYS
> > >
> > > Please verify that the build is from commit
> > > 2eb484150c0fa86a144fa3f3f6811e856e761dd6, tagged as v0.1.0-rc.2, by
> > > checking out the source tree and comparing it to the contents of the
> > > tarball.
> > >
> > > Please validate the release by checking that the signature and checksums
> > > are valid for the uploaded tarball and then unpacking it and ensuring
> > that
> > > `make && make check` exits cleanly.
> > >
> > > If you would like to further validate the packaging, the repository is
> > set
> > > up for Apache Rat to check for proper license headers and notifications.
> > As
> > > this is our first release, it is important to us that we get these
> > > processes correctly in place.
> > >
> > > If the vote passes, these artifacts will be proposed to Apache Incubator
> > > for release as Apache Annotator (incubating) 0.1.0.
> > >
> > > Regards,
> > > Randall Leeds
> > >
> >