Add "Opportunities" page #45
Poolitzer
tobigr
Loading…
Add table
Add a link
Reference in a new issue
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?
@ -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.I have a suggestion for how to phrase this:
We should note what needs to be included in the email:
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:
agreed, good suggestion
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.
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.
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
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.
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.
I reworded to "work would be paid by the hour at a negotiable gross rate".
Fair point. We do still want to get some more info about the applicants though, so I reworded it to "Please include a few lines about what relevant experiences you have for the respective position and, if available, a website or git platform account we could look at. We do not expect a full CV or other documentation."
Removed them now. The page is now called "Opportunities" instead of "Jobs".
@ -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>is pull requests really uppercased?
Made it lowercase
@ -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>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.
Yeah yeah that was a placeholder
@ -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>List of requirements:
Bonus:
Mentioning Lemmy explicitly is misleading. This is just another service TM.
Thanks, I will put these
@ -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>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.
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 ended up separating requirements from bonus points to keep consistency between the two open positions
Thanks for the reviews! I addressed the comments and tried to make compromises between the various opinions. Let me know if you like the new wordings.
Oh wait, I missed this. Yeah this makes sense. I put in the date "08.09.2025" for now, since I'll have a week of free time between 08 to 15 to handle applications. We can always postpone if we don't receive any application.
Add jobs pageto Add "Opportunities" page