Hello,
I am a bit at a loss :) Really I don't see how we can promote a camping
with screencast and examples e.g. even a blog example when we are then
essentially saying that it would be pointless anyway for camping to code a
blog as there is tumblr (or you name it, wordpress, blogger etc.).  Isn't
the point of coding/camping to experiment, let the imagination run wild
while building something cool (not just a blog of course) ?

I don't think that a totally static website is necessarily a good thing. It
is very limiting and creates a single way to dialogue with existing/future
users which can be done in a number of ways even without the forum (e.g.
fetching displaying the mailing list, allow comments on certain topics, Q&A
etc.). Sure you can do that with tumblr and pretty well but in my humble
opinion that's not the best way to promote the framework.

But hey what do I know ? I just finished reading "Running Sinatra" and they
do the very same thing in their sample blog (last chapter). They tell you
how to create a sinatra app where you do not have an online editor and all
it does it to create  static HTML files. I thought WOW why would I go and
install, learn the sinatra way if this is the display of what I can do with
it ?   Nothing wrong with static html. I have a blog with static files too
(but hey at least I have disqus comments embedded on each files so there is
a way to communicate with users + rsync and other stuff ) and you know..it
is 15 lines of bash code. It does exactly the same of that Sinatra app from
the book without having to run or install anything.

So I really don't get it I think !

Will see how I can progress with the screencasts but making them to display
them on a tumblr blog is not exactly very motivating. Perhaps I got caught
by the enthusiasm too quickly - my bad!
Best Wishes
David


On Thu, Mar 29, 2012 at 12:55 AM, Jenna Fox <a...@creativepony.com> wrote:

>  I just don't see the point in creating our own elaborate infrastructure
> which we then have to maintain indefinitely, which is more complicated than
> static files. Our site is static html right now because there's nothing
> about the site which is dynamic - but those static files were rendered by a
> camping app which I just mirrored to static files recently using wget so we
> could switch things over to github pages. Unless there's going to be some
> dynamic element to the camping site, I'd rather the stability and
> scalability afforded to us by github pages and static files than some token
> ritual of dogfooding. Both the sites of Ruby on Rails and Sinatra seem to
> use caching servers between their users and ruby backends, with sinatra's
> in particular caching responses for many hours. I think we're winning the
> ruby race - our cache caches for days, even weeks! It's a really smart
> cache.
>
> As for forums, I'm interested, and I agree it would be best done as a
> camping app, if for no better reason that there isn't really any good free
> forum software still being maintained which runs on ruby, as far as I know.
> For our blog though, tumblr is great. It's had very little downtime in
> recent weeks. I think it's worth forgiving them - their user base became
> something like ten times as big in the space of one day, after their
> collaboration with the The Colbert Report - for a site which takes photo,
> music, and video uploads, that's a pretty substantial change. They seem to
> have sorted it out now, only having very minor blips from time to time.
> Further, tumblr is based on the tumblog concept, which was pioneered *and
> named* by none other than our former friend Why The Lucky Stiff, and
> itself does run on our close relative, Ruby On Rails. In fact, a large
> proportion of GitHub is a Rails app too.
>
> —
> Jenna
>
> On Thursday, 29 March 2012 at 6:29 AM, david costa wrote:
>
> Hi Jenna this is great !
> let's see how the screencasts come along then you can see. Just one point
> about tumblr (which is good don't get me wrong) wouldn't it be better to
> have a small site on camping ? I am pretty excited to build this in camping
> and show the screencasts inside it. Of course will need to show code not
> nice words only ;) but this should be the final aim.
>
> I am not asking anyone to do it/code it etc. I am just saying this should
> be the ultimate goal because with no camping code in production people
> might think this is just a quick hack just for the fun of it with not much
> of a real use beside a proof of concept... which is a bit of a pity.
>
> Like there are hundreds of frameworks on git, google code etc. but how
> many can be bothered to try them out without having some working samples or
> a good site (and I really like your design !!) to show how is this working ?
>
> For example there is some activity in the mailing list so it could be
> something nice to show on the website (like this topic at
> http://comments.gmane.org/gmane.comp.lang.ruby.camping.general/1648) but
> of course within the site and not an external link.  This could be enough
> while there is no forum etc.
>
> On another note tumblr is not exactly very stable !
>
> *this said* I totally see your point as you have this functionality
> already on tumblr so if one wants to be up and quickly with something it is
> certainly better than any bigger but uncoded masterplan :)
>
> Regards
> David
>
>
>
> On Wed, Mar 28, 2012 at 3:52 PM, Jenna Fox <a...@creativepony.com> wrote:
>
> We have a tumblr blog - maybe we should turn on the 'ask' feature and make
> it a Q and A thing. It would grow in to a google friendly fact book, a bit
> like a stack exchange, for looking up specific problems and techniques.
> Tumblr is a nice medium for adding photos and screencasts and the likes
> too.
>
> —
> Jenna Fox
>
> On Thursday, 29 March 2012 at 12:22 AM, Paul van Tilburg wrote:
>
> On Wed, Mar 28, 2012 at 06:57:51AM -0600, Philippe Monnet wrote:
>
> I think it would be fun too. Love meta stuff.
> In general I think the more tutorials / screencasts / posts / sites
> on Camping, the merrier.
>
>
> Although I generally agree, I'd prefer them to be somewhat
> organised/structured. For example, the blog is a good basic app,
> but I would like to have tutorials for specific things such as:
> adding cookies, sessions, using different view/template systems,
> integrating multiple apps, etc. Rather than having a screencast of a
> "wiki" app that happens to mention sessions.
>
> In my opinion the Camping site should answer questions/help out
> with different aspects of creating/extending/maintaining a Camping
> application. This is something that currently requires joining
> #camping on IRC, asking the question and waiting for a long time.
> (Not there that is anything whatsover wrong with our IRC-channel. :)
>
> Cheers,
> Paul
>
> _______________________________________________
> Camping-list mailing list
> Camping-list@rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
>
>
> --
> Web: http://paul.luon.net/home/ | E-mail: p...@luon.net
> Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181
> _______________________________________________
> Camping-list mailing list
> Camping-list@rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
>
>
> _______________________________________________
> Camping-list mailing list
> Camping-list@rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
>
> _______________________________________________
> Camping-list mailing list
> Camping-list@rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
>
>
> _______________________________________________
> Camping-list mailing list
> Camping-list@rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
_______________________________________________
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list

Reply via email to