Podling Suitable Names Search
  1. Podling Suitable Names Search
  2. PODLINGNAMESEARCH-23

Establish whether "Apache CloudStack" is a suitable name

    Details

    • Type: Suitable Name Search Suitable Name Search
    • Status: Closed
    • Resolution: Fixed
    • Podling:
      CloudStack
    • Proposed Name:
      CloudStack
    • Evidence Of Open Source Adoption:
      Hide
      Ohloh search for CloudStack has 6 results
      3 of those results are various copies of the Apache CloudStack codebase around the internet.
      one is knife-cloudstack - a knife plugin for Apache CloudStack
      one is a collection of puppet manifests for the pre-ASF incarnation of the projects' infrastructure
      The final result is for CloudBridge (an AWSAPI translation layer) which was a separate add-on component for CloudStack but was merged into the CloudStack codebase prior to the move to the ASF.

      Github has 143 projects found when searching for CloudStack
      All of the projects are Apache CloudStack, or related to Apache CloudStack (things like nagios plugins for monitoring Apache CloudStack or configuration management plugins for Apache CloudStack) or blank with the following exceptions:
      https://github.com/pombredanne/TSP-CloudStack
      https://github.com/beloglazov/openstack-centos-kvm-glusterfs
      https://github.com/xiangzhai/xcloud
      https://github.com/johntdyer/enstratus-chef
      https://github.com/neillturner/ec2dream
      https://github.com/specialunderwear/puppet-kicker
      https://github.com/astratto/vcloud-rest
      https://github.com/ipauldev/enpribus
      https://github.com/kfix/BoxJig
      https://github.com/murraju/ucslib
      https://github.com/astratto/knife-vcloud
      Show
      Ohloh search for CloudStack has 6 results 3 of those results are various copies of the Apache CloudStack codebase around the internet. one is knife-cloudstack - a knife plugin for Apache CloudStack one is a collection of puppet manifests for the pre-ASF incarnation of the projects' infrastructure The final result is for CloudBridge (an AWSAPI translation layer) which was a separate add-on component for CloudStack but was merged into the CloudStack codebase prior to the move to the ASF. Github has 143 projects found when searching for CloudStack All of the projects are Apache CloudStack, or related to Apache CloudStack (things like nagios plugins for monitoring Apache CloudStack or configuration management plugins for Apache CloudStack) or blank with the following exceptions: https://github.com/pombredanne/TSP-CloudStack https://github.com/beloglazov/openstack-centos-kvm-glusterfs https://github.com/xiangzhai/xcloud https://github.com/johntdyer/enstratus-chef https://github.com/neillturner/ec2dream https://github.com/specialunderwear/puppet-kicker https://github.com/astratto/vcloud-rest https://github.com/ipauldev/enpribus https://github.com/kfix/BoxJig https://github.com/murraju/ucslib https://github.com/astratto/knife-vcloud
    • Evidence Of Registration:
      Hide
      Searched TESS - found only the following two serial numbers:
      85345128
      85341605

      Both registered to Citrix Systems.
      Show
      Searched TESS - found only the following two serial numbers: 85345128 85341605 Both registered to Citrix Systems.
    • Evidence Of Use On World Wide Web:
      First 5 pages of google search are exclusively about the project, or projects links themselves. (on Feb 13 2013)

      Activity

      Hide
      Shane Curcuru added a comment -
      Approved.

      Note that this really points out a hole in the podling name search policy. We need to update it to say (something like): If the podling has a well-established name over a period of several years, and the donor of the podling's IP is explicitly granting the trademark rights to the name to the ASF as part of the incubation/graduation, then the podling name search step is simply informing trademarks@ of this fact.

      If there's a well-established name (or especially a registered one, although that's not required) being donated, that in of itself is a very strong indicator that the name will continue to be suitable, especially when we include it within the Apache Foo branding. Obviously, if there are any previous or current complaints or issues with the pre-existing name, then trademarks@ and the PPMC need to evaluate those to ensure they can be dealt with as an Apache project.

      Thanks to CloudStack PPMC for being diligent as always!
      Show
      Shane Curcuru added a comment - Approved. Note that this really points out a hole in the podling name search policy. We need to update it to say (something like): If the podling has a well-established name over a period of several years, and the donor of the podling's IP is explicitly granting the trademark rights to the name to the ASF as part of the incubation/graduation, then the podling name search step is simply informing trademarks@ of this fact. If there's a well-established name (or especially a registered one, although that's not required) being donated, that in of itself is a very strong indicator that the name will continue to be suitable, especially when we include it within the Apache Foo branding. Obviously, if there are any previous or current complaints or issues with the pre-existing name, then trademarks@ and the PPMC need to evaluate those to ensure they can be dealt with as an Apache project. Thanks to CloudStack PPMC for being diligent as always!
      Hide
      David Nalley added a comment -
      Thanks for the approval Shane.

      Closing this issue.
      Show
      David Nalley added a comment - Thanks for the approval Shane. Closing this issue.

        People

        • Assignee:
          Unassigned
          Reporter:
          David Nalley
        • Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development