Re: Please update your podling status page

[John D. Ament]

To give a summary of what we're talking about on hipchat

- do a 'svn info' and check the URL.  It should be "URL: 
https://svn.apache.org/repos/asf/incubator/public/trunk;
- If its not (double check the http vs https) use svn relocate to change to 
this URL

John

On 2016-11-25 16:20 (-0500), "John D. Ament" wrote: 
> Hi Mark,
> 
> I did check, you're in the incubator group so you have write access to the 
> repo.\u2002\u2002What do you get when you try to commit?
> 
> I'm in the hipchat room if you have time and can look at this in more real 
> time.
> 
> John
> 
> On 2016-11-25 14:52 (-0500), Mark Bretl  wrote: 
> > Hi John,
> > 
> > I am working on editing the documents in SVN, however, it seems I do not
> > have permission to check in. Would you be able to help me with that or can
> > you point me in the right direction?
> > 
> > Best Regards,
> > 
> > --Mark
> > 
> > On Fri, Nov 25, 2016 at 9:05 AM, John D. Ament 
> > wrote:
> > 
> > > Dear Geode PMC
> > >
> > > Congratulations on becoming a top level project.  Please complete your
> > > incubator graduation steps.  They can be found here:
> > > http://incubator.apache.org/guides/graduation.html#unincubate
> > >
> > > John
> > >
> > 
> 

Re: Please update your podling status page

[John D. Ament]

Hi Mark,

I did check, you're in the incubator group so you have write access to the 
repo.  What do you get when you try to commit?

I'm in the hipchat room if you have time and can look at this in more real time.

John

On 2016-11-25 14:52 (-0500), Mark Bretl  wrote: 
> Hi John,
> 
> I am working on editing the documents in SVN, however, it seems I do not
> have permission to check in. Would you be able to help me with that or can
> you point me in the right direction?
> 
> Best Regards,
> 
> --Mark
> 
> On Fri, Nov 25, 2016 at 9:05 AM, John D. Ament 
> wrote:
> 
> > Dear Geode PMC
> >
> > Congratulations on becoming a top level project.  Please complete your
> > incubator graduation steps.  They can be found here:
> > http://incubator.apache.org/guides/graduation.html#unincubate
> >
> > John
> >
> 

Re: Please update your podling status page

[Mark Bretl]

Hi John,

I am working on editing the documents in SVN, however, it seems I do not
have permission to check in. Would you be able to help me with that or can
you point me in the right direction?

Best Regards,

--Mark

On Fri, Nov 25, 2016 at 9:05 AM, John D. Ament 
wrote:

> Dear Geode PMC
>
> Congratulations on becoming a top level project.  Please complete your
> incubator graduation steps.  They can be found here:
> http://incubator.apache.org/guides/graduation.html#unincubate
>
> John
>

[GitHub] incubator-geode issue #295: [GEODE-1984] #comment Fix Issue Make GatewaySend...

[metatype]

Github user metatype commented on the issue:

https://github.com/apache/incubator-geode/pull/295
  
@davinash I think you merged `master` into your feature branch.  I suggest 
closing this PR and starting a new one.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-geode issue #291: [GEODE-1122] Fixed Dependency on environment var...

[metatype]

Github user metatype commented on the issue:

https://github.com/apache/incubator-geode/pull/291
  
@davinash I think you merged `master` into your feature branch.  I suggest 
closing this PR and starting a new one.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: JSON License and Apache Projects

[Anthony Baker]

Thanks William!

I filed GEODE-2142 for tracking the legal requirement for remove JSON.

Anthony

