I think your first paragraph shows the crux of the problem and hints a direction to follow: there is no urgent need to move Rivet out of ASF because Tcl is not a buzzword in the open source community and it's unlikely to become so just because gets labeled with 'fork me on github'. We could probably move out with Rivet (and your arguments are quite strong for it) if we had something to lay on Rivet itself that might attract Tcl'ers who are now drawing on more popular languages when it comes to web programming. And web programming is ubiquitous because web technology comes handy in many different scopes and I'm certain many Tcl'ers go to PHP, Java or Rails for building websites even when they don't need all the power of those long established tools and don't have strong branding requirements (yes, people like to see those shiny words on what they paid for)
Maybe it's time we throw into the arena what we have done in these years, let it be torn into pieces, criticized and reassembled in something that might look attractive at least for those who have already a penchant for Tcl. If you allow a few more weeks I will start myself presenting what I've been doing in the last 2 years with Rivet and what I did with it. Don't expect anything perfect, but I made with it quite a few websites for various purposes -- Massimo On 12/18/2014 06:05 PM, Damon Courtney wrote: > Tcl is not a popular language. It’s not GOING to be a popular > language. Nothing we do in Rivet will change that. Although, Rails > made Ruby popular, so who knows. I don’t care. I use what I like and > will continue to do so. > > The point was simply that the open source world is much more vibrant > in places NOT ruled by bureaucracy. No, we’re not going to get a herd > of programmers take a look at Rivet by going somewhere else, but > having everyone jump through stupid hoops to even try can’t help. > I’ll admit that this is purely self-serving on my part. I don’t want > to have to jump through the stupid hoops either. Not when I can just > grab any project off Github that I want and start working in > minutes. > > I suppose the Apache project lends some credibility (for some), but I > don’t see it much these days. Any project that wants to attract > attention now lives on Github. Do we really want to keep voting and > submitting quarterly updates about how nothing is really happening? > Or getting chastised for not sending said reports? > > Also, holy shit, are we still f*cking using Subversion?! This makes > the whole Apache Project look like asshats. Ridiculous. > > D > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
