My 2 cents: I will not participate in discussions in a web forum. I’ve
never found one (including google groups) that I can use.
On Fri, Aug 8, 2014 at 10:32 PM, Stu [email protected] wrote:
Having a centralized area for user contrib tutorials for both clarification
and education, user code commits to further enhance the site as well as
getting back to the basics of mentoring from older community members to aid
noobies to both ruby and programming.
Only that the “centralized area” part won’t work - the web just has
too many places. I mean, it’s unlikely to be able to deliberately
make a site central - either it happens because users are flowing that
way, or it doesn’t.
Kind regards
robert
On Fri, Aug 8, 2014 at 11:50 PM, tamouse pontiki
[email protected] wrote:
My 2 cents: I will not participate in discussions in a web forum. I’ve never
found one (including google groups) that I can use.
Well, GG is particularly awful. I’d even say it’s one of the worst -
if not the worst - service from Google. For any extended period of
time I’d rather read Usenet with tin than GG.
Cheers
robert
Right on. I couldn’t figure out a way to subscribe via email-only
commands to meta or try.discourse.org, nor could I find a way to
subscribe on the website with the text-only lynx browser.
Subscribe via email does not exist at the moment, we would need to
build that, I would be happy to write it if needed for a move like this.
We already have the lions share of the code used for “invite” user
Those who are concerned about the mailing list part of thing. Create an
account
on meta and turn the email volume up: http://imgur.com/exR4k8A after
doing that
you would no longer need to do anything via a web browser (except for
create
topic on meta) cause we don’t have this filled in
http://imgur.com/5w4TbAl
I think the hybrid approach can work.
The bigger issue I can not resolve is sociological changes that will
follow.
Reducing barriers to conversation will change the face of the group, we
could
isolate some of this with categories, but overall a “new” type of people
would
start posting here which may go against some people’s desire.
I wonder if anyone here would refuse to have the content mirrored in a
web
forum? That is a concern I can not really address.
On Fri, Aug 8, 2014 at 5:18 PM, Robert K.
[email protected]
wrote:
too many places. I mean, it’s unlikely to be able to deliberately
make a site central - either it happens because users are flowing that
way, or it doesn’t.
It was an idealistic statement. I figured if the forum was going to be
sunsetted for one reason or another that one possible future ruby-talk
feature could be a place for community driven edification(maybe like
user-owned wikis with user level trust to allow their friends editing
rights or commit bits, if you will). Seems like many of the sites that
did
this died out or where displaced by SO. Voting systems (like SO) seem
more
for just getting an answer than grokking the programming paradigms. I
would
also recommend a pastebin style feature even though there are many such
sites and tools out there already.
On Fri, Aug 8, 2014 at 4:04 PM, Eric W. [email protected] wrote:
commands to meta or try.discourse.org, nor could I find a way to
stores messages in git, and allows extracting messages to any
mbox/Maildir/IMAP location as well as feeding mlmmj lists.[1] http://public-inbox.org/ + http://ssoma.public-inbox.org/
Maybe this: GitHub - matz/mail: A Really Ruby Mail Library
vi/mutt or emacs/cmail nano/pico/pine/(re)alpine etc. I agree it’s a
huge
user base that would be abandoned by being only assessable via graphical
browser only. Mapping out and reducing the digital divide would be
imperative. I’m not sold on discourse either. It’s main selling point is
that it is optimized for search engines and has that twitter bootstrap
js
mobile theme. I am curious how discourse mailing lists feature stands up
to
the tried and true methods. I don’t believe ruby-talk forums/usenet/ML
ever
really had a problem with being crawled so it’s a redundancy. Worse case
we
could fork discourse and strip it of any limitations and implement
what’s
missing by using ruby at what it’s best at: molding the language to the
problem domain (which in the case is the ruby community needs).
Stu
Hi Tamouse,
And if Discourse would be highly transparent and we could interact
with “the forum” by e-mail as we do today?
Today, there’s some people that interact with the Ruby-Talk list
only by the web forum.
I’m not sure if this is already accomplished by Discourse. But if so,
it would be great!
I’ve recently subscribed to http://parley.rubyrogues.com but didn’t
have the time to explore it well.
I’ll set on all email options now and see how it works to get a more
clear ideia of how it is.
Attaching a capturing of how the preferences look like.
Abinoam Jr.
Hi,
In message “Re: Are we dying?”
on Sat, 9 Aug 2014 08:48:10 +1000, Sam S.
[email protected] writes:
|I wonder if anyone here would refuse to have the content mirrored in a web
|forum? That is a concern I can not really address.
The mailing lists have been archived in our server from the beginning,
so I expect no one would complain about mirroring. For your
information, I have received very few removal requests in last 15+
years of mailing lists history.
matz.
The key word in that idea is “archive”. Having a searchable archive has
proven distinctly useful to me (and surely to others as well) on more
than
one occasion. It is difficult for me to imagine what objection anyone
might
have to such an archive.
However, NOT having all primary questions and discussions go to a
mailing
list folder in my inbox seems to discourage promotion of an actively
engaged community.
It is interesting to note that this mailing list/forum question, when
the
subject is an entire operating system, seems (in my experience) to be
resolved in favor of a forum-primary solution, perhaps because the
questions tend to be so highly technical (and so not of broad interest)
and
because there are multiple versions of the OS involved. (I’m thinking of
the Ubuntu/Kubuntu, etc. forums). But even then there is the option to
be
notified of responses to a thread, so that continued involvement is
easy.
What is NOT easy, however, is to see what people in general are talking
about today. For that, one must browse to the forum, then sign in, then
click a while, etc. That effort-barrier simply discourage involvement,
to
my mind.
So, I check in on the Ruby community discussion fairly often. I never go
to
the Kubuntu forum unless I need something. That’s a huge difference.
Tom
Excerpts from Tom C.'s message of 2014-08-08 19:55:04 +0200:
Hi,
+1 !!!I don’t want a web interface. I find emails much easier to search when I
need to find something that’s been discussed in past.–
Darryl L. Pierce [email protected]
http://mcpierce.blogspot.com/
Famous last words:
“I wonder what happens if we do it this way?”
I agree completely. I’d hate to, but if the mailing list were replaced
by a
web interface (whatever its exact form), I’d stop following it. Having
messages
just popping in my mailbox is extremely convenient. Having to remember
to check
the web page, even if only once or twice a day wouldn’t be.
Stefano
Hi,
The virtual drive. This solves the abelian. I have a j. Ask. – There
are fewer tk-dnds with the direct approach to Discourse from forum load
but there are fewer people who know Ruby at that layer for tk-d and j.
It’s Zellian3 to mention it. The way to boe is longer $t-s-d-f. For
the macro, ACD is l-47.2378 but use a direct disk without a cable. This
prevents proton wash. Use q-T.
Mr. Brandon M. Ericsson
studentID: 14B8281076
[email protected]
From: ruby-talk [email protected] on behalf of Quintus
[email protected]
Sent: Sunday, August 10, 2014 4:23 AM
To: Ruby users
Subject: Re: Are we dying?
“Abinoam Jr.” [email protected] writes:
And if Discourse would be highly transparent and we could interact
with “the forum” by e-mail as we do today?
I have no problems with the ML being accessible read-write through a web
forum interface, as long as it does not result in the large amount of
spam ruby-talk received from ruby-forum.com. The main problem I have
seen with (even replyable) notification emails (at least those from
GitHub) is that they dont properly set the references mail header,
i.e. instead of creating a proper discussion tree in my mail client that
shows who replied to whom, the result is a starting email to which all
following responses are mapped directly. This makes it significantly
harder to follow the branches a larger discussion creates (and
especially ignoring those branches you are not interested in).
Valete,
Marvin
Blog: http://www.quintilianus.eu
I will reject HTML emails. | Ich akzeptiere keine HTML-Nachrichten.
|
Use GnuPG for mail encryption: | GnuPG fr Mail-Verschlsselung:
http://www.gnupg.org | The GNU Privacy Guard
“Abinoam Jr.” [email protected] writes:
And if Discourse would be highly transparent and we could interact
with “the forum” by e-mail as we do today?
I have no problems with the ML being accessible read-write through a web
forum interface, as long as it does not result in the large amount of
spam ruby-talk received from ruby-forum.com. The main problem I have
seen with (even replyable) notification emails (at least those from
GitHub) is that they don’t properly set the references mail header,
i.e. instead of creating a proper discussion tree in my mail client that
shows who replied to whom, the result is a starting email to which all
following responses are mapped directly. This makes it significantly
harder to follow the branches a larger discussion creates (and
especially ignoring those branches you are not interested in).
Valete,
Marvin
Blog: http://www.quintilianus.eu
I will reject HTML emails. | Ich akzeptiere keine HTML-Nachrichten.
|
Use GnuPG for mail encryption: | GnuPG für Mail-Verschlüsselung:
http://www.gnupg.org | The GNU Privacy Guard
phew!
I’m not a native english speaker and was just thinking about how bad
my english was. I just didn’t understand nothing at all!!!
Abinoam Jr.
On Sun, Aug 10, 2014 at 6:01 PM, Robert K.
On Sun, Aug 10, 2014 at 5:54 PM, Brandon Ericsson
[email protected] wrote:
Hi,
The virtual drive. This solves the abelian. I have a j. Ask. – There are
fewer tk-dnds with the direct approach to Discourse from forum load but there are
fewer people who know Ruby at that layer for tk-d and j. It’s Zellian3 to mention
it. The way to boe is longer $t-s-d-f. For the macro, ACD is l-47.2378 but use a
direct disk without a cable. This prevents proton wash. Use q-T.
???
From what phrase generator did you pull that?
Cheers
robert
On Fri, 8 Aug 2014 15:07:16 -0300
Amadeus F. [email protected] wrote:
Maybe this could be an opportunity for discourse to be a transparent
medium between mailing lists and the forum?On Fri, Aug 08, 2014 at 11:55:04AM -0600, Tom C. wrote:
For me, a mailing list is essential. I do not and will not follow
forums - simply too much bother, and I don’t have the time. I WILL
consult a forum to solve specific problems, but that’s it.
+1
keep the mailing-list, but offer a new medium anyways
On Wed, 6 Aug 2014 10:21:55 +0200
Robert K. [email protected] wrote:
think it’s worthwhile trying? If so we should probably collect
feedback to judge how many people here would make the move.Kind regards
robert
I would make the move …
Ember rocks, Discourse also.
On 10/16/14 20:48, Sam S. wrote:
I have been watching stuff here for a few months and traffic is quite
low. There are some interesting discussions but they are few and far
apart.
Quality, though. I’ve asked a couple questions and gotten great
responses. Not too fond of forums.
Leam
I do not see Rust (hosted on Discourse) http://discuss.rust-lang.org/
or Ember http://discuss.emberjs.com/ have any particular issues with
quality.
Why do you think a hybrid forum/mailing list would have issues? If
anything moderation becomes a possibility.
I have been watching stuff here for a few months and traffic is quite
low. There are some interesting discussions but they are few and far
apart.
I think it would be good for Ruby to promote a modern forum built in
Ruby. When people first learn about Ruby they visit
Ruby Programming Language and then look at
Community … sadly the “lists and
newsgroups” stuff is arcane and old. By using something like Discourse
you would be showing off to the community that “hey, we can build this
stuff in Ruby” its open source, it is also far more welcoming.
I will work hard to maintain feature parity with the current mailing
list (most of the boxes are already ticked anyway), and fix stuff
people find missing after a move. I would also very much like to take
a shot at migrating the data.
Can somebody forward me an archive of all the old stuff so I can give
a shot at migrating the data over so you can have a look (I will make
it read only / non-indexable for the initial import)
Sam S. [email protected] wrote:
Can somebody forward me an archive of all the old stuff so I can give
a shot at migrating the data over so you can have a look (I will make
it read only / non-indexable for the initial import)
I don’t know about official archives, but gmane.org has NNTP archives.
The following slrnpull.conf should work:
-------------------- slrnpull.conf ----------------------
group_name max expire headers_only
gmane.comp.lang.ruby.general 1000000000 1000000000 0
usage: slrnpull -d $PWD -h news.gmane.org --no-post
On Fri, Oct 17, 2014 at 3:37 AM, Eric W. [email protected]
wrote:
gmane.comp.lang.ruby.general 1000000000 1000000000 0
usage: slrnpull -d $PWD -h news.gmane.org --no-post
IMO the official and oldest archive of the mailing list is here:
http://blade.nagaokaut.ac.jp/ruby/ruby-talk/index.shtml
Wait, #1 is a reply (and funnily it’s from an old email account of
mine):
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/1
Hm, maybe there is some numeric overflow…
Kind regards
robert