[RWP] ok people, lets fix the reaaccess site

Tue Dec 21 21:55:29 EST 2010

Well, lets get back to basics.
This mailing list covers the forum aspect, for the exchanging of 
projects/presets etc. an ftp site somewhere would cover that.
All tha really need be done is to have a site which summerizes the purpose 
of the program, gives links, and some getting started tips.
Quick, simple, and... now that i think about it, what the site was when the 
project first got off the ground.
----- Original Message ----- 
From: "Scott Chesworth" <scottchesworth at gmail.com>
To: "Reapers Without Peepers" <rwp at reaaccess.com>
Sent: Tuesday, December 21, 2010 9:25 PM
Subject: Re: [RWP] ok people, lets fix the reaaccess site


> Hi chaps,
>
> I own the ReaAccess.com domain and hosting, and am holding my hands up
> looking pretty guilty as I write this. There was talk of a wiki-based
> system here a while ago if you recall? I thought that a sensible move
> would be to make the domain a forum because:
> A) It's easier to post knowledge to that than to a wiki, so after a
> while people could just cherry-pick the best topics and make them
> sticky.
> B) it would encourage a sense of comunity between users, perhaps more
> sharing of example projects/templates/whatever.
> C) Most of the action happens in the forum at reaper.fm, it seemed
> right that we should fall in line with that model.
>
> Having thrown BBPress onto the domain, I moved job/house/had some huge
> real life changes to grapple with which totally got in the way of
> finishing up, and as Brian rightly says, it's slipped further and
> further down the things to do list. Before reading this thread, it was
> buried in the cluttered corner of doom I reserve for avoidance. This,
> obviously, is not good enough.
>
> I checked the domain today and was incredulous at the amount of spam
> that has been racking up in my absence, in spite of several anti-spam
> measures being installed. After a bit of research into BBPress, it
> would seem that it too is at something of a standstill, so as neat and
> stripped down as it is, it probably isn't the right basket to put our
> eggs in.
>
> So, this is a call to arms. Do we have amongst us a techie type who
> can get the framework in place? Personally, I'm still taken with the
> idea of a forum, but anything is preferable to what's there now. I'd
> do this myself, but real life is still far too hectic. I can and hope
> always to be able to meet the other commitments I've made to the
> ReaAccess developer, but they are my strong suit, hence they take far
> less time than the webbie stuff in which I'm a bit of a newbie, all be
> it a keen one.
> Hosting-wise the payments are taken care of, you'd have 5 MySQL
> databases to play with, PHP, Apache2, could probably get shell access
> if I request it, and more bandwidth per month than you could shake a
> stick at. Appreciation-wise you'd have a comunity of 50 upward mailing
> list members, which means somewhere between 5-10 actual contributors
> if previous projects are anything to go by.
>
> As an insentive to get things off the ground, I can tell you that
> Ivan, the dude that makes all this happen is very close to a new
> release. We've got good stuff happening with sends/receives/the master
> track amongst other perks such as multiple and non-contiguous
> track/item selection. It's a round off the edges type release, but I
> think you're all going to like it. It would be super awesome if we
> could get some momentum back as a comunity and keep Ivan enthused,
> because once he gets going he works like a demon.
>
> Any takers? Feel free to email on or off list, the choice is yours.
>
> Thanks much, and sorry once again for falling so far behind with the
> state of the domain. I assure you that I haven't been sitting on a
> beach sipping cocktails.
>
> Scott
>
> On 12/22/10, Derek Lane <derek at pdaudio.net> wrote:
>> I'd be willing to help in  any way, if it let the reaaccess team spend 
>> more
>> time
>> developing
>>
>>   ----- Original Message -----
>>   From: Bryan Smart
>>   To: Reapers Without Peepers
>>   Sent: Tuesday, December 21, 2010 6:04 PM
>>   Subject: Re: [RWP] ok people, lets fix the reaaccess site
>>
>>
>>   Right now, the site is a Wordpress. That's fine if a single person 
>> wants
>> to maintain the entire site. It isn't as easy for a team of people to
>> collaborate on a Wordpress site, though. The best that you can do is to 
>> add
>> several people as authors, and give them permission to post articles in
>> certain areas of the site. They can't update any of the site structure, 
>> or
>> perform any other large scale edits.
>>
>>
>>
>>   It's obvious that the ReaAccess people don't have the time to work on 
>> the
>> site. They can either let the site be another obligation that they can't
>> meet, dragging them down, or they can deligate part of the work to others 
>> in
>> the community. In the first case, the site will only be updated 
>> irregularly
>> and in spirts, if ever, and it will be harder to attract new users to 
>> your
>> project. If the second, then you need to put a system in place for
>> deligating the tech writing projects.
>>
>>
>>
>>   If you have the time to rearchitect, then it would be better to create 
>> a
>> site based on Drupal or Joomla. That would give you lots of options for
>> passing out responsibility of different areas of the site to different
>> people. You can, for example, create authors that can only write in their
>> assigned section. However, you can also create users to serve as editors.
>> Editors would be trusted users that can write or edit in multiple 
>> sections.
>> They'd take most of the editing/approval/site admin tasks off of you, 
>> while
>> not being able to edit the core functionality of the site.
>>
>>
>>
>>   If you don't have time for any of that, then, at minimum, you need to
>> create some users on your Wordpress site as editors, Give them assigned
>> sections, such as FAQ, getting started documents, etc, and add widgets to
>> the sidebar and archive references in the main body of the page that 
>> would
>> display content that has been created in their sections.
>>
>>
>>
>>   Anyway, unless you're making lots of money, you can't come up with
>> resources to do it all internally. You either must learn to spread the 
>> work
>> around, properly supervised, or get buried under the mounting to-do list.
>>
>>
>>
>>   Bryan
>>
>>
>>
>>   From: rwp-bounces at reaaccess.com [mailto:rwp-bounces at reaaccess.com] On
>> Behalf Of Derek Lane
>>   Sent: Tuesday, December 21, 2010 4:36 PM
>>   To: Reapers Without Peepers
>>   Subject: [RWP] ok people, lets fix the reaaccess site
>>
>>
>>
>>   The developers of rea access are some amazing people.  Their work is
>> solid, and, at least for me, itlets me be very productive in tasks from
>> tracking/mixing to mastering/restoration.
>>
>>   The problem is, the reaaccess site is  broken.  So it keeps the 
>> community
>> from growing due to the fact that the actual project isn't available as a
>> link, anywhere on the site.
>>
>>   If someone could  fix reaaccess.info, I'd appreciate it.
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>>   _______________________________________________
>>   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
>