Re: [VOTE] Accept CarbonData into the Apache Incubator

[Sandeep Deshmukh]

+1 (non-binding)

Regards,
Sandeep

On Mon, May 30, 2016 at 7:04 PM, lidong  wrote:

> +1 (non-binding)
>
>
> Thanks,
> Dong
> ---
> Apache Kylin - http://kylin.apache.org
> Kyligence Inc. - http://kyligence.io
>
>
> Original Message
> Sender:Jean-Baptiste Onofréj...@nanthrax.net
> Recipient:generalgene...@incubator.apache.org
> Date:Monday, May 30, 2016 14:07
> Subject:Re: [VOTE] Accept CarbonData into the Apache Incubator
>
>
> My own +1 (binding) ;) Regards JB On 05/25/2016 10:24 PM, Jean-Baptiste
> Onofré wrote:  Hi all,   following the discussion thread, I'm now calling a
> vote to accept  CarbonData into the Incubator.   ​[ ] +1 Accept CarbonData
> into the Apache Incubator  [ ] +0 Abstain  [ ] -1 Do not accept CarbonData
> into the Apache Incubator, because ...   This vote is open for 72 hours.
>  The proposal follows, you can also access the wiki page:
> https://wiki.apache.org/incubator/CarbonDataProposal   Thanks !  Regards
> JB   = Apache CarbonData =   == Abstract ==   Apache CarbonData is a new
> Apache Hadoop native file format for faster  interactive  query using
> advanced columnar storage, index, compression and encoding  techniques  to
> improve computing efficiency, in turn it will help speedup queries an
> order of  magnitude faster over PetaBytes of data.   CarbonData github
> address: https://github.com/HuaweiBigData/carbondata   == Background ==
>  Huawei is an ICT solution provider, we are committed to enhancing
> customer experiences for telecom carriers, enterprises, and consumers on
> big data, In order to satisfy the following customer requirements, we
> created a new Hadoop native file format:   * Support interactive OLAP-style
> query over big data in seconds.  * Support fast query on individual record
> which require touching all  fields.  * Fast data loading speed and support
> incremental load in period of  minutes.  * Support HDFS so that customer
> can leverage existing Hadoop cluster.  * Support time based data
> retention.   Based on these requirements, we investigated existing file
> formats in  the Hadoop eco-system, but we could not find a suitable
> solution that  satisfying requirements all at the same time, so we start
> designing  CarbonData.   == Rationale ==   CarbonData contains multiple
> modules, which are classified into two  categories:   1. CarbonData File
> Format: which contains core implementation for file  format such as
> columnar,index,dictionary,encoding+compression,API for  reading/writing
> etc.  2. CarbonData integration with big data processing framework such as
> Apache Spark, Apache Hive etc. Apache Beam is also planned to abstract  the
> execution runtime.   === CarbonData File Format ===   CarbonData file
> format is a columnar store in HDFS, it has many features  that a modern
> columnar format has, such as splittable, compression  schema ,complex data
> type etc. And CarbonData has following unique  features:    Indexing
>    In order to support fast interactive query, CarbonData leverage
> indexing  technology to reduce I/O scans. CarbonData files stores data
> along with  index, the index is not stored separately but the CarbonData
> file itself  contains the index. In current implementation, CarbonData
> supports 3  types of indexing:   1. Multi-dimensional Key (B+ Tree index)
> The Data block are written in sequence to the disk and within each  data
> blocks each column block is written in sequence. Finally, the  metadata
> block for the file is written with information about byte  positions of
> each block in the file, Min-Max statistics index and the  start and end MDK
> of each data block. Since, the entire data in the file  is in sorted order,
> the start and end MDK of each data block can be used  to construct a B+Tree
> and the file can be logically represented as a  B+Tree with the data blocks
> as leaf nodes (on disk) and the remaining  non-leaf nodes in memory.  2.
> Inverted index  Inverted index is widely used in search engine. By using
> this index,  it helps processing/query engine to do filtering inside one
> HDFS block.  Furthermore, query acceleration for count distinct like
> operation is  made possible when combining bitmap and inverted index in
> query time.  3. MinMax index  For all columns, minmax index is created so
> that processing/query  engine can skip scan that is not required.   
> Global Dictionary    Besides I/O reduction, CarbonData accelerates
> computation by using  global dictionary, which enables processing/query
> engines to perform all  processing on encoded data without having to
> convert the data (Late  Materialization). We have observed dramatic
> performance improvement for  OLAP analytic scenario where table contains
> many columns in string data  type. The data is converted back to the user
> readable form just before  processing/query engine returning results to
> user.    Column Group    Sometimes users want to perform
> processing/query on 

