+1 excited for the future of annotation! On Tue, Feb 6, 2018 at 11:02 AM, Tushar Choubisa <smiley...@gmail.com> wrote:
> +1 > > On Tue, Feb 6, 2018 at 9:01 PM, Joshua Choi <js_c...@icloud.com> wrote: > > > +1—I’ve been busy with medical school, but I still wish to help out as > > well as I can. > > > > > On Feb 6, 2018, at 9:30 AM, Jim Jagielski <j...@jagunet.com> wrote: > > > > > > +1 > > > > > >> On Feb 2, 2018, at 1:49 PM, Benjamin Young <byo...@bigbluehat.com> > > 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/ <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 <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 < > > https://github.com/apache/incubator-annotator/wiki/Proposal> > > >> [2] http://annotator.apache.org/ <http://annotator.apache.org/> > > >> [3] https://github.com/apache/incubator-annotator < > > https://github.com/apache/incubator-annotator> > > >> [4] https://github.com/apache/incubator-annotator/issues/18 < > > https://github.com/apache/incubator-annotator/issues/18> > > >> > > >> > > >> -- > > >> http://bigbluehat.com/ <http://bigbluehat.com/> > > >> http://linkedin.com/in/benjaminyoung <http://linkedin.com/in/ > > benjaminyoung> > > >
