[jira] Updated: (SHINDIG-146) Terminology change: Replace "syndicator" with "container" to be in line with current gadgets terminology.

["Santiago Gala (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SHINDIG-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Santiago Gala updated SHINDIG-146:
----------------------------------

    Attachment: SHINDIG-146-for-humans.patch

Patch (series of small incremental commits) for humans.

It will not apply, as subversion does not understand the rename
syntax from git and I'm trying to get feedback rather than it to be applied.

http://github.com/sgala/apache-incubator-shindig/commits/synd-rename/ shows the commits, but they are not that readable, specially renames.



> Terminology change: Replace "syndicator" with "container" to be in line with current gadgets terminology.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-146
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-146
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Features, Gadgets Server - Java, Gadgets Server - PHP, Sample container & Examples
>            Reporter: Kevin Brown
>         Attachments: SHINDIG-146-for-humans.patch
>
>
> Currently, the term "syndicator" (or "synd") is used throughout the code base to refer to container-specific details. This is mostly a terminology holdover from igoogle, and we should move towards renaming these pieces "container" to be in line with current opensocial / gadgets terminology. Suggested changes:
> - Rename SyndicatorConfig classes to ContainerConfig
> - Rename "syndicator" parameters / variables throughout the code base to "container"
> - Rename "synd" URL parameter to "container" -- possibly maintain "synd" as an alias so that existing deployments don't have to be modified.
> The vast majority of shindig deployments will only ever need to support a single container, so most of these changes won't affect those deployments, but for any deployments that support multiple containers (such as gmodules.com), this change will matter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.