Archive for Processing is an (unofficial) archive of resources for the Processing community. It collects software related to Processing, p5.js, Python mode / Processing.py, p5py, pyp5js, R Mode / Processing.R, and other related languages, modes, libraries, and tools.
The project is intended to make the distributed ecosystem of open source libraries, modes, tools, example sets, and documentation a bit more robust. It does this by acting as a fallback, providing simple redundancy via a list of forked GitHub repositories and offline backup for distributed binaries. These forks and binary backups are to help guard against future project loss. In particular, given that many of the core open source resources of the Processing community are generously self-hosted by their contributing authors, the archive attempt to keep such works available even if their associated accounts, websites, et cetera are no longer maintained.
Archive for Processing may also serve as a list / index for browsing the amazing variety of Processing resources. However, this is an infrequently updated archive, not a directory – it is not comprehensive. More importantly, it is not a live mirror! Always use original official author repositories whenever available.
This GitHub organization account approaches this goal in the following ways:
-
Forks:
- Maintain a list of forks of public GitHub repositories.
- The forks are browseable from the github organization page:
https://github.com/archive-for-processing - For projects under development or maintainence, the forks
are periodically updated to their latest master commit. - To recommend a fork, open an issue on this repo: https://github.com/archive-for-processing/archive-for-processing
-
Contributions
-
Libraries, Tools, and Modes disseminated through the PDE
Contributions Manager periodically have their metadata
with pointers to the latest properties files and download URLs
backed up to the /data branch of this repo: https://github.com/archive-for-processing/archive-for-processing -
Binaries are periodically backed up offline. These files
are not distributed through GitHub, but are archived in case
an old release is lost.
-
The archive contains both inactive and active projects – it includes forks of ongoing, under-development repositories.