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. 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! >;-> ** 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. 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. Jon
Luis Lavena
2009-Aug-05 02:56 UTC
[Rubyinstaller-devel] Next Steps for the OCI Project Site
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: http://rubyonrails.org/download http://rubyonrails.org/documentation http://rubyonrails.org/community 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. >Agree.> > 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. -- Luis Lavena AREA 17 - 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
> > ** 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?Integrate the links more seamlessly. Speaking of which, we need to decide what to do with http://rubyinstaller.rubyforge.org/wiki/wiki.pl?RubyInstallerNews. Currently I''m for putting a few snippets on the placeholder page and update the RubyForge page with a link similar to Gordon''s mod to http://rubyinstaller.rubyforge.org/wiki/wiki.pl?RubyInstaller> Sent you the login information, so now the monkey is in your back.Monkey received and firmly clutching my 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 linksAgree on (2) and (3). I don''t follow you on the Downloads at RubyForge. Are you saying you *do not* want downloads available from http://rubyinstaller.org/downloads/ but want it to link back to the correct RubyForge download page? If this is the case, I see no reason why we don''t immediately start putting the preview releases and DevKit downloads on RubyForge. WRT the mailing list, what are your thoughts on Charles Roper''s idea?
FYI, I''ve copied Pavel''s homepage mockup over to http://rubyinstaller.org/proto/ and will use that location to make the mods while working with Pavel to keep coordinated with his design. While the page isn''t going to be complex, I''d like for you to regularly check it and let me know if you have any browser/platform problems. I plan on checking with: FF 3.5.x on Win2K, WinXP, Vista, XUbuntu IE6 on Win2K (ugh) IE8 on WinXP, Vista Chrome 2.0.x on WinXP, Vista Safari 4.0.x on WinXP Jon
Gordon Thiesfeld
2009-Aug-05 15:50 UTC
[Rubyinstaller-devel] Next Steps for the OCI Project Site
On Wed, Aug 5, 2009 at 9:44 AM, Jon<jon.forums at gmail.com> wrote:> Speaking of which, we need to decide what to do with http://rubyinstaller.rubyforge.org/wiki/wiki.pl?RubyInstallerNews. > > Currently I''m for putting a few snippets on the placeholder page and update the RubyForge page with a link similar to Gordon''s mod to http://rubyinstaller.rubyforge.org/wiki/wiki.pl?RubyInstaller >I put a link to the rubyforge news page* for now. Luis is putting regular updates there. *http://rubyforge.org/news/?group_id=167
Gordon Thiesfeld
2009-Aug-05 16:05 UTC
[Rubyinstaller-devel] Next Steps for the OCI Project Site
2009/8/5 James Stallings II <james.stallings at gmail.com>:> Hey Y''all, >Hi James> I parted company with ruby some time back (it just didnt scale well for the > application area I entered) and have been increasingly tasked with deleting > messages since the recent increase in activity with your project. Would > someone mind telling me how to exit the list properly? >Check here: http://rubyforge.org/mailman/listinfo/rubyinstaller-devel If you still have trouble, let me know off-list, and I''ll see what I can do.> No offense, ruby rocks, just not for me at this time :DNone taken. I know how annoying it can be to be stuck on a list and unable to unsubscribe. Gordon
Gordon Thiesfeld
2009-Aug-05 16:09 UTC
[Rubyinstaller-devel] Next Steps for the OCI Project Site
On Wed, Aug 5, 2009 at 9:44 AM, Jon<jon.forums at gmail.com> wrote:>> > ** 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? > > Integrate the links more seamlessly. >I''ve forked Luis'' todo gist with my thoughts on this. http://gist.github.com/162777
Luis Lavena
2009-Aug-05 16:30 UTC
[Rubyinstaller-devel] Next Steps for the OCI Project Site
2009/8/5 James Stallings II <james.stallings at gmail.com>:> Thanks Matt, > > Right now I''m doing some approximately realtime work (what -is- realtime > anyway ;) >Yeah, realtime is not even realtime. Linux sucks at that too :P> A lot of metaverse/virtual worlds stuff. Timing sensitive, server-side > physics simulation and the like. Speed is critical.Well, I did broadcasting video interfacing with proprietary hardware, so had to deal with C, C++ and Assembler for LONG time (like 12 years). Ruby become my sanity check to avoid repetitive tasks, and now turned to be more centered for my current endeavors.> Thanks for the assist, and good luck with the project - keep up the great > work :) >Thanks to you, you can unsubscribe using the links at the footer of the messages. Have a good life! -- Luis Lavena AREA 17 - 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
Luis Lavena
2009-Aug-09 00:41 UTC
[Rubyinstaller-devel] Next Steps for the OCI Project Site
On Wed, Aug 5, 2009 at 1:09 PM, Gordon Thiesfeld<gthiesfeld at gmail.com> wrote:> On Wed, Aug 5, 2009 at 9:44 AM, Jon<jon.forums at gmail.com> wrote: >>> > ** 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? >> >> Integrate the links more seamlessly. >> > > I''ve forked Luis'' todo gist with my thoughts on this. > > http://gist.github.com/162777Merged it, thanks. What is the status for CHM? Can it be merged? -- Luis Lavena AREA 17 - 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
Gordon Thiesfeld
2009-Aug-09 01:05 UTC
[Rubyinstaller-devel] Next Steps for the OCI Project Site
On Sat, Aug 8, 2009 at 7:41 PM, Luis Lavena<luislavena at gmail.com> wrote:> > What is the status for CHM? Can it be merged? > --Here''s my todo list for getting the rake task ready. [*] Generate CHM files for Core and Standard Library (Gordon Thiesfeld) [ ] Finish Rdoc_CHM 2.4.0, and release gem on Rubyforge: see http://wiki.github.com/vertiginous/rdoc_chm [ ] Add a main page to the main CHM file [ ] Content about Rubyinstaller project [ ] links to pertinent Ruby sites [ ] move config stuff from recipes/tools/docs.rake to config/ruby_installer.rb [ ] Test against Ruby 1.8 and Ruby 1.9 Hopefully I''ll have this done tonight. Thanks, Gordon
Gordon Thiesfeld
2009-Aug-09 12:36 UTC
[Rubyinstaller-devel] Next Steps for the OCI Project Site
On Sat, Aug 8, 2009 at 8:05 PM, Gordon Thiesfeld<gthiesfeld at gmail.com> wrote:> On Sat, Aug 8, 2009 at 7:41 PM, Luis Lavena<luislavena at gmail.com> wrote: >> >> What is the status for CHM? Can it be merged?It''s not where I wanted it to be at this point, but my night hasn''t turned out the way I had hoped. I ended up at work all night. I''ve got rdoc_chm ready for it''s 2.4.0 release. Unfortunately, I can''t see straight, so tha''ts going to have to wait.> > Here''s my todo list for getting the rake task ready.This is where I''m at now [1] [ ] Documentation [*] Generate CHM files for Core and Standard Library (Gordon Thiesfeld) [*] Finish Rdoc_CHM 2.4.0 [2], and release gem on Rubyforge [X] Add a main page to the main CHM file [X] Content about Rubyinstaller project [X] links to pertinent Ruby sites [ ] move config stuff from recipes/tools/docs.rake to config/ruby_installer.rb [X] Test against Ruby 1.8 and Ruby 1.9 The pull requiest has been sent! The rake docs code is ugly, but it works. You''ll need to install the HTML Help library[3], then if you clone my rdoc_chm repo[4], and run rake install_gem, you should be ready to run the tasks I''ve created. I also uploaded[5] a a 1.8.6 and 1.9.1 version of the ruby documenatation so that people can look it over.> Hopefully I''ll have this done tonight. >Not quite ;-) Gordon [1]http://gist.github.com/162777 [2] http://wiki.github.com/vertiginous/rdoc_chm [3] http://msdn.microsoft.com/library/default.asp?url=/library/en-us/htmlhelp/html/hwMicrosoftHTMLHelpDownloads.asp [4] git clone git://github.com/vertiginous/rdoc_chm.git [5] http://github.com/vertiginous/rubyinstaller/download