On Aug 21, 2012, at 11:48 PM, Santhosh M S wrote:

> 
> 
> Could we repost the entire blog and indicate that this blog originally 
> appeared here with the here being a hyperlink to the corporate blog without 
> mentioning the name of the corporation.
> 
> More thoughts?

I'm +1 on this.

Alan.


> 
> Santhosh
> 
> 
> ________________________________
> From: Russell Jurney <[email protected]>
> To: "[email protected]" <[email protected]> 
> Sent: Tuesday, August 21, 2012 7:17 PM
> Subject: Re: Pig as Connector with MongoDB and Node.js
> 
> I like the idea of re-blogging the entire thing with a link back to
> the company. Blogs take time, and time is money, so posting to the Pig
> blog first isn't likely. Even personal posts about Pig on my blog
> datasyndrome.com, I'd rather post them on my blog and reblog/link back
> on the Pig blog. This is consistent with common practice.
> 
> The real point here is to get common place to recognize, index and
> distribute blog post HOWTOs as documentation. If there's value in the
> post, we should reblog it with a link back.
> 
> Russell Jurney http://datasyndrome.com
> 
> On Aug 21, 2012, at 7:03 PM, Alan Gates <[email protected]> wrote:
> 
>> Are you saying we should only post things to the Pig blog that isn't already 
>> on a corporate blog?  I'm not sure that's going to fly, since companies pay 
>> people to write blogs for them.  They aren't going to be excited to publish 
>> on Apache first.
>> 
>> If we don't feel comfortable posting things on the Pig blog that have 
>> already been posted on a corporate blog we could instead post very short 
>> blogs entries that say something like "A blog on X has been posted over on 
>> http://Y, go take a look".
>> 
>> Alan.
>> 
>> On Aug 17, 2012, at 3:28 PM, Santhosh M S wrote:
>> 
>>> Thanks Alan! I went to that site before my previous email and I did not 
>>> find anything and hence the post.
>>> 
>>> If the content has no association with any corporation, we should first 
>>> post it on the Apache Pig Blog and then cross post it on the corporate 
>>> blog. This way, we can decouple the community interests from the corporate 
>>> interests.
>>> 
>>> Thoughts?
>>> 
>>> Santhosh
>>> 
>>> 
>>> ________________________________
>>> From: Alan Gates <[email protected]>
>>> To: [email protected]
>>> Sent: Friday, August 17, 2012 3:20 PM
>>> Subject: Re: Pig as Connector with MongoDB and Node.js
>>> 
>>> http://blogs.apache.org/pig/
>>> 
>>> We don't have any posts there yet.
>>> 
>>> Alan.
>>> 
>>> On Aug 17, 2012, at 3:15 PM, Santhosh M S wrote:
>>> 
>>>> Before we post the blog, can someone post the URL for the Apache Pig Blog. 
>>>> Search engine queries are not returning anything useful.
>>>> 
>>>> Thanks,
>>>> Santhosh
>>>> 
>>>> 
>>>> ________________________________
>>>> From: Jonathan Coveney <[email protected]>
>>>> To: [email protected]
>>>> Sent: Friday, August 17, 2012 12:09 PM
>>>> Subject: Re: Pig as Connector with MongoDB and Node.js
>>>> 
>>>> I'm ok with that as long as it is clear it came from a corporate blog, and
>>>> of course, if people feel uncomfortable they should voice that opinion.
>>>> 
>>>> I think it is good to show that a variety of people use Pig, and I mean,
>>>> it's not really a surprise that Pig is developed, used, and promoted by
>>>> corporations :)
>>>> 
>>>> 2012/8/17 Alan Gates <[email protected]>
>>>> 
>>>>> I'm happy to repost these kinds of blog entries on the Pig blog.  But one
>>>>> thing we as a community need to decide is how we want to handle references
>>>>> to corporate blogs.  My proposal would be that any entries supporting and
>>>>> promoting Apache Pig should be allowed.  But I have an obvious conflict of
>>>>> interest here, so I'd like to get other people's inputs.
>>>>> 
>>>>> Alan.
>>>>> 
>>>>> On Aug 16, 2012, at 3:07 PM, Russell Jurney wrote:
>>>>> 
>>>>>> I wrote a Pig tutorial to publish data with Mongo and Node.js.
>>>>>> 
>>>>>> 
>>>>> http://hortonworks.com/blog/pig-as-connector-part-one-pig-mongodb-and-node-js
>>>>>> 
>>>>>> Is it possible to reblog on the Pig blog?
>>>>>> 
>>>>>> Russell Jurney
>>>>>> twitter.com/rjurney
>>>>>> [email protected]
>>>>>> datasyndrome.com

Reply via email to