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

[TB Dinesh]

+1

:)

On Thu, 4 Jun, 2020, 18:53 Suzan Uskudarli, 
wrote:

>
> All checks succeed:
>
> 1. gpg --verify apache-annotator-*.tar.gz.asc  --  OK (good sigs from
> Randall Leeds)
> 2. sha256sum  and sha512sum --  OK
> apache-annotator-0.1.0-rc.4-incubating.tar.gz: OK
> 3. git remote show origin -- OK
> 4. git describe  -- OK   (v0.1.0-rc.4)
> 5. git fetch --unshallow origin tag v0.1.0-rc.4 -- OK
> 6. git status --ignored  -- OK (On branch v0.1.x, no changes added to
> commit )
> 7. make check: OK
> 8. License - OK
>
> I am attaching all the results in case it may be useful
>
> I don't know if I am eligible to vote, if I am +1
>
> On Wed, Jun 3, 2020 at 9:26 PM Benjamin Young 
> wrote:
>
>> Just completed all the tests, and everything looks great!
>>
>> +1
>>
>> (sorry again for the delay!)
>> Benjamin
>>
>>
>> --
>>
>> http://bigbluehat.com/
>>
>> http://linkedin.com/in/benjaminyoung
>>
>> 
>> From: Benjamin Young 
>> Sent: Tuesday, June 2, 2020 5:06 PM
>> To: dev@annotator.incubator.apache.org <
>> dev@annotator.incubator.apache.org>
>> Subject: Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0
>> (-rc.4)
>>
>> Started work on this today, but my day got eaten. 😕 I'll try again
>> tomorrow...
>>
>> Apologies,
>> Benjamin
>>
>>
>>
>> --
>>
>> http://bigbluehat.com/
>>
>> http://linkedin.com/in/benjaminyoung
>>
>> 
>> From: Gerben 
>> Sent: Tuesday, June 2, 2020 7:49 AM
>> To: dev@annotator.incubator.apache.org <
>> dev@annotator.incubator.apache.org>
>> Subject: Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0
>> (-rc.4)
>>
>> +1 indeed.
>>
>> I ran all checks except Rat.
>>
>> On 31/05/2020 02:52, Randall Leeds wrote:
>> > My test results:
>> >
>> > - Signature OK
>> > - Checksums OK
>> > - Local tag matches remote tag
>> > - Contents of the tarball are clean
>> > - Running "make check" passes (Node.js v10.19.0)
>> > - Apache Rat shows no files with license issues
>> >
>> > Vote: +1
>> >
>>
>

Re: Weekly calls/chats?

[TB Dinesh]

Thanks. We are skipping today's call. Looking forward to minutes

On Thu, 26 Mar, 2020, 20:36 Gerben,  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
> > , in
> > 
> >
> > ===
> >
> > 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 
> >> 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: [VOTE] Release Apache Annotator (incubating) version 0.1.0 (-rc.2)

[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
> > >
> >

Re: Weekly calls/chats?

[TB Dinesh]

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: Weekly calls/chats?

[TB Dinesh]

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,  wrote:

> For the weekly rhythm, let’s check in again today? Same time (5 March,
> 21:00GMT), same place: .
>
> 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  wrote:
> >>
> >> 
> >>
> >>> On 20 Feb 2020, at 22:34, Gerben  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
>

Targeting audio

[TB Dinesh]

Hi all,

We are trying to build some annotation tools and looking forward to
use and contribute to the Apache Annotator project. I am briefly
mentioning the context and our need here.

We have been working on Renarration Web and Alipi tools - A social
semantic web approach to bring accessible content to the low-literates
Internet users. This approach relies on Web Annotation as a
fundamental need for the billions who cannot read and write but need
to hyperlink media to help manifest a Web with audio, images, videos,
3D point cloud, .. .

We imagine a scenario where a mesh-radio setup in a rural location can
bring in a culture of creating, editing and sharing of audios. In this
world, even to navigate and discover, one would need an annotation
service to label parts of audio. Audio fragments can then be annotated
by image or portions of an image - which can be used to render the
audio with images. This process can help renew a culture of
storytelling online, even among the indigenous communities who shy
away from text.

Thanks to Gerben visiting us here in Bangalore, we have been
discussing ways to use a browser to help interconnect data (text and
media) using annotations.
To start with, we are creating browser extensions that enable
selecting a fragment of an html document, of an audio file, and
perhaps soon also of an image. Then to annotate a selected fragment,
we will need to select another fragment elsewhere to use as the
annotation body. But as a first step, we simply bookmark the fragments
of interest.

More details and state of progress soon by Gerben and Bhanu.

-dinesh

Some contextual links:
j.mp/RuralJunctions
j.mp/Janastu-mesh

Re: Annotator logo??

[TB Dinesh]

Yeah.. highlighting the links on the web

On Wed, 19 Jun, 2019, 01:52 Sarven Capadisli,  wrote:

> On 14/06/2019 14.40, Daniel Gruno wrote:
> > Hi folks,
> > do we have a logo for the annotator project? I'm asking specifically
> > because the project shows up on www.apache.org from time to time, but it
> > doesn't show a logo (so the page breaks).
> >
> > If we have a logo, where is it?
> > If we don't, I did a little doodle, at https://i.imgur.com/2WoIRc6.png
> > that we could either adopt or use temporarily till we find something
> > nifty (I have it as SVG and all that).
> >
> > WDYT?!
> >
>
>
> I think "Annotator" is in context of the Web and so the logo shouldn't
> imitate paper and pen.
>
> -Sarven
> http://csarven.ca/#i
>
>

Re: Initial Committers Roll Call

[TB Dinesh]

+1

:)

