Re: Was: Plone 5.0 release date

David Bain <[email protected]> Wed, 13 May 2015 08:10:28 -0500
Newsgroups gmane.comp.web.zope.plone.user
Message-ID <CAEXdPTFLXLWCibY-x=PcqCFJp+01B+UPnAv+B62sjWkiVOCC6A@mail.gmail.com>
@Jota,
This is not necessarily a direct response to all of what you raised but
just some of my impressions.

I personally haven't been very engaged in terms of code contribution to
core etc... So my general philosophy is to talk less when I'm doing less.

I'd agree with the idea of a note on tagged releases that explains that the
installers will follow, perhaps a public document explaining the typical
release period.

I recently launched a fairly significant website with a small team, the
process made me realize how engrossed one can get with little details and
miss other details. So the fact that people miss details sometimes isn't
because of a sinister agenda but simply because they were focusing on other
details.

I think the Plone foundation as a group is listening and some of the most
recent communication from representatives seems to suggest that they are
taking suggestions on board.

I "feel" the community leaning in, I feel momentum. So let's press for more
open dialogue and hands-on contributions so that as quickly as is
responsible we'll get to the best and most valuable Plone 5 possible.



-


David Bain, RHCSA
Owner at Alteroo
[email protected]
www.alteroo.com
(876) 475-5824


On Wed, May 13, 2015 at 7:36 AM, Jota <[email protected]> wrote:

>
> (thread here:
> http://plone.293351.n2.nabble.com/Plone-5-0-release-date-td7573694.html
> <http://plone.293351.n2.nabble.com/Plone-5-0-release-date-td7573694.html>
> )
>
>
> David Bain-5 wrote
> > For the sake of clarity, my understanding of what Jota said is:
> > 1. Plone needs to get their marketing and communication act together
> > 2. Plone is sick (not clear on everything he was getting at with that
> > point)
> >
> > My feeling is that point 1 is very important and the community should
> keep
> > this concern in view.
> >
> > @Jota regarding the second point, I think identifying the bug was the
> most
> > value I got out of what you communicated. I had to do a lot of filtering
> > because everything else felt like an angry rant.
> >
> > What's the relationship to the Plone project at this point, are you
> > absolutely indifferent about the improvement of Plone?
> > Or perhaps your comments were meant to stir the community towards
> positive
> > action? I cannot tell but would benefit from clarification.
>
>
> Maybe I can answer this way:
>
>
> > Exactly. We discovered a big issue while the installers were being
> > built, so I held off making an announcement until b2. Expect that soon.
>
> 1. two weeks latter and no news about this...
> 2. if it really is a BIG issue, then why not be transparent and tell the
> community about it so to engage more people in trying to help and quickly
> find a solution?
> 3. and, if there was a BIG issue with b1, why is it still available at
> https://plone.org/products/plone/releases/5.0 -->
>
> https://launchpad.net/plone/5.0/5.0b1/+download/Plone-5.0b1-UnifiedInstaller.tgz
> ???
> (or am I understanding this all wrong?)
> 4. I know about many relationships and marriages that had go broken simply
> by this kind of miscommunication....
>
>
>
> > Releases are generally announced when we have a critical mass of
> > installers
> > available. If we publicize the tagging of a release before the installers
> > are ready, we'd spend a lot of time answering "where are the installers"
> > questions.
>
> WRONG!
> If you publicize the tagging of a release and also care to tell that "the
> installers are not yet available, please be patient" (maybe in bold just to
> be sure), I think people will understand it (unless they cannot read
> English).
> Publicizing the tagging of a release is like telling the community "warm up
> our engines, something new is coming soon", and this can be very helpful to
> engage people!!
> And, if at the same time there are some change-log to read, it will be
> better yet.
> One can start to test it, and when the installers are ready, then the full
> announcement made, for the general public availability.
>
> So, all this behaviour and mentality from some people that are in key roles
> (it is nothing personal, I am sure they all are great persons), are not
> good
> to Plone, because this does not help to bring more people into the boat.
>
> The other aspect is that the roadmap of Plone, it's current and planned
> features, are not in sync with the actual expectations and needs of
> companies and businesses, so in general it is very hard to sell Plone for
> new projects and costumers.
> And others that provide similar solutions are not sleeping,
>
> This is just my opinion, don't want to upset anyone!
> J.
>
>
>
>
>
>
> --
> View this message in context:
> http://plone.293351.n2.nabble.com/Was-Plone-5-0-release-date-tp7573840.html
> Sent from the General Questions mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Plone-Users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-users
>

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

_______________________________________________
Plone-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-users