@panicbit @jyn514 I would gladly assign either of you maintainer access for this rust implementation. I am currently the only "active" maintainer and to be honest, I barely have bandwidth for the main implementation.

Originally posted by @oxr463 in https://github.com/proot-me/proot-rs/issue_comments/708418138

See: https://meta.stackoverflow.com/a/394443/8507637

Need to find new maintainers / committers and keep this project going.

See: https://www.notion.so/proot-rs-fcb41901ad534a23b83352d6f14d612a

See: https://hub.docker.com/u/proot

The testsuite needs lots of love, but for now, here are some steps to add a new test.

There are more than one type of test, compiled tests written in c, or shell scripts.

Also, if you take a peek at test/GNUmakefile, you will see some tests are hard-coded in there for some reason.

I recently added test/test-python01.sh, so you can use that one as a proper example.

See also: proot-me/proot#164

author: {{author}}
date: {{date}}

{{title}}

{{section}}

Reference

See Also

Organizations

Applications open January 14, 2020 at 14:00 (Eastern Standard Time)

• Mentor organizations must run an active open source or free software project.
• Have produced and released software under an OSI approved license.
• Must not be based in a country currently embargoed by the United States.

Source: https://summerofcode.withgoogle.com/terms/org

See also: https://google.github.io/gsocguides/mentor/notes-for-first-year-organizations

• First Contributions, (See: firstcontributions/firstcontributions.github.io#219)
• Up For Grabs, (See: up-for-grabs/up-for-grabs.net#2960)
• Edit Recruiting Page

• Command-line interface
• Loader, (See: https://github.com/proot-me/proot/blob/master/doc/proot/changelog.rst#release-v500)
• Extension(s)

Reference(s):

• https://www.wikihow.com/Write-a-Technical-Specification
• https://www.nescode.com/blog/how-write-technical-specification-document

See: https://www.mkdocs.org/user-guide/configuration/#nav

• Copy into blog repository
• Delete from source repository

Source: https://github.com/proot-me/proot/blob/master/doc/articles/

See: proot-me/proot#134 (comment)

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 [email protected]

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 [email protected] when it is done.

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

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

The workflow main.yml is referencing action peaceiris/actions-gh-pages using references v2. However this reference is missing the commit d2178821cb5968f5b7c818210297f3dbeea3114c which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

A project to get a Linux shell running on iOS, using usermode x86 emulation and syscall translation.
https://github.com/tbodt/ish

See also: proot-me/proot#81, proot-me/proot#155

• Add to timeline
• Update post with results

I think it would be ideal to create a blog post describing the current state of PRoot i.e. the transition of maintainership from the original author, and the issues faced by the current maintainers leading to the large gap since the last release.

See also: proot-me/proot#157

--

https://github.com/proot-me/proot/blob/master/doc/proot/changelog.txt