> On Nov 24, 2016, at 4:38 PM, William Markito Oliveira 
>  wrote:
> 
> Interesting thread about json parsing libraries and licensing.  
> 
> Sent from my iPhone
> 
> Begin forwarded message:
> 
>> From: Ted Dunning 
>> Date: November 24, 2016 at 2:28:47 PM PST
>> To: "gene...@incubator.apache.org" 
>> Subject: Re: JSON License and Apache Projects
>> Reply-To: gene...@incubator.apache.org
>> 
>> Stephan,
>> 
>> What you suggest should work (if you add another dependency to provide the
>> needed classes).
>> 
>> You have to be careful, however, because your consumers may expect to get
>> the full json.org API.
>> 
>> I would suggest that exclusions like this should only be used while your
>> direct dependency still has the dependency on json.org. When they fix it,
>> you can drop the exclusion and all will be good.
>> 
>> 
>> 
>>> On Thu, Nov 24, 2016 at 2:21 AM, Stephan Ewen  wrote:
>>> 
>>> Just to be on the safe side:
>>> 
>>> If project X depends on another project Y that uses json.org (and thus
>>> project X has json.org as a transitive dependency) is it sufficient to
>>> exclude the transitive json.org dependency in the reference to project Y?
>>> 
>>> Something like that:
>>> 
>>> 
>>> org.apache.hive.hcatalog
>>> hcatalog-core
>>> 0.12.0
>>> 
>>>   
>>> org.json
>>> json
>>>   
>>> 
>>> 
>>> 
>>> Thanks,
>>> Stephan
>>> 
>>> 
>>> On Thu, Nov 24, 2016 at 10:00 AM, Jochen Theodorou 
>>> wrote:
>>> 
 is that library able to deal with the jdk9 module system?
 
 
> On 24.11.2016 02:16, James Bognar wrote:
> 
> Shameless plug for Apache Juneau that has a cleanroom implementation of
>>> a
> JSON serializer and parser in context of a common serialization API that
> includes a variety of serialization languages for POJOs.
> 
> On Wed, Nov 23, 2016 at 8:10 PM Ted Dunning 
> wrote:
> 
> The VP Legal for Apache has determined that the JSON processing library
>> from json.org  is not usable as
>>> a
>> dependency by Apache projects. This is because the license includes a
>> line
>> that places a field of use condition on downstream users in a way that
>>> is
>> not compatible with Apache's license.
>> 
>> This decision is, unfortunately, a change from the previous situation.
>> While the current decision is correct, it would have been nice if we
>>> had
>> had this decision originally.
>> 
>> As such, some existing projects may be impacted because they assumed
>>> that
>> the json.org dependency was OK to use.
>> 
>> Incubator projects that are currently using the json.org library have
>> several courses of action:
>> 
>> 1) just drop it. Some projects like Storm have demos that use twitter4j
>> which incorporates the problematic code. These demos aren't core and
>> could
>> just be dropped for a time.
>> 
>> 2) help dependencies move away from problem code. I have sent a pull
>> request to twitter4 j,
>>> for
>> example, that eliminates the problem. If they accept the pull, then all
>> would be good for the projects that use twitter4j (and thus json.org)
>> 
>> 3) replace the json.org artifact with a compatible one that is open
>> source.
>> I have created and published an artifact based on clean-room Android
>>> code
>>  that replicates the most
>> important
>> parts of the json.org code. This code is compatible, but lacks some
>> coverage. It also could lead to jar hell if used unjudiciously because
>>> it
>> uses the org.json package. Shading and exclusion in a pom might help.
>>> Or
>> not. Go with caution here.
>> 
>> 4) switch to safer alternatives such as Jackson. This requires code
>> changes, but is probably a good thing to do. This option is the one
>>> that
>> is
>> best in the long-term but is also the most expensive.
>> 
>> 
>> -- Forwarded message --
>> From: Jim Jagielski 
>> Date: Wed, Nov 23, 2016 at 6:10 AM
>> Subject: JSON License and Apache Projects
>> To: ASF Board 
>> 
>> 
>> (forwarded from legal-discuss@)
>> 
>> As some of you may know, recently the JSON License has been
>> moved to Category X (https://www.apache.org/legal/resolved#category-x
>>> ).
>> 
>> I understand that this has impacted some projects, especially
>> those in the midst of doing a release. I also understand that
>> up until now, really, there has been no real "outcry" over our
>> usage of it, especially from end-users and other