Re: [VOTE] Apache SystemML 0.10.0-incubating (RC1)

[Luciano Resende]

Thanks,

Please consider this vote canceled and I will work on another RC with
proper fix for the binary files in the source distro.

On Tue, May 31, 2016 at 7:13 PM, John D. Ament 
wrote:

> On Tue, May 31, 2016 at 9:54 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > We will update trunk to remove the specified files. Will we need to
> begin
> > > voting again for another release candidate with these changes, or would
> > it
> > > suffice that the next release will have this fix?
> >
> > Depends on how other IPMC members vote, if you get 3 +1 votes and more
> > +1’s than -1’s then it’s a release.
> >
>
> Agreed, my vote would be -1 on including binaries in the source release.
>
> However, one thing to point out, we're not asking you to remove binaries
> files from your source repository, just not include them in the source
> release.  For any file you're excluding, you should explain how to create
> it, e.g. the hadoop.dll is created by compiling hadoop or by downloading
> their binary (and explain how to configure the build to point to those
> binaries, if needed to compile/test)
>
>
> >
> > IMO having executable binary files in a source release means you
> shouldn’t
> > release it. See the 4th paragraph here. [1]
> >
> > Thanks,
> > Justin
> >
> > 1. http://www.apache.org/dev/release.html#what
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Release Apache Trafodion 2.0.0 (incubating)

[Justin Mclean]

Hi,

+1 (binding) to release source package, but -1 for the client connivence binary 
until the 4 clause BSD licensing issue is resolved.

For the source released I checked:
- all files have incubating
- signatures check out
- disclaimer exists
- LICENSE and NOTICE good
- No unexpected binary in source
- All ASF licensed file have ASF headers

The source LICENSE has a minor issue. It mentions the 4 clause BSD license 
which is not compatible with the Apache license (only the 2 and 3 clause BSD 
licenses are) [1][2]. In this case the extra clause has been recinded [3] you 
might want to reword/state that in the license.

But that does mean there is an issue with the client binary release as that 
includes OpenSSL which lists a 6 clause BSD style license (similar to a 4 
clause BSD license) and SSLeay under a 4 clause BSD license. You may need to 
clarify this on legal discuss. It may be that their intent to move to an Apache 
licence may mean you can hold off on doing anything but I’m not 100% sure. 
[4][5]

I would also remove the GPL license text from the server’s LICENSE file to make 
it clear which license it’s included under. If something is dual licensed you 
select which licence you want to use. 

Thanks,
Justin

1. http://www.apache.org/legal/resolved.html#category-a
2. https://issues.apache.org/jira/browse/LEGAL-185
3. https://opensource.org/licenses/BSD-3-Clause
4. https://www.openssl.org/blog/blog/2015/08/01/cla/
5. https://wiki.openssl.org/index.php/License



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache SystemML 0.10.0-incubating (RC1)

[John D. Ament]

On Tue, May 31, 2016 at 9:54 PM Justin Mclean 
wrote:

> Hi,
>
> > We will update trunk to remove the specified files. Will we need to begin
> > voting again for another release candidate with these changes, or would
> it
> > suffice that the next release will have this fix?
>
> Depends on how other IPMC members vote, if you get 3 +1 votes and more
> +1’s than -1’s then it’s a release.
>

Agreed, my vote would be -1 on including binaries in the source release.

However, one thing to point out, we're not asking you to remove binaries
files from your source repository, just not include them in the source
release.  For any file you're excluding, you should explain how to create
it, e.g. the hadoop.dll is created by compiling hadoop or by downloading
their binary (and explain how to configure the build to point to those
binaries, if needed to compile/test)


>
> IMO having executable binary files in a source release means you shouldn’t
> release it. See the 4th paragraph here. [1]
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/dev/release.html#what
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache SystemML 0.10.0-incubating (RC1)

[Justin Mclean]

Hi,

> We will update trunk to remove the specified files. Will we need to begin
> voting again for another release candidate with these changes, or would it
> suffice that the next release will have this fix?

Depends on how other IPMC members vote, if you get 3 +1 votes and more +1’s 
than -1’s then it’s a release.

IMO having executable binary files in a source release means you shouldn’t 
release it. See the 4th paragraph here. [1]

Thanks,
Justin

1. http://www.apache.org/dev/release.html#what
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache SystemML 0.10.0-incubating (RC1)

[Deron Eriksson]

Hi Justin,

