From: Stefan Schantl <stefan.schantl@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] New Addon list
Date: Sat, 14 Jul 2012 12:58:33 +0200 [thread overview]
Message-ID: <500150D9.4060105@ipfire.org> (raw)
In-Reply-To: <85BF56FD-BEED-40D8-86F5-C7EC30AF36C2@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]
Hello Erik,
thanks for the hard work while writing these list.
But I think it is not a good idea to put the current ( upstream )
versions into this list, because it could be really difficult to keep
these list up to date.
Best wishes,
Stefan
> Hi all,
> i have completed now the list , also with the testing addons --> http://wiki.ipfire.org/nonpublic/addons/start so may it could substitute the existing one --> http://wiki.ipfire.org/de/addons/all. May it´s a lot of stress to hold this list up to date but may there are some ideas to change the criterias to make things easier, or are there some people who want to maintain this on ;-) ?
>
> Greetings
>
> Erik
>
> P.S. So may this is useless but i thought it can be also a good idea. Some response might be nice.
>
> Am 10.07.2012 um 13:22 schrieb Erik K.:
>
>> Hi all,
>> i was thinking about to create a addon list where all addons are listed (stable and testing). So there can be different criterias for example IPFire´s version number and the actual version number of the software (update needed ?), are there some wiki articles for this piece of software, the homepage of the software producers.
>>
>> So i have started this side in here --> http://wiki.ipfire.org/nonpublic/addons/start . It isn´t finished until now and i think this will take a little to list all addons.
>>
>> I have counted 118 Addons in stable and 28 in the testing tree. A lot of stuff meanwhile :-) but there are onyl ~ 60 Addons in the wiki explained. So to give some better background infos some links to the originated software developer and above all a list to overview the actual portfolio i thought this can be an idea.
>>
>> What do you think about this idea ? Do you have suggestions ?
>>
>> Greetings
>>
>> Erik
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
>
next prev parent reply other threads:[~2012-07-14 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 11:22 Erik K.
2012-07-14 9:43 ` Erik K.
2012-07-14 10:58 ` Stefan Schantl [this message]
2012-07-14 12:09 ` Erik K.
2012-07-14 12:21 ` Stefan Schantl
2012-07-14 12:24 ` Erik K.
2012-07-14 14:40 ` Erik K.
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=500150D9.4060105@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=documentation@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