Ideas
Ideas for ongoing Plone development.
- Conference object or standardized Folder of objects (Plone Lineage, Example)
- Plenary lecture object (photo, bio, abstract, slides, video, event details Example)
- Motion/Discussion/Vote object for Committees and Chapters (Plone Survey?)
- Terms and Conditions acceptance (similar to Drupal Legal module)
- Initial registration
- Upon first login after T&C are updated
- Mail integration
- Content rules so that PeopleList members get email when an item is added to specific folder (to invite discussion)
- Mailing lists from and within PeopleLists (Plone Listen?)
- Auto-generate a News and Events summary for email distribution (Plone Gazette?)
- LaTeX syntax support in text, titles, comments, etc. (KSS jsMath?)
- Paper submission, review, preprint, & discussion system
- Integrate functionality of multiple existing websites
- Pareja (current IT Society paper submission and review)
- Manuscript Central (related system used by many IEEE Societies)
- High-level requirements of Publication Committee
- arXiv (timestamps, preprint)
- Allow paper discussion, preferably with mathematics support (see LaTeX above)
- Be nice to unify journal, conference, and newsletter submission and review process
- Process for structuring conference and workshop websites (non-Plone) for import into Plone
- Capability to add users in batches (group additions) and to add people to PeopleLists in batches.
Call for Nominations - 2013 Marconi Prize
fancier profile registration
For the sparse users, can we encourage them to put a little more content? For the dense users, can we get them to input data about themselves like past AE status, committee memberships, etc, so that we can just approve an autolink?
Perhaps we can give them a drop-down list of committees or chapters and they can select which ones they belong to? We could make that required to register which should affect both sparse and dense.