On Feb 3, 2018 00:19, "Benjamin Young"  wrote:

> Hi all!
>
>
> This email is primarily for the folks who "signed up" to be initial
> committers during the Apache Annotator Proposal process [1] (each of whom
> are BCC'd on this email).
>
>
> It's possible that some of you forgot you'd added your name to that list,
> or that now (given the life and work and time) you may no longer have an
> interest in participating, or you may have been eagerly awaiting this to
> happen and somehow missed the initial setup of the project. Regardless,
> we'd love to have you join the party! :)
>
>
> Here's a quick update, and also some links to get setup as one of the core
> contributors to Apache Annotator [2].
>
>
> First, coding is coming along nicely mostly with thanks going to Randall
> and Gerben [3]. The primary focus has been on repository structure
> (monorepo), initial code structure/planning, and NPM publication
> planning/setup. If you're interested in any of this, please checkout the
> code repo.
>
>
> Second, there's a basic promo site (if you've not seen it) at
> http://annotator.apache.org/ We'd like to get the demo integrated [4] and
> begin to provide documentation there as we're able to write it (and would
> love help writing it!). ^_^
>
>
> Lastly (and this is where our BCC'd friends come in!), we need more
> initial committers active (at least!) on the mailing list. We have folks
> interested in contributing to the code who we can't (yet) add to the
> project because we lack voting members. If you are able and willing (or
> even just able ;) ), we'd greatly appreciate the help and input on the
> mailing list, even if you lack time to code or write docs (etc).
>
>
> If you're +1 on accepting the role you signed up for as an initial
> committer, please respond (on list!) to this email and begin
> reading/skimming this guide:
>
> http://www.apache.org/dev/new-committers-guide.html#guide-
> for-new-committers
>
>
> It can be a lot to take in, but I (and our loverly mentors) will be happy
> to help you through the process. :)
>
>
> Thank you (all!) for reading this email!
>
> Benjamin
>
>
> [1] https://github.com/apache/incubator-annotator/wiki/Proposal
>
> [2] http://annotator.apache.org/
>
> [3] https://github.com/apache/incubator-annotator
>
> [4] https://github.com/apache/incubator-annotator/issues/18
>
>
>
> --
>
> http://bigbluehat.com/
>
> http://linkedin.com/in/benjaminyoung
>

Re: [VOTE] Move issues & wiki to GitHub

[TB Dinesh]

+1 for this move

Re: DOM Iteration (was Re: Just a simple example?)

[TB Dinesh]

Sasha. Thanks.
Fyi. Demo works on Chrome. Not on Firefox.

