public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Contributing to IPFire by working on bugs
Date: Fri, 20 Mar 2020 16:02:29 +0000	[thread overview]
Message-ID: <3B0C6222-9459-46BF-980F-06ABCBFBAB9B@ipfire.org> (raw)
In-Reply-To: <cf4853d2-584b-cce5-cda6-6fa8f63183b4@md5collisions.eu>

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

Hello Stephan,

> On 20 Mar 2020, at 15:25, List <list(a)md5collisions.eu> wrote:
> 
> Hello *,
> 
> I was hoping to be able to start contributing to IPFire by resolving
> some bugs.

Yes! A very warm welcome. We got loads of those for you to find and fix :)

> How do newcomers do that ?
> 
> Do I need a bugzilla account ?
> 
> (https://bugzilla.readthedocs.io/en/5.0/using/creating-an-account.html)
> 
> The documentation requires me to visit the homepage and create a new
> account. Which is not possible.

We have a central account system that everything is using. Hence direct registration in Bugzilla is disabled. Unfortunately the documentation is default and cannot be easily changed.

If you did not already do so, please register on people.ipfire.org: https://people.ipfire.org/register

https://blog.ipfire.org/post/the-new-ipfire-community-portal

And on what to work on, here is a starter:

https://blog.ipfire.org/post/good-first-bugs

> It is pretty much plausible that I am just being blind. Could you help
> me out here ?

Please get in touch if you have any further questions!

Best,
-Michael

> 
> I'd really appreciate it.
> 
> Thanks for you time.
> 
> 
> Best regards,
> 
> Stephan
> 
> 


  reply	other threads:[~2020-03-20 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 15:25 List
2020-03-20 16:02 ` Michael Tremer [this message]
2020-03-20 17:23   ` List

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=3B0C6222-9459-46BF-980F-06ABCBFBAB9B@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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