Hi There,

What is the policy on using the Apache Blogs for projects. In the Apache Pig user mailing list we had a discussion on reposting corporate blogs on the Apache Blog for Pig and then link it back to the original post.

We arrived at a consensus that it should be fine to repost the blog and link it back without mentioning the name of the corporation. An example is shown below. We wanted to check with you if this is fine.

E.g:

The following blog is a repost from [ URL here ]

Reposted contents
Thanks,

Santhosh

Hello, Santhosh --thanks so much for your message. We're happy to help.

Unfortunately, the referenced URL didn't make it through. Is there any chance you can re-transmit in plaintext vs. embedded link?

Thanks in advance,
Sally

>________________________________
> From: Santhosh M S <[EMAIL PROTECTED]>
>To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Sent: Wednesday, 22 August 2012, 22:12
>Subject: Apache Blogging guidelines
>
>
>Hi There,
>
>
>What is the policy on using the Apache Blogs for projects. In the Apache Pig user mailing list we had a discussion on reposting corporate blogs on the Apache Blog for Pig and then link it back to the original post.
>
>
>We arrived at a consensus that it should be fine to repost the blog and link it back without mentioning the name of the corporation. An example is shown below. We wanted to check with you if this is fine.
>
>
>E.g:
>
>The following blog is a repost from [ URL here ]
>
>Reposted contents
>
>
>
>Thanks,
>
>Santhosh
>
>
>
>
>
>
>
>

Hi Sally,

Thanks for the quick response.

That was just an example. I will use the one that was discussed in the mailing list. The 'here' will be a hyperlink to the actual blog