On Tue, May 16, 2017 at 12:49 AM, Sasha Goodman  wrote:
> Here is a demo of simple annotation, thanks to Benjamin:
>
> https://predict-r.github.io/annotation-model/
>
>
> On Fri, May 12, 2017 at 12:19 PM Sasha Goodman 
> wrote:
>
>> I would be delighted if my efforts were useful in this project!!!
>> Regarding that code, if any parts are used it would make my week. The class
>> structure is sorta self-documented by the standard, and combined with
>> builders the classes it can accommodate a variety of motives.
>>
>> Highlighting is the most common motive now (correct me if I'm wrong). My
>> gut-feeling is that to get the support and time of hard core annotators,
>> the code needs to accommodate the idiosyncrasies of highlighting first. For
>> example, if there are thousands of highlights on a page, an annotation
>> builder might iterate/walk the document just once and fill in the thousands
>> of highlights in one pass. Also, a highlighting app would probably need to
>> modify the source document by inserting spans and such.
>>
>> If Randall needs familiar code for node iteration, tree walking, range
>> splitting, string similarity and normalization, that's cool! Custom code,
>> *especially* Polyfill type implementations, could smooth over browser
>> idiosyncrasies. Also, I saw a Jsperf.com microbenchmark that put custom
>> walkers on par with the native browser based ones.
>>
>> On a personal note, I do archival work and did not initially see the value
>> in modifying the source document by inserting spans (however, a highlight
>> app would need that). The main reason I'm excited about annotation is its
>> value for labeling data for text analysis and machine learning. A lot of
>> the advancements in machine learning are because of large bodies of data
>> that have been tagged. The most common examples are usually of images that
>> have regions selected and then labeled, but annotation could also help turn
>> semi-structured text into more structured text data (e.g. for labeling
>> parts of government documents). For archival work on mostly static
>> documents, there does not seem to be a need to modify source document. On
>> the other hand, for dynamically changing documents, inserting spans with
>> unique IDs seems appropriate because its more robust to document changes.
>> Yet, it is also vulnerable to turf battles with other extensions and the
>> page's own javascript, so I hope it's not a requirement of the Apache
>> library but rather a feature.
>>
>>
>> On Thu, May 11, 2017 at 1:43 PM Benjamin Young 
>> wrote:
>>
>>> Exciting to see this conversation happening. ^_^
>>>
>>>
>>> Randall, how feasible would it be to bring (soon) your libraries (even
>>> via copy/paste) into the Apache Annotator repo. I believe (according to
>>> GitHub) you're author/owner of 90%+ of the code in them, and (consequently)
>>> able to do that if you believe that's the right step.
>>>
>>>
>>> Sasha you're classes modeled around the selector and a "builder" sound
>>> very similar to the hopes I wrote up in
>>> https://cwiki.apache.org/confluence/display/ANNO/Planning
>>>
>>>
>>> I'd very much like to combine these efforts in some way.
>>>
>>>
>>> Additionally--and the thing driving me personally at the moment--I have
>>> to present on Apache Annotator next Wednesday!
>>>
>>> https://apachecon2017.sched.com/event/AbBW
>>>
>>>
>>> Consequently, I'd very much love it if we (collectively) could build a
>>> demo together! There's plenty to talk about wrt to annotation, community
>>> building, Web Annotation Data Model & Protocol, as well as why (those of us
>>> that are here at least) have chosen to start collaborating at the ASF.
>>>
>>>
>>> At any rate, I plan to be coding on all the things leading up to
>>> Wednesday, so any help, input, pointers, and code (hehe) that anyone wants
>>> to toss in ahead of my codez, I'd be most grateful to code together!
>>>
>>>
>>> Thanks, all!
>>>
>>> Benjamin
>>>
>>> --
>>>
>>> http://bigbluehat.com/
>>>
>>> http://linkedin.com/in/benjaminyoung
>>>
>>> 
>>> From: Randall Leeds 
>>> Sent: Thursday, May 11, 2017 3:34:24 PM
>>> To: dev@annotator.incubator.apache.org
>>> Subject: DOM Iteration (was Re: Just a simple example?)
>>>
>>> Great to see you here, Sasha!
>>>
>>> On Wed, May 10, 2017 at 5:39 PM Sasha Goodman 
>>> wrote:
>>>
>>> >
>>> > P.S. This afternoon I streamlined the TextQuoteSelector and
>>> > TextPositionSelector to work (in principle ) consistently with Randall
>>> > Leed's implementation that used NodeIterator and textContents.
>>> >
>>> >
>>> Neat :).
>>>
>>> I think my takeaway from the simple example thread, and something of which
>>> many of us were likely already well aware, is that there's a desire for a
>>> good highlighter implementation. A way to highlight text is often the
>>> first
>>> example people want to see.
>>>
>>> While I hope to see experimentation with implementations t

