diff --git a/opsec/contribute/70.png b/opsec/contribute/70.png new file mode 100644 index 0000000..e90d870 Binary files /dev/null and b/opsec/contribute/70.png differ diff --git a/opsec/contribute/71.png b/opsec/contribute/71.png new file mode 100644 index 0000000..365473e Binary files /dev/null and b/opsec/contribute/71.png differ diff --git a/opsec/contribute/72.png b/opsec/contribute/72.png new file mode 100644 index 0000000..2f484a2 Binary files /dev/null and b/opsec/contribute/72.png differ diff --git a/opsec/contribute/73.png b/opsec/contribute/73.png new file mode 100644 index 0000000..0969b77 Binary files /dev/null and b/opsec/contribute/73.png differ diff --git a/opsec/contribute/74.png b/opsec/contribute/74.png new file mode 100644 index 0000000..0fe7bfc Binary files /dev/null and b/opsec/contribute/74.png differ diff --git a/opsec/contribute/75.png b/opsec/contribute/75.png new file mode 100644 index 0000000..351ae09 Binary files /dev/null and b/opsec/contribute/75.png differ diff --git a/opsec/contribute/76.png b/opsec/contribute/76.png new file mode 100644 index 0000000..af39fad Binary files /dev/null and b/opsec/contribute/76.png differ diff --git a/opsec/contribute/index.html b/opsec/contribute/index.html index 2cc7fed..74f85b3 100644 --- a/opsec/contribute/index.html +++ b/opsec/contribute/index.html @@ -60,7 +60,7 @@
- Previous Page

nihilist@mainpc - 2024-10-06

+ Previous Page

nihilist@mainpc - 2025-04-03

How to become a Contributor

In this tutorial we're going to look at how you can contribute to the opsec blog, we'll look into how the work is being organized, and how to contribute via gitea.

Sidenote: Help us improve this tutorial by letting us know if there's anything missing or incorrect on this git issue directly!

@@ -110,7 +110,6 @@ To be showcased:

After discussing with me what task you want to do, we'll confirm on the price for that tutorial and after i get your confirmation i'll assign it to you, and that's when you can start to work on it.

Disclaimer: if you're not used to writing technical stuff, please aim for the tutorials that are labeled as "Simple" and that you actually understand. Don't try to bite more than you can chew, otherwise i might refuse further contributions coming from you. You should be at least familliar with the topic you intend to talk about.

-

Sidenote: Help us improve this tutorial by letting us know if there's anything missing or incorrect on this git issue directly!

@@ -141,7 +140,7 @@ To be showcased:
-

How to contribute new tutorials

+

How to contribute new tutorials

Now you first need to sign up on gitea, just ping me directly on SimpleX so that i create your account manually.

From here you'll also get to join the Contributors private chatroom where we brainstorm new contributions, formulate todolists, assign those todolists to contributors like you, and review those contributions:

@@ -329,9 +328,9 @@ To http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/6dv -

now from there your pull request is created, and i'll review it as soon as i get the time:

+

now from there your pull request is created, and I'll review it as soon as I get the time:

-

If it's not complete, i'll comment in there asking you to add what's missing, changes that you must actually finish before the deadline. To add further changes simply add more commits to it

+

If it's not complete, I'll comment in there asking you to add what's missing, changes that you must actually finish before the deadline. To add further changes simply add more commits to it


 [ mainpc ] [ /dev/pts/18 ] [~/Documents/blog-contributions]
 → vim opsec/newtutorial/index.html
@@ -378,6 +377,47 @@ Writing objects: 100% (5/5), 432 bytes | 432.00 KiB/s, done.
+ + +
+
+
+
+ +

Updating existing tutorials

+ +

Sometimes it happens that a tutorial is outdated, has errors or just needs some methodology updates. If you have an idea for something that could be added, or if you want to fix some errors in the tutorial, contact us on simplex or open an issue on gitea. We will discuss the changes and make sure they're going in the right direction. If it's a small change (like fixing typos or modifying just a few sentences), you can make a pull request with the changes without contacting us.

+ +

Usually, there are already a few issues for blog updates listed on the project board. If you want to help, feel free to pick one and start working on it.
+ The steps are similar to what we have for creating new tutorial - fork the repository, create a branch and edit appropriate blog post. When you're done with your changes, open a pull request so that we can review them.

+ +

Depending on how much of the tutorial is actually changed, you should credit yourself accordingly. For the sake of this example, let's say you're oxeo0 (the person making an update) and Nihilist is the original author of the blog post.

+ +

Small change

+

If the changes you've made are small (let's say less than 20% of the blog post), you should keep the name of the original author. You may change the date to inform readers it has been changed recently, but this is not strictly required. Do not add your XMR address in the footer. This doesn't mean that you won't be getting paid. If you're working on an issue on the project board, there's often a reward even for small edits.

+ + + +

Considerable change

+

If the changes you've made are considerable (let's say more than 20% of the blog post), you should credit yourself and the original author. Mention the tutorial has been updated by you at the top and keep both yours and author's XMR address in the footer.

+ + + +

Complete rewrite

+

Sometimes the tutorial needs to be rewritten entirely (more than 90% changes). In this case, you can treat the tutorial as if it was written by you from the beginning.

+ + + +

Special Case - Collaboration

+

If there is more than one person working on the tutorial, credit all as authors and list their XMR addresses.

+ + + +
+
+
+
+