This sounds like a good idea. I generally ask that new contributors go
through the freedos-devel list before they get added to the software list,
but I've generally been more loose with putting stuff on our ibiblio
archive. It would be great to have a more formal process for what to
include there.
Can I add two other suggestions, at risk of expanding the scope?
- I've taken an interest over the last year to go through the software list
and the ibiblio archive, and prune out any non-free software (programs
without source, licenses that limit source code reuse, etc). But i haven't
had the time I hoped to do all of that. This would be a good opportunity to
get help. If you find programs on the ibiblio archive that you think don't
belong, please post it on the list here so we can review it.
- What programming languages should we expect new contributors to use? The
FreeDOS Spec already says C or ASM for programs in Base, and is less strict
for non-Base programs. The reason is we want Base programs to be broadly
supportable by many developers, so we wanted programming languages most
people would use. Is that still the right distinction? (I think yes.)
jh
On Jan 24, 2015 12:39 PM, "Michael Brutman" <mbbrut...@brutman.com> wrote:
>
> 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.
>
>
> Mike
>
>
> ------------------------------------------------------------------------------
> 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
