|
Size: 1495
Comment: contribulyzer is needed to give proper credits to even small enhancements
|
Size: 1850
Comment: sharing my notes to find a team - online docs editor depending on centralized loging and moderation queue
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 24: | Line 24: |
| * (medium) centralized login.python.org [[http://code.google.com/p/rainforce/wiki/CentralizedLogin|spec]] - open (techtonik) == Documentation == * (medium) Online editor for Docs - open * depends on centralized login above * need to implement [[http://code.google.com/p/rainforce/wiki/CentralizedLogin|ModerationQueue]] for anonymous users |
This page lists major tasks and goals for enhancing *.python.org infrastructure along with their status. The page should be similar to this one or at least this one. If you have questions about tasks or their status - ask owner or try #pydotorg IRC channel. If we succeed in organizing our efforts around enhancing *.python.org services, then this page can be extended to cover core Python Development as well.
Legend
Task status description:
open: no one has claimed this task yet or the task has not been started
wip: work-in-progress; someone has claimed/started this task
done: task is finished
Additional tasks can be found on our SiteImprovements page.
Generic
- (high) Split Python codebase into modules for independent development - open (techtonik)
- convenient way for interested parties to subscribe and monitor information related to one module
- bugs
- code repository - ! (several views)
- use cases - !
- discussions
- drafts (wiki, google wave)
- documentation
- convenient way for interested parties to subscribe and monitor information related to one module
- (high) contribulyzer similar to used in Subversion community - open
(medium) centralized login.python.org spec - open (techtonik)
Documentation
- (medium) Online editor for Docs - open
- depends on centralized login above
need to implement ModerationQueue for anonymous users