From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Fwd: Update-Accelerator 3.0
Date: Tue, 05 Mar 2013 16:43:35 +0100 [thread overview]
Message-ID: <1362498215.13156.30.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <CAAiW7AfQYZbOPeaO73Q-1vnOWzRLZtW7VXvZ_QKi-cv2LYmhBQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2134 bytes --]
Hello,
On Tue, 2013-03-05 at 13:50 +0100, Jörn-Ingo Weigert wrote:
> @Devel: You are also welcome to share some ideas for upcoming version
> of update-accelerator
Here is an idea from me: I would like to rename "Update Accelerator",
because:
* It is hard to spell and a lot of people mispronounce it.
* It is a very long word. That's not only inconvenient to type but also
bloats navigation bars and so on.
* It really does not make clear what the software does, because it does
not accelerate the download of an update (at least not in the first
place), so it would be better to use the word "cache" here.
* If we enhance the functionality it won't be limited to "updates",
so that won't fit anymore either.
* We don't want to confuse it with the piece of software that is an
add-on for IPCop.
I could even find more reasons, but I couldn't find a name which is
better so far.
> Hello Fajar,
>
> I would like to say hello and get in contact with you.
>
> Michael from IPFire.org told me that you may have some requirements or
> ideas for an improved update accelerator, cause we plan to extend the
> current version (at this point it look like a complete rewrite o_O)
>
> So how is your current situation?
> It would be great if you can give some details of your current system,
> your users, for what you use the update accelerator, the kind of files
> you currently store and the space it currently used.
>
> What could be improved or changed in an upcoming version?
> What is disturbing you at moment?
>
> To share the ideas & requirements I've added a Wiki-Page on
> wiki.ipfire.org, where Ideas & current problems could be shared URL:
> http://wiki.ipfire.org/en/development/update-accelerator
Please move this to the "new" development area over here:
http://wiki.ipfire.org/devel/proxy/update-accelerator
The pages in /en/development are pretty outdated or wrong. We also
wanted to move the development stuff away from the part of the wiki that
is translated, because development documentation is not worth the
translation because of the limited amount of people who are reading it.
-Michael
next prev parent reply other threads:[~2013-03-05 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAiW7AfumUceBaNypjgWy0bTpV6UWQvWYHg5N=5-CyfrNS6UDA@mail.gmail.com>
2013-03-05 12:50 ` Jörn-Ingo Weigert
2013-03-05 15:43 ` Michael Tremer [this message]
2013-03-05 15:53 ` Jörn-Ingo Weigert
[not found] <CAEpw26XnNz3QfZskeE0E-ugKYZU9ArzKkejD6w2DU+fFqFhnrw@mail.gmail.com>
2013-03-06 22:03 ` Michael Tremer
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=1362498215.13156.30.camel@rice-oxley.tremer.info \
--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