Re: [music-dsp] maintaining musicdsp.org

2012-04-06 Thread david . lowenfels
adding recaptcha to an existing site would not be too difficult, and would get 
the job done.

if you decide to overhaul... I'm partial to Rails, it's pretty awesome.
(disclosure I'm a ruby/rails developer as my day job)
there are a handful of CMS solutions for rails 3, here are two options that 
look decent... I could help customize
http://refinerycms.com/
http://www.browsercms.org/

-D

On Apr 5, 2012, at 5:57 PM, Kevin Dixon wrote:

 I would vote for a CAPTCHA... specifically recaptcha
 http://www.google.com/recaptcha/whyrecaptcha
 
 -Kevin
 
 On Thu, Apr 5, 2012 at 1:03 PM, Bastian Schnuerle
 bastian.schnue...@silberstein.de wrote:
 just did wordpress for a friend .. looks nice .. +1 ..
 
 Am 05.04.2012 um 21:50 schrieb douglas repetto:
 
 
 
 I think even Wordpress would work very well for the content on
 musicdsp.org. I agree a full drupal site seems like overkill!
 
 douglas
 
 On 4/5/12 10:05 AM, Bjorn Roche wrote:
 
 
 On Apr 5, 2012, at 4:53 AM, Ross Bencina wrote:
 
 Hey Bjorn,
 
 On 5/04/2012 1:52 AM, Bjorn Roche wrote:
 
 Any thoughts about modernizing the whole thing with a fresh CMS?
 I think it would be easier to maintain, have built-in spam
 filters, and it would be easier to have multiple people do the
 work. Plus it would look more attractive. I don't think it would
 take much effort to redo the whole thing in, say, drupal.
 
 
 Have you ever set up a Drupal site? I have. It is not for
 small-time, non-commercial, low-maintenance overhead projects
 imho.
 
 
 Yes. Quite a few.
 
 Imho it would be a huge job to port the current site to Drupal and
 there is a lot of ongoing maintenance required to keep security
 patches up to date etc etc.
 
 
 Yes. The biggest problem is security updates. You are right: major
 PITA factor. This can be mitigated by a hosted solution, or a
 multi-site install where someone is already monitoring the site for
 security updates. But, at the end of the day, that might not be
 realistic.
 
 Doing the theme port alone would be a lot of work.
 
 
 I would not dream of porting the existing theme, but rather use a
 new, or built-in theme.
 
 Unless I'm completely out of touch it is really non-trivial to set
 up something like musicdsp.org in Drupal with adequate spam
 filtering. The standard Drupal capcha solution (Mollom) is not
 great -- in my experience it flags a lot of false positives (spam
 that isn't spam).
 
 
 Mollom sucks. Captchas alone catch the vast majority of spam. The
 rest can be handled with moderation.
 
 Anyway, this is really just a vote against Drupal for musicdsp.org,
 not against using a CMS.
 
 I actually think the current ad-hoc php solution is not so bad --
 but Bram knows more about these things than me.
 
 
 Recaptcha could be added to the existing site with fairly little
 effort, but there are other advantages to a CMS: they are easier to
 team-manage, organize, and they have a number of potentially useful
 features like taxonomies (giving the ability to tag and categorize
 algos by language and purpose for example.)
 
 bjorn
 
 - Bjorn Roche http://www.xonami.com Audio
 Collaboration http://blog.bjornroche.com
 
 
 
 
 -- dupswapdrop -- the music-dsp mailing list and website:
 subscription info, FAQ, source code archive, list archive, book
 reviews, dsp links http://music.columbia.edu/cmc/music-dsp
 http://music.columbia.edu/mailman/listinfo/music-dsp
 
 
 --
 ... http://artbots.org
 .douglas.irving http://dorkbot.org
 .. http://music.columbia.edu/cmc/music-dsp
 ...repetto. http://music.columbia.edu/organism
 ... http://music.columbia.edu/~douglas
 
 --
 dupswapdrop -- the music-dsp mailing list and website:
 subscription info, FAQ, source code archive, list archive, book reviews,
 dsp links
 http://music.columbia.edu/cmc/music-dsp
 http://music.columbia.edu/mailman/listinfo/music-dsp
 
 
 --
 dupswapdrop -- the music-dsp mailing list and website:
 subscription info, FAQ, source code archive, list archive, book reviews, dsp
 links
 http://music.columbia.edu/cmc/music-dsp
 http://music.columbia.edu/mailman/listinfo/music-dsp
 --
 dupswapdrop -- the music-dsp mailing list and website:
 subscription info, FAQ, source code archive, list archive, book reviews, dsp 
 links
 http://music.columbia.edu/cmc/music-dsp
 http://music.columbia.edu/mailman/listinfo/music-dsp

--
dupswapdrop -- the music-dsp mailing list and website:
subscription info, FAQ, source code archive, list archive, book reviews, dsp 
links
http://music.columbia.edu/cmc/music-dsp
http://music.columbia.edu/mailman/listinfo/music-dsp


Re: [music-dsp] maintaining musicdsp.org

2012-04-06 Thread Bram de Jong
guys guys guys don't get ahead of yourselves! :-)

musicdsp.org is pretty simple in terms of code. Rewriting in drupal
(or similar) would take way too long and would -this is much more
important- require someone who is dedicated to musicdsp.org for the
next few years (as I myself have very little experience with Drupal,
except the nightmare that is called security updates).

I'm just looking for someone who has a bit more time than me and feels
like hacking (not coding) a few extra things like a captcha
(recaptcha?) and what not into musicdsp's current code base - which is
PHP.

And anyway, if I would rewrite it, I would rewrite it in django as I
have a vast amount of experience with django. ;-))


 - Bram

