Introduction
A hub for information about the service options and deployments for Plone, with content types for:
Case studies
Service providers
Sites-that-use-Plone
Buzz (ie, public-focused mentions of Plone in media, etc.)
Potentially others, such as user groups and training announcements
Requires
Plone 4+
Recommended
If you are using this product to develop plone.net, you’ll also want to download the Plone.net theme
PloneNetTheme, http://svn.plone.org/svn/collective/PloneNetTheme/trunk/
Translation
Currently supports the following translations:
Spanish.
Historical
Code was originally designed and implemented for the successful, but now defunct plone.net. Plone.net was folded back in to plone.org at the Cioppino Sprint in early 2011:
This software is designed for the future plone.net. As such, while others are welcome to them, they are not neccessarily intended for public consumption. We welcome bug fixes, but please refrain from adding new features without talking with the developers first. Developed by Damien Baty <damien@pilotsystems.net>, Joel Burton <joel@joelburton.com>, Geir Baekholt <baekholt@plonesolutions.com>, and Paul Everitt <paul@zope-europe.org>. Contributions by Roberto Allende <rallende@menttes.com>, Leonardo Caballero <leonardocabllero@gmail.com>. Vision ------ plone.org currently mixes community and commercial announcements. During the last year the policy has gotten strict about not doing commercial postings. However, we need a place for providing business information to decision-makers. This is the vision for plone.net: "All the business information, attractive and organized, for decision-makers." We want to collect case studies, solution providers, mentions in the press, training announcements, books and articles, etc. And, we want to present this information in a well-organized fashion. Finally, we want a strong editorial process to ensure we don't have 500 companies claiming to be the galaxy's leading Plone company. :^) Additionally, we want the Plone Foundation to have a revenue stream. For example, we need to start exhibiting at conferences, to make sure we win "Best of Show", to make sure we're always considered the leaders. We plan to do the solution provider directory in a way where companies that sponsor the foundation get a better listing, just like the Pages Jaunes.
Changelog
0.2.7 - 05/12/2011
Fix package [aclark]
0.2.6 - 05/12/2011
Plone 4 compat [zenwryly, limi]
Package and release [aclark]
1 maintainer
Metadata
1 maintainer
Release files for Products.PloneServicesCenter 0.2.7
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 | |
|---|---|---|---|---|
| Products.PloneServicesCenter-0.2.7.zip | 109.3 kB | Without provenance | Details |
Release files / Products.PloneServicesCenter-0.2.7.zip
| Download URL | Products.PloneServicesCenter-0.2.7.zip |
|---|---|
| Size | 109.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fc8cf6bf7efcb49279bbc549e9fb7f01a9d2b37a3b624d319f043d93b1096f7
|
|
BLAKE2b-256 checksum How to use checksums |
a84b0107c5a446d1bc820ae0be332e607c2b598a0b479e8176e171232e28f070
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.PloneServicesCenter 0.2.7
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.
