Skip to content

Commit c57abb2

Browse files
committed
Add post for hacktoberfest 2021
1 parent d7e916e commit c57abb2

File tree

1 file changed

+55
-0
lines changed

1 file changed

+55
-0
lines changed
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title: Hacktoberfest 2021
3+
layout: post
4+
---
5+
6+
Are you ready for Hacktoberfest 2021? Void Linux is! We're excited
7+
to be participating for our 5th year. Contributions that help to
8+
address our out-of-date packages queue are especially welcome. This
9+
is a great way to dip your feet into the world of Linux distro package
10+
management and what happens behind the scenes to provide a wide
11+
selection of packages and make sure your system remains up to date.
12+
13+
Updating packages is very easy. You can select a package from the
14+
list of [out of date
15+
packages](http://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt)
16+
and update it using the tools in the [void-packages
17+
repo](https://github.com/void-linux/void-packages). The
18+
[manual](https://github.com/void-linux/void-packages/blob/master/Manual.md)
19+
might be of assistance when you are updating packages.
20+
21+
As a general rule, we recommend that newcommers to the Void Linux
22+
project steer clear of "structural" packages unless you have specific
23+
domain knowledge that qualifies you to work on high-risk packages.
24+
When selecting a package to update, prefer packages registered to
25+
`orphan@voidlinux.org`. These packages are otherwise unmaintained,
26+
and your contribution will have a bigger impact. You can update
27+
packages that have a maintainer assigned, but understand that
28+
conflicting changes between a maintainer and contributor will be
29+
resolved at the discretion of Void staff.
30+
31+
Here are some useful tips when updating packages:
32+
33+
* While we're not completely opposed to PRs that add new packages,
34+
you're much more likely to get your PR approved and merged if it's
35+
a well written update.
36+
* Don't PR broken code. Our maintainers are much less likely to give
37+
a second look to a PR that didn't build when it was submitted.
38+
* While it's possible to run xbps-src from an alien distro, this
39+
isn't really supported. If you're a seasoned Linux user and want
40+
to try Void, now is the time!
41+
* The update list is sometimes wrong. We'd love to get patches that
42+
improve its reliability by [ignoring beta
43+
versions](https://github.com/void-linux/void-packages/blob/master/Manual.md#checking-for-new-upstream-releases)
44+
or adding checks to packages that are not correctly detected as
45+
out of date.
46+
* If you have expertise in C, GNU Autotools, or other build systems,
47+
taking a look at projects that we've marked as incompatible
48+
with cross compilation and fixing the upstream issue can be
49+
an amazing contribution that impacts more than just Void.
50+
51+
We look forward to working with the amazing world of open source
52+
developers this month to improve Void and continue our high standards
53+
for quality and reliability. To ensure your PR has the best chance at
54+
being accepted, feel free to reach out for help as explained in the
55+
manual. Together, we can make this a high-impact Hacktoberfest.

0 commit comments

Comments
 (0)