NewPipe-eV/website
5
2
Fork 1
Code Issues 2 Pull requests 3 Projects Releases Packages 1 Wiki Activity Actions

Add jobs page #45

Open
Stypox wants to merge 6 commits from jobs into main
pull from: jobs
merge into: NewPipe-eV:main
Conversation 0 Commits 6 Files changed 29 +169 -20
Stypox commented 2025-08-20 18:31:46 +02:00
Owner
Copy link

image

![image](/attachments/a911a227-0bef-45d2-9424-7f9e64d012ba)
image.png
318 KiB
Stypox added 5 commits 2025-08-20 18:31:46 +02:00
Write Jobs page
All checks were successful
Build and publish Docker image / build (push) Successful in 30s
Details
Build and publish Docker image / build (pull_request) Successful in 35s
Details
9ad259bc12
Stypox added 1 commit 2025-08-20 18:35:49 +02:00
Align 'NewPipe e.V.' text in header properly
All checks were successful
Build and publish Docker image / build (push) Successful in 30s
Details
Build and publish Docker image / build (pull_request) Successful in 27s
Details
89825f167b
Stypox started working 2025-08-20 18:45:10 +02:00
Stypox stopped working 2025-08-20 18:45:14 +02:00
4 seconds
Stypox deleted spent time 2025-08-20 18:45:26 +02:00
- 4 seconds
fynngodau reviewed 2025-08-20 19:16:29 +02:00
jobs.html
@ -0,0 +50,4 @@
<h2>Jobs</h2>
</header>
<p>
NewPipe e.V. is looking for two people that could bring forward the NewPipe refactor and make our web infrastructure more resilient, as decided in <a href="posts/2025-02-08_5th_plenum.html">the 5th plenum meeting</a>. Note that at this time we can only hire <strong>independent contractors</strong> that can emit invoices, and work would be paid by the hour at a gross rate of 32€/h. You can apply by sending us an email at <a href="mailto:board@newpipe-ev.de">board@newpipe-ev.de</a> using the two buttons below.
fynngodau commented 2025-08-20 19:16:29 +02:00
Owner
Copy link

I have a suggestion for how to phrase this:

Unfortunately, as a small not-for-profit, we are unable to pay industry-standard rates. Still, we would like you to be able to dedicate time to our project and would thus like to pay you a compensation of 32 EUR per hour.

We should note what needs to be included in the email:

Please include a few lines about what relevant experiences you have for the respective position. We do not expect a full CV or other documentation. We will respond to every applicant.

Also, we should tell people until when they need to mail us to guarantee that we will still consider them – and when to expect things to move forward:

You have time until at least XX.XX.2025 to apply (or longer, if the position remains vacant). After this date, we will get back to you to agree on a time when we can get to know each other in an online meeting.

I have a suggestion for how to phrase this: > Unfortunately, as a small not-for-profit, we are unable to pay industry-standard rates. Still, we would like you to be able to dedicate time to our project and would thus like to pay you a compensation of 32 EUR per hour. We should note what needs to be included in the email: > Please include a few lines about what relevant experiences you have for the respective position. We do not expect a full CV or other documentation. We will respond to every applicant. Also, we should tell people until when they need to mail us to guarantee that we will still consider them – and when to expect things to move forward: > You have time until at least XX.XX.2025 to apply (or longer, if the position remains vacant). After this date, we will get back to you to agree on a time when we can get to know each other in an online meeting.
Poolitzer commented 2025-08-20 22:43:00 +02:00
Owner
Copy link

agreed, good suggestion

agreed, good suggestion
TheAssassin commented 2025-08-21 00:07:09 +02:00
Owner
Copy link

Please stop using the terms "hiring" or "job" or similar. We are looking for freelancers, after all. Also, I would not necessarily mention the salary publicly, as it is below market values and we may want to negotiate a bit in the process depending on their experience etc.

With a Werkvertrag, it would be easier, as then time is the contractor's problem and the expected outcome is well defined.

_Please_ stop using the terms "hiring" or "job" or similar. We are looking for freelancers, after all. Also, I would not necessarily mention the salary publicly, as it is below market values and we may want to negotiate a bit in the process depending on their experience etc. With a Werkvertrag, it would be easier, as then time is the contractor's problem and the expected outcome is well defined.
Stypox commented 2025-08-21 12:29:22 +02:00
Author
Owner
Copy link

Unfortunately, as a small not-for-profit, we are unable to pay industry-standard rates. Still, we would like you to be able to dedicate time to our project and would thus like to pay you a compensation of 32 EUR per hour.

I would avoid this sentence. It's not so bad of a pay (especially outside of Germany), it's not like we are paying 10€/h. People will decide if it's worth it or not.

Please stop using the terms "hiring" or "job" or similar.

