diff options
author | Ask Solem <askh@opera.com> | 2009-11-10 16:20:47 +0100 |
---|---|---|
committer | Ask Solem Hoel <ask@0x61736b.net> | 2009-11-10 16:20:47 +0100 |
commit | ea4d288ddeaf3b06e2a0781d3037660de8f36bb3 (patch) | |
tree | bffe532057b4005f1bfeee619d1f781c7ca222c2 | |
parent | 637bcbfa9a59f601761eb7df437ebb79fea80fb9 (diff) | |
download | chishop-ea4d288ddeaf3b06e2a0781d3037660de8f36bb3.tar.bz2 chishop-ea4d288ddeaf3b06e2a0781d3037660de8f36bb3.tar.xz chishop-ea4d288ddeaf3b06e2a0781d3037660de8f36bb3.zip |
Updated TODO with some features that PyPI has (more wanted!)
-rw-r--r-- | TODO | 58 |
1 files changed, 49 insertions, 9 deletions
@@ -1,12 +1,52 @@ | |||
1 | * Write a tutorial on how to set up the server, registering projects, and | 1 | PyPI feature replication |
2 | how to upload releases. | 2 | ======================== |
3 | |||
3 | * Make it possible to register users via distutils. | 4 | * Make it possible to register users via distutils. |
4 | (There should be a setting to turn this feature on/off). | 5 | There should be a setting to turn this feature on/off for private PyPIs. |
5 | * Add a pretty, user-friendly web site interface in addition to | 6 | [taken-by: sverrej] |
6 | the API interface. | 7 | |
7 | * Maybe add a permission "can upload new release", so more than one | 8 | * Roles (co-owners/maintainers) |
8 | user can change the same project. | ||
9 | * Should a project have co-owners? | ||
10 | - One possible solution: | 9 | - One possible solution: |
11 | http://github.com/initcrash/django-object-permissions/tree | 10 | http://github.com/initcrash/django-object-permissions/tree |
12 | 11 | I'm not sure what the difference between a co-owner and maintainer is, | |
12 | maybe it's just a label. | ||
13 | * Package author admin interface (submit, edit, view) | ||
14 | * Search | ||
15 | * Documentation upload | ||
16 | * Ratings | ||
17 | * Random Monty Python quotes :-) | ||
18 | * Comments :-) | ||
19 | |||
20 | Post-PyPI | ||
21 | ========= | ||
22 | |||
23 | * PEP-381: Mirroring infrastructure for PyPI | ||
24 | [taken-by: jezdez] | ||
25 | |||
26 | * API to submit test reports for smoke test bots. Like CPAN Testers. | ||
27 | Platform/version/matrix etc. | ||
28 | |||
29 | * Different listings: Author listings, classifier listings, etc. | ||
30 | |||
31 | * Search metadata | ||
32 | |||
33 | * Automatic generation of Sphinx for modules (so you can view them directly | ||
34 | on pypi, like CPAN), Module listing etc. | ||
35 | |||
36 | * Listing of special files: README, LICENSE, Changefile/Changes, TODO, | ||
37 | MANIFEST. | ||
38 | |||
39 | * Dependency graphs. | ||
40 | |||
41 | * Package file browser (like CPAN) | ||
42 | |||
43 | |||
44 | |||
45 | |||
46 | Documentation | ||
47 | ============= | ||
48 | |||
49 | * Write a tutorial on how to set up the server, registering projects, and | ||
50 | how to upload releases. | ||
51 | |||
52 | |||