Hi everyone, Is there any easy way to convert from Typo to WP, either directly or via some XML format or something? I've noticed several blogs migrating away from Typo, and I was just wondering if there's an automated process for it... Thanks, Mike
on 15.06.2006 13:33
on 15.06.2006 13:45
Mike Purvis a écrit : > Hi everyone, > > Is there any easy way to convert from Typo to WP, either directly or > via some XML format or something? I've noticed several blogs migrating > away from Typo, and I was just wondering if there's an automated > process for it... > > Thanks, > > Mike Hello Mike, Wordpress offers import from several blog engines, and from RSS feed. There also might exist an import script somewhere. After all, there IS an import script to switch from Wordpress to Typo, the one I used when I moved to Typo. I'll add some thoughts about why people shall switch from Typo to Wordpress, in other words what normal (non geek) people may think Typo lacks. - A decent antispam. Wordpress has a really powerful one, easy to install, and really tough to pass through (never happened to me) - Lots of themes and plugins, with dedicated sites. - A support forum with an active community to answer your questions. - A riche text editor (TinyMCE) - A very nice text filter engine that displays posts the way they're typoed (with line breaks and paragraphes without using html). - A lot of things you need to manually do with Typo. I do think the 3 first are what Typo really lacks. Cheers, Frederic -- Frédéric de Villamil "Quand tu veux chasser une belle fille, il vaut mieux commencer par draguer sa copine moche" -- conseil de go. http://t37.net http://fredericdevillamil.com neuro@7el.net tel: +33 (0)6 62 19 1337
on 15.06.2006 13:45
On 15 Jun 2006, at 12:31, Mike Purvis wrote: > Is there any easy way to convert from Typo to WP, either directly or > via some XML format or something? I've noticed several blogs migrating > away from Typo, and I was just wondering if there's an automated > process for it... If you have only a few posts then you could use the RSS importer that Wordpress has. Otherwise no. Not that it's difficult ... just somebody hasn't wrote the script yet. Unless it's a secret I haven't come across ;) Gary
on 15.06.2006 14:18
Okay, thanks. I have about 200 posts, plus a whackload of comments. I'll write my importer in php and then share it if it's clean enough. As for reasons, it's not particularly anything you listed, but rather, 1. Typo development has all but ceased, and my current version (1055) has several glaring bugs surrounding publishing. The biggest of these is that re-saving a draft sends an article live--a completely absurd behaviour. 2. I can't afford the time and money required to run a dedicated server. I hate to be snide about it, but after checking around a number of forums, I can't find a single shared hosting environment where people are reliably running Typo and not having problems with load or 500s or fastcgi or whatever. Wordpress has that whole Just Works factor, and as much as I've learned about Rails, I know a good deal more about hacking PHP. Mike
on 15.06.2006 15:07
On 6/15/06, Mike Purvis <mike@uwmike.com> wrote: > Okay, thanks. > > I have about 200 posts, plus a whackload of comments. I'll write my > importer in php and then share it if it's clean enough. Hi Mike, Please consider sharing it even if it's not clean. Chances are that someone will still find it pretty useful and might even clean it up for you. :) This thread came up with spooky timing for me, considering that I was right in the middle of trying to figure out how to migrate my posts over from typo to wordpress myself. I did go with the RSS importer (set to 1000 posts in the RSS feed), and modified my WP permalink URLs to include the '/archive/' part. It seemed to work surprisingly well, except that some of the pubDates in the feed seem to have been parsed wrong, resulting in the occasional permalink that off by a day. I'm in the process of fixing them by hand now in MySQL. I figured I would just write a quickie ruby + active_record script to bring the comments in later on. I guess one advantage of using using the RSS importer is that you don't have to deal with textile or markdown - it just imports straight html. -Pawel
on 15.06.2006 15:29
Typo is loosing some users with its strange devel process. I explain... few guy are doing a really good job on typo dev, but everything (but nothing) is on the trac, releasing patches (yes we can look at the source, I know) but nobody wants to go ahead with a typosphere announcing a "coming soon" message for several month now, a dead typogarden project! Some people don't want to hear it but perhaps the good thing to do is to create a REALLY ATTRACTIVE wiki with details on installing, configuring typo, and themes... and some info on programming stuff (API, classes,etc...) Typo helped me to discover RoR and I'm addicted but sometimes people need to see sparkling things to discover the real beauty! Regards
on 15.06.2006 15:32
cedric a écrit : > and some info on programming stuff (API, classes,etc...) > > Typo helped me to discover RoR and I'm addicted but sometimes people need > to see sparkling things to discover the real beauty! > > Regards > > Just install a support forum first. And have people to answer questions. And a page listing resources at first. And then code :) -- Frédéric de Villamil "Quand tu veux chasser une belle fille, il vaut mieux commencer par draguer sa copine moche" -- conseil de go. http://t37.net http://fredericdevillamil.com neuro@7el.net tel: +33 (0)6 62 19 1337
on 15.06.2006 16:07
On 15 Jun 2006, at 14:30, Frédéric de Villamil wrote: > > Just install a support forum first. And have people to answer > questions. > And a page listing resources at first. > www.typoforums.org fits that bill. G
on 15.06.2006 16:10
On Jun 15, 2006, at 7:03 AM, Gary Shewan wrote: > On 15 Jun 2006, at 14:30, Frédéric de Villamil wrote: >> Just install a support forum first. And have people to answer >> questions. >> And a page listing resources at first. > > www.typoforums.org fits that bill. Maybe it should be linked from the typosphere.org homepage. -- Josh Susser http://blog.hasmanythrough.com
on 15.06.2006 16:10
Gary Shewan a écrit : > On 15 Jun 2006, at 14:30, Frédéric de Villamil wrote: >> Just install a support forum first. And have people to answer >> questions. >> And a page listing resources at first. >> > > www.typoforums.org fits that bill. > Too bad there's no link on typosphere.org homepage... -- Frédéric de Villamil "Quand tu veux chasser une belle fille, il vaut mieux commencer par draguer sa copine moche" -- conseil de go. http://t37.net http://fredericdevillamil.com neuro@7el.net tel: +33 (0)6 62 19 1337
on 15.06.2006 16:23
Gary you're true, but many of tips discovered by typo users just stay on this mailing-list, and nobody seems to be attracted to put something on this forum (I don't know why!) A look to wordpress.org can give some clues (on the first page there's a link to almost everything!) Yes I am a bit focused on WP (even if I don't use it) but it was a little project that has grown because it was accessible. And I'm sure that typo is also a very good project for many people interested in ruby, rails, cms, etc... the comparison could be like Debian & Ubuntu, same roots but Ubuntu looks pretty!
on 15.06.2006 17:07
On 15 Jun 2006, at 15:20, cedric wrote: > Gary you're true, but many of tips discovered by typo users just > stay on > this mailing-list, and nobody seems to be attracted to put > something on > this forum (I don't know why!) Josh, Frédéric and yourself are certainly right. I wondered whether the lack of use of the Typo forums was because it wasn't well known or whether there wasn't a need for it ... probably more of the former I guess now. I'd say people are just too busy to put a info in Trac ... which leans more towards development sometimes. I should really write up what I've learned and put it there though... What would be the main things that people want to see covered ... just for the record? G
on 15.06.2006 17:20
Gary Shewan a écrit : > or whether there wasn't a need for it ... probably more of the former > I guess now. > > I'd say people are just too busy to put a info in Trac ... which > leans more towards development sometimes. I should really write up > what I've learned and put it there though... > > What would be the main things that people want to see covered ... > just for the record? > > G I might be stupid, but I don't see why Typo support forum is not on the same domain as the sources, the track or on a subdomain ? I mean, having : http://support.typosphere.org http://themes.typosphere.org http://plugins.typosphere.org with propoer links from everywhere to everywhere would have much more sense IMHO. 1/ people would find things much more easily 2/ typo and everything related would get a better google ranking 3/ it's just sounds logical to do this way, isn't it ? I know every open source project has its good and bad times, but I fear typo is really dying, and it's a pity, because it's a good project that should be really amazing. -- Frédéric de Villamil "Quand tu veux chasser une belle fille, il vaut mieux commencer par draguer sa copine moche" -- conseil de go. http://t37.net http://fredericdevillamil.com neuro@7el.net tel: +33 (0)6 62 19 1337
on 15.06.2006 18:02
On 15 Jun 2006, at 16:18, Frédéric de Villamil wrote: > > I might be stupid, but I don't see why Typo support forum is not on > the > same domain as the sources, the track or on a subdomain ? The simplest answer is that Typoforum.org is run by different people to Typosphere. > I know every open source project has its good and bad times, but I > fear > typo is really dying, and it's a pity, because it's a good project > that > should be really amazing. I wouldn't say it's dying. Just that there hasn't been a changeset for a while. But there was only really Piers working on it and he's probably tied up with real life work. Scott was working on the 4.0 release but again is probably tied up with other Rails work. Don't judge it as you would a PHP project - because there aren't that many rails coders that have tonnes of time for open source. It'll get moving again. It's just a pause. G
on 15.06.2006 18:57
Gary Shewan a écrit : >> typo is really dying, and it's a pity, because it's a good project > It'll get moving again. It's just a pause. > > G I know this, I'm doing rails myself, and I don't have time to code my own stuffs so... that's why I was talking about good and bad times. People have been doing great work on Typo, and I'm really glad with this. -- Frédéric de Villamil "Quand tu veux chasser une belle fille, il vaut mieux commencer par draguer sa copine moche" -- conseil de go. http://t37.net http://fredericdevillamil.com neuro@7el.net tel: +33 (0)6 62 19 1337
on 15.06.2006 19:00
I would think that it should be pretty natural simply to set up a Typo installation at http://www.typosphere.org and have recent changes blog there or something. On 6/15/06, cedric <cedric@feelfree.homelinux.com> wrote: > and some info on programming stuff (API, classes,etc...) > Typo-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/typo-list > --
on 15.06.2006 19:03
On 6/15/06, Gary Shewan <gpsnospam@gmail.com> wrote: > > I know every open source project has its good and bad times, but I > rails coders that have tonnes of time for open source. > > It'll get moving again. It's just a pause. > > G > _______________________________________________ > Typo-list mailing list > Typo-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/typo-list > If someone could just get something stable enough to release as a 4.0 release candidate, so people have some to track beyond SVN revisions, it would make a big difference. Also, the lack of proper trackback/pingback support when its near a 4.0 version needs to fixed, priority #1. Thats just essential blog functionality and really needs to be there. - rob -- http://www.robsanheim.com http://www.seekingalpha.com http://www.ajaxian.com
on 15.06.2006 19:16
On Thu, 15 Jun 2006 11:50:52 -0500, "Rob Sanheim" <rsanheim@gmail.com> wrote: >> _______________________________________________ >> Typo-list mailing list >> Typo-list@rubyforge.org >> http://rubyforge.org/mailman/listinfo/typo-list >> > > If someone could just get something stable enough to release as a 4.0 > release candidate, so people have some to track beyond SVN revisions, > it would make a big difference. Bingo -- I have two Typo sites that I run right now, externally they look/work great, but internally both have issues that I haven't been able to solved. One site can't add/edit 'Pages' at all (Application Error (Rails) while my site displays that problem on *some* pages, but then late last week all of a sudden I couldn't post! Svn update doesn't help so I'm just in a lurch while I think of what to do. If we had 4.0 we would have a fresh slate to build on, and trust me, if I got my sites up on 4.0, they'd stay there for a time; I really love the blog Typo has allowed me to create, but lately it's just been too much work to keep running. </rant> I really do appreciate all the efforts, this is a great system, I just would like to have it 'just work' for a longer period of time. P > > Also, the lack of proper trackback/pingback support when its near a > 4.0 version needs to fixed, priority #1. Thats just essential blog > functionality and really needs to be there. > > - rob > -- http://fak3r.com - you don't have to kick it
on 15.06.2006 19:19
phil a écrit : >>> > Bingo -- I have two Typo sites that I run right now, externally they look/work great, but internally both have issues that I haven't been able to solved. One site can't add/edit 'Pages' at all (Application Error (Rails) while my site displays that problem on *some* pages, but then late last week all of a sudden I couldn't post! Svn update doesn't help so I'm just in a lurch while I think of what to do. If we had 4.0 we would have a fresh slate to build on, and trust me, if I got my sites up on 4.0, they'd stay there for a time; I really love the blog Typo has allowed me to create, but lately it's just been too much work to keep running. >> functionality and really needs to be there. >> >> - rob >> I also think text filters simply dont work. -- Frédéric de Villamil "Quand tu veux chasser une belle fille, il vaut mieux commencer par draguer sa copine moche" -- conseil de go. http://t37.net http://fredericdevillamil.com neuro@7el.net tel: +33 (0)6 62 19 1337
on 15.06.2006 21:47
I was originally attracted to Typo because it was lean ... supermodel lean and it was built to work with a blog editor. Perfect in my book. No backend bloat. It also used Rails which was an interesting framework to learn. It's still only around a year old though and to be honest it's not the best thing since sliced bread and I don't understand that opinion. It does exactly the same as every other blog system - in fact it's a lot less stable and I'd count something like Textpattern far more superior. If you want something stable with lots of lovely looking themes then Typo isn't the best choice. It's probably a good idea to look elsewhere. Typo was originally written while waiting for a meeting to start and less than a handful of developers have got it to where it is at the moment. You can't compare that history against some of the other more established engines. I use it to play with Rails. I know it's unstable sometimes and I accept that because I live on trunk for Typo and Rails. Hmmm ... that's probably the worst attitude to have because I have a few thousand posts to my blog. 4.0 was only waiting for a better installation process from Scott. There's not going to be anything very different from trunk in a point release (unless I'm very mistaken). A lot of the problems can be attributed to host set-ups and the Rails version you are working from. I don't have very high expectations for 4.0 solving every problem ... I think some people do though. There might be disappointment. Having thought about it though ... typosphere is becoming a real joke as a frontend to the Typo world. Mebbe some more time should be spent hanging around typoforum... Gary
on 15.06.2006 22:40
Gary Shewan wrote: > I was originally attracted to Typo because it was lean ... supermodel > lean and it was built to work with a blog editor. I was originally attracted to Typo because it wasn't written in PHP. I'm still open to alternatives, as long as they're not written in PHP. mathew
on 15.06.2006 23:08
> I'm still open to alternatives, as long as they're not written in PHP.
Same here. Actually, I liked Typo because of Tobi's attitude towards
development, and the idea that something cool can come out of, what,
500 lines of code. It was what I wanted, and it worked. It still
works, somehow, but the community around it seems to falter a little
bit. I've never been one to use the flavor of the month, and if you
know me, switching to Typo from being "Employee Number One" of the
never really existing Wordpress Foundation, was a huge step. I don't
think Typo is doomed, but at this point it might be a good idea to
re-rally the community (Rails and Ruby are the hype, right now, and
Typo is one of that hype's flagships), work on expanding upon the
leanness, and make things a bit more conducive and accessible.
A theme garden works, but Drupal, for example, sucks when it comes to
themes, and still has a great following. A development community that
can communicate outside a mailing list, a repository of plugins,
filters, and themes, that I don't have to extract from Trac tickets
would be great, for example, however. Typo has a future, it just needs
a steward and a vessel to get there.
on 15.06.2006 23:27
Maybe the Typo community should look at supporting Rick's Mephisto blogging engine. Closer to the original Typo concept and it includes a converter for Typo blogs... http://svn.techno-weenie.net/projects/mephisto/trunk/
on 16.06.2006 00:13
Steve Longdo wrote: > Maybe the Typo community should look at supporting Rick's Mephisto > blogging engine. Closer to the original Typo concept and it includes > a converter for Typo blogs... > > http://svn.techno-weenie.net/projects/mephisto/trunk/ Wow, it has even less documentation than Typo! mathew
on 16.06.2006 00:39
> would be great, for example, however. Typo has a future, it just needs > a steward and a vessel to get there. Surely this is the problem -- we've lost our stewards! Piers and Scott are busy with work, and that's left Typo head-less. The consensus on this thread seems to be that we need to kickstart the community; the way to do that is to find out who owns/runs typosphere.org, and convince them to give two or three trusted long-time members of the community admin access. As far as documentation goes, the Trac on typosphere.org should be opened up to contributions from the community. I know that's effectively what typoforums.org offers, but wikis are more intuitive to navigate (and IMHO, putting documentation/howtos on threaded forums is equivalent to burying it). Uzair
on 16.06.2006 01:17
Exactly -- this is a great opportunity to make the existing community stronger which will then enable the community to grow. I'm going to start working on organizing the themes on Friday evening as I laid out in my message last night. Phil has been kind enough to share with me what he has already collected. I'll send updates to the list as I make progress. Tim Syed Uzair Aqeel wrote: > community admin access. > Typo-list mailing list > Typo-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/typo-list -- Timothy Freund http://digital-achievement.com http://edodyssey.com
on 16.06.2006 01:17
I agree with that idea. The Typo community should eat its own dog food and run an instance on typosphere.org. Give accounts to a few active individuals and let them post not just about Typo, but about the competition as well. That way we spread the responsibility out over several busy individuals rather than one busy individual, and by writing about innovations across the blogging community and not just within Typo we will better see how Typo stacks up against other offerings. Tim Jon Gretar Borgthorsson wrote: >>I know) but nobody wants to go ahead with a typosphere announcing a >>Regards > -- Timothy Freund http://digital-achievement.com http://edodyssey.com
on 16.06.2006 04:05
And did not work well after following the four lines of instructions. *sigh* I just want the RSS sidebar to work again.
on 16.06.2006 04:55
Well... You just have to find a revision before everything went bad and use that one. On 6/16/06, Ernie Oporto <ernieoporto@gmail.com> wrote: > > > > > > > --
on 16.06.2006 06:08
I think Typo's health has been in jeopardy for a long time. If you go through the last 50 or so changesets most are "new" functionality and very few address bugs or even community offered patches on Trac. Letting contributions languish on Trac uncommitted or even just left open permanently with no comment is not the sign of a healthy open source project. I agree that the unchanging landing page at typosphere.org for the last few months is sad. Since Planet Argon is now the official host of Typo, it would be nice if Robby Russel or some of the other capable folks at Planet Argon were added to Typo as commiters. It would seem that they should have a vested interest in its success.
on 16.06.2006 08:26
On 16/06/06, Jon Gretar Borgthorsson <jon.borgthorsson@gmail.com> wrote: > Well... You just have to find a revision before everything went bad > and use that one. Can anyone suggest one? Some of us are still on 2.6.0, and it's hard to help fix bugs when you can't test them.
on 16.06.2006 09:52
Myself I'm just using the latest trunk without problems. Not very stable though. On 6/16/06, Dick Davies <rasputnik@gmail.com> wrote: > _______________________________________________ > Typo-list mailing list > Typo-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/typo-list > --
on 16.06.2006 09:55
Jon Gretar Borgthorsson a écrit : > Myself I'm just using the latest trunk without problems. > Not very stable though. > > On 6/16/06, Dick Davies <rasputnik@gmail.com> wrote: >> On 16/06/06, Jon Gretar Borgthorsson <jon.borgthorsson@gmail.com> wrote: >>> Well... You just have to find a revision before everything went bad >>> and use that one. >> Can anyone suggest one? Some of us are still on 2.6.0, and it's hard to >> help fix bugs when you can't test them. >> Hi list, would it be just possible to : svn export the last really stable dev version and do a tar / zip of this add this archive to the current page on typosphere .org ? Every people are not familiar with using subversion so it would be really cool to have this done: we may have more testers here. -- Frédéric de Villamil "Quand tu veux chasser une belle fille, il vaut mieux commencer par draguer sa copine moche" -- conseil de go. http://t37.net http://fredericdevillamil.com neuro@7el.net tel: +33 (0)6 62 19 1337
on 16.06.2006 10:32
I just jumped aboard Typo yesterday. I can say guys, that you are doing a great job, I love the application, and I will continue to help in anyway possible.
on 16.06.2006 10:32
On 16/06/06, Jon Gretar Borgthorsson <jon.borgthorsson@gmail.com> wrote: > Myself I'm just using the latest trunk without problems. > Not very stable though. Those two statements seem to conflict a bit :)
on 16.06.2006 10:45
On 6/16/06, Dick Davies <rasputnik@gmail.com> wrote: > On 16/06/06, Jon Gretar Borgthorsson <jon.borgthorsson@gmail.com> wrote: > > Myself I'm just using the latest trunk without problems. > > Not very stable though. > > Those two statements seem to conflict a bit :) Hehe... Sorry. What I meant by stable is that I never get any administration errors or anything like that. Simply sometimes when the page is being viewed I get an Applicaton Error(rails). But then I just refresh and everything works. --
on 16.06.2006 12:45
On 16 Jun 2006, at 09:42, a lot of people wrote:
> A lot of things ...
With regards to a stable version of Typo.
I'm on r1055 for Typo. As for Rails I'm on r4444. I use Ecto to
post and get the odd error when setting the category but it's easy
enough to fix in admin. Once a day I have a cron job running which
kills off the dispatch.fcgi processes and keeps things (seemingly)
fresh. I cycle the production log every few days to make sure it
doesn't get too big and the errors I get are minimal ... but more
importantly they are still there. If you want a version of Typo that
doesn't crash ... it doesn't exist yet. Saying that though a lot of
the errors for me seem to be relating to Rails and not Typo.
Remember that both of them are still very much being developed and
the major problem that every Rails application seems to have is
deployment and stability.
Kester Dobson was providing trunk in a zipped format for those who
don't have a clue about SVN (www.justkez.com/typo/)
With regards to Typosphere
Steve Longdo is right - Planet Argon is the home of that. I haven't
heard anything from those guys in a long time and the hosting of
Typosphere and Trac for nothing (I guess) is admirable. But it
really is bordering on neglect ... any of those lads watching this list?
With regards to 'Stewardship'
Tobi is quite rightly giving all of his attention to Shopify. Scott
was doing exciting things with Google which I guess doesn't leave too
much time, Piers is probably neck deep in a tight coding schedule for
real money, Kevin is - no idea - where are you Kevin? :) But if
there are important patches to be included in trunk maybe somebody
could list them to make it easier if one of the maintainers dropped
in to include them in a changeset? With regards to documentation ...
well we could all have a hand in editing Trac ... it's not the best
for new users but it'd be a start. If people know a bit about
troubleshooting dropping by the forums more often would probably help
as well.
And Finally Mephisto and Radiant
I've had them both installed locally. Radiant does a good job as a
CMS but it's not a blogging system which is an important
difference ... for me at least :) Mephisto is interesting but there
is no documentation as Mathew points out and your host needs to have
rmagick installed and working. If Typo frustrates you, then you'll
go mad with that right now.
Gary
on 16.06.2006 16:12
> for new users but it'd be a start. If people know a bit about > troubleshooting dropping by the forums more often would probably help > as well. Great, we're in agreement. Now, who owns typosphere.org? I for one would like to be given write-access. I don't have much to add straight away, but I'm happy to sit down for an hour on the weekend and write something, or proofread what someone else has written. Once again this is just my personal opinion, but forums are a bad idea without some documentation in place. They are also not the right place to put documentation. The reasons are many, but the most obvious ones are duplication and navigation. Get typosphere.org going and the forums will come to life by themselves, and will in fact help us fix and add to the documentation on the website. There, I've put my hand up. Uzair
on 16.06.2006 16:12
Right on Tim, let me know when you're ready for them and I'll cut them down to small screenshot and archive. From there I'll post the 'orphans' to the list and see if we can retrieve some lost themes. P On Thu, 15 Jun 2006 18:14:17 -0500, Timothy Freund <tim@digital-achievement.com> wrote: > >> The consensus on this thread seems to be that we need to kickstart the >> putting documentation/howtos on threaded forums is equivalent to burying > Timothy Freund > believed to be clean. -- http://fak3r.com - you don't have to kick it -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
on 16.06.2006 16:24
On 16 Jun 2006, at 15:08, uzair@nairang.org wrote: > > Great, we're in agreement. Now, who owns typosphere.org? I for one > would > like to be given write-access. I don't have much to add straight > away, but > I'm happy to sit down for an hour on the weekend and write > something, or > proofread what someone else has written. Everybody has access to Trac. Just hit the 'Edit this page' button
on 16.06.2006 16:24
On Thu, 15 Jun 2006 18:14:55 -0500, Timothy Freund <tim@digital-achievement.com> wrote: > I agree with that idea. The Typo community should eat its own dog food > and run an instance on typosphere.org. Give accounts to a few active > individuals and let them post not just about Typo, but about the > competition as well. > > That way we spread the responsibility out over several busy individuals > rather than one busy individual, and by writing about innovations across > the blogging community and not just within Typo we will better see how > Typo stacks up against other offerings. Definintely, and now is the time to regroup, after all the Mepistop talk I did some looking around and found this snippet: -------------- Mephisto This is unrelated to the other happenings above, but I wanted to comment on this due to the recent happenings. The Rails Weblog has just swapped their blogging engine from Typo to Mephisto. Of course they would give Rick all the credit wouldnâ??t they. ;-p Mephisto is a new Rails based publishing system (yes, another one). We havenâ??t released an official version of it yet, but we hope to be doing that soon. At the moment Iâ??m implementing a new interface for Mephisto and we have to work out file management as well before we do an official release. Here is a sneak peak at the new interface (pay no mind to the text): [...] Some of you may or may not know, but I had a hand in Typo as well. Itâ??s actually how I met and started working with Tobias. So why are people swapping from Typo? I donâ??t mean to take anything away from the talented folks who are doing the upkeep on Typo, but to me, Typo has lost focus of itâ??s purpose. Typoâ??s purpose was to publish content, but it has quickly evolved into much more, the interface has suffered as a result of this. There is so much focus on the development that the usability has taken a big blow. Iâ??m not sure if the Typo team has an active designer on staff, but I know that a sole designer simply canâ??t keep up with the pace of development. Or, at least, this was the case right before I stopped working on it. (Disclaimer: I havenâ??t checked out any of the recent version of Typo). With Mephisto itâ??s primarily just me and Rick working on it, although we have received some great contributions from others. We both have very high standards and we want to see those high standards reflected in what we release to the public. Mephisto is still in itâ??s infancy, but keep your eyes pealed for more to come. http://encytemedia.com/blog/articles/2006/06/13/railsconf-railsday-vacation-and-mephisto -------------- So it's not just us that feel like this, but now it's becoming the consensus is in the Rails community; Typo has lost ground, but we need to look forward with what we can do to strengthen the community. First off has to be the website, make it easier to use obviously, but also have a 1-2-3-4 step process where a newbie can downlaod/install/run a 2.6.0 instance in short order. From there I think we *need* a target date and requirement list for 4.0.0, then a theme site to allow users all of the themes for 2.6.0 and a sep listing for -trunk, that way when 4.0.0 comes out there will be a slew of themes avail out of the gate. Sorry, but people will judge Typo in how it looks, but with the themes we have from the contest that's no problem, it's just making those themes available (how about shipping with the top 5 rated ones? As well as migrating them to work with -trunk/4.0.0. P >>>few guy are doing a really good job on typo dev, but everything (but >>>Typo helped me to discover RoR and I'm addicted but sometimes people >>>http://rubyforge.org/mailman/listinfo/typo-list > Typo-list mailing list > Typo-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/typo-list > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. -- http://fak3r.com - you don't have to kick it -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
on 16.06.2006 16:47
Some people are volunteering to update the documentation, others are
rescuing obsolete themes from TypoGarden. This is wonderful to see!
Typo may have more life in it yet.
But what about Typo's biggest problem?
http://www.typosphere.org/trac/browser/trunk
No commits since May 20th, and not a peep from anybody with commit
access. Well, one single peep. :)
http://thread.gmane.org/gmane.comp.web.typo.user/2677/focus=2686
r1055 is just not suitable for running a production blog and nobody
appears to be merging the patches in Trac. How can this be fixed?
- Scott
on 16.06.2006 17:04
Jon Gretar Borgthorsson wrote: > Well... You just have to find a revision before everything went bad > and use that one. I've mentioned this before, but If you want a good revision of typo trunk, I've been having luck with 1039 and Rails 1.1.1. Posting works, admin works, RSS works, comments work, fastcgi has only crashed once. mathew
on 16.06.2006 17:10
Jon Gretar Borgthorsson wrote: > Sorry. What I meant by stable is that I never get any administration > errors or anything like that. Simply sometimes when the page is being > viewed I get an Applicaton Error(rails). But then I just refresh and > everything works. I used to get that all the time. Then my web host contacted me and said Typo was running the server into the ground, and please could I switch to a more expensive plan that included fastcgi. mathew
on 16.06.2006 17:39
On Fri, 16 Jun 2006 09:59:08 -0500, mathew <meta@pobox.com> wrote: > Jon Gretar Borgthorsson wrote: >> Well... You just have to find a revision before everything went bad >> and use that one. > > I've mentioned this before, but If you want a good revision of typo > trunk, I've been having luck with 1039 and Rails 1.1.1. Posting works, > admin works, RSS works, comments work, fastcgi has only crashed once. Mathew Can you help us with this? I've asked off and on how to get to a 'stable' version of trunk. Namely: what are the steps? svn typo trunk svn rails 1038? rake migrate VERSION=??? Sorry if this is obvious, but I don't know how to target things to make this work. Thanks P > dangerous content by MailScanner, and is > believed to be clean. -- http://fak3r.com - you don't have to kick it -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
on 16.06.2006 17:45
On 6/16/06, mathew <meta@pobox.com> wrote: > Jon Gretar Borgthorsson wrote: > > Sorry. What I meant by stable is that I never get any administration > > errors or anything like that. Simply sometimes when the page is being > > viewed I get an Applicaton Error(rails). But then I just refresh and > > everything works. > > I used to get that all the time. Then my web host contacted me and said > Typo was running the server into the ground, and please could I switch > to a more expensive plan that included fastcgi. I actually was thinking about this being Apache related. Although I was using fastcgi of course. As serverpowered.com gives me 3 ip addresses for my money I quickly set up LightTPD alongside Apache and bound to a seperate IP and have that problem a lot less. Now I'm moving most things to Lighty. If only Lighty supported SVN I would make a complete switch. --
on 16.06.2006 19:01
On 6/16/06, Jon Gretar Borgthorsson <jon.borgthorsson@gmail.com> wrote: > > I actually was thinking about this being Apache related. Although I > was using fastcgi of course. As serverpowered.com gives me 3 ip > addresses for my money I quickly set up LightTPD alongside Apache and > bound to a seperate IP and have that problem a lot less. Now I'm > moving most things to Lighty. > > If only Lighty supported SVN I would make a complete switch. Have people been having problems with FastCGI on the newer revisions? My sad devotion to the older versions that used page_cache haven't helped me conjure up any new patches. The order of magnitude slowdown in pages per second served just wasn't worth it on my low CPU/memory capacity server. Of course now I realize I don't even know how that whole page_cache vs. action_cache debate worked out.
on 16.06.2006 19:04
On 6/16/06, Scott Bronson <bronson@rinspin.com> wrote: > http://thread.gmane.org/gmane.comp.web.typo.user/2677/focus=2686 > > r1055 is just not suitable for running a production blog and nobody > appears to be merging the patches in Trac. How can this be fixed? I supposed it's time to jump in here. I've been insanely busy with with work for the past couple months. Even worse, I'm oncall for work this week, and just haven't had the energy to deal with this thread. As I see it, we have a few problems (in random order): 1. Typosphere needs more detail. Adding a blog would be nice, as would more documentation. We've discussed this before, but no one has stepped forward to get it working. Technically, this is pretty easy. 2. No one is actively committing things to SVN. There are 3 semi-active developers on Typo right now (my, Piers, and Kevin), but none of us have much time right now. 3. Bugs are getting fixed/patches aren't being applied. This is sort of complex. First, it's been *really hard* to find patches, thanks to all of the spam in Trac. Kevin's beat the spam back quite a bit, but it's still hard. Perhaps we'd be best off if people would discuss patches here. 4. We're missing documentation, and Typo's hard to install. This is mostly my fault. I've been trying to fix the install process for months and just haven't found the time. 5. Typo isn't very stable. This is a bit different from "bugs aren't getting fixed." It's proven to be difficult to install Typo in different environments reliabily. Over the past year, I've seen a huge number of *weird* bug reports just really don't make sense. It's like the combination of Apache+FCGI+Ruby+rails+ruby FCGI+Typo+DB is tough to get reliable. 6. Typo has a huge resource footprint. For some reason, Typo seems to leak memory. I don't know how to debug this. In some environments, Typo can jump up to 50+ MB, while others seem relatively stable. Unfortunately, *there's no way to tell where the memory's going*. 7. Typo has gone down the "more features" route rather then the "small and fast" route. I don't know how to address this. It is what it is, largely because we've added the things that we want and people have asked for. Most of the "bloat" is my code, including things like sidebars and plugable text filters. 8. There's no stable 4.0 release, even after months. This is basically my fault, too. People have been waiting for the installer that I haven't been able to finish. With any luck, I'll have some free time once I'm back off being on-call, and I'll be able to spend 10-15 hours on the installer. Until then, can people help with bug fixes? If we can get a list of bugs that are really broken, and ideally a list of patches that need applied, then it'll be *vastly* easier to get changes applied. 9. We need maintainers with time. Right now, I think there are 6 or 7 people with SVN write access. 4 of those are basically done with Typo, leaving 3 of us semi-active. If a couple people could step up and demonstrate that they (a) have time, (b) know what they're doing, and (c) are good at dealing with bugs, then I'd be glad to add them to the commit list. So, what am I missing? Scott
on 16.06.2006 19:23
> Everybody has access to Trac. Just hit the 'Edit this page' button
Curious...that's what I thought too, but I don't have an 'edit this
page'
button. That's probably because I haven't logged in...except I don't
have a
login and there's no place to register from the looks of it.
Uzair
on 16.06.2006 22:32
On Fri, 16 Jun 2006, Scott Laird wrote: >> access. Well, one single peep. :) > > 1. Typosphere needs more detail. Adding a blog would be nice, as > would more documentation. We've discussed this before, but no one has > stepped forward to get it working. Technically, this is pretty easy. This effort seems to have a lot of people behind it. > > 2. No one is actively committing things to SVN. There are 3 > semi-active developers on Typo right now (my, Piers, and Kevin), but > none of us have much time right now. I would love to help here, and I can apply properly formatted patches to trunk, but I don't know enough about the entire typo codebase to really be able to hack on it yet. > > 3. Bugs are getting fixed/patches aren't being applied. This is sort > of complex. First, it's been *really hard* to find patches, thanks to > all of the spam in Trac. Kevin's beat the spam back quite a bit, but > it's still hard. Perhaps we'd be best off if people would discuss > patches here. I've found a few. I've also been doing a cleanup of trac, closing off old bugs that have been fixed, as well as closing off bugs that are obviously not bugs. I think I've picked off most of the low hanging fruit though. > > 4. We're missing documentation, and Typo's hard to install. This is > mostly my fault. I've been trying to fix the install process for > months and just haven't found the time. Do you have any code that you can throw onto trunk? I'd love to be able to at least try what you've got, and open bugs and/or write patches for it. > > 5. Typo isn't very stable. This is a bit different from "bugs aren't > getting fixed." It's proven to be difficult to install Typo in > different environments reliabily. Over the past year, I've seen a > huge number of *weird* bug reports just really don't make sense. It's > like the combination of Apache+FCGI+Ruby+rails+ruby FCGI+Typo+DB is > tough to get reliable. I think we need to put a bug triage in place. A lot of the bugs we haven't been able to track down because we don't know enough about the environment to place the problem. I've seen a lot of well written bugs that include all the necessary information, but I've also seen a lot of bugs that don't include the necessary info to even determine whether or not it's a problem with typo, or fastcgi, or rails, or lighthttpd, or what. > > 6. Typo has a huge resource footprint. For some reason, Typo seems > to leak memory. I don't know how to debug this. In some > environments, Typo can jump up to 50+ MB, while others seem relatively > stable. Unfortunately, *there's no way to tell where the memory's > going*. I haven't seen this. > > 7. Typo has gone down the "more features" route rather then the > "small and fast" route. I don't know how to address this. It is what > it is, largely because we've added the things that we want and people > have asked for. Most of the "bloat" is my code, including things like > sidebars and plugable text filters. These features are actually what differentiate typo from WP. Feature differentiation is good, and doesn't necessarily mean more features, it just means that Typo has different features. For example, our post editor sucks, but that was part of the design decision. Most typo users use an external blog tool to post to typo, so they don't need a good post editor. I think we need to find areas where we can add features that users want, without bloating the code. > > 8. There's no stable 4.0 release, even after months. This is > basically my fault, too. People have been waiting for the installer > that I haven't been able to finish. With any luck, I'll have some > free time once I'm back off being on-call, and I'll be able to spend > 10-15 hours on the installer. Until then, can people help with bug > fixes? If we can get a list of bugs that are really broken, and > ideally a list of patches that need applied, then it'll be *vastly* > easier to get changes applied. I've spent a good part of today going through the trac site, and I have a list of 7 defects that have a milestone of 4.0 http://www.typosphere.org/trac/query?status=new&status=assigned&status=reopened&milestone=4.0&type=defect&order=priority 5 of these defects have patches. There are 4 enhancements with a 4.0 milestone, only one blocks the release. That one is, umm, yours. http://www.typosphere.org/trac/query?status=new&status=assigned&status=reopened&milestone=4.0&type=enhancement&order=priority > > 9. We need maintainers with time. Right now, I think there are 6 or > 7 people with SVN write access. 4 of those are basically done with > Typo, leaving 3 of us semi-active. If a couple people could step up > and demonstrate that they (a) have time, (b) know what they're doing, > and (c) are good at dealing with bugs, then I'd be glad to add them to > the commit list. I don't have that much time, I don't really know what I'm doing, but I am good at dealing with bugs. It's what I do professionally. > > So, what am I missing? All we're missing now is a plan. I really think we should look at putting out a beta of 4.0 soon. I can help clean off bugs, and start to come up with a test plan for the patches that are in trac. I have NO IDEA how unit testing is done with rails, or ruby, but I'll take a look. Thanks for composing this response. > > > Scott > _______________________________________________ > Typo-list mailing list > Typo-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/typo-list > -- -------------------------------------------------------------------------- Matt Rose mattrose@folkwolf.net Visit my blog! http://folkwolf.net He's an obese Jewish househusband who must take medication to keep him sane. She's a tortured motormouth Valkyrie from the wrong side of the tracks. They fight crime!
on 18.06.2006 01:17
So, does anyone know how to go about getting a login? If yes, I volunteer to put this info on Trac :) Uzair