django-committees
- author:
Colin Powell
- date:
2011-02-19
- by:
One Cardinal Web Development
- license:
GPLv3
A simple pluggable django application for managing documents in a small not-for-profit organization.
At a small organization, we have a governing board, composed of variable-length termed seats, term limits, alternate members, offices: a president, vice president, secretary and treasurer. The rest of the governing is done via committees, wether standing or ad-hoc. The whole government is governed by bylaws and policies. This app should organize all these elements in one place for reference.
Models
TERM_LIMIT=2
- BoardOffice (Pres, vp, sec, at-large, alternate, ex-officio…)
title
slug
description
officer?
officer_rank (INT)
- BoardTerm
start_date
end_date
office (Office)
- BoardMember
Person (Profile)
Term (BoardTerm)
- Meeting
Event
Minutes
Members (BoardMember)
Guests (VarChar)
Adjourn
- BoardMeeting (Meeting)
Agenda
- Minutes
Meeting
Draft?
Content
Attachment
- CommitteeMember
Person
- Committee
title
description
chairs
members (CommitteeMember)
reports
- CommitteeTerm
start_date
end_date
committee
- Report
Date
Content
Author (Person)
URLs
Just an example hook up spot:
view: index = government/ - index to show gov. board, committees, latest meetings/minutes view: board_detail = government/board/ - detail of board make-up, past boards and minutes/meetings view: board_meeting_detail = government/meetings/<year>/<month>/ - detail of a meeting with minutes, members, etc. view: committee_list = government/committees/ - list of all committees and membership view: committee_detail = government/committees/<slug> - detail of one committee view: report_list = government/reports/<year>/<month>/<committee_slug> view: meeting_list = government/meetings/ - list of all meetings in the system
Metadata
Release files for django-committees 1.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-committees-1.1.3.tar.gz | 10.9 kB | Without provenance | Details for django-committees-1.1.3.tar.gz |
Release files / django-committees-1.1.3.tar.gz
| Download URL | django-committees-1.1.3.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
790a174f7847f03c8d4faecc5b0cf565094ee6063edc04a6282fe2b345343176
|
|
BLAKE2b-256 checksum How to use checksums |
78718920d39ca206af4c83494c551df270808c83749400ece805cbf2c5057ae9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-committees 1.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.