|
|
@@ -269,6 +269,63 @@ Oscar is released under the permissive `New BSD license`_ (see summary_).
|
|
269
|
269
|
|
|
270
|
270
|
.. _`New BSD license`: https://github.com/django-oscar/django-oscar/blob/master/LICENSE
|
|
271
|
271
|
|
|
|
272
|
+Contributing to the Project
|
|
|
273
|
+---------------------------
|
|
|
274
|
+
|
|
|
275
|
+We welcome contributions to the project! Whether it's a bug fix, a new feature, or just some documentation improvements, your contributions are greatly appreciated.
|
|
|
276
|
+
|
|
|
277
|
+To contribute, please follow these steps:
|
|
|
278
|
+
|
|
|
279
|
+Fork the project repository on GitHub.
|
|
|
280
|
+Clone your forked repository to your local machine.
|
|
|
281
|
+Create a new branch for your changes.
|
|
|
282
|
+Make your changes, and commit them with clear commit messages.
|
|
|
283
|
+Push your changes to your forked repository.
|
|
|
284
|
+Open a pull request on the original project repository, explaining your changes.
|
|
|
285
|
+Please note that all contributions are subject to review, and may be modified or rejected if they do not meet the project's standards.
|
|
|
286
|
+
|
|
|
287
|
+Code of Conduct
|
|
|
288
|
+---------------
|
|
|
289
|
+
|
|
|
290
|
+We want everyone involved in the project to feel safe and respected, regardless of their background or identity. As such, we have adopted the following Code of Conduct:
|
|
|
291
|
+
|
|
|
292
|
+Our Pledge
|
|
|
293
|
+----------
|
|
|
294
|
+
|
|
|
295
|
+In the interest of fostering an open and welcoming environment, we pledge to:
|
|
|
296
|
+
|
|
|
297
|
+Be friendly and welcoming to all contributors.
|
|
|
298
|
+Respect differing viewpoints and experiences.
|
|
|
299
|
+Accept constructive criticism and feedback graciously.
|
|
|
300
|
+Focus on what is best for the community and the project.
|
|
|
301
|
+
|
|
|
302
|
+Our Standards
|
|
|
303
|
+-------------
|
|
|
304
|
+
|
|
|
305
|
+We expect all contributors to:
|
|
|
306
|
+
|
|
|
307
|
+Use welcoming and inclusive language.
|
|
|
308
|
+Be respectful of differing viewpoints and experiences.
|
|
|
309
|
+Gracefully accept constructive criticism.
|
|
|
310
|
+Focus on what is best for the community and the project.
|
|
|
311
|
+
|
|
|
312
|
+Our Responsibilities
|
|
|
313
|
+--------------------
|
|
|
314
|
+
|
|
|
315
|
+Project maintainers are responsible for:
|
|
|
316
|
+
|
|
|
317
|
+Enforcing the Code of Conduct.
|
|
|
318
|
+Investigating and addressing reported violations of the Code of Conduct.
|
|
|
319
|
+Making clear and fair decisions about disciplinary actions for violations of the Code of Conduct.
|
|
|
320
|
+Scope
|
|
|
321
|
+This Code of Conduct applies to all contributors, both online and offline, in all project spaces, including but not limited to project forums, mailing lists, GitHub repositories, and in-person events.
|
|
|
322
|
+
|
|
|
323
|
+Enforcement
|
|
|
324
|
+-----------
|
|
|
325
|
+
|
|
|
326
|
+If you witness or experience unacceptable behavior, or have any other concerns, please notify the project maintainers at viggo@highbiza.nl & joey@highbiza.nl. All reports will be kept confidential, and the project maintainers will work with you to determine a resolution.
|
|
|
327
|
+
|
|
|
328
|
+We reserve the right to take any action deemed necessary to enforce this Code of Conduct, including but not limited to warning the offender, banning the offender from the project's spaces, or reporting the offender to relevant authorities.
|
|
272
|
329
|
Case studies
|
|
273
|
330
|
------------
|
|
274
|
331
|
|