[GitHub] tilgovi commented on issue #24: LICENSE and NOTICE in packages

2018-03-28 Thread GitBox
tilgovi commented on issue #24: LICENSE and NOTICE in packages URL: https://github.com/apache/incubator-annotator/issues/24#issuecomment-376985238 My read is that we should have a NOTICE file even if it contains nothing but our header. Per the ASL, the content of that NOTICE file would

[GitHub] tilgovi commented on issue #28: Failing during `yarn start`

2018-03-28 Thread GitBox
tilgovi commented on issue #28: Failing during `yarn start` URL: https://github.com/apache/incubator-annotator/issues/28#issuecomment-376990184 I just noticed this, too. I've got some WIP to address it. I'll assign myself. For the moment, you can always run build and then test and

[GitHub] tilgovi commented on issue #28: Failing during `yarn start`

2018-03-28 Thread GitBox
tilgovi commented on issue #28: Failing during `yarn start` URL: https://github.com/apache/incubator-annotator/issues/28#issuecomment-376990241 Although, that won't work in the webpack tests, I think. This is an automated

[GitHub] BigBlueHat opened a new issue #28: Failing during `yarn start`

2018-03-28 Thread GitBox
BigBlueHat opened a new issue #28: Failing during `yarn start` URL: https://github.com/apache/incubator-annotator/issues/28 The tests reference a `../lib` directory which is absent (perhaps auto-generated at runtime or something?) and it causes the following errors: ``` ERROR in

[GitHub] BigBlueHat commented on issue #24: LICENSE and NOTICE in packages

2018-03-28 Thread GitBox
BigBlueHat commented on issue #24: LICENSE and NOTICE in packages URL: https://github.com/apache/incubator-annotator/issues/24#issuecomment-376959263 @tilgovi @apache/annotator-committers I've added LICENSE to all packages and NOTICE to just (for now) `packages/fragment-identifier` based

[GitHub] BigBlueHat closed issue #24: LICENSE and NOTICE in packages

2018-03-28 Thread GitBox
BigBlueHat closed issue #24: LICENSE and NOTICE in packages URL: https://github.com/apache/incubator-annotator/issues/24 This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: Initial Committers Roll Call

2018-03-28 Thread Benjamin Young
Thanks to everyone who +1'd this last month! I've just (officially) added two of our "initial committers" to our list: - Robert - https://people.apache.org/phonebook.html?uid=robcast - Dinesh - https://people.apache.org/phonebook.html?uid=tbdinesh That gives us 5 (counting Jim who's also a

[GitHub] BigBlueHat closed issue #26: Documentation link error

2018-03-28 Thread GitBox
BigBlueHat closed issue #26: Documentation link error URL: https://github.com/apache/incubator-annotator/issues/26 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and

Re: Initial Committers Roll Call

2018-03-28 Thread Benjamin Young
Fabulous, Steve! Thank you. :) We've started working on getting our initial committers up (above 2...now at 4!) so that we can hold proper votes for the project. We've got an active contributor who we'd like to vote in, and haven't been able to yet--my guess is it'd be the same for getting

Re: Initial Committers Roll Call

2018-03-28 Thread Steve Blackmon
I don’t do javascript but I’ll participate on the Annotator PPMC to help the project through incubation. sblack...@apache.org AID: sblackmon On Mar 28, 2018 at 9:14 AM, Benjamin Young wrote: Thanks to everyone who +1'd this last month! I've just (officially) added two

[GitHub] BigBlueHat commented on issue #26: Documentation link error

2018-03-28 Thread GitBox
BigBlueHat commented on issue #26: Documentation link error URL: https://github.com/apache/incubator-annotator/issues/26#issuecomment-376955642 @djKooks I updated the README to clarify that the "development documentation" is a `localhost` only resource atm. Hopefully that makes things

Podling Report Reminder - April 2018

2018-03-28 Thread johndament
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 18 April 2018, 10:30 am PDT. The report for your podling will form