On Thu, Oct 1, 2015 at 4:21 PM, Marvin Humphrey <[email protected]> wrote: > On Thu, Oct 1, 2015 at 11:02 AM, Sam Ruby <[email protected]> wrote: > >> Lets see if we can meet each other half way, and then circle back to >> updating the site. > > Well, what does it mean to meet half way?
You want instructions on the site. I've provided instructions that don't work for you. Moving those instructions to the site won't help. I think getting instructions that work should be done before they are posted. Getting feedback on the instructions is what I am seeking. >> For starters, whimsy is not monolithic, and different tools are at >> different places. > > OK -- so I should be able to then create a reminders tool which is independent > from everything else in whimsy and doesn't have any dependencies outside the > Ruby standard library... right? No. Every language these days has package managers which will help with dependencies. Think CPAN, PEAR, pip, maven, npm, etc. For Ruby, it is gem. >> Next, there are steps between step 1 and 2 above. Every tool will >> need a data source, typically svn or LDAP. The svn files will need to >> be checked out, and you may already have done so; if so you will need >> to tell the tool where to find the checkout (different people >> understandably have different conventions). For LDAP, you will need >> to configure your machine somewhat. > > Extra version control checkouts are acceptable, because I and other potential > contributors already grok those tools. > > Also possibly acceptable: multiple version control checkouts/clones, followed > by a shell script which sets up environment variables. > > svn co [...] whimsy > cd whimsy > source bin/setup_env.sh > >> I've put together some places to get started (in preferred order): >> >> https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/README >> >> https://github.com/rubys/whimsy-agenda#readme >> >> https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/www/test/roster >> >> If I can get people to try them (in order), indicate how far they got >> on their own, what changes they feel are needed (feel free to directly >> commit them and/or submit a pull request), and where they got stuck, >> I'll try to help. > > I'm "stuck" at `gem install whimsy-asf`. Ruby comes with my operating system. > I don't want to mess with the system installation, which meeds that I need to > research how to persuade the `gem` tool to install into an arbitrary lib > directory, then modify some environment var so that ruby knows about the > custom lib directory, etc. That's useful information. I could talk you through rvm or rbenv, which will allow you to manage separate installations of ruby and associated gems. But they will still require you to install something. But if you want complete isolation, I would suggest a docker image or a vagrant VM. This will take care of setting up everything, and not affect your system install. Given this requirement, can I suggest that you start with the *second* link in my original list, namely https://github.com/rubys/whimsy-agenda#readme ? > I, and other potential contributors, can surely figure all this out in due > time -- but I don't think we should have to. And I feel as though if I > compromise with you now, guzzle the kool-aid and spend N hours tricking out my > system, that my point about all these dependencies posing a barrier to entry > will be lost. > > Marvin Humphrey - Sam Ruby
