Agora Octave: Difference between revisions
Jump to navigation
Jump to search
Fgnievinski (talk | contribs) No edit summary |
(Add Category:Outdated pages.) |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
'''Agora''' | {{Warning|This page is outdated (September 2018).}} | ||
'''Agora Octave''' is a place dedicated for rapid collaboration related to GNU Octave and distribution of community contributed code and packages. You can browse code submissions or contribute your own. | |||
== Features (desired) == | == Features (desired) == | ||
| Line 8: | Line 10: | ||
* Tags and Flags. Is [https://docs.djangoproject.com/en/dev/howto/custom-template-tags/ this] what we want? | * Tags and Flags. Is [https://docs.djangoproject.com/en/dev/howto/custom-template-tags/ this] what we want? | ||
* Download counts. | * Download counts. | ||
You can upload your code to Agora. The code is classified according the following criteria. | |||
* Single file | |||
:: The file is full responsibility of the uploader. | |||
:: Octave and Agora do not check or support this submissions. | |||
* Bundle of files | |||
:: The file(s) is(are) full responsibility of the uploader. | |||
:: The bundle passes a structure check to see if it is compatible with the builtin Octave installer. This doesn't mean the bundle with install flawlessly. | |||
:: Octave and Agora do not check or support this submissions. | |||
* Forge | |||
:: The file(s) is(are) responsibility of its maintainer and the Agora maintainers community. | |||
:: This package will install using the builtin Octave installer. | |||
[[File:agora.png|center|380px]] | |||
The Forge packages have must comply with | |||
* At least one package maintainer. | |||
* Must install and work with the latest Octave release. | |||
* The must be released under a [http://en.wikipedia.org/wiki/List_of_FSF-approved_software_licenses GPL compatible] license. | |||
* All functions (except private ones) must be documented using [http://en.wikipedia.org/wiki/Texinfo Texinfo]. | |||
* The package must have all the [http://www.gnu.org/software/octave/doc/interpreter/Creating-Packages.html#Creating-Packages required files]. | |||
* If the package has a doc folder it should be written in [http://en.wikipedia.org/wiki/Texinfo Texinfo]. | |||
These packages are also recommended to comply with | |||
* No shadowing of Octave core functions. | |||
* No direct inclusion of external dependencies. | |||
== See also == | == See also == | ||
* [[Octave | * [[Octave Forge]] | ||
== Further reading == | == Further reading == | ||
| Line 17: | Line 49: | ||
== External links == | == External links == | ||
[http://agora.octave.org/ Agora website] | * [http://agora.octave.org/ Agora website] | ||
[[Category: | [[Category:Outdated pages]] | ||
Latest revision as of 01:45, 17 October 2019
This page is outdated (September 2018).
Agora Octave is a place dedicated for rapid collaboration related to GNU Octave and distribution of community contributed code and packages. You can browse code submissions or contribute your own.
Features (desired)[edit]
- User account. ✔
- User profile. ✔
- User ratings.
- Comments.
- Tags and Flags. Is this what we want?
- Download counts.
You can upload your code to Agora. The code is classified according the following criteria.
- Single file
- The file is full responsibility of the uploader.
- Octave and Agora do not check or support this submissions.
- Bundle of files
- The file(s) is(are) full responsibility of the uploader.
- The bundle passes a structure check to see if it is compatible with the builtin Octave installer. This doesn't mean the bundle with install flawlessly.
- Octave and Agora do not check or support this submissions.
- Forge
- The file(s) is(are) responsibility of its maintainer and the Agora maintainers community.
- This package will install using the builtin Octave installer.
The Forge packages have must comply with
- At least one package maintainer.
- Must install and work with the latest Octave release.
- The must be released under a GPL compatible license.
- All functions (except private ones) must be documented using Texinfo.
- The package must have all the required files.
- If the package has a doc folder it should be written in Texinfo.
These packages are also recommended to comply with
- No shadowing of Octave core functions.
- No direct inclusion of external dependencies.
See also[edit]
Further reading[edit]
- Django Upload files
- a good read when thinking about this, is a Zen of Comprehensive Archive Networks with some afterthoughts on the the design of CPAN. I think that an important thing to learn is to get something as simple as an anonymous FTP server working.