Joostina - CMS based on Joomla 1.0.x

[Dead Krolik]

Hello

Russian community present to Joomla community new CMS, based on Joomla 1.0.x, called Joostina.

http://joostina-cms.org

At our site you can read only features and descriptions. There are now available English version. We are translating language files. But Joostina works on many russian sites rigth now.

We look at 1.5 and we think, that this cms is too slow. 1.5 will
not support old extensions in future. 1.5 has future, but not today.

We want to use CMS, that will support old extensions (there are so many good
extensions) and we improved all 1.0.x characteristics (perfomance, templating,
caching, full ajax in admin area, seo improvements, builtin backup,
builtin captcha ...).

We don't want repeat the fate of Elxis. We need for community and
developers support.

It's developing already one year. But now it is only russian, almost all
our community that don't use 1.5 use this CMS.

Appeal of Joostina team to Joomla community

[baijianpeng]

Great project! All extensions for Joomla 1.0.x are saved now. They will not die when Joomla 1.0.x ends its life.

I had seen some plans about Joostina on its support forum, it seems that the authors/developers of Joostina have some excellent improvements.

Congratulations for your English version release! Wish you will make it better and better.

However, I did not find language files for Administration backend in the latest Joostina 1.2.0 RC6. Hope you can add this feature soon.

Since you have no forum on Joostina official website, I would like to claim here that I will translate this CMS into Chinese language and I hope I can be the ONLY Chinese translator for it.

Thanks for your efforts.

[masterchief]

Good luck with your project. By heck I know how much work it takes.

A word of advice though.

Be very sure what you focus is. If your focus is to provide a "home" (akin to an old persons home) for abandoned 1.0 extensions, I think that's a great endeavor, although it would be short lived (maybe a year or two at the max).

If you are wanting to expand the feature set of 1.0 so that people can delay the migration from 1.0 to 1.5 even further, then I'd really think seriously about whether that's a good thing to do. Even though there are some die-hard sites that will be difficult to migrate, the bottom line is 1.0 is a dying market (commercial or otherwise). Be careful you don't put too much effort into a 1.0 clone only to have it evaporate as Joomla progresses into 1.6 and 2.0 (and besides, people stuck on 1.0 are going to have to see a nett benefit on side-grading to Joostina and, guys/gals, you are going to have make sure it works and doesn't bust someone's site).

I think a home for 1.0 to give it a little more usable life is a great thing ... but for anything more, I'd question the medium to long term viability. I guess the first thing I'd do is actually find out how many 1.0 sites out there _can't_ move to 1.5 easily (and that's a hard can't, not just don't want to). If there are less than 100,000 I'd really be thinking whether it's worth it. Once 1.6 is in play I doubt many developers will bother supporting 1.0 (many don't now, and for good reason - it's not as good as 1.5).

Anyway, take it or leave it but that's what I think. But hey, if you are wanting to provide a true fork of 1.0, that's ok with me. You just have a hard road ahead of you

[Dead Krolik]

On my God, how many English I can not respond to every word, this is too difficult for me.

I understand you, but our goal here - it is a official point of view of Joomla team. We really want to make a CMS, which will be a continuation of 1.0.x and in the future, a real alternative to functional of 1.5.

If any Joomla-core "peoples" can say anything - please say it. It will only welcome.

Sorry for my terrible English

[masterchief]

Why do you want to continue 1.0 development?

