Re: initial scope & API

2017-08-23 Thread Benjamin Young
Sorry for the top post kids...Outlook. >_<


Randall, great work on this new build system! I'll have some follow-up 
issues/questions soon!


Gerben, I'm super glad you're still here! :D My July (like Randall's) was full 
of unexpected things--travel, a death in the family, and more... Consequently, 
that meant I fell behind on my duties here. Apologies.

I do think we're getting close to being ready for a bi-weekly check-in style 
approach.

Also, anyone (and everyone) should feel free to contribute 
ideas/thoughts/hopes/concerns here and on the repos: 
http://annotator.apache.org/

More emails to follow. :)
Benjamin


--

http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung


From: Randall Leeds 
Sent: Saturday, August 12, 2017 9:05:26 PM
To: dev@annotator.incubator.apache.org
Subject: Re: initial scope & API

On Fri, Aug 11, 2017 at 5:12 AM Gerben  wrote:

>
> Two weeks passed without response, I guess my suggestion for biweekly
> progress is rather hopeless. Perhaps a more likely productive approach
> could be to try meet up again somewhere sometime, and spend a day or two
> on creating a basic outline and setup?
>

My apologies, Gerben. I had a really busy July and then I was a bit sick
for a week.

I've just pushed a PR to refresh the build system and hopefully unblock us
all starting to contribute more. The tooling should be more familiar to
others now, using webpack. A demo page is set up in the repo just to sketch
how we might start writing.

I'll look over the overview in the wiki. Thanks for starting that!

We can continue to discuss API, but concrete next steps for me are going to
probably be to import existing repos (dom-anchor-*) and get the test
infrastructure and CI ported over for those.

If there's anything I can do to unblock others, please feel free to poke me
repeatedly here or on IRC.

R


Re: initial scope & API

2017-08-12 Thread Randall Leeds
On Fri, Aug 11, 2017 at 5:12 AM Gerben  wrote:

>
> Two weeks passed without response, I guess my suggestion for biweekly
> progress is rather hopeless. Perhaps a more likely productive approach
> could be to try meet up again somewhere sometime, and spend a day or two
> on creating a basic outline and setup?
>

My apologies, Gerben. I had a really busy July and then I was a bit sick
for a week.

I've just pushed a PR to refresh the build system and hopefully unblock us
all starting to contribute more. The tooling should be more familiar to
others now, using webpack. A demo page is set up in the repo just to sketch
how we might start writing.

I'll look over the overview in the wiki. Thanks for starting that!

We can continue to discuss API, but concrete next steps for me are going to
probably be to import existing repos (dom-anchor-*) and get the test
infrastructure and CI ported over for those.

If there's anything I can do to unblock others, please feel free to poke me
repeatedly here or on IRC.

R


Re: initial scope & API

2017-08-11 Thread Gerben
On 2017-07-26 17:56, Gerben wrote:
> On 2017-07-11 02:29, Gerben wrote:
>> Sure, on the wiki could work. Just to get the ball rolling, I drafted a
>> possible outline with some questions:
>> https://github.com/apache/incubator-annotator/wiki/Overview-(WIP)
>>
>>
>> On 2017-07-09 02:22, Benjamin Young wrote:
>>> Agreed. Let's begin working on some API design while Randall finishes 
>>> sorting out the build kit and importing his libraries.
>>>
>>> We can do that on the wiki, if that works:
>>> https://github.com/apache/incubator-annotator/wiki
>>>
>>> Cool? :)
>>>
> Any thoughts from your side on scope and API? (quite related, issue 7
> : "Make the
> purpose of this tool clear(er)") Would be nice to hear from at least
> both of you (Benjamin, Randall) what you are roughly thinking of making
> here.
>
> My (possibly wrong) impression is that everybody waits for others to
> start doing something. Would it help to give ourselves some homework and
> try schedule a first few milestones and progress calls? E.g. settle on
> an initial scope & API outline in the next two weeks, then call to both
> round that up and decide what we try implement in the two subsequent weeks?
>
> Gerben
>
> (also, perhaps better to switch to bottom-posting, if we grow a longer
> thread)

Two weeks passed without response, I guess my suggestion for biweekly
progress is rather hopeless. Perhaps a more likely productive approach
could be to try meet up again somewhere sometime, and spend a day or two
on creating a basic outline and setup?



Re: initial scope & API (was: Precise-links browser extension)

2017-07-26 Thread Gerben
On 2017-07-11 02:29, Gerben wrote:
> Sure, on the wiki could work. Just to get the ball rolling, I drafted a
> possible outline with some questions:
> https://github.com/apache/incubator-annotator/wiki/Overview-(WIP)
>
>
> On 2017-07-09 02:22, Benjamin Young wrote:
>> Agreed. Let's begin working on some API design while Randall finishes 
>> sorting out the build kit and importing his libraries.
>>
>> We can do that on the wiki, if that works:
>> https://github.com/apache/incubator-annotator/wiki
>>
>> Cool? :)
>>

Any thoughts from your side on scope and API? (quite related, issue 7
: "Make the
purpose of this tool clear(er)") Would be nice to hear from at least
both of you (Benjamin, Randall) what you are roughly thinking of making
here.

My (possibly wrong) impression is that everybody waits for others to
start doing something. Would it help to give ourselves some homework and
try schedule a first few milestones and progress calls? E.g. settle on
an initial scope & API outline in the next two weeks, then call to both
round that up and decide what we try implement in the two subsequent weeks?

Gerben

(also, perhaps better to switch to bottom-posting, if we grow a longer
thread)