#Renaming The following changes should be incorporated into various systems: * TYPO3 -> TYPO3 (CMS) * FLOW3 -> (TYPO3) Flow * TYPO3 v5 / Phoenix -> (TYPO3) Neos ##Last changes * 2012-11-19 - Add examples (stucki) ##Possible Time line * tbd. #Affected platforms ##Forge * soutRename project identifiers in the databasesout * e.g. typo3v4-core -> cms-core? or typo3-cms-core? ~olly * Please use just "typo3cms" in case the blank of "TYPO3 CMS" has to be dropped. Don't use "typo3-cms". That is: drop the blank instead of replacing it by "-". ~mb * I would go for "typo3cms" too ~francois * => **DONE 2013-11-16 **by Bastian Bringenberg and Ernesto (typo3cms, typo3cms-core and typo3cms-documentation) * Project identifiers \& structure * Top categories * (I suggest to have at least streamlined names for the top level projects (typo3flow, typo3cms, typo3neos) and then the substructure you need (typo3cms-core). It's important that people don't start using just "CMS" as a product name. It's either "TYPO3" or "TYPO3 CMS". ~robert) * I'm ok with "typo3cms", but isn't it a bit overkill for the newer products? Why not just "neos", "flow"? ~francois * typo3 / typo3cms / cms ? * flow / typo3flow ? * neos / typo3neos ? * Project identifiers * typo3-core / typo3cms-core / cms-core ? * xyz-core-security * xyz-workspaces / xyz-core-workspaces ? * xyz-distribution-introduction * extension-*example* (stays the same) * flow * typo3flow-distribution-base / flow-distribution-base ? * typo3flow-package-*example* / flow-package-*example* ? * neos * typo3neos-distribution-base / neos-distribution-base ? * Documentation related keys: (NOTE Stucki: this part should be clear after the questions above have been answered.) * Use "typo3cms-doc-" + the name of the Git repository * E.g. * doc\_core\_tsref Git repo: Documentation/TYPO3CMS/Reference/Typoscript New identifier: typo3cms-doc-typoscript * => **DONE 2013-11-20 **by Bastian Bringenberg * what about mapping the file structure from git to keys? packages-typo3-flow, distributions-typo3-neos-base-distribution, … ###Tasks * adjust repository settings for renamed projects * add .htaccess redirect to new URLs * problems? * are there any RSS/JSON/etc. exports used that depend on the project key? ~olly * Creating New Script should be edited too * if we are on that, can new projects be put to Git instead, or at least have a possibility to chose SVN or Git? ~olly Check general naming schema/structure tree and mapping to git/gerrit (required for automation)? * the mapping happens with the project key, stored in the gerrit database ##Svn * deprecated (soon), I would not put work in it * what happens, if we rename the project keys in redmine? * This can be solved using normal HTTP redirects. Some regular expressions will hopefully help us for this. ~stucki * Server Team Meeting / 2013-04-16: We agree that we won't change SVN repositories. They will keep the old names. ##**Git / Gerrit** * figure out, how to rename projects in Gerrit (renaming of project and group in DB + movement in filesystem?) * we are currently testing the rename-project (\url{https://gerrit.googlesource.com/plugins/rename-project)} and rename-group commands * tables affected judging from the schema * account\_group\_names (name, forge\_project\_id) * account\_groups (name) * account\_project\_watches (project\_name) * changes (dest\_project\_name) * projects (name, forge\_project\_id) <- this is unused in 2.2, right? * ref\_rights (project\_name) <- this is unused in 2.2, right? * in \url{https://groups.google.com/forum/?fromgroups=#}!topic/repo-discuss/a0llZ4Df57Y Shawn says it's enough to rename a project on disk and adjust the changes table * we change the group names as well, so we need to change the first two as well * gerrit rename-group via ssh should take care of that without any SQL * the watches were overlooked by Shawn, it seems, so we need some SQL here * projects and ref\_rights can be ignored * git repositories need to be moved on the gerrit server, the git server and the forge server [rename-project and replication should take care of this, export-daemon-ok is needen on git ~peterN] * soutreplication configuration - any changes neededsout? [AFIK no, ~peterN] * soutpermissions need to be changedsout [should be done by rename-group command ~peterN] * checkout config, adjust, commit, push back. this should do for the majority of changes needed: mkdir tmp \&\& cd tmp \&\& git init scp -p review.typo3.org:hooks/commit-msg .git/hooks/ git fetch ssh://review.typo3.org/FLOW3/Packages/TYPO3.FLOW3.git refs/meta/config \&\& git checkout FETCH\_HEAD git checkout -b config #git config -f project.config <option> <value> perl -pi -e 's/FLOW3/Flow/g' project.config git commit -a git push ssh://review.typo3.org/FLOW3/Packages/TYPO3.FLOW3.git HEAD:refs/for/refs/meta/config * keep the old repositories until a tbd. point of time up to date(no copy, check option of redirect? symlink?)? * would this allow to still clone TYPO3v4/Core.git, since some deployments might rely on that URI? ~olly * keeping old repos in old location leads to confusion, people will get stuck on old revisions, 404 is better than outdated information ~pn * Remove all files from the old location. Maybe put in a README file, which points the users to the new repository location! Naming scheme (?) * CMS/Core * CMS/Extensions * Neos/... * Flow/Distributions/ * Flow/Packages/ * Flow/.... * Others/Teams/Server (?) * Project/Teams/Server (?) Rename project identifiers in the database Naming scheme suggestion by Robert: * git.typo3.org/Packages/ * git.typo3.org/Distributions/ * git.typo3.org/Websites/ * git.typo3.org/Teams/ * git.typo3.org/Projects/ Point is: as soon as a git repository uses namespaces it should end up in Packages using their existing or future composer package name with dotted notation (e.g. TYPO3.Flow, TYPO3.Neos). Distributions and sites should have a common naming scheme for the composer package name and git repo: typo3/neos-base-distribution -> git.typo3.org/Distributions/TYPO3.Neos-Base-Distribution.git typo3/cms-base-distribution -> git.typo3.org/Distributions/TYPO3.CMS-Base-Distribution.git typo3/flowtypo3org -> git.typo3.org/Packages/TYPO3.FlowTypo3Org.git typo3/flowtypo3org-website -> git.typo3.org/Websites/TYPO3.FlowTypo3Org-Website.git ... to be refined ##Translation server ## All core and TER projects start with a TYPO3. So I think that we don't have to rename anything on the Pootle server. We start some test on Flow, and the package will be named TYPO3.Flow. or Flow. (no sure what's the best solution) For Neos ... we don't discuss the naming convention actually => Server Team Meeting / 2013-04-16: This needs to be done by the translation team. ##Mailing lists * It will be very difficult to rename any newsgroups and/or mailing lists * Proposal: Keep all typo3-* (related with TYPO3 CMS) mailing lists as they are, only rename ex v5/Phoenix and FLOW3 lists/groups * agreed, some of the lists like typo3.dev, typo3.german, etc. keep the whole TYPO3 history ~olly * We basically need to: ~robert * rename flow3-general to typo3-flow (migrate the archive, migrate the subscriber list) * remove flow3-announce (migrate the archive to the new typo3-flow, no need to migrate the subscribers list) * remove flow3-team-core (no need to keep the archives) * rename typo3-project-5\_0-general to typo3-neos (migrate the archive, migrate the subcribers list) * remove typo3-team-core-v5 (migrate the archive to the new typo3-neos, no need to migrate subcribers list) * remove typo3-project\_5\_0-internal (no need to keep the archives, those who participated still have the emails) * remove typo3-project\_5\_0-tcr (no need to keep the archives, those who participated still have the emails) How to rename the lists: soutMailmansout: - rename list name: TODO: How to do that? - it would be nice if old addresses (e.g. flow3-general@lists.typo3.org) will be forwarded, but it's not a must-have - change the target newsgroup to sync with (that's an option in the mailman list configuration) Newsgroup: - TODO: check how to rename groups in inn - update files in /etc/news/ (grep for the newsgroup name) Forum: - TODO: how to proceed? Final checks: - Check if syncing between lists <-> newsgroups works still ##Twitter **souttwitter.com/typo3serversout** - Icon colors DONE! ##URLs for documentation: docs.typo3.org et. al. Previously defined naming scheme has to be adjusted. Current naming scheme is at \url{http://docs.typo3.org/typo3cms/} We need to agree on how we map the documentation of our repositories to public urls. Discussion about that was started recently in \url{http://lists.typo3.org/pipermail/typo3-project-documentation/2012-October/004192.html} The goal is to create a real database lookup table that helps us map: **gitRepositoryName** to ** relPathToManualInUrl** and vice versa. See the table below. See further notes at the end of the table. Draft of a table: ============ .. note:: In this etherpad you can choose a **monospace font type** at "Settings of this pad"!!!! gitRepositoryName , relPathToManualInUrl Documentation/TYPO3/Example/ExtensionManual.git , typo3cms/ExtensionManualExample Documentation/TYPO3/Example/OfficialManual.git , typo3cms/OfficialManualExample Documentation/TYPO3/Guide/Administrators.git , typo3cms/AdministratorsGuide Documentation/TYPO3/Guide/FrontendLocalization.git , typo3cms/FrontendLocalizationGuide Documentation/TYPO3/Guide/Installation.git , typo3cms/InstallationGuide Documentation/TYPO3/Guide/Security.git , typo3cms/SecurityGuide Documentation/TYPO3/Reference/CodingGuidelines.git , typo3cms/CodingGuidelinesReference Documentation/TYPO3/Reference/CoreApi.git , typo3cms/CoreApiReference Documentation/TYPO3/Reference/FileAbstractionLayer.git , typo3cms/FileAbstractionLayerReference Documentation/TYPO3/Reference/IndexedSearch.git , typo3cms/IndexedSearchReference Documentation/TYPO3/Reference/InsideTypo3.git , typo3cms/InsideTypo3Reference Documentation/TYPO3/Reference/Skinning.git , typo3cms/SkinningReference Documentation/TYPO3/Reference/Tca.git , typo3cms/TcaReference Documentation/TYPO3/Reference/Tsconfig.git , typo3cms/TsconfigReference Documentation/TYPO3/Reference/Typo3Services.git , typo3cms/Typo3ServicesReference/ Documentation/TYPO3/Reference/Typoscript.git , typo3cms/TyposcriptReference/ Documentation/TYPO3/Reference/TyposcriptSyntax.git , typo3cms/TyposcriptSyntaxReference/ Documentation/TYPO3/Tutorial/Editors.git , typo3cms/EditorsTutorial/ Documentation/TYPO3/Tutorial/GettingStarted.git , typo3cms/GettingStartedTutorial/ Documentation/TYPO3/Tutorial/Typoscript45Minutes.git , typo3cms/TyposcriptIn45MinutesTutorial/ name differs! Documentation/TYPO3/Guide/Tutorial/GettingStarted.nl\_NL.git , typo3cms/GettingStartedTutorial/nl\_nl Documentation/TYPO3/Reference/Typoscript.fr\_FR.git , typo3cms/TyposcriptReference/fr\_fr Documentation/TYPO3/Reference/Typoscript.en\_US.git , typo3cms/TyposcriptReference/en\_us (about 17.000 TYPO3v4 extensions in general) , typo3cms/drafts/ (about 17.000 TYPO3v4 extensions in general) , typo3cms/extensions/<extension key> TYPO3v4/Extensions/news.git , typo3cms/extensions/news TYPO3v4/CoreProjects/workspaces/version.git , TYPO3v4/CoreProjects/workspaces/workspaces.git , typo3cms/extensions/Workspaces FLOW3/Documentation.git , flow FLOW3/Packages/TYPO3.DocTools.git , flow/packages/TYPO3/DocTools FLOW3/Packages/TYPO3.FLOW3.git , flow/packages/TYPO3/Flow FLOW3/Packages/TYPO3.Fluid.git , flow/packages/TYPO3/Fluid ((book in arbitrary repository))...git , books/... Documentation/TYPO3/Book/ExtbaseFluid.git , books/ExtbaseAndFluid FLOW3/...git , flow/... NEOS/...git , neos/... Sites/...git , sites/... SURF/...git , surf/... Teams/...git , teams/... ##Notes on documentation URLs It is important to keep in mind that "relPathToManualInUrl" may appear in different contexts such as: \url{http://typo3.org/docs/typo3cms/TyposcriptReference/} \url{http://typo3.org/docs/flow/}... \url{http://typo3.org/docs/neos/}... \url{http://typo3.org/documentation/document-library/typo3cms/TyposcriptReference/} \url{http://typo3.org/documentation/document-library/flow/}... \url{http://typo3.org/documentation/document-library/neos/}... \url{http://docs.typo3.org/typo3cms/TyposcriptReference/} \url{http://docs.typo3.org/flow/}... \url{http://docs.typo3.org/neos/}... Example text: "See the 'typo3cms/InstallationGuide'" Example text: "See the 'flow/InstallationGuide'" Example text: "See the 'neos/InstallationGuide'"