This morning, we had a brief discussion about the fact that we have several public references our source code in SVN. These references will need to be updated to reference Git. We don't yet have a clear plan for this, but surveying the terrain seems like a good start.
First off, our public website: The "Download Infusion" page refers to SVN http://fluidproject.org/products/infusion/download-infusion/ references tag in SVN: includes live link and text of the svn command As well, the wiki is rife with references. A search for "SVN" turned up 33 pages of search results. A scan of the first 10 of these pages turned up the following pages, which mention SVN and/or link to the repository: http://wiki.fluidproject.org/display/fluid/Source+Code http://wiki.fluidproject.org/display/fluid/Contributing+Code http://wiki.fluidproject.org/display/fluid/Process+for+Granting+Commit+Access http://wiki.fluidproject.org/display/fluid/Getting+Started+in+Fluid+Development http://wiki.fluidproject.org/display/fluid/Coding+and+Commit+Standards http://wiki.fluidproject.org/display/fluid/Contributing+to+a+Fluid+Component http://wiki.fluidproject.org/display/fluid/Tagging+the+Source+Code http://wiki.fluidproject.org/display/fluid/Building+a+Bundle http://wiki.fluidproject.org/display/fluid/Subversion+Tips+and+Tricks http://wiki.fluidproject.org/display/fluid/Project+Infrastructure http://wiki.fluidproject.org/display/fluid/Infusion+Build+Scripts http://wiki.fluidproject.org/display/fluid/Deploying+the+Infusion+Builder http://wiki.fluidproject.org/display/fluid/Custom+Infusion+Builds+With+Ant http://wiki.fluidproject.org/display/fluid/Writing+JavaScript+Unit+Tests http://wiki.fluidproject.org/display/fluid/Installing+and+Configuring+Fluid+Engage http://wiki.fluidproject.org/display/fluid/Fearless+JavaScript+1.0 http://wiki.fluidproject.org/display/fluid/User+Interface+Development+with+jQuery+Workshop http://wiki.fluidproject.org/display/fluid/Installing+the+Fliquor+Portlet http://wiki.fluidproject.org/display/fluid/Showcase+of+Recent+Work http://wiki.fluidproject.org/display/fluid/Embedded+Fluid+license http://wiki.fluidproject.org/display/fluid/Data+Import http://wiki.fluidproject.org/display/fluid/Tabindex+Focus+Navigation+Tests http://wiki.fluidproject.org/display/fluid/Walkthrough+-+Building+and+using+the+Image+Reorderer+in+Sakai http://wiki.fluidproject.org/display/fluid/Lightbox+Technical+Overview http://wiki.fluidproject.org/display/fluid/Versioning+the+Fluid+Framework http://wiki.fluidproject.org/display/fluid/McCord+Document+Conversion plus each of the individual release pages (including "current"), e.g. http://wiki.fluidproject.org/display/fluid/Fluid+Infusion+1.2 I'm not at all convinced that we're going to be able to come up with any form of simple or automated process for updating all these references: For one, the URL references are not all to the same URL (some to trunk, some to a tag, some to an incubator project...). For another, several of them include narrative references and snippets of SVN command-line instructions. I think we might just have to have an all-hands-on-deck blitz where everyone picks a section of the wiki and fixes stuff. Does anyone have any alternative suggestions? -- Anastasia Cheetham Inclusive Design Research Centre [email protected] Inclusive Design Institute OCAD University _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
