search

Perl-Evozon / PearlBee

116 stars 44 forks source link

Is this a dead project? #75

Open itnomad opened 7 years ago

itnomad commented 7 years ago

I have a PearlBee installation that I've been using more or less as a personal diary for over 2 years. I would like to do more with PearlBee. I often meet people that are interested in using a system such as PearlBee. With the current code, I can not seem to get a new working PearlBee up and running. My old one runs fine, just with not all the features working. Changes to the code have been made since my first installation 2 years ago. I get the feeling that most of those working on this software have moved on to maybe Perl 6 stuff. Is there another Perl blogging software that can be recommended? Will development continue on PearlBee? I could try to help, but my coding abilities are still not up to a level that most coders would find useful. Is anyone willing to patiently bring me along to a point where I can contribute to this project? Or will the code base come to a point where it works? Or should I move on to another project? I like Perl, I wouldn't mind learning Perl 6. I'm looking for suggestions, but really need a blogging platform that I can start using for other peoples projects.

drforr commented 7 years ago

drforr/blogs-perl-org started as a PearlBee instance, and should probably be considered this project's spiritual successor. Originally the intent was to backport what we could from blogs-perl-org but there were some core issues, mainly support for multiple blogs and "pages" from the MovableType schema on blogs.perl.org that make it hard to backport changes from blogs-perl-org now. I'd love to have input on drforr/blogs-perl-org, especially regarding properly doing DBIC - we inherited a certain style from PearlBee and the developers sort of rolled with that rather than refactoring things - there's of course much more to that story than I'm allowed to talk about.

While I'm tempted to use this (drforr/blogs-perl-org) as the basis for a Perl 6 application, there's little that I'd salvage from this aside from the HTML and the basic schema. The Perl 5 code would go for obvious reasons, and I'd end up rewriting the routes to be more consistent. They were a compromise between PearlBee and MovableType routes, and for a standalone application I'd almost be tempted to treat it as a greenfield and just work from scratch. I'm going to take some time over the holidays to get the Perl 6 Template Toolkit stuff properly working, and then I can see how much HTML can be salvaged from this application.