I know, but couldn't find a better wording in various places. Could you rephrase the various sentences in the file to not use those words? I really don't know how to write them better

I would not necessarily mention the salary publicly

It's public anyway (in the 5th plenum meeting notes) so I thought it was worth mentioning. But if we don't want to mention it here explicitly, I think we should at least indicate in which ballpark the salary would be. I'd hate to see a job offering without any mention whatsoever of how much I'd get paid.

> Unfortunately, as a small not-for-profit, we are unable to pay industry-standard rates. Still, we would like you to be able to dedicate time to our project and would thus like to pay you a compensation of 32 EUR per hour. I would avoid this sentence. It's not so bad of a pay (especially outside of Germany), it's not like we are paying 10€/h. People will decide if it's worth it or not. > Please stop using the terms "hiring" or "job" or similar. I know, but couldn't find a better wording in various places. Could you rephrase the various sentences in the file to not use those words? I really don't know how to write them better > I would not necessarily mention the salary publicly It's public anyway (in the 5th plenum meeting notes) so I thought it was worth mentioning. But if we don't want to mention it here explicitly, I think we should at least indicate in which ballpark the salary would be. I'd hate to see a job offering without any mention whatsoever of how much I'd get paid.
Stypox commented 2025-08-21 12:38:47 +02:00
Author
Owner
Copy link

We do not expect a full CV or other documentation.

But it'd still be useful to get a CV I guess, right? Not as a requirement, but if one already has a CV lying around, why not send it to us so we can learn more about that person?

> We do not expect a full CV or other documentation. But it'd still be useful to get a CV I guess, right? Not as a requirement, but if one already has a CV lying around, why not send it to us so we can learn more about that person?
fynngodau commented 2025-08-21 12:43:14 +02:00
Owner
Copy link

But it'd still be useful to get a CV I guess, right? Not as a requirement, but if one already has a CV lying around, why not send it to us so we can learn more about that person?

In the past, reading that it is voluntary to submit one made me personally think that it would reflect badly upon me not to submit one. That's why my preference is to say we don't want one, as I really don't want to know which school someone went to. But I'm fine if the outcome of this discussion is different.

> But it'd still be useful to get a CV I guess, right? Not as a requirement, but if one already has a CV lying around, why not send it to us so we can learn more about that person? In the past, reading that it is voluntary to submit one made me personally think that it would reflect badly upon me not to submit one. That's why my preference is to say we don't want one, as I really don't want to know which school someone went to. But I'm fine if the outcome of this discussion is different.
Poolitzer approved these changes 2025-08-20 22:44:47 +02:00
jobs.html
@ -0,0 +64,4 @@
<section>
<h3>Android developer for NewPipe</h3>
<div>
<p>We are looking for a developer for the NewPipe app, especially to bring forward <a href="https://newpipe.net/blog/pinned/announcement/newpipe-0.28.0-released/#progress-on-the-refactor">the refactor</a>. Your main task would be to port UI components from XML to <strong>Jetpack Compose</strong>, while keeping an eye on style and <strong>usability of the interfaces</strong>, and to implement the business logic in Kotlin using view models, dependency injection, and other modern technologies. You would be working in close contact with other TeamNewPipe members and open Pull Requests to <a href="https://github.com/TeamNewPipe/NewPipe">NewPipe</a> (on the <code>refactor</code> branch), <a href="https://github.com/TeamNewPipe/NewPlayer">NewPlayer</a> and <a href="https://github.com/TeamNewPipe/NewPipeExtractor">NewPipeExtractor</a>.</p>
Poolitzer commented 2025-08-20 22:43:46 +02:00
Owner
Copy link

is pull requests really uppercased?

is pull requests really uppercased?
👍 1
TheAssassin reviewed 2025-08-21 00:03:46 +02:00
jobs.html
@ -0,0 +79,4 @@
<h3>System administrator</h3>
<div>
<p>We are looking for a sysadmin that could setup some new services on NewPipe e.V.'s servers (e.g. Lemmy) and help with regular maintenance. You would be working alongside our volunteer sysadmin <a href="https://github.com/TheAssassin">@TheAssassin</a>, who has already compiled a list of tasks to delegate.</p>
<p>Bonus points for your application if you: are already self-hosting something for yourself, have experience with Ansible.</p>
TheAssassin commented 2025-08-21 00:03:46 +02:00
Owner
Copy link

This does not correctly represent the list of requirements. Ansible knowledge is a necessity, not a "bonus". We cannot afford teaching someone the basics of configuration management at such an hourly rate. Plus, we are looking for people with actual experience in commercial environments. We can always lower our expectations later.

