Hi, Just thinking out loud.
Pros to keeping just one repository: Makes it possible to update code and web site in one pull request. I don't know anyone who is doing that now however. Longer term, though, we will want to encourage documentation to be updated alongside code so this may be the direction we want to go. Makes it easier to have a notion of code + web site being on the same release thread. Of course that can still be done with separate repositories; it is just twice the work from an infrastructure perspective. Pros for having separate repositories: Makes it easier for the web site to be "pan-release". For example, one can maintain separate pages for past releases and pages for future releases. It might be interesting to inquire of other projects why they do things the way they do. Dave -----Original Message----- From: Gunnar Tapper [mailto:[email protected]] Sent: Tuesday, November 10, 2015 3:59 PM To: [email protected] Subject: Website Updates Hi folks: I'm working on updating the website. As I look around, I find that some projects seem to have a separate repository for the website. I assume that it's so that the website can be updated asynchronously from the actual project. Examples: - http://phoenix.apache.org/building_website.html - https://geode.incubator.apache.org/contribute/ What would be the pros and cons you'd see for Apache Trafodion? Is anyone dead against a separate repository for the website? -- Thanks, Gunnar *If you think you can you can, if you think you can't you're right.*
