Void Linux discussion
 help / color / mirror / Atom feed
From: Kai Stian Olstad <void+list@olstad.com>
To: voidlinux@googlegroups.com
Subject: Re: contributing back to voidlinux
Date: Sat, 24 Aug 2019 15:12:49 +0200	[thread overview]
Message-ID: <59e3d5d65019af636576a7e21def9fa9@olstad.com> (raw)
In-Reply-To: <87v9umvlch.fsf@disroot.org>

On 24.08.2019 13:41, Lugubris wrote:
> How can I contribute back to voidlinux?

Time in the sense of writing docs and create/update packages.


> I would help by managing a few packages, is there a quick guide for
> that?

A good start is
https://github.com/void-linux/void-packages/

That has the following links
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md
https://github.com/void-linux/void-packages/blob/master/Manual.md


> Note that this is my first time trying to contribute back, also I don't
> have much knowledge on how linux packages work but I can look for
> updates from upstream and update the void repo when upstream marks as
> stable if thats easy enough.

It require a little more involvement than that, you should at a minimum 
be able build the packages on your own machine.
But if you read the above documentation you will learn how to do that 
and then the path to Void packaging is not that difficult.


-- 
Kai Stian Olstad

-- 
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/59e3d5d65019af636576a7e21def9fa9%40olstad.com.

  reply	other threads:[~2019-08-24 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-24 11:41 Lugubris
2019-08-24 13:12 ` Kai Stian Olstad [this message]
2019-08-24 15:29   ` Lugubris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=59e3d5d65019af636576a7e21def9fa9@olstad.com \
    --to=void+list@olstad.com \
    --cc=voidlinux@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).