Greetings,
I have a bit of spare time lately and would like to contribute to the site doing few tests.
I would like to test policy behind blog post, in particular URL and markup validation/sanification.
To do so I would like to proceed here, in production, opening and then editing a blog post I will create just for testing purposes (and then delete when I have finished).
I know that probably there are more orthodox way to do test, like set up a git pod for a better testing environment, but these increase the complexity on my side and in any cases I don't see how any of the test i was thinking about (related to encoding, validation and sanification) may create problems at all to the platform.
So I am here asking to the staff if may I proceed like i ask, clearly I will report to staff (through GitHub issue) any problems I will found (if any is found).
For any doubt or clarification, about which test I would like to do, fell free to ask
Greetings,
I have a bit of spare time lately and would like to contribute to the site doing few tests.
I would like to test policy behind blog post, in particular URL and markup validation/sanification.
To do so I would like to proceed here, in production, opening and then editing a blog post I will create just for testing purposes (and then delete when I have finished).
I know that probably there are more orthodox way to do test, like set up a git pod for a better testing environment, but these increase the complexity on my side and in any cases I don't see how any of the test i was thinking about (related to encoding, validation and sanification) may create problems at all to the platform.
So I am here asking to the staff if may I proceed like i ask, clearly I will report to staff (through GitHub issue) any problems I will found (if any is found).
For any doubt or clarification, about which test I would like to do, fell free to ask
I don't see any reason why you shouldn't be allowed to do that, as long as you follow the rules here: https://lichess.org/page/blog-etiquette (the test you describes seems very unlikely to break any of those rules).
I don't see any reason why you shouldn't be allowed to do that, as long as you follow the rules here: https://lichess.org/page/blog-etiquette (the test you describes seems very unlikely to break any of those rules).
@AsDaGo said in #3:
I don't see any reason why you shouldn't be allowed to do that, as long as you follow the rules here: lichess.org/page/blog-etiquette (the test you describes seems very unlikely to break any of those rules).
I was just afraid that my testing would be miss interpreted as an attempt to breach site security.
Anyway I have seen that it's possible to write a blog post without publish it (and sanification will be applied anyway), so I think this is the way to go.
@AsDaGo said in #3:
> I don't see any reason why you shouldn't be allowed to do that, as long as you follow the rules here: lichess.org/page/blog-etiquette (the test you describes seems very unlikely to break any of those rules).
I was just afraid that my testing would be miss interpreted as an attempt to breach site security.
Anyway I have seen that it's possible to write a blog post without publish it (and sanification will be applied anyway), so I think this is the way to go.
Also see https://github.com/lichess-org/lila/security/policy.
@revoof said in #5:
Also see github.com/lichess-org/lila/security/policy.
Very useful thank you
@revoof said in #5:
> Also see github.com/lichess-org/lila/security/policy.
Very useful thank you