[
https://issues.apache.org/jira/browse/SHINDIG-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588541#action_12588541
]
Santiago Gala commented on SHINDIG-146:
---------------------------------------
What as we going to do with this patch?
On the minus side, applying it is likely to cause some conflicts to people
doing major works, on the plus side, the earlier it gets in the simpled it will
be to keep terminology clean.
I think it is basically done after I tweaked a couple of small problems, the
last commits in
http://github.com/sgala/apache-incubator-shindig/commits/synd-rename-2
Feedback on it?
I can commit myself, specially if a series of "topic" commits renaming one or a
few variables at a time is preferred to a big patch.
> 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-2.patch,
> SHINDIG-146-for-humans-squashed-2.patch,
> SHINDIG-146-for-humans-squashed.patch, SHINDIG-146-for-humans.patch,
> SHINDIG-146-for-robots-squashed-2.patch, SHINDIG-146-for-robots-squashed.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.
