[Rubyinstaller-devel] One-Click Ruby Installer needs a new home, can you help him?

Luis Lavena luislavena at gmail.com
Tue May 19 19:16:10 EDT 2009

On Tue, May 19, 2009 at 11:24 AM, Michal Suchanek <hramrach at centrum.cz> wrote:
> 2009/5/19 Luis Lavena <luislavena at gmail.com>:
>> ...
>> Well, again hosting is going to be out of my pocket too, so if a
>> generous company thinks that One-Click Ruby Installer deserves a
>> homepage and they could host it, will be awesome, but I'm not holding
>> my breath.
> I think that hosting a web site (as opposed a download site) is not
> completely out of question.

Well, I believe the hosting part of the equation is not a problem.
Downloads are going to be located as usual at RubyForge.

The intention of this is not replace RubyForge for bug reporting or
downloads, but provide a better, simplified and clean access to Ruby
for Windows, which ruby-lang is not offering and neither RubyForge or
the current Wiki page.

> However, it is necessary to know what kind of hosting is required.

I mention the development of the site in Radiant CMS or a Ruby CMS, so
the hosting is going to be Ruby/Rails based.

> Still if you hosted the site yourself it would be sort of reassuring
> to know that as long as the the installer is going forward the site is
> likely to stay, too.

Well, that's what I said, I intend to host myself. Also, I intend to
contribute with my personal money for the design of it.

>> Like a Wiki :-)
> No, unlike a Wiki.

Well, I tried to be ironic, but I meant to say more as Knowledge Base
containing links to the different resources in the different
categories: from compiling to using Ruby in different scenarios
(either on Windows or deploys from it to Linux).

> ...
> I imagine it is possible to turn commit messages and release notes for
> downloads into news articles automatically if they are hosted on a
> reasonably cooperative site.

Manual administration is not going to be a problem, being the central
location of all this will make things more easy.

> A script could easily select the newest article from each important
> category to create a clean and simple top page that offers all
> important information in one place.

Which basically Radiant can do it with some Ruby magic.

> Perhaps I got too distracted by the application icon :-)

Sorry :-)

So, in better words I think I going to run this as a Bounty/Contest/Challenge:

I'm going to open a Pledgie, and put some money there. This means the
designers that want to participate will need to be able to collect
money using Paypal.

Next, Designers can create mockups of the homepage, and use "as
inspiration" the logo/branding for the installer that already exist:


Important things the site needs to allow:

* Simple, clean, friendly design.
* Latest news about releases.
* Latest version information
* Latest Links added to the Knowledge Base
* Access to Download information pages
* Access to Knowledge Base pages
* Access to Get Help pages
* Access to Contribute information pages

Advance details:

* Download information will contain both 1.8 and 1.9 latest downloads.
* Prior download can be accessed via RubyForge
* Knowledge Base pages are small descriptions and links to the source
of the information, either a blog, a wiki or a screencast being hosted
* Get Help pages are going to summarize mailing list or groups where
users will likely get more feedback about their issues running Ruby on
* Contribute will provide links and information to access RubyForge or
GitHub and what are the requirements to help on the project.

Mockups are going to be open to the wild as a poll, and people will pick them.

Pledgie will remain active until deadline of the poll.

Once the poll deadline has reached, the best mockup which follows the
above criteria is going to be selected as "winner", which leads us to
the next point:

Before any designer do the mock up, they need to consider:

* Once design is approved, both hompages and inner page needs to be
completed as valid HTML+CSS
* Cross browser (yeah, IE, I'm talking about that beast) needs to be
considered as supported.
* Designer could have experience integrating this with Radiant and
provide advice, but is not mandatory.
* Full pledgie money is going to be paid when HTML and CSS elements
are handed over to RubyInstaller project team, in public, using a Git
* Credits and copyright of the design will remains in the design
owner, but he must give authorization for usage in rubyinstaller.org.

I want this be the most clean, clear and public as possible. I want
community choose what community likes, not what my personal taste

All the money collected up to the date of the poll is going to be
transfered, so is a risk, could be 100 or could be 2K, community will

Sounds good? I'm going to take this copy and use for the pledgie ;-)


Luis Lavena
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

More information about the Rubyinstaller-devel mailing list