The following blog is a repost from [http://hortonworks.com/blog/pig-as-connector-part-one-pig-mongodb-and-node-js here]

<The entire contents of the corporate blog will follow>

Thanks,
Santhosh

________________________________
 From: Sally Khudairi <[EMAIL PROTECTED]>
To: Santhosh M S <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Sent: Wednesday, August 22, 2012 7:32 PM
Subject: Re: Apache Blogging guidelines
 

Hello, Santhosh --thanks so much for your message. We're happy to help.

Unfortunately, the referenced URL didn't make it through. Is there any chance you can re-transmit in plaintext vs. embedded link?

Thanks in advance,
Sally

>________________________________
> From: Santhosh M S <[EMAIL PROTECTED]>
>To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Sent: Wednesday, 22 August 2012, 22:12
>Subject: Apache Blogging guidelines
>
>
>Hi There,
>
>
>What is the policy on using the Apache Blogs for projects. In the Apache Pig user mailing list we had a discussion on reposting corporate blogs on the Apache Blog for Pig and then link it back to the original post.
>
>
>We arrived at a consensus that it should be fine to repost the blog and link it back without mentioning the name of the corporation. An example is shown below. We wanted to check with you if this is fine.
>
>
>E.g:
>
>The following blog is a repost from [ URL here ]
>
>Reposted contents
>
>
>
>Thanks,
>
>Santhosh
>
>
>
>
>
>
>
>

Thanks, Santhosh.

OK, I get the meta issue of my failure to grok the context the first time around...

Using the referenced article as an example, I would request that this be done in instances where the author is a contributor to the project. So this would look something along the lines of --

>[Subject] Pig as Hadoop Connector, Part One: Pig, MongoDB and Node.js
>
>[Body] Apache Pig Committer Russell Jurney has published a series on Pig as a connector for Apache Hadoop.
>
>Apache Pig is a dataflow oriented, scripting interface to Hadoop. Pig enables you to manipulate data as tuples in simple pipelines without thinking about the complexities of MapReduce.
>
>But Pig is more than that. Pig has emerged as the 'duct tape' of Big Data, enabling you to send data
 between distributed systems in a few lines of code. In this series, we're going to show you how to use Hadoop and Pig to connect different distributed systems, to enable you to process data from wherever and to wherever you like.
>
>...
>
>The full post is available at [ URL here ]

For those articles not authored by Apache Committers, then perhaps have the post drafted with an intro from someone within the PMC, along with the first paragraph (or two) as appropriate with the link. So using the Russell Jurney article above, it would read as:

>[Subject] Suggested Read -- Pig as Hadoop Connector, Part One: Pig, MongoDB and Node.js
>
>[Body] The Apache Pig Project Management Committee suggests the following blog series on Pig as a connector for Apache Hadoop:
> 
>Apache Pig is a dataflow oriented, scripting interface to Hadoop. Pig enables you to manipulate data as tuples in simple pipelines without thinking about the complexities of MapReduce.
>
>But Pig is more than that. Pig has emerged as the 'duct tape' of Big Data, enabling you to send data between distributed systems in a few lines of code. In this series, we're going to show you how to use Hadoop and Pig to connect different distributed systems, to enable you to process data from wherever and to wherever you like.
>
>...
>
>The full post is available at [ URL here ] 
I hope this helps! Feel free to ping me if you need anything else.

Cheers,
Sally

>________________________________
> From: Santhosh M S <[EMAIL PROTECTED]>
>To: Sally Khudairi <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Sent: Wednesday, 22 August 2012, 23:53
>Subject: Re: Apache Blogging guidelines
>
>
>Hi Sally,
>
>
>Thanks for the quick response.
>
>
>That was just an example. I will use the one that was discussed in the mailing list. The 'here' will be a hyperlink to the actual blog
>
>
>The following blog is a repost from [http://hortonworks.com/blog/pig-as-connector-part-one-pig-mongodb-and-node-js here]
>
>
><The entire contents of the corporate blog will follow>
>
>
>Thanks,
>Santhosh
>
>________________________________
> From: Sally Khudairi <[EMAIL PROTECTED]>
>To: Santhosh M S <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Sent: Wednesday, August 22, 2012 7:32 PM
>Subject: Re: Apache Blogging guidelines
>
>
>Hello, Santhosh --thanks so much for your message. We're happy to help.
>
>
>Unfortunately, the referenced URL didn't make it through. Is there any chance you can re-transmit in plaintext vs. embedded link?
>
>Thanks in advance,
>Sally
>
>
>
>>________________________________
>> From: Santhosh M S <[EMAIL PROTECTED]>
>>To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>>Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>>Sent: Wednesday, 22 August 2012, 22:12
>>Subject: Apache Blogging guidelines
>>
>>
>>Hi There,
>>
>>
>>What is the policy on using the Apache Blogs for projects. In the Apache Pig user mailing list we had a discussion on reposting corporate blogs on the Apache Blog for Pig and then link it back to the original post.
>>
>>
>>We arrived at a consensus that it should be fine to repost the blog and link it back without mentioning the name of the corporation. An example is shown below. We wanted to check with you if this is fine.

Thanks a lot Sally. I appreciate your quick response and the precise advice.

Regards,
Santhosh
________________________________
 From: Sally Khudairi <[EMAIL PROTECTED]>
To: Santhosh M S <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2012 7:47 PM
Subject: Re: Apache Blogging guidelines
 

Thanks, Santhosh.

OK, I get the meta issue of my failure to grok the context the first time around...

Using the referenced article as an example, I would request that this be done in instances where the author is a contributor to the project. So this would look something along the lines of --

>[Subject] Pig as Hadoop Connector, Part One: Pig, MongoDB and Node.js
>
>[Body] Apache Pig Committer Russell Jurney has published a series on Pig as a connector for Apache Hadoop.
>
>Apache Pig is a dataflow oriented, scripting interface to Hadoop. Pig enables you to manipulate data as tuples in
 simple pipelines without thinking about the complexities of MapReduce.
>
>But Pig is more than that. Pig has emerged as the 'duct tape' of Big Data, enabling you to send data
 between distributed systems in a few lines of code. In this series, we're going to show you how to use Hadoop and Pig to connect different distributed systems, to enable you to process data from wherever and to wherever you like.
>
>...
>
>The full post is available at [ URL here ]

For those articles not authored by Apache Committers, then perhaps have the post drafted with an intro from someone within the PMC, along with the first paragraph (or two) as appropriate with the link. So using the Russell Jurney article above, it would read as:

>[Subject] Suggested Read -- Pig as Hadoop Connector, Part One: Pig, MongoDB and Node.js
>
>[Body] The Apache Pig Project Management Committee suggests the following blog series on Pig as a connector for Apache Hadoop:
> 
>Apache Pig is a dataflow oriented, scripting interface to Hadoop. Pig enables you to manipulate data as tuples in simple pipelines without thinking about the complexities of MapReduce.
>
>But Pig is more than that. Pig has emerged as the 'duct tape' of Big Data, enabling you to send data between distributed systems in a few lines of code. In this series, we're going to show you how to use Hadoop and Pig to connect different distributed systems, to enable you to process data from wherever and to wherever you like.
>
>...
>
>The full post is available at [ URL here
 ] 
I hope this helps! Feel free to ping me if you need anything else.

Cheers,
Sally

>________________________________
> From: Santhosh M S <[EMAIL PROTECTED]>
>To: Sally Khudairi <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Sent: Wednesday, 22 August 2012, 23:53
>Subject: Re: Apache Blogging guidelines
>
>
>Hi Sally,
>
>
>Thanks for the quick response.
>
>
>That was just an example. I will use the one that was discussed in the mailing list. The 'here' will be a hyperlink to the actual blog
>
>
>The following blog is a repost from [http://hortonworks.com/blog/pig-as-connector-part-one-pig-mongodb-and-node-js here]
>
>
><The entire contents of the corporate blog will follow>
>
>
>Thanks,
>Santhosh
>
>________________________________
> From: Sally Khudairi <[EMAIL PROTECTED]>
>To: Santhosh M S <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>Sent: Wednesday, August 22, 2012 7:32 PM
>Subject: Re: Apache Blogging guidelines
>
>
>Hello, Santhosh --thanks so much for your message. We're happy to help.
>
>
>Unfortunately, the referenced URL didn't make it through. Is there any chance you can re-transmit in plaintext vs. embedded link?
>
>Thanks in advance,
>Sally
>
>
>
>>________________________________
>> From: Santhosh M S <[EMAIL PROTECTED]>
>>To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>>Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>

Sally, is it ok to include the name of the company that contributes
the post, in the title of the post? I want companies competing to
write the best docs, so recognizing them seems smart, as in PoweredBy
pages.

For example: Acme Co on Using Pig to Analyze Twister with Bloom Filters

Russell Jurney http://datasyndrome.com

On Aug 23, 2012, at 8:51 PM, Santhosh M S <[EMAIL PROTECTED]> wrote:

> Thanks a lot Sally. I appreciate your quick response and the precise advice.
>
> Regards,
> Santhosh
>
>
> ________________________________
> From: Sally Khudairi <[EMAIL PROTECTED]>
> To: Santhosh M S <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Sent: Thursday, August 23, 2012 7:47 PM
> Subject: Re: Apache Blogging guidelines
>
>
> Thanks, Santhosh.
>
> OK, I get the meta issue of my failure to grok the context the first time around...
>
> Using the referenced article as an example, I would request that this be done in instances where the author is a contributor to the project. So this would look something along the lines of --
>
>> [Subject] Pig as Hadoop Connector, Part One: Pig, MongoDB and Node.js
>>
>> [Body] Apache Pig Committer Russell Jurney has published a series on Pig as a connector for Apache Hadoop.
>>
>> Apache Pig is a dataflow oriented, scripting interface to Hadoop. Pig enables you to manipulate data as tuples in
> simple pipelines without thinking about the complexities of MapReduce.
>>
>> But Pig is more than that. Pig has emerged as the 'duct tape' of Big Data, enabling you to send data
> between distributed systems in a few lines of code. In this series, we're going to show you how to use Hadoop and Pig to connect different distributed systems, to enable you to process data from wherever and to wherever you like.
>>
>> ...
>>
>> The full post is available at [ URL here ]
>
> For those articles not authored by Apache Committers, then perhaps have the post drafted with an intro from someone within the PMC, along with the first paragraph (or two) as appropriate with the link. So using the Russell Jurney article above, it would read as:
>
>> [Subject] Suggested Read -- Pig as Hadoop Connector, Part One: Pig, MongoDB and Node.js
>>
>> [Body] The Apache Pig Project Management Committee suggests the following blog series on Pig as a connector for Apache Hadoop:
>>
>> Apache Pig is a dataflow oriented, scripting interface to Hadoop. Pig enables you to manipulate data as tuples in simple pipelines without thinking about the complexities of MapReduce.
>>
>> But Pig is more than that. Pig has emerged as the 'duct tape' of Big Data, enabling you to send data between distributed systems in a few lines of code. In this series, we're going to show you how to use Hadoop and Pig to connect different distributed systems, to enable you to process data from wherever and to wherever you like.
>>
>> ...
>>
>> The full post is available at [ URL here
> ]
>
>
> I hope this helps! Feel free to ping me if you need anything else.
>
> Cheers,
> Sally
>
>
>
>> ________________________________
>> From: Santhosh M S <[EMAIL PROTECTED]>
>> To: Sally Khudairi <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> Sent: Wednesday, 22 August 2012, 23:53
>> Subject: Re: Apache Blogging guidelines
>>
>>
>> Hi Sally,
>>
>>
>> Thanks for the quick response.
>>
>>
>> That was just an example. I will use the one that was discussed in the mailing list. The 'here' will be a hyperlink to the actual blog
>>
>>
>> The following blog is a repost from [http://hortonworks.com/blog/pig-as-connector-part-one-pig-mongodb-and-node-js here]
>>
>>
>> <The entire contents of the corporate blog will follow>
>>
>>
>> Thanks,
>> Santhosh
>>
>> ________________________________
>> From: Sally Khudairi <[EMAIL PROTECTED]>
>> To: Santhosh M S <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>

Russell Jurney! Your ears must have been ringing :-)

Yes, you may reference the organization, but please keep in mind that the ASF is vendor-neutral, we need to tread carefully.

So you can refer to yourself (for your blogpost) as "Apache Pig Committer and TITLE at EMPLOYER Russell Jurney ...", or the PMC's suggested read "the latest article on BigData by Computerworld" --that sort of thing is OK.

Does that make sense? Does that answer your question?

Cheers,
Sally

Sent from my HTC

----- Reply message -----
From: "Russell Jurney" <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Cc: "Sally Khudairi" <[EMAIL PROTECTED]>, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Subject: Apache Blogging guidelines
Date: Thu, Aug 23, 2012 11:57 PM
Sally, is it ok to include the name of the company that contributes
the post, in the title of the post? I want companies competing to
write the best docs, so recognizing them seems smart, as in PoweredBy
pages.

For example: Acme Co on Using Pig to Analyze Twister with Bloom Filters

Russell Jurney http://datasyndrome.com

On Aug 23, 2012, at 8:51 PM, Santhosh M S <[EMAIL PROTECTED]> wrote:

> Thanks a lot Sally. I appreciate your quick response and the precise advice.
>
> Regards,
> Santhosh
>
>
> ________________________________
> From: Sally Khudairi <[EMAIL PROTECTED]>
> To: Santhosh M S <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Sent: Thursday, August 23, 2012 7:47 PM
> Subject: Re: Apache Blogging guidelines
>
>
> Thanks, Santhosh.
>
> OK, I get the meta issue of my failure to grok the context the first time around...
>
> Using the referenced article as an example, I would request that this be done in instances where the author is a contributor to the project. So this would look something along the lines of --
>
>> [Subject] Pig as Hadoop Connector, Part One: Pig, MongoDB and Node.js
>>
>> [Body] Apache Pig Committer Russell Jurney has published a series on Pig as a connector for Apache Hadoop.
>>
>> Apache Pig is a dataflow oriented, scripting interface to Hadoop. Pig enables you to manipulate data as tuples in
> simple pipelines without thinking about the complexities of MapReduce.
>>
>> But Pig is more than that. Pig has emerged as the 'duct tape' of Big Data, enabling you to send data
> between distributed systems in a few lines of code. In this series, we're going to show you how to use Hadoop and Pig to connect different distributed systems, to enable you to process data from wherever and to wherever you like.
>>
>> ...
>>
>> The full post is available at [ URL here ]
>
> For those articles not authored by Apache Committers, then perhaps have the post drafted with an intro from someone within the PMC, along with the first paragraph (or two) as appropriate with the link. So using the Russell Jurney article above, it would read as:
>
>> [Subject] Suggested Read -- Pig as Hadoop Connector, Part One: Pig, MongoDB and Node.js
>>
>> [Body] The Apache Pig Project Management Committee suggests the following blog series on Pig as a connector for Apache Hadoop:
>>
>> Apache Pig is a dataflow oriented, scripting interface to Hadoop. Pig enables you to manipulate data as tuples in simple pipelines without thinking about the complexities of MapReduce.
>>
>> But Pig is more than that. Pig has emerged as the 'duct tape' of Big Data, enabling you to send data between distributed systems in a few lines of code. In this series, we're going to show you how to use Hadoop and Pig to connect different distributed systems, to enable you to process data from wherever and to wherever you like.
>>
>> ...
>>
>> The full post is available at [ URL here
> ]
>
>
> I hope this helps! Feel free to ping me if you need anything else.
>
> Cheers,
> Sally
>
>
>
>> ________________________________
>> From: Santhosh M S <[EMAIL PROTECTED]>
>> To: Sally Khudairi <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>