Re: Site and case study submissions

T Kim Nguyen <[email protected]> Tue, 19 Jul 2011 08:01:55 -0500
Newsgroups gmane.comp.web.zope.plone.website
Message-ID <[email protected]>
I agree that we would do a disservice to ourselves by publishing poorly written case studies.  

Would it be possible to divide them up among a number of us to edit?  Use a Poi to track which ones are outstanding so none fall through the cracks?

A top level URL like /case-studies makes a lot of sense.

    Kim

On Jul 19, 2011, at 4:00 AM, Jean Jordaan <[email protected]> wrote:

> Hi all
> 
> I'm moderating site and case study submissions if I have a spare moment. 
> Recently some have been coming through with poor English and bad spelling,
> even after a couple of rounds of rejection. 
> 
> Should I be forgiving and publish? The linked sites are fine, the authors
> just aren't native English speakers. 
> 
> Personally I feel that having bad English on the plone.org site is
> unacceptable. Perhaps we should log submissions in need of editing as bugs,
> but I suspect no one will get round to editing. In the end it's the
> responsibility of the original authors to get the submission up to scratch
> ... maybe they could flattr editors to get them to polish their submissions. 
> 
> Another note: the sites are published at
> http://plone.org/support/sites/sitename .. that seems like an awkward URL:
> sitename does not constitute support for Plone at all, so it shouldn't be
> under /support/. It is a marketing listing. Just
> http://plone.org/sites/sitename looks fine to me. 
> 
> http://plone.org/support/case-studies/casestudy is slightly less bad, but
> http://plone.org/case-studies/casestudy is still better. 
> 
> Finally: https://dev.plone.org/plone/ticket/11652
> 
> --
> View this message in context: http://plone.293351.n2.nabble.com/Site-and-case-study-submissions-tp6598036p6598036.html
> Sent from the plone.org Web Site mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> Magic Quadrant for Content-Aware Data Loss Prevention
> Research study explores the data loss prevention market. Includes in-depth
> analysis on the changes within the DLP market, and the criteria used to
> evaluate the strengths and weaknesses of these DLP solutions.
> http://www.accelacomm.com/jaw/sfnl/114/51385063/
> _______________________________________________
> Plone-website mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-website
> The Wiki: http://plone.org/development/current/projects/WebsiteTeam

------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Plone-website mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-website
The Wiki: http://plone.org/development/current/projects/WebsiteTeam