This document is an extension to my original statement.
It explains why I’m leaving Ruby Central and what has happened in recent weeks.
Before diving into recent events, it’s useful to clarify how I’ll use certain terms in this post.
These definitions are not official Ruby Central terminology, but they reflect the way many of us in the Ruby open source community think about roles and responsibilities.
| <style> | |
| table { | |
| border: #ddd solid 1px; | |
| } | |
| td, th { | |
| padding: 8px; | |
| border: #ddd solid 1px; | |
| } | |
| td p { | |
| font-size: 15px !important; |
Album rankings and notes about same. Albums are ranked on the 4.0 scale, with some albums given additional credit as Exceptional, Essential, or Canon. Basically anything "exceptional" should be considered required listening. Anything "essential" should be in your record collection. Anything that's "canon" is foundational and really should be in your collection.
Grades are somewhat subjective but I also try to look at albums objectively. Meaning that some albums are my favorites but for possibly sentimental or subjective reasons. For example, Prison by Steven Jessie Bernstein is interesting and one of my favorites, but it's almost a curiosity rather than a prime example of musicicianship. Some albums just hit that nostalgia just right. Other albums, like The Queen is Dead (The Smiths) or Under the Pink are Essential albums that are required listening for anybody looking to understand those eras and later
I hereby claim:
To claim this, I am signing this object:
This document is meant to serve as a baseline definition for Project Atomic hosts, to be implemented from CentOS, Fedora, and Red Hat Enterprise Linux (RHEL).
The purpose of the document is not to restrict the packages or services offered with an Atomic host, but to ensure a baseline of functionality and working standard that each product team can implement before adding additional functionality.
The initial working draft is being taken from work going into RHEL Atomic, but it is expected that the CentOS Atomic SIG and Fedora Cloud Workgroup will provide input and direction to Project Atomic going forward. This is simply the first cut at a shared understanding that gives each team a basis for cooperation.
| # Apache CloudStack 4.1.0 Released | |
| The Apache CloudStack project is pleased to announce the 4.1.0 release of the CloudStack Infrastructure-as-a-Service (IaaS) cloud orchestration platform. This is the first major release from Apache CloudStack since its graduation from the Apache Incubator on March 20th. | |
| Apache CloudStack is an integrated software platform that allows users to build a feature-rich IaaS. CloudStack includes an intuitive user interface and rich API for managing the compute, networking, accounting, and storage resources for private, hybrid, or public clouds. | |
| The 4.1.0 release represents more than five months of development effort by the Apache CloudStack community. The release includes many new features and bugfixes from the 4.0.x cycle. The 4.1.0 release also marks major changes in the codebase to make CloudStack easier for developers, a new structure for creating RPM/Debian packages, and completes the changeover to using Maven as a build tool. | |
| ## New Features |
[ANNOUNCE] Apache CloudStack 4.0-Incubating Released
The Apache CloudStack (Incubating) project is pleased to announce the 4.0 release of the CloudStack Infrastructure-as-a-Service (IaaS) cloud orchestration platform. This is the first release from within the Apache Software Foundation (ASF).
Apache CloudStack is a Java-based platform that delivers an integrated platform that allows users to build a feature-complete IaaS. Apache CloudStack includes the compute, networking, accounting, storage, and user interface components to needed for private, hybrid, or public clouds.
The 4.0 release represents the culmination of more than six months work by the Apache CloudStack community. The release includes more than a dozen new features, many bugfixes, security fixes, and a fully audited codebase that complies with ASF guidelines.
##New Features:
#Apache CloudStack Collaboration Summit Call for Proposals
We're pleased to announce that the Call for Proposals for the first Apache CloudStack Collaboration Summit is now open!
The Collaboration Summit will feature tracks for users and developers of Apache CloudStack, with presentations that provide insight into best practices in deploying and developing Apache CloudStack. This will be an outstanding opportunity for developers to collaborate, share ideas, and get work done face-to-face with other Apache CloudStack contributors to improve Apache CloudStack.
The summit will be held Las Vegas at The Venetian, from Friday, November 30th through Sunday, December 2nd.
##Proposals
| <p> | |
| <pre> | |
| <code> | |
| git config --global github.user <em>username</em> | |
| git config --global github.token <em>token</em> | |
| git config --global github.token <em>token</em> | |
| </code> | |
| </pre> | |
| </p> |
| created by | |
| Yasuhiro Matsumoto | |
| script type | |
| utility | |
| description | |
| This is vimscript for gist (http://gist.github.com) | |
| Usage: |