Thank you for reviewing the SystemML release candidate. I agree about the
large number of artifacts at [1]. It would also help us in terms of project
maintenance to decrease the number of artifacts that we are generating.

We will update trunk to remove the specified files. Will we need to begin
voting again for another release candidate with these changes, or would it
suffice that the next release will have this fix?

Thank you,
Deron



On Tue, May 31, 2016 at 6:18 PM, Justin Mclean 
wrote:

> Hi,
>
> Sorry -1 (binding) due to unexpected binaries in the source release.
>
> For the source artefact I checked:
> - signatures and hashes good
> - file name contain incubating
> - DISCLAIMER exists
> - LICENSE and NOTICE correct
> - There are unexpended binary in the source release (see below)
> - All files have apache headers
> - Can compile from source
>
> There’s a number of binary files included in the source release:
> ls ./src/test/config/hadoop_bin_windows/bin
> hadoop.dll  hadoop.lib  libwinutils.lib winutils.pdb
> hadoop.exp  hadoop.pdb  winutils.exe
>
> There a large number of files at [1] so it’s not entirely clear what the
> release artefacts are to vote on you might want to just include the .zip /
> .tar.gz files next time.
>
> I also looked at the binary release, nice to see entirely different
> LICENSE there based on the contents of the file. Minor issue there’s no
> need to list the copyright for abego software or ANTLR software in the
> NOTICE file as both are BSD licensed. [2] Please fix this for the next
> release.
>
> Thanks,
> Justin
>
>
> 1.
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.10.0-incubating-rc1/
> 2. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache SystemML 0.10.0-incubating (RC1)

[Justin Mclean]

Hi,

Sorry -1 (binding) due to unexpected binaries in the source release.

For the source artefact I checked:
- signatures and hashes good
- file name contain incubating
- DISCLAIMER exists
- LICENSE and NOTICE correct
- There are unexpended binary in the source release (see below)
- All files have apache headers
- Can compile from source

There’s a number of binary files included in the source release:
ls ./src/test/config/hadoop_bin_windows/bin
hadoop.dll  hadoop.lib  libwinutils.lib winutils.pdb
hadoop.exp  hadoop.pdb  winutils.exe

There a large number of files at [1] so it’s not entirely clear what the 
release artefacts are to vote on you might want to just include the .zip / 
.tar.gz files next time.

I also looked at the binary release, nice to see entirely different LICENSE 
there based on the contents of the file. Minor issue there’s no need to list 
the copyright for abego software or ANTLR software in the NOTICE file as both 
are BSD licensed. [2] Please fix this for the next release.

Thanks,
Justin


1. 
https://dist.apache.org/repos/dist/dev/incubator/systemml/0.10.0-incubating-rc1/
2. http://www.apache.org/dev/licensing-howto.html#permissive-deps
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache SystemML 0.10.0-incubating (RC1)

[Luciano Resende]

Just want to reiterate my +1,

And also mention that we got one of our mentors to vote on the dev list
thread
https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg00617.html

Anyone else willing to help us get this release out.

Thanks

On Thu, May 26, 2016 at 2:55 PM, Luciano Resende 
wrote:

>
> Please vote to approve the release of the following candidate as Apache
> SystemML version 0.10.0!
>
> The PPMC vote thread:
>
> https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg00532.html
>
> And the result:
>
> https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg00599.html
>
> The tag to be voted on is v0.10.0-rc1
> (ddf0e0941afe5d9c2cc7c574a6983aadd98c1fc3)
>
>
> https://github.com/apache/incubator-systemml/tree/ddf0e0941afe5d9c2cc7c574a6983aadd98c1fc3
>
> The release files, including signatures, digests, etc. can be found at:
>
> https://repository.apache.org/content/repositories/orgapachesystemml-1005
>
> The distribution and rat report is also available at:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.10.0-incubating-rc1/
>
> The vote is open for at least 72 hours and passes if a majority of at
> least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache SystemML 0.10.0
> [ ] -1 Do not release this package because ...
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Could you please add my id (hzeller) as a contributor

[Nick Burch]

On Tue, 31 May 2016, Hans Zeller wrote:
Could you please add my wiki id, hzeller to the Contributors group, so I 
can add the report?


Karma granted, enjoy!

Nick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Could you please add my id (hzeller) as a contributor

[Hans Zeller]

Hi,

We are preparing the Trafodion report to the Incubator PMC and would like
to add it to the wiki page https://wiki.apache.org/incubator/June2016.

Could you please add my wiki id, hzeller to the Contributors group, so I
can add the report?

Thanks,

