It's totally reasonable, and is also the exact sort of guidelines I would want to establish if I were the maintainer of an open-source project.
However, I think it's amusing that the website lists all of these cool reasons why someone should use Web Origami, and then the repo more-or-less says "here's all of these rules you should abide by if you want to even CONSIDER using this project". One page is meant to draw users in, the other to fend them off.
i can only find two rules: treat the developer and his time with respect, and say hello before filing a bug[*]. the rest are statements to tell everyone what they can expect, nothing that they actively need to do.
[*] i disagree with "Bugs are a lousy way to say hello". though i think i know where the developer comes from, but if i am going to make a contribution, i'll just do that, and maybe start the contribution with a short introduction, but i am not going to say hello until i actually have something to contribute. i agree with everything else though, and expecially with all the things i should expect if i contribute something.
One page is meant to draw users in, the other to fend them off
i'd say it's meant to draw in friendly users and fend off the unfriendly ones. if you have participated in other projects you should understand why some developers feel that this is necessary.
However, I think it's amusing that the website lists all of these cool reasons why someone should use Web Origami, and then the repo more-or-less says "here's all of these rules you should abide by if you want to even CONSIDER using this project". One page is meant to draw users in, the other to fend them off.