public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Suggest fixes / patches
Date: Tue, 08 Mar 2022 12:29:12 +0100	[thread overview]
Message-ID: <be3ce29d427ec40421f447c7b897324a8107e9ee.camel@ipfire.org> (raw)
In-Reply-To: <001e01d82a7d$50b1ae50$f2150af0$@gmail.com>

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

Hi Stephane,

first welcome to this part of the project :-). The webinterface
definitely needs some love. So every contribution there is very
welcomed :-)

Regarding your contribution on GitHub
https://github.com/ipfire/ipfire-2.x/pull/69 this is was not the right
method. That's absolutely does not hurt as our documentation might be a
little bit unclear here. 

To improve this and to give you and any bode else an easier start, I
wrote some short Readme. This can be found here:

https://patchwork.ipfire.org/project/ipfire/patch/20220308111824.4967-1-jonatan.schlag(a)ipfire.org/

I hope it ends up in the repository soon, that on GitHub it is more
clear how we accept contributions. To support that I kindly ask you if
you could review this patch and add a comment if it makes our process
more clear to you?

Thanks in advance.

Best Regards

Jonatan


Am Freitag, dem 25.02.2022 um 20:24 +0100 schrieb Steph78630:
> Hi all,
>  
> already a user and contributor for the French translation of IPFire,
> I would now like to propose patches / work to improve the interface.
>  
> Not being used to this approach, I hope to use the right method...
>  
> I thank you in advance for your support and advice.
>  
>  
> Best regards, Stephane
>  



           reply	other threads:[~2022-03-08 11:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <001e01d82a7d$50b1ae50$f2150af0$@gmail.com>]

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=be3ce29d427ec40421f447c7b897324a8107e9ee.camel@ipfire.org \
    --to=jonatan.schlag@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