You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2025-02-16-newpipe-0.27.6-rewrite-team-states.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Many PRs opened on the NewPipe repository share a common challenge: while author
33
33
34
34
The team is also lacking some **triaging manpower** to handle all of the issues and discussions that are opened on the repository. Despite this it is usually easy to identify new issues/regressions or pressing problems thanks to the active community, but it is much harder to distinguish old tickets that are useful from the niche ones.
35
35
36
-
I want to end this paragraph with a **call-to-action**: if you have some time and want to help, feel free to get in touch with us [on the Matrix channel](#conclusion-and-contact) and ask us for something to work on, and **we will give you indications**. When opening a Pull Request, make sure your proposal is not just a Proof-of-Concept, but **provide the best code you can write and highlight the areas that need more work**, so the team can review and merge the PR fast. If you want to learn modern Android development (Kotlin, Jetpack Compose, Hilt and other modern practices), working on the NewPipe rewrite might be a good *opportunity* for you, and the team members will be able to provide you with good guidance.
36
+
We want to end this paragraph with a **call-to-action**: if you have some time and want to help, feel free to get in touch with us [on the Matrix channel](#conclusion-and-contact) and ask us for something to work on, and **we will give you indications**. When opening a Pull Request, make sure your proposal is not just a Proof-of-Concept, but **provide the best code you can write and highlight the areas that need more work**, so the team can review and merge the PR fast. If you want to learn modern Android development (Kotlin, Jetpack Compose, Hilt and other modern practices), working on the NewPipe rewrite might be a good *opportunity* for you, and the team members will be able to provide you with good guidance.
37
37
38
38
With this said, we want to **deeply thank [all of the contributors]({{ site.baseurl }}/blog/pinned/announcement/State-of-the-Pipe-2023/#about-the-people-behind-newpipe)** that *opened a PR, fixed a bug, proposed a design, helped triaging an issue,* … You are clearly the best!
39
39
@@ -185,4 +185,4 @@ We sincerely **thank all people who have donated** to the NewPipe team and now t
185
185
186
186
## Conclusion and contact
187
187
188
-
In the name of the team, I would like to thank every contributor, triager, translator, tester, donor, and even every user that wrote us kind emails. The community around NewPipe is truly fantastic! If you wish to start contributing, you can reach out to us via Matrix [#newpipe:matrix.newpipe-ev.de](https://matrix.to/#/#newpipe:matrix.newpipe-ev.de) or IRC ([#newpipe on Libera.Chat](https://web.libera.chat/#newpipe)).
188
+
In the name of the team, we would like to thank every contributor, triager, translator, tester, donor, and even every user that wrote us kind emails. The community around NewPipe is truly fantastic! If you wish to start contributing, you can reach out to us via Matrix [#newpipe:matrix.newpipe-ev.de](https://matrix.to/#/#newpipe:matrix.newpipe-ev.de) or IRC ([#newpipe on Libera.Chat](https://web.libera.chat/#newpipe)).
0 commit comments