* Blog links work
* Author and date for blog titles looks nice
* Cloud Providers link works
* Some review comments for the [blog
post](https://github.com/jclouds/jclouds-site/commit/76e9a653b83d123fcc43cde0d8cca235b3bec761)
Many thanks for putting that together, @nacx, and for all your work on
Addressed your comments, commited, and published. Thanks for reviewing @demobox
!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36738059
Addressed your comments, commited, and published
Thanks, Ignasi!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36740301
Go to
http://9cd9cd55c584fecebb2b-4536752bb6f4d6735190fddcc68c121b.r39.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36646658
Closed #58.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58
@nacx Thought of one more. It would be nice to have if we could have the actual
blog posts under jclouds.apache.org/blog//MM/DD instead of how they current
are under jclouds.apache.org//MM/DD.
I'm in the middle of a 12 hour meeting right now so I really don't have a
chance to dig into
@everett-toews I tried that but that broke all other links in the site, and
couldn't find a way to do that... :(
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36566809
Is this my browser/window size, or intentional?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36567304
@demobox It's not intentional, and it should be great to have it fixed before
merging. The logo issue was mentioned [here in the old pull
request](https://github.com/jclouds/jclouds-site/pull/51#issuecomment-31812479),
and I couldn't make it be properly aligned. Any help on this is highly
[jclouds-site-pull-requests
#198](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/198/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36573582
Go to
http://6c51efcb70dd975b240c-f3a3f42054c8a2f614324a87c08e9be8.r64.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36573801
I've just added a blog post about the move to the ASF, the new site and the
1.7.0 and 1.7.1 release. It's been a while since the last post, and we should
properly announce the new site and the new releases.
I'm not the best one at writing, so feel free to comment or directly edit the
post!
[jclouds-site-pull-requests
#199](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/199/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36575137
Go to
http://5f5c76d0ae31c29657f3-ce10666acc207bc2a2c4d10e66026eca.r10.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36575235
Go to
http://1b8a48b71b14668ec88e-8f018a5e0a20b39abc763cc7fc4f2ba7.r87.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36576456
Agree @demobox. I'm working on getting a better TOC. I'm making it similar to
[toficy](http://gregfranko.com/jquery.tocify.js/), but due to the layout of our
pages it does not render properly, so it myself.
It looks like this, and keeps fixed in its position (does not disappear when
scrolling
It looks like this
Nice! Being able to minimize or hide this would be a bonus, but as you said:
let's get this merged sooner rather than later if we think it's good enough,
and work on improvements later.
---
Reply to this email directly or view it on GitHub:
Go to
http://11c69b2b2e415d6b3f25-ddbcfa626cc19773f6332a93a4e5e344.r88.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36483996
@nacx As you can see in b945be5 I shortened the gettingstarted dir to just
start and installation-guide to just install. I did that because i'm not
crazy about compound words in URLs and such an important URL like
http://jclouds.apache.org/start/install/ should be short. If you're not happy
I like both @everett_toews. Thanks!
What's left before merging then?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36484597
I just noticed the Installation Guide is for 1.7.0. That should be 1.7.1.
That's it. Let's go for it!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36485189
Great!
Tonight I'll update the guides to point to 1.7.1, disable the atOC in the
ComputeService guide and merge.
I'll also try to write a blog post about the rebranding, 1.7.0 and 1.7.1. If I
have it soon and can be reviewed it would be nice to use it to announce the new
site.
Nice job all!
[jclouds-site-pull-requests
#196](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/196/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36261531
Finally I had time to finish the genetic TOC. It has room for improvements, but
basically it generates a TOC based on the page headings (h1 to h3, but if you
think having from h4 to h6 too in the TOC is a good idea is a trivial change),
with the appropriate nesting levels.
To use it in a page,
Finally I had time to finish the generic TOC.
Nice, thanks @nacx! One initial comment about the sample TOC: it's so long that
a reader now has to scroll down quite a way to see some content.
Is there some way we could make this expandable, with minimized being the
default? Either section by
Thinking more about it, I think *toolkit* is a better name. jclouds is not just
a library, is a set of libraries that can be used to manage the cloud, so I
think *toolkit* defines better what jclouds is.
I've just uploaded a commit with the slogan changed in the main page, and also
rebranded
We should also write a blog post announcing the new year changes: new site,
1.7.0 (with all its stuff) and 1.7.1, and ideally should be published along
with the new site, to properly announce it.
---
Reply to this email directly or view it on GitHub:
[jclouds-site-pull-requests
#192](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/192/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36113017
Go to
http://10720684367b760da111-612fee7537882e5d5391dafbf9b878ad.r97.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36113179
[jclouds-site-pull-requests
#193](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/193/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36114464
[jclouds-site-pull-requests
#194](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/194/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36116316
Go to
http://3c529895763ecb8a8cf5-8b5ff73a2fe803863960f0ac1c5775da.r50.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36116484
In terms of ranking I think people search for things like digitalocean java
api, s3 java, etc. But I'm not sure how people search for this kind of
thing: perhaps portable isn't also relevant in searches… I just don't know,
and would also like to have feedback from more people on this :)
Just
but Akka defines itself as a toolkit too
Ah...interesting data point. Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36140965
Go to
http://ad45a6d358f43958e25a-1b323d3a83db100c58eca5c5f5e6a3c4.r84.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36179544
* Rebranded the community index site and the jclouds user list to make the,
better looking.
* Also moved the supported providers link from the Community menu to the
Documentation one, as that is what jclouds does, not what people does with
jclouds.
* Removed the Report a Bug from the
Go to
http://b42d7362ca1187be989e-a12ebec22ba501beca2d2bd61aa12867.r19.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-35997188
Couple of random comments:
Do we need to add Load Balancer here, since we list it as one of the
abstraction APIs on the front page?
I like our current mission statement and I think it should be on the front
page. My only change was to basically replace Java and Clojure with JVM. I'm
on crazy about using an acronym in our mission statement but it should
somehow reflect that it works with many Java technologies.
Honestly
On Feb 22, 2014, at 12:58 AM, Andrew Phillips
notificati...@github.commailto:notificati...@github.com wrote:
How about something like The Java multi-cloud library? Does cloud
interfaces sound a little too abstract to others, too? We see a lot of
developers asking about cloud APIs or cloud
Go to
http://2e452be9bb477df01422-0c307192fbf46be1ea27e735ac77.r15.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-36067775
Apache jclouds® is an open source multi-cloud toolkit for the Java platform.
jclouds gives you the
freedom to create applications that are portable across clouds while giving
you full control to use
cloud-specific features.
I like this. The only word I'm not 100% sure about is toolkit.
Added Load Balancer providers, DigitalOcean and CloudSigma DC
Thanks for the updates, @nacx! Just about:
In terms of consistent capitalization, would Get in Touch!, Attend an Event
and Who is
Regarding stand-alone application, jclouds-cli is arguably fills this, albeit
poorly. Having an end-user example of how to take advantage of jclouds
cross-provider functionality would give the project and our users a huge boost.
I opened
I also like the proposed slogan but perhaps with library instead. I think it
describes better what jclouds is amd how it can be used, but I'd also be happy
with toolkit. Don't have a very strong preference.
@gaul, Ioannis already did an example web console for jclouds. Do you have in
mind
jclouds-cli is arguably fills this, albeit poorly
Indeed. But it's more of a downstream project than the core of jclouds
itself? Certainly, it's not the _only_ usable bit of jclouds we release.
---
Reply to this email directly or view it on GitHub:
slogan
How about something like The Java multi-cloud library? Does cloud
interfaces sound a little too abstract to others, too? We see a lot of
developers asking about cloud APIs or cloud providers, but I don't hear the
term cloud interfaces much. If we _do_ want to stick to that theme, how
[jclouds-site-pull-requests
#189](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/189/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-35675163
Go to
http://08abda524d9802e1e79f-de8b32be9b04620f0c76a8ecd94c22bf.r55.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/58#issuecomment-35675369
@nacx How would you feel about renaming the gettingstarted dir to just start?
I'm not crazy about compound words in URLs.
Also, how about renaming installation-guide to just install?
---
Reply to this email directly or view it on GitHub:
Let's publish this!
What's left that __absolutely__ needs to be done?
- [ ] Decide on the slogan
- [ ] Decide on the tag line
When these thing are done, let's publish it. We should publish on March 3rd or
before, in time for the next meetup.
---
Reply to this email directly or view it on
51 matches
Mail list logo
