proot-me / blog

PRoot Developer Blog
https://proot-me.github.io/blog
8 stars 2 forks source link

Questionnaire for offering software to GNU #4

Closed oxr463 closed 3 years ago

oxr463 commented 4 years ago

General Information

Do you agree to follow GNU policies? Yes.

If your program is accepted to be part of the GNU system, it means that you become a GNU maintainer, which in turn means that you will need to follow GNU policies in regards to that GNU program. (Summarized above, see maintainers document for full descriptions.)

Package name and version: PRoot v5.2.0-alpha

https://github.com/proot-me/proot/releases/tag/v5.2.0-alpha

Author Full Name : Cédric VINCENT cedric.vincent@st.com

https://raw.githubusercontent.com/proot-me/proot/master/AUTHORS

URL to package home page (if any):

https://proot-me.github.io

URL to source tarball:

Please make a release tarball for purposes of evaluation, whether
or not you publicly release it.  If you don't have
anywhere to upload it, send it as an attachment.

https://github.com/proot-me/proot/archive/v5.2.0-alpha.tar.gz

Brief description of the package:

chroot, mount --bind, and binfmt_misc without privilege/setup for GNU/Linux

Code

Dependencies:

Please list the package's dependencies (source language, libraries, etc.).

Configuration, building, installation:

It might or might not use Autoconf/Automake, but it must meet GNU
standards.  Even packages that do not require compilation
must follow these standards, so installers have a uniform way to
define target directories, etc.  Please see:
http://www.gnu.org/prep/standards/html_node/Configuration.html
http://www.gnu.org/prep/standards/html_node/Makefile-Conventions.html

Documentation:

We require using Texinfo (http://www.gnu.org/software/texinfo/)
for documentation, and recommend writing both reference and tutorial
information in the same manual.  Please see
http://www.gnu.org/prep/standards/html_node/GNU-Manuals.html

Internationalization:

If your package has any user-visible strings, please make them
translatable to other languages using GNU Gettext:
http://www.gnu.org/software/gettext/

TODO

Accessibility:

Please discuss any accessibility issues
with your package, such as use of relevant APIs.

Security:

Please discuss any possible security issues with your package:
cryptographic algorithms being used, sensitive data being stored,
possible elevation of privileges, etc.

Licensing:

Both the software itself and all dependencies (third-party libraries, etc.) must be free software in order to be included in GNU. In general, official GNU software should be released under the GNU GPL version 3 or any later version, and GNU documentation should be released under the GNU FDL version 1.3 or any later version.

Please see http://www.gnu.org/philosophy/license-list.html for a practical guide to which licenses are free (for GNU's purposes) and which are not. Please give specific url's to any licenses involved that are not listed on that page.

https://raw.githubusercontent.com/proot-me/proot/master/COPYING

Similar free software projects:

Please explain what motivated you to write your package, and search at least the Free Software Directory (http://www.gnu.org/directory/) for projects similar to yours. If any exist, please also explain what the principal differences are.

N/A - none that I could find.

Any other information, comments, or questions:

Again, please email the questionnaire to gnueval@gnu.org when it is done.

Source: https://www.gnu.org/help/evaluation.html

See: https://directory.fsf.org/wiki/Proot

oxr463 commented 4 years ago

I believe PRoot should become part of coreutils if possible, right along with chroot.

katakombi commented 4 years ago

That would be amazing! :)