I was trying to be more sensitive than to use "crapware", but yes, I
understand.
I think that for something to be included it needs to have the correct
license, it needs to do what it says it does, it needs to be of some value
to a larger audience and not just fill a small niche. And I'm also
suggesting that we start looking at the code in more detail. Not
everything "first timer" project should be automatically included;
something should prove itself to be valuable first.
There are going to need to be some judgement calls made about what gets in
and what does not. A "no" might be due to duplication, too small of a
niche, etc. It does not prevent somebody from continuing their project.
I'm willing to do code reviews to help make this happen. I've learned
quite a bit over the years on my projects and I want to help feed that
back. But this only works if there is a pool of us.
Mike
On Sat, Jan 24, 2015 at 11:36 AM, Tom Ehlert <t...@drivesnapshot.de> wrote:
>
>
> while I am in general agreement with you, reality behaves different.
> your proposal is about as likely to occur as commercial grade
> FreeDOS-64. in other words: it won't happen. ever.
>
> > I think we need a vetting process for new software that developers
> > want to include with FreeDOS. I'm glad that people are asking to be
> > included, but there is a certain level of review that we should be doing.
>
> > - The source code should be reviewed for obvious problems; back
> > doors and security problems, unsafe code that might trash files, etc.
>
>
> > - The program should do what it advertises to do. As an example,
> > an encryption program should provide a reasonable level of
> > encryption. (No code based on a simplistic cipher should be allowed to
> call itself "encryption.")
>
>
> > - The build environment and instructions should be fully explained
> > so that others can easily rebuild and verify the executable.
>
> > If we get enough volunteers to review code that becomes a great way
> > to pass down the tribal knowledge.
>
> > It would also help to ensure
> > that the FreeDOS repositories do not become a new form of wild and crazy
> shareware library.
>
> the word you were searching for is crapware.
>
> shareware was a way for small developers to distribute their software
> *product*, often professional developed software of high quality and
> shouldn't be confused with 'my first program'.
> successful programs were PKZIP, RAR, and a couple others.
>
> actually most modern software is distributed as shareware (try first,
> buy if happy).
>
> Tom
>
>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
