Ya, then there's posts like:

==========================================================
From: Sigurd Magnusson <[email protected]>
Date: Wed, 25 Feb 2009 16:43:04 +1300
Subject: SilverStripe 2.3.0 released.

The open source SilverStripe CMS and MVC framework (PHP5) has now had
a v2.3.0 release:

It brings a significant set of new features, described at:
http://www.silverstripe.org/silverstripe
-2-3-0-released-1000s-of-improvements/

Cheers,

Sigurd Magnusson.
==========================================================

and the millions of silverstripe events being posted. They themselves aren't
so bad
but it's pretty obvious that either the rules aren't being followed, or
they're being pushed.

This is a standards mailing list, not a "hey check out open source project
X" mailing list.

On Mon, Mar 16, 2009 at 8:51 PM, Mark Harris <[email protected]> wrote:

> Glen Wallis wrote:
>
>> Am I the only person on this list who is sick of the constant and blatant
>> advertising for this Content Management System? Don't we have rules
>> against
>> this? If so, they are not being enforced.
>>
>>
> I thought the post was brief, informative and to the point. If everyone on
> this list with a commercial or open source product or service is prevented
> from speaking about it at all, we'd lose a lot of content. I don't think
> Sigurd's posts are over the top, any more than the numerous Dreamweaver,
> Joomla, Drupal or <insert_CMS_name_here> posts, and I do think you're
> over-reacting just a tad.
>
> Cheers
>
> ~mark
>
>
>
> *******************************************************************
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: [email protected]
> *******************************************************************
>
>


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************

Reply via email to