Re: I Annotate Hack Day

[TB Dinesh]

tbdin...@gmail.com  is mine for a hangout

On Thu, May 4, 2017 at 11:19 PM, Andrew Hedges  wrote:
> This detail is super helpful. Thanks, Dinesh!
>
> We’ll be using a channel on the Annotating All Knowledge Slack team that
> day.
>
> https://hypothes.is/aak-slack/
>
> Please send me the Google account(s) for us to add to the Hangout on the
> day.
>
> Also, feel free to ask any Hypothesis-specific questions in our #public
> channel to get a head start on Saturday.
>
> Looking forward to your team’s participation!
>
> Andrew Hedges
> Engineering Manager, Hypothesis
> http://hypothes.is
>
> On May 4, 2017, at 8:41 AM, TB Dinesh  wrote:
>
> We will be on slack (hypothesis channel?) for the iannotate.org hackday
> (will be a hack night as it will be 9pm to 5am over here in India!)
> and also on #servelots irc on freenode for internal discussions
>
> Hangout should be okay for video intros.
> We can provide the hangout ids on Slack when we get started on the 6th.
>
> Our specific use case is written up here
>   https://www.w3.org/annotation/wiki/Use_Cases/Social_Semantic_web
>
> Here is what we have as a goal for Saturday:
>
> to authenticate a user,
>   {how is this done in h and can we use the auth api of h?}
> to annotate something on a page,
>   {we plan to start with annotator.apache.org code}
> to generate a w3c rec standard anno,
> to store the annotation in repo,
>   {we will have a hosted mangoserver conforming to w3c annotation protocol}
> to pull annos related to a page,
> to filter based on users, etc
> to annotate video
> to annotate images
> to be able to store lists of annotations
>
> We look at the projects/code at
>
> https://github.com/openannotation/annotator/wiki
>
> and see how to bring parts of it to annotator.apache.org
>
> note: what the best resource to use to add image annotation to annotator?
> iiif has some things we can reuse or do we just use code from annotorious
>
> Look forward to pointers on this - sooner the better - so we can get
> prepared for the hackday.
>
> Looking forward,
> -dinesh and team
>
>
>
> On Wed, May 3, 2017 at 10:47 PM, Andrew Hedges  wrote:
>
> Hey Dinesh,
>
>
> Of course I welcome your participation however you think it makes sense.
>
> We'll of course be on our public Slack channel throughout the day and could
>
> use a Hangout to videoconference you and others in for the intros and EOD
>
> presentations. Let me know how you'd like to take part.
>
>
> Andrew Hedges
>
> Engineering Manager, Hypothesis
>
> http://hypothes.is
>
>
> On May 1, 2017, at 10:35 PM, TB Dinesh  wrote:
>
>
> Hi Andrew..
>
>
> We can remotely hack up from Bangalore and other places.
>
>
> Keep us posted
>
>
> On 2 May 2017 10:56, "Andrew Hedges"  wrote:
>
>
> Hi everyone! I'm writing to set the stage for the I Annotate Hack Day
>
> coming up this Saturday @ Fort Mason Center, Landmark Building C, Room
>
> C-230.
>
>
> We have nearly 40 people signed up to participate. The day will be pretty
>
> informal, but will flow roughly as follows:
>
>
> 8:30–9:00am — Coffee, tea, & light breakfast
>
> 9:00am — Kickoff & intros, share what project you're working on or let
>
> others know you're available to help with theirs
>
> 9:30am–Noon — Hack alongside Hypothesis engineers and other I Annotate
>
> attendees
>
> Noon–1:00pm — Lunch
>
> 1:00–4:30pm — Hack day, continued
>
> 4:30pm — Presentations and demos by participants
>
> 5:30–8:00pm — Hack Day BBQ @ 3 Fort Mason
>
>
> The Hack Day is not Hypothesis-specific, but Hypothesis engineers will be
>
> available to work alongside anyone leveraging our stack or API.
>
>
> We're super excited by the level of interest in the Hack Day and can't
>
> wait to see what you're working on!
>
>
> See you Saturday,
>
> Andrew & the Hypothesis Engineering Team
>
>
> -
>
> Andrew Hedges
>
> Engineering Manager, Hypothesis
>
> http://hypothes.is
>
>
>

Re: I Annotate Hack Day

[TB Dinesh]

