Mailinglist Archive: opensuse-wiki (174 mails)

< Previous Next >
Re: [opensuse-wiki] AI3: QA - FlaggedRevs & Wiki Forum
  • From: Rupert Horstkötter <rhorstkoetter@xxxxxxxxxxxx>
  • Date: Thu, 10 Dec 2009 11:55:04 +0100
  • Message-id: <26d1a5470912100255w40fbcb9r8222aa47363ea011@xxxxxxxxxxxxxx>
Rajko,

2009/12/10 Rajko M. <rmatov101@xxxxxxxxxxx>:
On Wednesday 09 December 2009 04:12:58 Rupert Horstkötter wrote:
...
Rajko, is FlaggedRevs able to provide an RSS feed for draft revisions?
Kim, is vBulletin (i.e. the RSS grabber you have) able to use this
FlaggedRevs RSS feed and post corresponding threads at the Wiki forum?

I have to check that, but I suspect the answer will be no. It is either buried
in Mediawiki itself as option, like the existing one, with email reports on
page changes, or it requires extension.

That's unfortunate. Seems that I got you wrong in the transition
meeting. I thought the "email reports" you mention would have been a
RSS feed.

We mentioned idea last night, and I just checked functionality of SimpleFeed
extension. It is just input method, the same as Forums feed grabber, as
mentioned in Kim's mail.

On the other hand, manually linking article, that one wants to be reviewed can
be option too if there is no other tools available, but even that option
requires working wiki with FlaggedRevs, so that we can check what link to
provide in the forum post.

Sure manually linking is also possible. Question is how to encourage
people to do this. On the other hand the sole motivation to get his
article flagged as "quality" should be at least some kind of
motivation for the editor to kickoff the reviewing for his article at
forums.o.o manually. If he do not the article will just remain as a
"Draft" .. if we need to go for the manual approach we should define
the reviewing as a requirement to get a "Quality" flag. That said, I'd
still appreciate to have the "automagical" method.


...
Lots of questions and hopefully the start of a fruitful discussion.
Let's brainstorm and come up with something really awesome for the
sake of the openSUSE community. Your turn gentlemen ...

We have to think on communication capabilities of software and people.
Overloading forums with potentially hundreds of automatically generated
articles, what that brings?

It ensures the utilization of the reviewing process. I doubt it would
be hundreds of threads cause as I said we just want to have threads
for "Distro documentation pages", i.e. pages that are interesting for
the enduser, not every crap we have in the wiki. If RSS turns out to
be possible in the end .. couldn't we configure the RSS to just output
new drafts in main namespace and leave all team pages, meeting logs
etc etc apart?

Maybe manual selection can do better job, where we present articles that
really need review of many people that should be their users.
The fact is that from that process wiki team will learn what is asked for and
direct future articles in that direction.

Yeah! Let's investigate the abilities we have on the table and then
make a decision about the best approach.

Please let think about other possibilities we may investigate besides
the RSS approach. Isn't there a kind of bridge between vBulletin and
MediaWiki available? Or if not, are we able to code something by
ourselves?

Pseudocode:
if [new draft in monitored namespace] && [thread doesn't exist yet] then
create thread
elif [particular thread does exist already] then
re-open existing thread and update draft URL
fi

Best,
R

Best,
R


--
Regards Rajko,

openSUSE Wiki Team: http://en.opensuse.org/Wiki_Team
People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-wiki+help@xxxxxxxxxxxx





--
Rupert Horstkötter
openSUSE Community Assistant
http://en.opensuse.org/User:Rhorstkoetter
Email: rhorstkoetter@xxxxxxxxxxxx
Jabber: ruperthorstkoetter@xxxxxxxxxxxxxx
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-wiki+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups