[changing the subject to focus on connect.o.o]
Am Samstag, 10. Februar 2018, 20:19:44 CET schrieb Stasiek:
First of all I will be biased as non member and
wannabe, to make this
change, sorry. I am totally for it.
I wouldn't call you biased for wanting to become a member ;-)
Second of all Connect sucks, we all know it, and all
will admit it.
It's written in PHP, and every bit of PHP I dealt with I just have
rewritten to something that at least works.
We all know that connect sucks, but that's not really PHP's fault ;-)
Connect is "just" an old system and didn't get enough maintenance, and
I'm afraid that a lack of maintenance causes problems in all programming
Oh, and I'll scare you a bit more - our wikis run with MediaWiki, which
is written in PHP - and works ;-)
I propose something more
useful and streamlined for connect, let's say connect++ (going with
old cool++ marketing). Instead of making some fake social media
wannabe, let's make useful centralized hub for openSUSE
infrastructure. And in ruby, because that seems way more popular and
common around here.
It would be useful to connect: OBS, bugzilla, mailing lists, news,
paste, whatever people will need, want or care about (by adding
plugins). Let's make it also custom for every person, so they can
just have widgets they need.
Actually that is not my idea, that is idea dating back to old openSUSE
days with myopensuse, which was never fully realized.
I made mock-up of this in 5 minutes:
I noticed the fixed link in the follow-up mail, but I like that one
Let me start with a warning: This mail will be a mix of "reality
sometimes hurts" and my usual strict review style (which can scare
people, even if they rarely admit it ;-) so please read it until the
end before you get mad at me ;-)
There's nothing wrong with the ideas in your mockup. Doing the mockup
was easy, but I should probably warn you that collecting all this data
on one platform might be harder than you think. Bugzilla, OBS,
mailinglists, paste.o.o, ... don't have a common interface you could
use, so you'll need separate implementations for each system.
Actually we had a system to centralize notifications -
. The idea behind it was good, but in practise it's
much easier if each service includes notification management and sends
out its notification mails or offers RSS feeds itsself. Therefore hermes
was shut down to avoid that level of indirection.
Also, not all services used hermes for their notifications (for example,
bugzilla never did), so it only centralized notifications from a few
All this doesn't mean I'll stop you or anybody else from implementing
your proposal (quite the opposite), I just want to make clear that it
will be more interesting[tm] than it might look, and will need constant
maintenance if one of the services changes the way you use to collect
Personally, I already have most of your proposal implemented by using
mail notifications everywhere.
I fetch my mails anyway, and reading some more mails (which get filtered
into lots of folders) is easier than going to a website. Even if that
website has everything in one place, I still have to go there, and
"recent $foo" means things will scroll out if someone doesn't check them
for a while. A "more from $foo" link will help a bit, but I'm quite sure
I don't want to read the mailinglists via a connect replacement ;-)
Maybe people who are more used to Facebook etc. have a different opinion
on this and think that mail is an ancient way to stay up to date ;-) so
as I already said - if you want to implement this, I won't stop you, and
I'm sure there are people who will like that page.
In a way, it makes more sense than adding friends and
making groups on
which nobody ever interacts. That kind of things should be left to
Matrix/IRC or whatever.
IMHO the usecase is more "phonebook" and not "interaction" (where IRC
and mail are indeed better), see below for details.
Although one more useful thing could be integrated
profiles, as much of a gimmick it was to make yourself an openSUSE
business card and public profile, it was one of the best
functionalities of Connect ;)
The current usage of connect.o.o is (quick summary, I hope I didn't miss
- membership management (can be simplified if everybody likes the
reforming proposal, but is still needed)
- profile pages aka "phonebook" - this can mostly be replaced with user
pages in the wiki.
However, I wouldn't put my phone / mobile number on a public wiki
page. That's where connect's option to share some things only with a
specific group of people is helpful. (I'm not sure if we really need
this feature and if it's worth the effort, I'm just pointing out that
I'd miss it.)
- groups - can be useful to find people with similar interests etc.
(replaceable for example by using groups on the wiki user pages)
and also to share personal information (again, phone numbers etc.)
only with specific people
- polls - but as we learned in last year's elections, this feature is
more or less broken on connect.o.o.
- travel support - AFAIK that's already a separate app, so splitting it
out to a different server shouldn't be too hard (note the "AFAIK" -
I don't know all the technical details)
To sum it up:
The two must-have features we currently have in connect are
- membership management
- travel support
Everything else - both the existing features on connect.o.o and your
proposal - would "only" be nice to have ;-)
Sorry if this mail sounds discouraging or negative - this is not my
intention, and in a way, I hate myself for writing a mail where I need
to mention that. However, I'd also consider it unfair not to explain
that some things are harder than they might look. So, sorry- reality
sometimes isn't too encouraging ;-)
"Herbsten" ist in der Pfalz synonym zu
"Trauben lesen" zu verstehen,
was nichts anderes als "Trauben ernten" bedeutet ;-)
Jo, und alles, was
in Überstunden gepflückt wird, nennt man Spätlese.
Bin ja nicht blöd. :-) [> Christian Boltz und Ratti]
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org