We will be on slack (hypothesis channel?) for the iannotate.org hackday
(will be a hack night as it will be 9pm to 5am over here in India!)
and also on #servelots irc on freenode for internal discussions

Hangout should be okay for video intros.
We can provide the hangout ids on Slack when we get started on the 6th.

Our specific use case is written up here
   https://www.w3.org/annotation/wiki/Use_Cases/Social_Semantic_web

Here is what we have as a goal for Saturday:

to authenticate a user,
   {how is this done in h and can we use the auth api of h?}
to annotate something on a page,
   {we plan to start with annotator.apache.org code}
to generate a w3c rec standard anno,
to store the annotation in repo,
   {we will have a hosted mangoserver conforming to w3c annotation protocol}
to pull annos related to a page,
to filter based on users, etc
to annotate video
to annotate images
to be able to store lists of annotations

We look at the projects/code at

https://github.com/openannotation/annotator/wiki

and see how to bring parts of it to annotator.apache.org

note: what the best resource to use to add image annotation to annotator?
iiif has some things we can reuse or do we just use code from annotorious

Look forward to pointers on this - sooner the better - so we can get
prepared for the hackday.

Looking forward,
-dinesh and team



On Wed, May 3, 2017 at 10:47 PM, Andrew Hedges  wrote:
> Hey Dinesh,
>
> Of course I welcome your participation however you think it makes sense.
> We'll of course be on our public Slack channel throughout the day and could
> use a Hangout to videoconference you and others in for the intros and EOD
> presentations. Let me know how you'd like to take part.
>
> Andrew Hedges
> Engineering Manager, Hypothesis
> http://hypothes.is
>
> On May 1, 2017, at 10:35 PM, TB Dinesh  wrote:
>
> Hi Andrew..
>
> We can remotely hack up from Bangalore and other places.
>
> Keep us posted
>
> On 2 May 2017 10:56, "Andrew Hedges"  wrote:
>>
>> Hi everyone! I'm writing to set the stage for the I Annotate Hack Day
>> coming up this Saturday @ Fort Mason Center, Landmark Building C, Room
>> C-230.
>>
>> We have nearly 40 people signed up to participate. The day will be pretty
>> informal, but will flow roughly as follows:
>>
>> 8:30–9:00am — Coffee, tea, & light breakfast
>> 9:00am — Kickoff & intros, share what project you're working on or let
>> others know you're available to help with theirs
>> 9:30am–Noon — Hack alongside Hypothesis engineers and other I Annotate
>> attendees
>> Noon–1:00pm — Lunch
>> 1:00–4:30pm — Hack day, continued
>> 4:30pm — Presentations and demos by participants
>> 5:30–8:00pm — Hack Day BBQ @ 3 Fort Mason
>>
>> The Hack Day is not Hypothesis-specific, but Hypothesis engineers will be
>> available to work alongside anyone leveraging our stack or API.
>>
>> We're super excited by the level of interest in the Hack Day and can't
>> wait to see what you're working on!
>>
>> See you Saturday,
>> Andrew & the Hypothesis Engineering Team
>>
>> -
>> Andrew Hedges
>> Engineering Manager, Hypothesis
>> http://hypothes.is
>>
>

Re: Planning

[TB Dinesh]

Thanks Benjamin. Will pick up on this this coming week.

On Sat, Feb 4, 2017 at 12:01 AM, Randall Leeds 
wrote:

> Thanks Benjamin. I'm not going to get a chance to really look at this until
> Monday, but wanted to acknowledge. Cheers.
>
> On Thu, Feb 2, 2017, 07:20 Benjamin Young  wrote:
>
> > So. I wrote a thing:
> >
> > 
> > https://cwiki.apache.org/confluence/display/ANNO/Planning
> >
> >
> > It's what's been in my head for awhile. This just puts it on "paper." :)
> >
> >
> > Please send your feedback in here for edit the Wiki (let me know if you
> > need credentials!).
> >
> >
> > Also, if you're name is on this "initial committers" list, please write
> me
> > here so I can a) know you're still interested/available and b) get you
> > setup with all the things.
> >
> >
> > https://cwiki.apache.org/confluence/display/ANNO/Annotator+Proposal#
> AnnotatorProposal-InitialCommiters
> >
> >
> > Cheers!
> >
> > Benjamin
> >
> > --
> >
> > http://bigbluehat.com/
> >
> > http://linkedin.com/in/benjaminyoung
> >
>