[RWP] ReaAccess.com needs a webmaster

[Scott Chesworth]

With you all the way Indigo. There's no reason that what we've got to
work with from Ivan and the new developments can't all be in one
place, in fact considering not everyone will own hardware when their
getting started, this approach probably makes the most sense to ease
people into Reaper.

Patrick's editing post is golden, succinct and well put. It's exactly
the sort of thing that could be up there now and be gradually fleshed
out as developments happen. On other projects, I've found it easier to
summon the motivation to put guides and stuff together when I know
they're going to be linked to perminantly, guess the email list
approach isn't 100% my thing. Hopefully there'll be others that feel
the same way and we can have multiple contributors when the site gets
off the ground.

Scott


On 2/3/12, indigo <33indigo at charter.net> wrote:
> I hope you find someone who can handle the webmaster job
> Reaper with reaAccess does deserve a website of its own.
> .I think we have real breakthroughs in access from the Behringer
> BCF2000, using Klinke's VST that configures the BCF2000 to control
> Reaper, and Tim Burgess's Mackie Display Reader, which speaks the
> display of the BCF2000.
> These eventually should  give more access, even if Ivan's ReaAccess
> Version 2 never arrives.
> I have been gathering bits and pieces of info on running Reaper from
> screenreaders, as you suggest, like the excellent instructions on audio
> editing that Patrick Perdue just posted, and eventually hope to get a
> guide together.
> Reaper seems to be settling in as a viable alternative daw.
> I only wish that we could get more bits and pieces of instructions from
> skilled users, so we can  offer a coherent user's guide to beginners.
>
> Indigo L
>
>
>   On 2/2/2012 8:08 PM, Scott Chesworth wrote:
>> Hey folks,
>>
>> I've chased a few leads, waited patiently for results that haven't
>> come, twiddled my thumbs for a while and come to the conclusion that
>> waiting for ReaAccess 2.0 before making any changes to our .com site
>> makes no sense. If 2.0 ever materialises with an English translation,
>> then of course it would be welcome there, but in the meantime, we need
>> some sort of web presence. The address of the site makes sense no
>> matter what method we use to gain access to Reaper, right?
>>
>> This is essentially a call to arms to see whether there's anyone who
>> fancies being a webmaster. I'm in the middle of an album release,
>> planning a tour, and studying hard, so there aren't enough hours in
>> the day to keep up with the traffic on MidiMag to stay on top of new
>> developments and run a site. If you've already got skills, I'll shoot
>> over a few login details and you're in business. Alternatively, if
>> you're familiar with a particular environment, I can hand over the
>> server with your CMS of choice preinstalled and ready to go. Nobody is
>> expecting a rival to the huge source of info that is the Cockos forum
>> or any such miracle here, but it would be great to have even something
>> as simple as a regularly updated blog so that people can stay current
>> without needing to wade through email lists. That work in progress
>> manual from an accessibility standpoint that I know a few people are
>> contributing bits too would be valuable to have online too. When
>> you're getting started with something as huge as Reaper, any correct
>> info is surely good info, even if it's not totally finished and
>> refined.
>>
>> If you've got ideas and are willing to take on a task, let's be hearing
>> ya!
>>
>> Scott
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>