Mailinglist Archive: opensuse-project (930 mails)
| < Previous | Next > |
[opensuse-project] Re: Strategy discussion @ forums
- From: Jim Henderson <hendersj@xxxxxxxxx>
- Date: Sat, 26 Jun 2010 03:18:47 +0000 (UTC)
- Message-id: <i03rim$5t6$2@xxxxxxxxxxxxxxx>
On Fri, 25 Jun 2010 19:52:17 -0500, Rajko M. wrote:
Nope. We've got someone who's made modifications on the gateway
software, but there are many other features we'd like to see but Marcel
just hasn't had the time to write more code.
One of the biggest complaints we get from people who come from a pure
"web forum" world (which I don't, I come from an NNTP world myself) is
that they can't edit messages after the window closes. This is because
the gateway doesn't handle edits at all - though the NNTP protocol does
have capabilities for superceding old posts (which is how I think edits
could be handled). It also doesn't handle forum thread/message moves
very gracefully (read: at all). To move messages effectively becomes
much more of a challenge because the server timestamps the posts, which
means reposting the messages would cause them to be timestamped at a
different time from when the message was originally posted.
In my mind, the ideal would be for it to be event driven
(bidirectionally). I find I often post a reply to a message and someone
else replies from the web interface in that 10 minute window; two answers
are better than none, but if the answers are contradictory, that can lead
to a little confusion.
That's fair. I talked with Kim (the technical admin) about this, and he
said when it's done, we intend to have one template - the CSS coming from
opensuse.org. As I understand it vBulletin's template (which controls
the layout of elements on the page - ie, message list, message text,
thread view, forum overview, etc) is in code and that'll stay stock. The
CSS all comes from the new openSUSE pages. (This will be active when
they finish the iChain integration work, which is underway and has been
for a few weeks now).
That sounds good to me. Stephan's thread is a good starting point and I
think we might see some of those communication issues come out in that
discussion, too.
Jim
--
Jim Henderson
Please keep on-topic replies on the list so everyone benefits
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
On Thursday 24 June 2010 23:36:21 Jim Henderson wrote:
There is a little bit of lag - gating the messages back and forth
between the NNTP server and the web interface is a cron job that runs
every 10 minutes.
Anything event driven?
(now I know why I have to wait to see my post)
Nope. We've got someone who's made modifications on the gateway
software, but there are many other features we'd like to see but Marcel
just hasn't had the time to write more code.
One of the biggest complaints we get from people who come from a pure
"web forum" world (which I don't, I come from an NNTP world myself) is
that they can't edit messages after the window closes. This is because
the gateway doesn't handle edits at all - though the NNTP protocol does
have capabilities for superceding old posts (which is how I think edits
could be handled). It also doesn't handle forum thread/message moves
very gracefully (read: at all). To move messages effectively becomes
much more of a challenge because the server timestamps the posts, which
means reposting the messages would cause them to be timestamped at a
different time from when the message was originally posted.
In my mind, the ideal would be for it to be event driven
(bidirectionally). I find I often post a reply to a message and someone
else replies from the web interface in that 10 minute window; two answers
are better than none, but if the answers are contradictory, that can lead
to a little confusion.
The web interface can be used too, but it should be way simpler then
current.
... the caveat that
it not require template changes - CSS shouldn't, I don't think, require
any recoding ...
It should not require any change in a code if number of posts per page
can be increased, or set to unlimited, by some system variable.
The css will rely on existing elements and it will actually ignore some
of them that are superfluous for this type of discussion. It can be
listed as one of skins.
That's fair. I talked with Kim (the technical admin) about this, and he
said when it's done, we intend to have one template - the CSS coming from
opensuse.org. As I understand it vBulletin's template (which controls
the layout of elements on the page - ie, message list, message text,
thread view, forum overview, etc) is in code and that'll stay stock. The
CSS all comes from the new openSUSE pages. (This will be active when
they finish the iChain integration work, which is underway and has been
for a few weeks now).
Apropos another thread:
The communication issues are to blame for high percentage of problems we
have, either directly as lack of appropriate path for the message, or
indirectly, inducing issues that otherwise would not exist.
I can open the thread when I sort things out. It was long ago when I
used this knowledge and I need update first :) (anyone to help, give
directions :)
That sounds good to me. Stephan's thread is a good starting point and I
think we might see some of those communication issues come out in that
discussion, too.
Jim
--
Jim Henderson
Please keep on-topic replies on the list so everyone benefits
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
| < Previous | Next > |