The API is really, really poor compared to 1.5 (no Joomla developer should be learning to develop for 1.0 - that's just crazy).

Why not put the effort into learning 1.5 or helping people migrate from 1.0 to 1.5?

[Dead Krolik]

Mmm. We can compare 1.0 and 1.5 with many parameters.

You insist on API, but magabytes (!) of MVC-code and std class wrappers it's not a really convenient API (code is really beautiful but incomprehensible). And there are so many other parameters to compare: number of files, distribution size, functional (now 1.5 and 1.0 has same), speed of development, requirements for hosting.

Joostina is not a Joomla. We made big work to extend things, that nobody can do in Joomla within two years. Our goal now - stable release in English, but we plan do many things: templating, optional UTF support, improvements of std components, but CMS structure will remains simple.

[Tonie]

Yout goal is to continue development of 1.0, not just adding support for current sites running 1.0. This is basically a fork that's going in a separate direction.

[mcsmom]

Hi,

Please understand that if you want to fork you need to create a completely new name and a logo that does not violate the Joomla! trademark.
To create a custom distribution you need to make up your own name or request trademark use permission.

[Dead Krolik]

mcsmom

http://en.wikipedia.org/wiki/Fork_(soft ... velopment)

Free or open source software is, by definition, that which may be forked without permission of the original creator.

http://opensource.org/docs/osd

3. Derived Works
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.

Name and logo is original, not the same as in Joomla.


Tonie

This is basically a fork that's going in a separate direction.

And what?

[mcsmom]

No, the logo is half of the Joomla Logo and the name is half of the Joomla name.
You need to invent a name and a logo that are completely your own.

I really suggest you get in contact with someone with legal experience with these issues just as the Joomla team did when they left Mambo.

Good luck with your CMS, the GPL is great in the way that it lets you do this.

[masterchief]

You insist on API, but magabytes (!) of MVC-code and std class wrappers it's not a really convenient API (code is really beautiful but incomprehensible).

Good luck then. I think you are making a really bad decision if you are ignoring MVC. It will be difficult to find experienced Joomla developers that share your opinion.

[beededea]

This is an old post but one that is relevant to reply to now. Joostina has come of age for the English speaking world, or almost...Joostina 1.2 with English language support seems to be a workable solution for those moribund Joomla 1.0.15 sites with no upgrade place to go! I have just installed Joostina 1.2 from scratch with an english.php for the backend and installed 30 or so components, modules and plugins and each has installed without a hitch. I now have a relatively painless upgrade path ready for my Joomla 1.0.15 sites. I need to test an upgrade of an existing joomla 1.0.15 site but it seems reasonable to suggest that it might just work...

See the translated backend - 85% complete here:
http://lightquick.co.uk/images/stories/ ... -large.jpg

[mcsmom]

You still need to deal with the fact that your name is a trademark infringement. Please seek legal counsel before going any further with it. You should make an original name that you can take credit for. Just call it Stina or something.

[beededea]

I don't need to deal with it - but the Joostina team might

I think it has been around for a year or so now, doesn't that set a precedent?

[mcsmom]

If you aren't involved why are you here promoting it?
No, it doesn't. They are well aware that there is an issue and what they need to do.

[beededea]

Because it is useful to all Joomla 1.0 users and if it is useful then it should be pushed! Why not? I can say that Artio JoomSEF is a good SEF tool and recommend that people use it. I don't have to commercially benefit from something to say it is a good idea. That's what forums are for, to disseminate useful information... I found this one post for Joostina - I have something to say so I said it here!

I personally have 10-15 Joomla 1.0.15 sites belonging to clients that will never upgrade to Joomla 1.5 because the process for each is painful. The clients in general will pay no more money for these sites and do not see the benefit to moving to Joomla 1.5 when the same amount of work could move them to another platform. They are also fully trained in the backend tools for 1.0.15 and don't want any changes that would disrupt work. With a Joostina upgrade each site is two hours work and that is mostly waiting for files to copy. It is so simple and provides a perfect route for the Joomla 1.0.15 sites that are stuck in the doldrums. Also, Joostina is an improvement on Joomla 1.0.15, it has a lot of built-in tools, an SQL console. You ought to have a look.

More importantly a good stable Joomla 1.0.15 site benefits from the Joostina upgrade because you can take advantage of the support environment created by the Joostina users. They seem dynamic, friendly and are pushing their fork of Joomla 1.0.15. they have a thriving community. They also seem like nice people. Do I need any more reasons?

You sound a bit negative about it to me, I prefer a bit of positivity. Joomla 1.5 does not need to be the be-all and end-all. I have loads of Joomla 1.5 sites but it is not the solution to everything!

[beededea]

Oh yes, and if they need to change the name, well they can change it, wouldn't matter to me. I'd still think it is a good idea. I notice that Artio JoomSEF has 'Joo' in it too, in fact it goes one letter further with an 'm'.

Keep smiling!