Below is an overview of the GPII mailing lists. These are public and free for anyone to join. They are topic oriented lists and should be used for day to day communication, discussions, announcements and technical jibber jabber.
For confidential information, project management and internal announcements, please use the other means (For the Cloud4All project, use the SP lists).
Anything related to the general architecture of GPII. This includes security, storage, protocols, APIs, the general architecture framework.
- List: email@example.com:
- Sign up: http://lists.gpii.net/cgi-bin/mailman/listinfo/architecture
- Archive: http://lists.gpii.net/pipermail/architecture/
firstname.lastname@example.org: Anything related to preferences and profiles. This includes standards work, sample/personal profiles, preferences, matchmaker, meta-data. To sign up, go to: http://lists.gpii.net/cgi-bin/mailman/listinfo/profiles email@example.com: Relevant anybody who is creating and/or distributing products compatible with GPII/Cloud4All products and services – free and open source, commercial and proprietary. This includes SP3 of the C4A project and work on the Settings and Launch Handlers. To sign up, go to: http://lists.gpii.net/cgi-bin/mailman/listinfo/vendors firstname.lastname@example.org: Unified Listing and Marketplace. Subjects related to a federation of repositories of solutions and components, unified listing of AT, and the GPII Market Place. To sign up, go to: http://lists.gpii.net/cgi-bin/mailman/listinfo/ulist email@example.com: Developer Space. While not directly related to Cloud4All, this is part of GPII and I thought I mention it here as well. The Developer Space will be a compilation of parts, tools, frameworks and resources for developers to help and lower cost in development of AT. Everything related to this goes on this list. To sign up, go to: http://lists.gpii.net/cgi-bin/mailman/listinfo/dspace
As mentioned in a previous mail: Ad-hoc lists can be created for heavy discussions to offload a topic list. It should be clear what topic list the ad-hoc list is a sub-topic of. Creation of ad-hoc lists should be reported on main topic list and once the ad-hoc list is done, its conclusions should be reported back to the main topic list. Google groups can be used, or the creation of an @lists.gpii.net list can be requested from Kasper Markus (Raising The Floor) or Colin Clark (IDRC).