Hans Zeller

Re: Request to add me to Incubator Wiki (KeithTurner)

[John D. Ament]

Done, happy editing!

On Tue, May 31, 2016 at 5:52 PM Keith Turner  wrote:

> Wiki user name: KeithTurner
>

[RESULT] [VOTE] Release Apache Ranger 0.5.3 (incubating) - rc3

[Velmurugan Periasamy]

Incubator PMC,  

The vote has passed with 3 “+1” votes from IPMC members (who provided their 
votes in Dev VOTE thread) and no “0” or “-1” votes.

+1 (binding): 
- Alan Gates 
- Jakob Homan
- Colm O hEigeartaigh

+0:
None

-1:
None

I will proceed with official release. Thank you so much for your time, guidance 
and help in releasing Apache Ranger 0.5.3 (incubating).

Thank you,
Vel

VOTE thread reference -
http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201605.mbox/%3C62DE2F5B-31FC-47F7-834A-460304E33EFD%40apache.org%3E
 

On May 24, 2016, at 1:13 PM, Velmurugan Periasamy  wrote:

> Incubator PMC:
> 
> Apache Ranger community has voted on and approved a proposal to release 
> Apache Ranger 0.5.3 (incubating). 
> 
> [VOTE RESULT] thread:
>https://lists.apache.org/thread.html/Ztlreja8-xl1xr8
> 
> Apache ranger-0.5.3-rc3 release candidate (addressing few issues raised in 
> previous IPMC reviews) is now available with the following artifacts up for 
> IPMC vote. I kindly request that the Incubator PMC members review and vote on 
> this incubator release.
> 
> Git tag for the release:
>https://github.com/apache/incubator-ranger/tree/ranger-0.5.3-rc3
> 
> Source release:
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating-rc3/apache-ranger-incubating-0.5.3.tar.gz
> 
> Source release verification:
>PGP Signature:  
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating-rc3/apache-ranger-incubating-0.5.3.tar.gz.asc
>MD5/SHA  Hash:  
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.3-incubating-rc3/apache-ranger-incubating-0.5.3.tar.gz.mds
>Keys to verify the signature of the release artifact are available at:
>https://dist.apache.org/repos/dist/release/incubator/ranger/KEYS
> 
> Release Notes:
>https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62694969  
> 
> Build verification steps can be found at:
>http://ranger.incubator.apache.org/quick_start_guide.html
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Here is my +1 (non binding)
> 
> Thanks,
> Vel

Request to add me to Incubator Wiki (KeithTurner)

[Keith Turner]

Wiki user name: KeithTurner

RE: [PROPOSAL] Apache Annotator

[Benjamin Young]

Yeah. A bit of both, actually. ;)

JSON-LD is the new bridge builder / peace-maker in this space.

There's an RDF-based data model "underneath" but the expression of it can be 
treated as "plain JSON" for those who don't do RDF.

For instance, I have the beginnings of the Web Annotation Protocol built on 
Apache CouchDB:
https://github.com/BigBlueHat/ldp-on-couchdb

The Web Annotation Protocol is based on LDP BasicContainers--which really just 
(re)defined GET, POST, PUT, and DELETE + Link headers for finding your way 
around:
https://www.w3.org/TR/annotation-protocol/

Anyhow, it's getting uptake from folks who have little to no interest in RDF or 
graphs as well as folks who depend heavily on RDF and graphs--which is about 
the best scenario we can hope for these days. :)

Thanks for the thoughts, Nick!
Benjamin

-Original Message-
From: Nick Kew [mailto:n...@apache.org] 
Sent: Tuesday, May 31, 2016 4:36 PM
To: general@incubator.apache.org
Subject: Re: [PROPOSAL] Apache Annotator

On Tue, 2016-05-31 at 18:13 +, Benjamin Young wrote:
> Yeah. Lots has happened in the intervening 14 years. :)

:) 

Thanks for the reply.  I kind-of thought it might've done, but (having followed 
your first link and found only javascript that had nothing to say on the 
subject) I was looking for ...
well, I guess your reply and the links in it.

Lots more reading to do, but I see it's moved from RDF and pie-in-the-sky to 
JSON and some more realistic expectations.

--
Nick Kew


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Apache Annotator

[Nick Kew]

On Tue, 2016-05-31 at 18:13 +, Benjamin Young wrote:
> Yeah. Lots has happened in the intervening 14 years. :)

:) 

Thanks for the reply.  I kind-of thought it might've done,
but (having followed your first link and found only javascript
that had nothing to say on the subject) I was looking for ...
well, I guess your reply and the links in it.

