www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Kinsella (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-5195) Create a planet instance to host http://planet.cloudstack.**.apache.org
Date Mon, 05 Nov 2012 17:36:11 GMT

     [ https://issues.apache.org/jira/browse/INFRA-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Kinsella updated INFRA-5195:
---------------------------------

    Comment: was deleted

(was: Shane (from trademarks@) gave us blessing to use http://planet.apache.org/cloudstack
(pasting email below for the record, I had previously CCed Daniel on it).

Any thoughts on timing on when INFA can work on this would be appreciated.

On Oct 19, 2012, at 5:11 PM, Shane Curcuru <asf@shanecurcuru.org> wrote:

Thanks for the patience and thoughts from a number of people on this one.  There are two issues
from the branding point of view:

1- Apache projects should live on *.apache.org domain names.  I've commented in INFRA-5195
to note this.  So planet.cloudstack.org is not appropriate.  Using a consistent project/product
and domain name in the form of "Apache Foo / foo.apache.org" is a fundamental part of ASF
branding.

Personally I like planet.apache.org/cloudstack, but the details of whatever name format on
*.apache.org you want is up to the PPMC and Infra to figure out.

2- I'm presuming that this is a feed that (P)PMC members will actively curate, so that only
"quality" feeds are being included - things that normal users of Apache Cloudstack would be
interested in reading (in general, I mean we all include blog posts of our cats or kids now
and then!).  But only a committer can actually directly add a new feed, not just anyone.

I think this is OK on (for example) planet.apache.org/cloudstack AS LONG AS there's a disclaimer
on the aggregation page that the individual feeds are available under separate licenses. 
As long as we do due diligence to let users know that various feed contents come from $random
people, and are not necessarily under the Apache license, it should be fine - even if some
feeds are from non-committers.

Heck, an auto-icon that differentiates committer posts from non-committer posts would be really
cute (but not required).

Does that make sense?

----
(Discussion) Licensing and submissions and feeds, oh my!  At the higher level, and important
concept in ASF policies is that we license *all* of our software under the Apache license.
 The principle of least surprise is important: when someone grabs code from any *.apache.org
domain, they can expect that it will be available under the Apache License unless it has BIG
RED SCREAMING LETTERS that obviously warns them otherwise.

This is easy with code: only iCLA holders can checkin, and even patches from outsiders should
be obviously "Contribution" as defined in the AL2.0.  It's usually easy with websites, since
they're typically in SVN, or are in a wiki that requires signup that again assures us the
submitter knows it's a "Contribution".

Aggregating feeds is different, since there's not necessarily a purposeful donation from the
author of the feed.  I.e. an author may say today that they use CC-BY on some post - but that
doesn't necessarily mean the whole feed will always be that.  Likewise, if PMC members add
feeds of non-committers, it's not necessarily clear that the original feed's posts' author
is intending all it's contents to be a "Contribution".

That's not to say we can't make this work, just an explanation of why this is an important
thing to label and make clear to users.


- Shane Curcuru
VP, Brand Management
The Apache Software Foundation
)
    
> Create a planet instance to host http://planet.cloudstack.**.apache.org
> -----------------------------------------------------------------------
>
>                 Key: INFRA-5195
>                 URL: https://issues.apache.org/jira/browse/INFRA-5195
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: VMWare
>            Reporter: John Kinsella
>
> Greetings. The CloudStack community would like to set up a "planet" blog aggregator.
Due to one of our goals of allowing feeds from non-committers, we intend to point planet.cloudstack.org
to the server, so as to not use the apache.org namespace.
> Based off an irc descussion in #asfinfra last week, we'd like to host this in a VM on
ASF infrastructure. We held a VOTE on the topic to move forward in this direction. The results
(+7) are in the email thread at the URL below.
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201208.mbox/%3C348B2883-E8A4-4B99-AC3E-BEF2ACD63D3A%40stratosec.co%3E
> Happy to provide any additional details that are needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message