On 11.03.2015 08:58, Dmitriy Setrakyan wrote: > On Tue, Mar 10, 2015 at 10:20 PM, Branko Čibej <[email protected]> wrote: > > >>> On top of that, everyone in the >>> community has a chance to suggest edits to any piece of the documentation >>> via "Suggest Edits" link on every page (yet another cool feature provided >>> by readme.io). >>> >>> However, I believe we have to live with creating documentation in >> readme.io >>> first and then exporting it to GIT. I have also created a script which >>> automatically goes through all MD files in the documentation and adds >>> Apache License to it. >> Can you write an automated script that proves that every change in the >> documentation was made by an Ignite committer? Because that's what all >> this boils down to: having a verifiable audit trail for every line of >> source or documentation in a release. This is fundamental to the legal >> requirements for a release. This is also the reason why the ASF insists >> that repositories must be hosted on our infrastructure. >> > There is plenty of documentation in Apache TLPs which is being hosted in > Atlasssian Confluence as well (https://cwiki.apache.org/). I assure you > that in those cases Confluence is the primary editor of that documentation, > and that it never ends up directly in the source tree. Can you explain why > that process is any better than the one we have setup?
The difference is in the *.apache.org vs. *.io. As I said, hosting this externally (pasting from repo isn't the same as generating) doesn't feel right to me, but I'm not sure if it actually violates any policies. You have to understand that I'm not being pedantic for the sake of making your life miserable, although I can quite understand if you're feeling that way lately. :) I'm all for making things as simple as possible for developers and users. But as I said elsewhere, the policies aren't arbitrary. -- Brane