Lots more reading to do, but I see it's moved from RDF and
pie-in-the-sky to JSON and some more realistic expectations.

-- 
Nick Kew


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [PROPOSAL] Apache Annotator

[Benjamin Young]

Yeah. Lots has happened in the intervening 14 years. :)

The new thing is called the Web Annotation Data Model [1] and it's born out of 
work by the Web Annotation Working Group [2] which in turn built on the work 
created in the Open Annotation Community Group [3].

Annotea was used merely as a historical point--not the technical foundation of 
anything (afaik). You're welcome to dig through the Open Annotation CG mail 
archives for what their view of that was, but it doesn't directly effect this 
potential Apache project, nor its code--which will be focused in part on Web 
Annotation Data Model support and tooling...which I hope you'll find is more 
sane with 14 more years of "school of hard knocks" education at its back. :)

Cheers!
Benjamin

[1] http://www.w3.org/TR/annotation-model/
[2] https://www.w3.org/community/openannotation/
[3] https://lists.w3.org/Archives/Public/public-openannotation/

-Original Message-
From: Nick Kew [mailto:n...@apache.org] 
Sent: Tuesday, May 31, 2016 12:04 PM
To: general@incubator.apache.org
Subject: Re: [PROPOSAL] Apache Annotator

On Tue, 2016-05-31 at 13:46 +, Benjamin Young wrote:
> Hi all,
> 
> I have been working with the AnnotatorJS.org community to move our community 
> to the ASF. We have in the past been a BDFL-led group, but that has proved 
> unsustainable and resulted in many forks and lost opportunity.

