New features > crowdfunding

[brutusmaximus]

I'm working with CMSMS since 2009. I'm a webdesigner and developer. Every time a new version/update is released I'm looking forward to check the new features. Like the last big CMSMS 2.0 announcement! (looking forward to the release)

Sometimes I wish "my wanted features" (i.e. improved file and image manager) could be on the changelog.

I'm full aware of the fact that all CMSMS members are working for "free" and the amount of free time is limited.

Wouldn't it be a great idea to create a "CMSMS 2.1 wanted features list" and let the community "vote" for their wanted feature. By voting I mean donate an x amount of money to your wanted feature. The (ie. top3)features that recieves the most money(support) will be build by a CMSMS Core Developer.

I'm prepare to donate money if my wanted features could be build. I know that developing (core) modules, will take alot of time. So if the community could crowdfund the next new features, we all benefit from it.

I'm looking forward to any response how we could support and improve CMSMS by crowdfunding.

[Wishbone]

Which features are on your list?

[brutusmaximus]

This is just a wishlist!

• Multilangual

• Improved file browser / file upload (GBFilepicker = Default filebrowser)

• Improved image editor (crop function)

• AdvancedContent = Default page

• External template system(CSS/HTML) with version control

• Replace News with ListIt2 (and all extra features) + SEO friendly url)+ automatic rss feed creation for link with Social Media (linkedin/twitter/facebook)

• Simpler and more color neutral admin template

• auto backup db

[brutusmaximus]

@Calguy1000 would you build most voted features, if there would be enough money crowdfunded ?

[calguy1000]

Keep in mind that our intent is to keep CMSMS as small, and modular as possible. it will at no time become a 'kitchen sink' application to attempt to solve everybody's problem for everything. We would rather have 25 modules to solve a problem like workflow, versioning, multilingual... than to try to solve everybody's problems in the core.

With that said. It is my personal opinion that crowd funding is a good idea that just has not really worked yet (in the strict sense) for CMSMS or addon modules. Though some people have funded modules, and others have funded addons to those modules. and some minor changes to core modules (like News) have been funded.

Next I'll address the specific points. Most of this has been addressed already in one or more posts, talks, blog articles, geekmoot presentations....

1. Multilingual

We are making more changes in CMSMS 2.0 to allow third party developers to swap out bigger portions of the core system (like the template stuff, and the content manager stuff). However, we have no intentions to add multi-lang support to the CMSMS core. We feel that this will remain the domain of third parties.

2. Improved file browser / file upload (GBFilepicker = Default filebrowser)

I personally, have no plans to really change this. This is because of my general feeling that addon modules should 'own' their images and files.

Content pages are really the only thing that link to existing images at this time. News, and most other modules 'own their attachments'. This is a different way of thinking. The thought is that rather than having a huge structure of files that are shared by a few modules, or re-used a few times, when an article that contains an image is deleted, the image should be deleted as well.

This does not mean that some things couldn't be approved on... However GBFilepicker will not become part of the core.

3. Improved image editor (crop function)

In 2.0 we're improving file manager, and investigating moving the imagemanager functions into FileManager. We may add a few things in there as well for general image editing.... cropping may be one, we'll have to see.

4. AdvancedContent = Default page

It's already possible to change the default content type, and restrict the list of content types in the content type dropdown when adding/editing a page.

5. External template system(CSS/HTML) with version control

This will be the domain of third party modules. In 2.0 we're introducing a new system to manage templates, stylesheets, and designs... it should be possible for a third party developer to write a module like 'TemplateExternalizer' only better.

6. Replace News with ListIt2 (and all extra features) + SEO friendly url)+ automatic
rss feed creation for link with Social Media (linkedin/twitter/facebook)

Will not happen. Listit2 is a third party module, and we will not 'include it' in the core. It has different goals than our News module does.

7. Simpler and more color neutral admin template

I am not a designer... go ahead and write one, though we will be making this simpler in 2.0.

8. auto backup db

Will not happen. Database dump, and backups are the domain of the host/provider/system, or third party modules. This functionality is not directly in the domain of building websites or managing contents. Most control panels have database backup mechanisms and file managers etc etc. As well, when managing multiple sites on one host using a proper backup system is the best way to go.

--
Now, all that said. I am (and so are many other developers) willing to write almost any module for CMSMS as long as the revenue for that module meets our goals. However, adding them to the core is a completely separate and complex discussion.

[brutusmaximus]

Calguy thank you for your extended answer reply.

I think you're making good points. Since I'm not a phpdeveloper, I'm completely dependend of the modules.

So when I want to start a crowfunding project to support cmsms, its better to focus on crowdfunding for (existing) modules.

[brutusmaximus]

@Calguy how about starting with a crowdfunding for versioning. What is the amount of money the community need to gather for a versioning module so that we can use git to update the cmsms ?

@inCTRLdesign I would write versioning... if somebody pays me to it's not a thing for the core though.