On 9/4/20 12:05 AM, Vinzenz Vietzke wrote:
Am Donnerstag, 3. September 2020, 21:41:47 CEST schrieb Christian Boltz:
Hello,
Are we as a project and marketing ok with people posting info on
news.o.o. as long as it's community related?
I always recognized news-o-o as some magazine where anything is
possible as long as it's somehow related to openSUSE.
That sounds more like how I would describe planet.o.o.
(Mostly - on planet.o.o we also get some off-topic posts from community
members, and that's fine.)
No. There's a fundamental difference: curation, or the level of it. On planet-
o-o I get content written by members. Most of the time it's openSUSE related
in a very loose way. Just if someone's constantly and totally off topic their
content gets removed.
On a magazine there are a few people getting content into a curation queue
like via email or pull request for their reviewing. Plus these people try
actively to generate content to the page. [1]
Playing devil's advocate on your "somehow related to openSUSE"
definition:
I recently asked one of the upstream AppArmor devs to adjust some
library paths in the Ubuntu Chromium profile so that they match the
openSUSE paths.
According to your definition, that's "related to openSUSE", so - should
I write an article on news.o.o about it? ;-)
(No, I don't plan to write such an article, and even think that this is
too minor for my own blog/planet.o.o - but I hope this example helps to
understand where I see the problem.)
See above and following:
news-o-o has no clear definition what it is. If it's strictly "news from the
openSUSE project" like in press releases then we need to have a separate place
for stuff like a report from a release party.
If it's not but more like an overall magazine then we need to make sure the
huge news don't get buried.
...
Would it be feasible to do the same setup as
https://github.com/openSUSE/news-o-o and make it a new blog area.
Maybe blog.opensuse.org rather than magazine.opensuse.org. Of course,
we have https://planet.opensuse.org, which just connects blogs.
Exactly, we have planet.o.o.
And, see above, we decided not to provide a blog platform for individual
users anymore because hosting a blog somewhere[tm] is very easy.
Yes and no. We don't need to provide a technical platform for individuals as
in wordpress.com et al. Instead we should provide a platform for community
content that's not individual and off-topic enough for leaving it at planet-o-
o.
I think there are some people such as myself that may get annoyed if
news.o.o ends up with too many posts because then the actual news
gets buried in everything else and the signal to noise ratio of
things I care about to things I don't gets too low.
+1
Also, articles featuring a specific package also feel off-topic for
news.o.o [2] - in the recent case, I'd have expected the post in
someone's blog and then on planet.o.o. Independent of the question in
which repo this package lives.
Again: missing definition of news-o-o.
I might repeat myself, but the way Fedora is doing it is just great. Good
content, balanced between community news, announcements and tutorials.
I looked at the Matomo out of curiosity to see the interest these type
of articles generate. Both this and the previous one appear to generate
a lot more interest than normal, so I believe we should offer some
option here.
Maybe having articles featuring content like this isn't exactly what
some project members want, but the numbers don't lie.
Building something new could work, but the existing structure is set up
and brings in new readers to news.o.o., which might bring in new
followers on social media, etc. I'm in favor of content like this posted
on news.o.o. I know some aren't in favor of this and I don't agree with
them on this topic.
As long as there is a clear set of rules in the README.md and the author
meets the criteria, I don't see a problem with it.
The Criteria (meet two of the five rules)
Criteria 1 - Author must provide a call to action for the community.
I.E. - Asking for community help.
Criteria 2 - Article is meant to increase awareness of a package/s with
the intent to make it apart of the official repositories. Advertising
home repositories is discouraged and may be subject to removal of the
article. Any packages linked to home projects need to include a
disclaimer regarding the absence of security as the packages are
currently not official and have not gone through the legal and quality
assurance processes.
Criteria 3 - Article informs readers of the efforts of an open-source
project/s and how they relate explicitly to the openSUSE Project, its
community and users.
Criteria 4 - Is an official package in the distribution, an official
openSUSE distribution or a project within the openSUSE Project.
Criteria 5 - Provides a "how to use" or "tutorial" about on an official
package within the openSUSE distribution.
Thoughts?
v/r
Doug
--
To unsubscribe, e-mail: opensuse-marketing+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-marketing+ow...@opensuse.org
