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: Captive Portal
Date: Fri, 06 Oct 2017 11:30:48 +0100	[thread overview]
Message-ID: <1507285848.433.44.camel@ipfire.org> (raw)
In-Reply-To: <c485d598-b188-9b09-9d6a-ff51afb4fc3e@ipfire.org>

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

Hey,

thanks for those feature suggestions. Could you create tickets and maybe Alex
can have a look what he can implement? I am quite sure that none of it is a
must-have for the first release, so this won't delay the release.

-Michael

On Fri, 2017-10-06 at 09:11 +0200, Daniel Weismüller wrote:
> Another wish ;-)
> 
> It would be fine if it were possible to edit the remarks.
> Especially if you use "Terms & Conditions" there is no way to left a remark.
> Maybe we could autofil the remark with the hostname of the machine.
> 
> -
> Daniel
> 
> Am 24.09.2017 um 21:26 schrieb Michael Tremer:
> > Hi,
> > 
> > the captive portal development needs a few more hands.
> > 
> > Below you can download the latest ISO image (and other image formats) with
> > the
> > captive portal integrated. So far this seems to work fine. I have given it a
> > good test and despite a few design things, I couldn't find any bigger
> > issues.
> > 
> >    http://people.ipfire.org/~ms/captive-portal/
> > 
> > Who would like to give it a try and help testing so that we can ship this
> > with
> > 115?
> > 
> > Best,
> > -Michael
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-10-06 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-24 19:26 Michael Tremer
2017-10-06  6:53 ` Daniel Weismüller
2017-10-06  7:11 ` Daniel Weismüller
2017-10-06 10:30   ` Michael Tremer [this message]

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=1507285848.433.44.camel@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