Which things do you want most in Cotonti?

I really like the Usergallery, that's why I've voted for Image & Media Gallery.
Even way back in the days with LDU, that gallery was doing a great job
Then Seditio, and it still worked...
Too bad that Cotonti doesn't have one.
Yes, there's MediaLibrary, but that has no PFS integration...yet.

I can only hope that a good gallery comes out soon; galleries have proven their usefulness

Yes, I agree.
And I would have a Gallery like Usergallery second version, with categories (like page structure) not only with tags or folder index as I can see in basic gallery with jQuery from Koradhil or the latest third versions of Usergalley...

I'm not exactly sure what is meant by Taxonomy. I voted Social Integration, Blogs/Miniblogs and Other.

Firstly, social integration is something that has the potential to boost the public use of Cotonti as a CMS, as well as the success of Cotonti powered websites. Social integration will enable the creation of Cotonti mash-ups.

Secondly, blogging is a very important aspect of the internet nowadays. Cotonti should offer, in whatever way, a perfect platform for blogging. We should, in my opinion, at least be able to offer the same functionality and usability as the Wordpress system.

Finally, I voted Other, and this is also my main concern. Cotonti should be delivered as a framework, with separate modules for main functionality and plugins for extra functionality. Basically, Cotonti should only include the user system, the admin panel and pages/structure. All other core functionality should be put into modules and separated from the core, so you can rip out any unneccesary modules. The reason why I prefer to see it that way is because I often build custom web applications for my customers, in which most of the current core functionality is unneeded and therefore ripped out. This goes mainly for the forums and polls, but often also the PM system and ratings/comments and sometimes the PFS system.

I voted for Blogs, Gallery and Quad Speed-up.
No particular reason behind voting for quad speed-up, I just like speed-ups and clean-ups and most ups except throw-ups haha.

Honestly, we're missing a serious blog functionality. It would probably be something based on the pages/structure, but with a seperate admin section... I guess. I don't think we should clone WordPress though.

The gallery is essential, end of story. Even for situations when most core features get disabled by clients, like Gert explained above.

I'd consider adding a contact form plugin in the distribution as well... I believe it's a must have.

I prefer to see multiple download packages (or even better: custom on-the-fly packages). On the frontpage we would still offer the regular package as default, but on the downloads page (or elsewhere) we could put a form with checkboxes to include or exclude certain parts of the package (such as plugins or modules). Of course a developer can simply remove these parts from the default package (providing most core functionality gets put into modules), but offering custom downloads is just a nicer way to do it.

I really like this idea Gert, great stuff! We could have recommended package (core + picked plugs), a minimal package (core + vital plugs), an advanced package and a custom package with checkboxes. A real time calculation of overall size and features would be neat too.

I voted for blogs - I think blogs should be handled with care though. I believe we can benefit from users being able to post their own respective blogs.... this would go well with social integration.

Something not mentioned is a more robust user search, maybe by location?

Go for the speed and clean up first.

There has been a lot off changes in the core, so best thing to do is stabilize it and clean it up before you continue. In the end this is a better way, end you'll end up with fast and a clean core.

keep it ez

I would have a good file manager in the core. With multiple uploads, drag&drop files from system windows to personal user filespace, friendly graphic interface (like Windows or other OSes).
Users are disoriented by the actual PFS (isn't it still the old LDU one?).

And a gallery system perfectly integrated with this new PFS...

donP is right... This old pfs is really ancient.. It is time for a new one. If I only could vote for that..
But clean up the code too

Is Cotonti that slow for you, ez?

Code can always be made better, faster, smarter.. so far I like how cotonti is coming together. I have to agree with others about the PFS... something should be done to update it. Galleries should be in my opinion at least, only slightly integrated in PFS to provide for sites that don't use files and only galleries or vice versa... or both. Blah, I'm babbling.

Koradhil:

---

Cotonti should be delivered as a framework, with separate modules for main functionality and plugins for extra functionality. Basically, Cotonti should only include the user system, the admin panel and pages/structure. All other core functionality should be put into modules and separated from the core, so you can rip out any unneccesary modules. The reason why I prefer to see it that way is because I often build custom web applications for my customers, in which most of the current core functionality is unneeded and therefore ripped out. This goes mainly for the forums and polls, but often also the PM system and ratings/comments and sometimes the PFS system.

I with you absolutely agree and I support this position.
Has voted for Taxonomy

This is the reason I totally disagree with blogs and multiblogs or social integration... there are so many other places to do social integration that I think nobody would think to create a facebook or twitter alternative with a Cotonti driven website

Trustmaster:

---

Is Cotonti that slow for you, ez?

NO (do not want to offend anyone), but a good and clean base is always better to build with
it is good, but Cotonti is growing like hell... (everybody has to watch out that is stays mean, lean, fast and clean).
I agree with Aristei and Koradhil about a small core with plugins. I also rip out most off the functions for my sites.