I see there's a link to W3C annotations.  Is that the basis for it?
How far has that come since it was a textbook example of how not to use RDF 
(e.g.
https://lists.w3.org/Archives/Public/www-tag/2002Jul/0232.html ).

I guess the real question is, is the system still based on confusing URIs used 
as invariants in RDF with URLs you dereference on the Web, as W3 annotea was?

--
Nick Kew


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Podling name search - early or late?

[Liang Chen]

+1 for confirming the name early for podling project

Liang



--
View this message in context: 
http://apache-incubator-general.996316.n3.nabble.com/Podling-name-search-early-or-late-tp49856p49901.html
Sent from the Apache Incubator - General mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Request to add me to Incubator Wiki (HemanthYamijala)

[John D. Ament]

Added, happy editing!

On Tue, May 31, 2016 at 1:13 PM Hemanth Yamijala  wrote:

> Wiki user name: HemanthYamijala
>

Request to add me to Incubator Wiki (HemanthYamijala)

[Hemanth Yamijala]

Wiki user name: HemanthYamijala

[VOTE] Release Apache Trafodion 2.0.0 (incubating)

[Steve Varnau]

Hello,

This is a call to vote on releasing Apache Trafodion 2.0.0-incubating
(Release Candidate 3).

The trafodion community has approved RC3 for release.
Vote result:
http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/201605.mb
ox/%3Cebe8936d36c9cedc2fbf65a94e6c5cbf%40mail.gmail.com%3E
Or in Pony Mail: https://lists.apache.org/thread.html/Zl1sh41t2mahwox

Voting thread:
http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/201605.mb
ox/%3C85e78601a290f595707ee81d033c6b4c%40mail.gmail.com%3E

Release artifacts:
https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.0.0
-RC3
Artifacts are signed with my key (7F14AF20), which is in
https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS
This is the first release we are including convenience binaries built from
the source code artifact.

The tag for this candidate is "2.0.0rc3". Git repository:
git://git.apache.org/incubator-trafodion.git
https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=tag;h=
1a8942c91e58212968d94478db18005568f4

The JIRA release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318620;
version=12333044

Instructions for
Setting up build environment:
https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environ
ment
Building:
https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Please vote by Friday, June 3, Noon Pacific Time (7pm UTC).

Thank you,
--Steve

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Requesting edit privileges for the Incubator Wiki

[Nick Burch]

On Tue, 31 May 2016, Queenie Ma wrote:

I would like to be granted edit privileges for the Incubator Wiki so that I
can update the Incubator PMC report for June 2016 for the Quarks project.

Name: Queenie Ma


Karma granted, enjoy!

Nick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Apache Annotator

[Nick Kew]

On Tue, 2016-05-31 at 13:46 +, Benjamin Young wrote:
> Hi all,
> 
> I have been working with the AnnotatorJS.org community to move our community 
> to the ASF. We have in the past been a BDFL-led group, but that has proved 
> unsustainable and resulted in many forks and lost opportunity.

I see there's a link to W3C annotations.  Is that the basis for it?
How far has that come since it was a textbook example of how not
to use RDF (e.g.
https://lists.w3.org/Archives/Public/www-tag/2002Jul/0232.html ).

I guess the real question is, is the system still based on
confusing URIs used as invariants in RDF with URLs you
dereference on the Web, as W3 annotea was?

-- 
Nick Kew


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Requesting edit privileges for the Incubator Wiki

[Queenie Ma]

Hello,

I would like to be granted edit privileges for the Incubator Wiki so that I
can update the Incubator PMC report for June 2016 for the Quarks project.

Name: Queenie Ma
Email: queeni...@apache.org


Thank you,
Queenie Ma

RE: [PROPOSAL] Apache Annotator

[Benjamin Young]

Thanks, John!

Posted:
https://wiki.apache.org/incubator/AnnotatorProposal

-Original Message-
From: John D. Ament [mailto:johndam...@apache.org] 
Sent: Tuesday, May 31, 2016 9:50 AM
To: general@incubator.apache.org; Benjamin Young 
Subject: Re: [PROPOSAL] Apache Annotator

Hi Benjamin,

I've added bigbluehat to the contributors group, feel free to post your 
proposal there.

John

On Tue, May 31, 2016 at 9:46 AM Benjamin Young 
wrote:

> Hi all,
>
> I have been working with the AnnotatorJS.org community to move our 
> community to the ASF. We have in the past been a BDFL-led group, but 
> that has proved unsustainable and resulted in many forks and lost opportunity.
>
> Recently, many community members gathered at the http://iannotate.org/ 
> conference and subsequent hackathon and discussed the future of the 
> project. We again concluded that the ASF held the most promise for a 
> governance style that could support our growing community and assure 
> that collaboration continue into the future.
>
> Our Incubator Proposal is current here (also below in markdown):
> https://github.com/openannotation/annotator/wiki/Apache-Incubation-Pro
> posal
>
> I would be happy to move the proposal to the incubator wiki-my user 
> name there is `bigbluehat`.
>
> Our current mailing list has a running vote/discussion around this 
> proposal and our move to the ASF:
> https://lists.okfn.org/pipermail/annotator-dev/2016-May/001615.html
>
> Lastly, we have a Champion (Daniel Gruno), but are still in need of 
> Mentors.
>
> Thank you for considering this proposal!
> Benjamin - bigblue...@apache.org
>
>
>
> Apache Annotator Proposal:
>  Abstract
> > A short descriptive summary of the project. A short paragraph, 
> > ideally
> one sentence in length.
>
> Annotation enabling code for browsers, servers, and humans.
>
>  Proposal
> > A lengthier description of the proposal.
>
> The Annotator community seeks to build a foundational set of libraries 
> under a liberal license providing the pieces necessary for developers 
> to add annotation to their projects.
>
>  Background
> > Provides context for those unfamiliar with the problem space and history.
>
> Annotator.js was originally created by Open Knowledge (formerly The 
> Open Knowledge Foundation) to provide annotation over works by Shakespeare.
> Since that time, Annotator has found its way into a wide range of 
> browser-based annotation systems such as Hypothes.is, 
> LacunaStories.com, and various academic, publishing, and scientific research 
> projects.
>
> Sadly, this increased usage has primarily happened in forks of the 
> main code or through copy-left licensed plugins that prevent their use 
> by many community members.
>
> However, the community remains interested in combined collaboration 
> and interested in a foundational future for annotation--both in 
> browsers as well as servers and desktop/mobile applications.
>
>  Rationale
>
> > Explains why this project needs to exist and why should it be 
> > adopted by
> Apache.
>
> Annotation is often implemented in projects in ad hoc ways with 
> developers often re-solving problems well known to the Annotator 
> community. The Annotator community works to provide knowledge and code 
> to help developers more quickly implement or improve annotation within their 
> projects.
>
> We believe bringing the Annotator community into the Apache Software 
> Foundation will allow for wider recognition of the annotation problem 
> space, help more developers find their way to solving this shared 
> problem, provide increased cohesion for our own somewhat fractured 
> community, and increase the use of commonly shared code within a wide range 
> of projects.
>
>  Initial Goals
>
> * create a collaborative space for the existing Annotator contributors 
> and community
> * further ignite interest and activity around annotation
> * build foundational libraries for annotation
> * implement code to support the Web Annotation Data Model, Protocol, 
> and other annotation related specifications
> * potentially re-license Annotator under the Apache License 2.0
>   * Annotator is currently licensed under a combination of the MIT & 
> GPL
> * consolidate (where possible) community activity around building 
> add-ons, annotation storage providers, and use-case specific feature 
> sets
> * grow interest and activity in annotation
>
>  Current Status
>
> # Meritocracy
> > Apache is a meritocracy.
>
> The project is in transition from a primarily BDFL-based model to one 
> with a more diverse set of committers. There are 36 total known 
> commiters to Annotator. 3 commiters having done the bulk of the coding 
> and decision making. 2 of those commiters acting as project leadership.
>
> However, the community is much larger and more diverse when the 
> various forks and plugin authors are considered.
>
> We intend to invite and include participants from a wide 

Re: [PROPOSAL] Apache Annotator

[John D. Ament]

Hi Benjamin,

I've added bigbluehat to the contributors group, feel free to post your
proposal there.

John

On Tue, May 31, 2016 at 9:46 AM Benjamin Young 
wrote:

> Hi all,
>
> I have been working with the AnnotatorJS.org community to move our
> community to the ASF. We have in the past been a BDFL-led group, but that
> has proved unsustainable and resulted in many forks and lost opportunity.
>
> Recently, many community members gathered at the http://iannotate.org/
> conference and subsequent hackathon and discussed the future of the
> project. We again concluded that the ASF held the most promise for a
> governance style that could support our growing community and assure that
> collaboration continue into the future.
>
> Our Incubator Proposal is current here (also below in markdown):
> https://github.com/openannotation/annotator/wiki/Apache-Incubation-Proposal
>
> I would be happy to move the proposal to the incubator wiki-my user name
> there is `bigbluehat`.
>
> Our current mailing list has a running vote/discussion around this
> proposal and our move to the ASF:
> https://lists.okfn.org/pipermail/annotator-dev/2016-May/001615.html
>
> Lastly, we have a Champion (Daniel Gruno), but are still in need of
> Mentors.
>
> Thank you for considering this proposal!
> Benjamin - bigblue...@apache.org
>
>
>
> Apache Annotator Proposal:
>  Abstract
> > A short descriptive summary of the project. A short paragraph, ideally
> one sentence in length.
>
> Annotation enabling code for browsers, servers, and humans.
>
>  Proposal
> > A lengthier description of the proposal.
>
> The Annotator community seeks to build a foundational set of libraries
> under a liberal license providing the pieces necessary for developers to
> add annotation to their projects.
>
>  Background
> > Provides context for those unfamiliar with the problem space and history.
>
> Annotator.js was originally created by Open Knowledge (formerly The Open
> Knowledge Foundation) to provide annotation over works by Shakespeare.
> Since that time, Annotator has found its way into a wide range of
> browser-based annotation systems such as Hypothes.is, LacunaStories.com,
> and various academic, publishing, and scientific research projects.
>
> Sadly, this increased usage has primarily happened in forks of the main
> code or through copy-left licensed plugins that prevent their use by many
> community members.
>
> However, the community remains interested in combined collaboration and
> interested in a foundational future for annotation--both in browsers as
> well as servers and desktop/mobile applications.
>
>  Rationale
>
> > Explains why this project needs to exist and why should it be adopted by
> Apache.
>
> Annotation is often implemented in projects in ad hoc ways with developers
> often re-solving problems well known to the Annotator community. The
> Annotator community works to provide knowledge and code to help developers
> more quickly implement or improve annotation within their projects.
>
> We believe bringing the Annotator community into the Apache Software
> Foundation will allow for wider recognition of the annotation problem
> space, help more developers find their way to solving this shared problem,
> provide increased cohesion for our own somewhat fractured community, and
> increase the use of commonly shared code within a wide range of projects.
>
>  Initial Goals
>
> * create a collaborative space for the existing Annotator contributors and
> community
> * further ignite interest and activity around annotation
> * build foundational libraries for annotation
> * implement code to support the Web Annotation Data Model, Protocol, and
> other annotation related specifications
> * potentially re-license Annotator under the Apache License 2.0
>   * Annotator is currently licensed under a combination of the MIT & GPL
> * consolidate (where possible) community activity around building add-ons,
> annotation storage providers, and use-case specific feature sets
> * grow interest and activity in annotation
>
>  Current Status
>
> # Meritocracy
> > Apache is a meritocracy.
>
> The project is in transition from a primarily BDFL-based model to one with
> a more diverse set of committers. There are 36 total known commiters to
> Annotator. 3 commiters having done the bulk of the coding and decision
> making. 2 of those commiters acting as project leadership.
>
> However, the community is much larger and more diverse when the various
> forks and plugin authors are considered.
>
> We intend to invite and include participants from a wide array of
> annotation problem spaces to collaborate in this new shared space.
>
> # Community
> >  Apache is interested only in communities.
>
> Community calls had been being done every 3-6 months with reports of the
> calls outcome being posted to the mailing list and the annotatorjs.org
> website.
>
> Most activity within the project happens on the mailing 

[PROPOSAL] Apache Annotator

[Benjamin Young]

Hi all,

I have been working with the AnnotatorJS.org community to move our community to 
the ASF. We have in the past been a BDFL-led group, but that has proved 
unsustainable and resulted in many forks and lost opportunity.

Recently, many community members gathered at the http://iannotate.org/ 
conference and subsequent hackathon and discussed the future of the project. We 
again concluded that the ASF held the most promise for a governance style that 
could support our growing community and assure that collaboration continue into 
the future.

Our Incubator Proposal is current here (also below in markdown):
https://github.com/openannotation/annotator/wiki/Apache-Incubation-Proposal

I would be happy to move the proposal to the incubator wiki-my user name there 
is `bigbluehat`.

Our current mailing list has a running vote/discussion around this proposal and 
our move to the ASF:
https://lists.okfn.org/pipermail/annotator-dev/2016-May/001615.html

Lastly, we have a Champion (Daniel Gruno), but are still in need of Mentors.

Thank you for considering this proposal!
Benjamin - bigblue...@apache.org



Apache Annotator Proposal:
 Abstract
> A short descriptive summary of the project. A short paragraph, ideally one 
> sentence in length.

Annotation enabling code for browsers, servers, and humans.

 Proposal
> A lengthier description of the proposal.

The Annotator community seeks to build a foundational set of libraries under a 
liberal license providing the pieces necessary for developers to add annotation 
to their projects.

 Background
> Provides context for those unfamiliar with the problem space and history.

Annotator.js was originally created by Open Knowledge (formerly The Open 
Knowledge Foundation) to provide annotation over works by Shakespeare. Since 
that time, Annotator has found its way into a wide range of browser-based 
annotation systems such as Hypothes.is, LacunaStories.com, and various 
academic, publishing, and scientific research projects.

Sadly, this increased usage has primarily happened in forks of the main code or 
through copy-left licensed plugins that prevent their use by many community 
members.

However, the community remains interested in combined collaboration and 
interested in a foundational future for annotation--both in browsers as well as 
servers and desktop/mobile applications.

 Rationale

> Explains why this project needs to exist and why should it be adopted by 
> Apache.

Annotation is often implemented in projects in ad hoc ways with developers 
often re-solving problems well known to the Annotator community. The Annotator 
community works to provide knowledge and code to help developers more quickly 
implement or improve annotation within their projects.

We believe bringing the Annotator community into the Apache Software Foundation 
will allow for wider recognition of the annotation problem space, help more 
developers find their way to solving this shared problem, provide increased 
cohesion for our own somewhat fractured community, and increase the use of 
commonly shared code within a wide range of projects.

 Initial Goals

* create a collaborative space for the existing Annotator contributors and 
community
* further ignite interest and activity around annotation
* build foundational libraries for annotation
* implement code to support the Web Annotation Data Model, Protocol, and other 
annotation related specifications
* potentially re-license Annotator under the Apache License 2.0
  * Annotator is currently licensed under a combination of the MIT & GPL
* consolidate (where possible) community activity around building add-ons, 
annotation storage providers, and use-case specific feature sets
* grow interest and activity in annotation

 Current Status

# Meritocracy
> Apache is a meritocracy.

The project is in transition from a primarily BDFL-based model to one with a 
more diverse set of committers. There are 36 total known commiters to 
Annotator. 3 commiters having done the bulk of the coding and decision making. 
2 of those commiters acting as project leadership.

However, the community is much larger and more diverse when the various forks 
and plugin authors are considered.

We intend to invite and include participants from a wide array of annotation 
problem spaces to collaborate in this new shared space.

# Community
>  Apache is interested only in communities.

Community calls had been being done every 3-6 months with reports of the calls 
outcome being posted to the mailing list and the annotatorjs.org website.

Most activity within the project happens on the mailing list. There is also a 
relatively inactive #annotator channel on irc.freenode.net. The website is 
primarily for promotion and includes promotion of community plugins and 
showcases projects using Annotator. Documentation is published on 
readthedocs.org and linked to from the website.

There are many Annotator and W3C Annotation Data Model