[Rubyinstaller-devel] Next Steps for the OCI Project Site
luislavena at gmail.com
Tue Aug 4 22:56:14 EDT 2009
On Tue, Aug 4, 2009 at 6:25 PM, Jon<jon.forums at gmail.com> wrote:
> My impression is that we've got a good handle on this one and just need to get the work done. I also think we need to break the effort into at least two phases.
> ** Phase 1 ** goal is to quickly get a static pages up for http://rubyinstaller.org/ and http://rubyinstaller.org/downloads/ that are similar in theme to the work Pavel will be doing for Phase 2.
> These static pages will integrate with both RubyForge and GitHub and some of this has already started.
By integration you mean: pull of RubyForge information or just
integrate the links more seamlessly?
> I've let the monkey jump on my back for this one ;) My plan is to create some time and get something up within the next 3-5 days for us to review and critique.
> Luis...get me the hosting info/access ASAP or I'm putting the monkey on your back! >;->
Sent you the login information, so now the monkey is in your back.
> ** Phase 2 ** goal should be to resource the development of the Radiant-based CMS that Pavel's going to take the lead as well as identify *specifically* what we want for the initial content as well as how we'd like it to integrate in with the existing RubyForge and GitHub sites. I'm currently of the strong opinion that the Radiant-based site needs to be THE single go-to site for the OCI project.
We then need to know if we are going to maintain the GitHub wiki (we
already pointed lot of people there) Or move it to our Radiant site.
My personal preference is keep the following:
1) RubyForge: Tracker, Downloads and Mailing list
2) GitHub: Code repository and Wiki
3) Radiant: News and download links
This means A) we need to find a way to either pull the information or
just display the relevant links to users are not lost going back and
forth the sites.
For what is worth:
All linking to different places.
> While I think the development site should be accessible for review, I am strongly against it trying to be shoe horned into trying to fulfill both short-term and long-term roles. It's role should be the real project portal and Phase 1 should be made "good enough" to allow us to do more project evangelizing while Phase 2 is being completed.
> Thoughts...please make sure we understand whether the feedback is for Phase 1 or Phase 2 or both.
Again, I believe Phase 1 should not try to do a lot and for Phase 2,
we shouldn't try to reinvent the wheel doing Wiki, bug tracking and
other stuff already established like RubyForge or discard the work
done over GitHub.
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