On Fri, Apr 6, 2012 at 8:12 AM,  david.lowenf...@gmail.com wrote:
 adding recaptcha to an existing site would not be too difficult, and would 
 get the job done.

 if you decide to overhaul... I'm partial to Rails, it's pretty awesome.
 (disclosure I'm a ruby/rails developer as my day job)
 there are a handful of CMS solutions for rails 3, here are two options that 
 look decent... I could help customize
 http://refinerycms.com/
 http://www.browsercms.org/

 -D

 On Apr 5, 2012, at 5:57 PM, Kevin Dixon wrote:

 I would vote for a CAPTCHA... specifically recaptcha
 http://www.google.com/recaptcha/whyrecaptcha

 -Kevin

 On Thu, Apr 5, 2012 at 1:03 PM, Bastian Schnuerle
 bastian.schnue...@silberstein.de wrote:
 just did wordpress for a friend .. looks nice .. +1 ..

 Am 05.04.2012 um 21:50 schrieb douglas repetto:



 I think even Wordpress would work very well for the content on
 musicdsp.org. I agree a full drupal site seems like overkill!

 douglas

 On 4/5/12 10:05 AM, Bjorn Roche wrote:


 On Apr 5, 2012, at 4:53 AM, Ross Bencina wrote:

 Hey Bjorn,

 On 5/04/2012 1:52 AM, Bjorn Roche wrote:

 Any thoughts about modernizing the whole thing with a fresh CMS?
 I think it would be easier to maintain, have built-in spam
 filters, and it would be easier to have multiple people do the
 work. Plus it would look more attractive. I don't think it would
 take much effort to redo the whole thing in, say, drupal.


 Have you ever set up a Drupal site? I have. It is not for
 small-time, non-commercial, low-maintenance overhead projects
 imho.


 Yes. Quite a few.

 Imho it would be a huge job to port the current site to Drupal and
 there is a lot of ongoing maintenance required to keep security
 patches up to date etc etc.


 Yes. The biggest problem is security updates. You are right: major
 PITA factor. This can be mitigated by a hosted solution, or a
 multi-site install where someone is already monitoring the site for
 security updates. But, at the end of the day, that might not be
 realistic.

 Doing the theme port alone would be a lot of work.


 I would not dream of porting the existing theme, but rather use a
 new, or built-in theme.

 Unless I'm completely out of touch it is really non-trivial to set
 up something like musicdsp.org in Drupal with adequate spam
 filtering. The standard Drupal capcha solution (Mollom) is not
 great -- in my experience it flags a lot of false positives (spam
 that isn't spam).


 Mollom sucks. Captchas alone catch the vast majority of spam. The
 rest can be handled with moderation.

 Anyway, this is really just a vote against Drupal for musicdsp.org,
 not against using a CMS.

 I actually think the current ad-hoc php solution is not so bad --
 but Bram knows more about these things than me.


 Recaptcha could be added to the existing site with fairly little
 effort, but there are other advantages to a CMS: they are easier to
 team-manage, organize, and they have a number of potentially useful
 features like taxonomies (giving the ability to tag and categorize
 algos by language and purpose for example.)

 bjorn

 - Bjorn Roche http://www.xonami.com Audio
 Collaboration http://blog.bjornroche.com




 -- dupswapdrop -- the music-dsp mailing list and website:
 subscription info, FAQ, source code archive, list archive, book
 reviews, dsp links http://music.columbia.edu/cmc/music-dsp
 http://music.columbia.edu/mailman/listinfo/music-dsp


 --
 ... http://artbots.org
 .douglas.irving http://dorkbot.org
 .. http://music.columbia.edu/cmc/music-dsp
 ...repetto. http://music.columbia.edu/organism
 ... http://music.columbia.edu/~douglas

 --
 dupswapdrop -- the music-dsp mailing list and website:
 subscription info, FAQ, source code archive, list archive, book reviews,
 dsp links
 http://music.columbia.edu/cmc/music-dsp
 http://music.columbia.edu/mailman/listinfo/music-dsp


 --
 dupswapdrop -- the music-dsp mailing list and website:
 subscription info, FAQ, source code archive, list archive, book reviews, dsp
 links
 http://music.columbia.edu/cmc/music-dsp
 http://music.columbia.edu/mailman/listinfo/music-dsp