[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Eclipse Blogging
|
So if the blog platform introduce a reduction of
quality about the CI or GitHub integration, adding a few
more hours of delays for each answer, then it's
definitely not something profitable to the community. If
the blog platform has very low SLA, so low that its
issues are never prioritized and it's always failing,
then it means it will be itself of bad quality, often
failing, never evolving, and will become a dead service
very soon.
Also, many people will still fairly prefer to publish
to their own blog, to boost their company or personal
branding in the ecosystem, allowing them more
opportunities. So I don't think many people will want to
sue such a common platform.
Realistically, I don't think this is in the best
interest of the community to ask it from EF.
Dude, lighten up. You talk about the EF webmasters and
the infra like they are about to die.
About to die? Maybe he knows something we don't? :)
Mickael's point is valid, nonetheless. We are trying to focus our
energies on services that add value to the community. If it is
decided by a large percentage of the community that an
Eclipse-branded blog platform is what adds value, we'll certainly
entertain it. Otherwise, we'd rather focus on GitLab, CI,
supporting working groups with strong marketing and web presence,
artifact signing and distribution and frankly, we need more
security.
This is a great conversation thread, Wim. Thank you for speaking
up. We need more of that.
Denis