This does not correctly represent the list of requirements. Ansible knowledge is a necessity, not a "bonus". We cannot afford teaching someone the basics of configuration management at such an hourly rate. Plus, we are looking for people with actual experience in commercial environments. We can always lower our expectations later.
Stypox commented 2025-08-21 12:30:09 +02:00
Author
Owner
Copy link

Yeah yeah that was a placeholder

Yeah yeah that was a placeholder
Stypox marked this conversation as resolved
TheAssassin reviewed 2025-08-21 00:16:25 +02:00
jobs.html
@ -0,0 +78,4 @@
<section>
<h3>System administrator</h3>
<div>
<p>We are looking for a sysadmin that could setup some new services on NewPipe e.V.'s servers (e.g. Lemmy) and help with regular maintenance. You would be working alongside our volunteer sysadmin <a href="https://github.com/TheAssassin">@TheAssassin</a>, who has already compiled a list of tasks to delegate.</p>
TheAssassin commented 2025-08-21 00:16:25 +02:00
Owner
Copy link

List of requirements:

  • Linux system administration
  • prior experience in ops ("system administration")
  • IaC and configuration management, Ansible skills (so that they can quickly learn our existing setup)
  • Docker/Podman/containers

Bonus:

  • DevOps (CI/CD, e.g., with GitHub/Gitea actions, GitLab CI)
  • experience with database administration
  • backups with borg(matic)
  • experience with K8s (as this is on the wishlist)

Mentioning Lemmy explicitly is misleading. This is just another service TM.

List of requirements: - Linux system administration - prior experience in ops ("system administration") - IaC and configuration management, Ansible skills (so that they can quickly learn our existing setup) - Docker/Podman/containers Bonus: - DevOps (CI/CD, e.g., with GitHub/Gitea actions, GitLab CI) - experience with database administration - backups with borg(matic) - experience with K8s (as this is on the wishlist) Mentioning Lemmy explicitly is misleading. This is just another service TM.
Stypox commented 2025-08-21 12:30:23 +02:00
Author
Owner
Copy link

Thanks, I will put these

Thanks, I will put these
tobigr reviewed 2025-08-21 10:09:04 +02:00
jobs.html
@ -0,0 +65,4 @@
<h3>Android developer for NewPipe</h3>
<div>
<p>We are looking for a developer for the NewPipe app, especially to bring forward <a href="https://newpipe.net/blog/pinned/announcement/newpipe-0.28.0-released/#progress-on-the-refactor">the refactor</a>. Your main task would be to port UI components from XML to <strong>Jetpack Compose</strong>, while keeping an eye on style and <strong>usability of the interfaces</strong>, and to implement the business logic in Kotlin using view models, dependency injection, and other modern technologies. You would be working in close contact with other TeamNewPipe members and open Pull Requests to <a href="https://github.com/TeamNewPipe/NewPipe">NewPipe</a> (on the <code>refactor</code> branch), <a href="https://github.com/TeamNewPipe/NewPlayer">NewPlayer</a> and <a href="https://github.com/TeamNewPipe/NewPipeExtractor">NewPipeExtractor</a>.</p>
<p>Bonus points for your application if you: have experience with native Android development, already know modern Android development practices (Kotlin, Jetpack Compose, Dependency Injection, etc.), have contributed to open source projects in the past.</p>
tobigr commented 2025-08-21 10:09:04 +02:00
Owner
Copy link

Why is experience with Android development and knowledge of modern Android dev practives a bonus and not a requirement? If we do not expect people to know NewPipe we should at least expect them to know Android development. Or do you think that we would need to offer higher wages with this requirement? 32€/h is not a wage that a student in the first semester would get.

Why is experience with Android development and knowledge of modern Android dev practives a bonus and not a requirement? If we do not expect people to know NewPipe we should at least expect them to know Android development. Or do you think that we would need to offer higher wages with this requirement? 32€/h is not a wage that a student in the first semester would get.
Stypox commented 2025-08-21 12:35:54 +02:00
Author
Owner
Copy link

I did not want to set hard requirements as they might be off-putting for some people (e.g. one may consider his experience with Android not enough to meet the hard requirement, although maybe it would instead be good enough). Obviously we can always reject applications later if they don't seem fit, it's not like we expect to get 100s of applications.

I did not want to set hard requirements as they might be off-putting for some people (e.g. one may consider his experience with Android not enough to meet the hard requirement, although maybe it would instead be good enough). Obviously we can always reject applications later if they don't seem fit, it's not like we expect to get 100s of applications.
👍 1
tobigr marked this conversation as resolved
All checks were successful
Build and publish Docker image / build (push) Successful in 30s
Required
Details
Build and publish Docker image / build (pull_request) Successful in 27s
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin jobs:jobs
git checkout jobs
Sign in to join this conversation.
Reviewers
No reviewers
Poolitzer
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: NewPipe-eV/website#45
No description provided.
Delete branch "jobs"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?