unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: rixed@happyleptic.org
To: guile-user@gnu.org
Cc: anton.vidovic@gmx.de
Subject: Re: guile user base
Date: Mon, 28 Nov 2011 10:42:31 +0100	[thread overview]
Message-ID: <20111128094231.GA20529@ccellier.rd.securactive.lan> (raw)
In-Reply-To: <20111123233913.GA7011@shuttle.happyleptic.org>

Thank you all for your responses.

The target audience of the newsletter I was contemplating being free
software hackers rather than inexperienced programmers, I don't think
a wiki, a stackoverflow-style website nor a web forum would suit ; In
essence because the information that would be provided would be
obsolete quite quickly.

There are certainly many cool things that could be done to attract
newcomers - first and foremost, update the web site as mentioned - but
that's not my intent for many reasons (mostly, I think guile is more
useful as a free software extension tool than as a general programming
learning tool, but this is of topic). What _I_ feel the need of, being
part of the herd of free software programmers inexperienced with scheme,
is a succinct and up to date source of news related to the project, so
that I can:

- see how well or how bad things are going
- what's coming
- what's requiring help
- what other projects use guile and how
- how to make the most of this or that uber-feature
- ideas of new things to try
- examples of common problems and solutions
- explanations on how things work from the inside
- etc...

In short, anything to keep me up to date, give my ideas and knowledge.
I believe this can be useful to people already using guile as well as
attract the attention of potential new users.

A monthly newsletter of the size of the Chicken Gazette looks appropriate
to me. As for the free time I'm willing to spend on this, well, I'm
offering to compile a first edition only in the hope that other people
would volunteer for the next, as :

- I'm not knowledgeable in Guile not Scheme
- I have not many time per week for anything that's not coding (pity my
  children)
- I'm not comfortable with English
- Scheme comes only third in my list of favorite programming languages
  (C and OCaml being the firsts, for those interested)

Anyway, I'm going to try to compile some first newsletter with abstracts
from the guile MLs and IRC channel. I may also bug some people
personally for some more infos. Then I will host the thing, buz about
it a little and see what I catch in my net :-)
Enough talking, we will see then.




  parent reply	other threads:[~2011-11-28  9:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 23:39 guile user base rixed
2011-11-27 22:23 ` Ludovic Courtès
2011-11-28  0:14   ` Linas Vepstas
2011-11-28 13:00     ` Ludovic Courtès
2011-11-28 13:25       ` Peter Brett
2011-11-28 22:42         ` Ludovic Courtès
2011-11-28  9:42 ` rixed [this message]
2011-11-28 16:03   ` Linas Vepstas
2011-11-28 22:50   ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2011-11-24 20:29 Anton Vidovic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111128094231.GA20529@ccellier.rd.securactive.lan \
    --to=rixed@happyleptic.org \
    --cc=anton.vidovic@gmx.de \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).