From: Andreas Ericsson <ae@op5.se>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: [RFC] Git User's Survey 2009 - second trial run, and question about announcing it
Date: Mon, 06 Jul 2009 10:14:20 +0200 [thread overview]
Message-ID: <4A51B25C.9040904@op5.se> (raw)
In-Reply-To: <94a0d4530907051312u1c4bc811i4015b1eb753a8b1e@mail.gmail.com>
Felipe Contreras wrote:
> On Sun, Jul 5, 2009 at 10:45 PM, Jakub Narebski<jnareb@gmail.com> wrote:
>
>> It's just that somehow for "Git Development Community" a mailing list
>> is enough. We don't have official git blog, we don't have bugtracker
>> (issue tracker). At the beginning git didn't even had _homepage_.
>
> How do you know that? Have you already asked that question in a survey
> already? ;)
>
The git developer community flourishes without official blogs, and it
did so even before we had a webpage. In truth, I visit the mailing
list archives more often than I visit the webpage. It doesn't *need* a
blog (or a forum, or a tracker, or whatever), but some people might
find such things helpful. Personally, I'm a huge fan of having it all
in one place.
> As an experiment I added http://gitrss.q42.co.uk/announce.rss to my
> Google Reader, and through some tricks you can actually see how many
> people are subscribed to that feed: 26. For reference
> gitlog.wordpress.com has 28, and Planet IM, a relatively unknown
> planet: 844.
>
> And I have many friends who don't follow git's mailing list, so no, I
> don't think a mailing list is enough for official announcements.
>
There are no forums suitable for everyone who are interested in git
development. We can (sort of) rely on package maintainers for the
various distros to keep track of groundbreaking changes. People who
compile from source are sort of on their own if they don't want to
follow the mailing list or in some other way find out what's going
on. I don't have a problem with that, and it matches what I'd have
expected myself if I was building something from source.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2009-07-06 8:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 23:30 [RFC] Git User's Survey 2009 - second trial run, and question about announcing it Jakub Narebski
2009-07-03 0:22 ` Junio C Hamano
2009-07-03 22:23 ` Jakub Narebski
2009-07-03 23:19 ` Felipe Contreras
2009-07-04 1:26 ` David Aguilar
2009-07-04 8:24 ` Felipe Contreras
2009-07-04 22:43 ` Jakub Narebski
2009-07-04 23:46 ` Felipe Contreras
2009-07-04 22:40 ` Jakub Narebski
2009-07-04 23:53 ` Felipe Contreras
2009-07-05 17:53 ` Jakub Narebski
2009-07-05 18:30 ` Junio C Hamano
2009-07-05 19:15 ` Felipe Contreras
2009-07-05 19:45 ` Jakub Narebski
2009-07-05 20:12 ` Felipe Contreras
2009-07-06 8:14 ` Andreas Ericsson [this message]
2009-07-06 11:16 ` Jakub Narebski
2009-07-06 12:31 ` Felipe Contreras
2009-07-06 13:14 ` Andreas Ericsson
2009-07-06 21:49 ` Elijah Newren
2009-07-04 9:05 ` Martin Renold
2009-07-06 21:44 ` Jakub Narebski
[not found] ` <40aa078e0907071716k40d6ce9cwc0f9801f4042ef3a@mail.gmail.com>
2009-07-08 1:02 ` Jakub Narebski
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A51B25C.9040904@op5.se \
--to=ae@op5.se \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=newren@gmail.com \
/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 NNTP newsgroup(s).