Managing Module Installations

[jnovak]

I have a few questions concerning the installation of the new modules being developed by the OS community:

1. Do any of these new modules ever make it into the core code? Isn't that the idea behind having a robust OS development community?
2. What is the best way to manage the installation of these modules while still being able to upgrade when Sugar releases a new version?
3. How do you ensure compatibility betwwen modules from different developers?
4. When a new Sugar version is released, what is the upgrade process, do the OS modules have to be uninstalled? If so, is the data associated with the module lost?

Some of the modules I would like to load are: Sugar Maps, Zucker Reports, Zucker Docs, Power Prospecting, Organization Charts, Gantt Chart, Sub-Panels, Project Duplication, Teams, Module Builder, Resource Manager, In/Out Board, Admin Tools, Who's On-Line, etc. What problems might I encounter with these modules during installation and during Sugar updates?

Thanks,
John Novak

[jnovak]

Is there any accepted best practice in managing module installation from multiple developers along with the upgrades published by the Sugar Development Team?

THanks,
John Novak

[ftreml]

Do any of these new modules ever make it into the core code? Isn't that the idea behind having a robust OS development community?

yes, a handful of former community projects are part of the core code, as far as I know.

What is the best way to manage the installation of these modules while still being able to upgrade when Sugar releases a new version?

Sugar contains a "Module Loader", where you can manage your installed addon modules and patches.

How do you ensure compatibility betwwen modules from different developers?

ask the developers if they are compatible. self-contained modules typically are compatible with others, as only new functionality is added, and none of the curent functionality is changed.

When a new Sugar version is released, what is the upgrade process, do the OS modules have to be uninstalled? If so, is the data associated with the module lost?

usually no reinstallation is required, but it depends on the module - some of them work this way, some of them not.

What problems might I encounter with these modules during installation and during Sugar updates?

most of the community projects are based on work people do in their spare time. not all of them are developed further, not all of them are compatible with all Sugar releases, not all of them provide new releases compatible with new Sugar releases within days.