git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: 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: Sun, 5 Jul 2009 23:12:57 +0300	[thread overview]
Message-ID: <94a0d4530907051312u1c4bc811i4015b1eb753a8b1e@mail.gmail.com> (raw)
In-Reply-To: <200907052145.27995.jnareb@gmail.com>

On Sun, Jul 5, 2009 at 10:45 PM, Jakub Narebski<jnareb@gmail.com> wrote:
> On Sun, 5 July 2009, Felipe Contreras wrote:
>> On Sun, Jul 5, 2009 at 9:30 PM, Junio C Hamano<gitster@pobox.com> wrote:
>>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>>>> I guess Junio's blog is the most official one ATM,...
>>>
>>> Sorry, don't.
>>>
>>>  - Even if you are pretending to be a git community member, you are merely
>>>   a phoney if you are not reading it.
>>>
>>>  - If you want to be up-to-date with what is happening in the community,
>>>   you should be reading it.  Any important announcement always will
>>>   appear there.
>>>
>>> That would be an official blog.  I do not use mine that way, and nobody
>>> has to follow it in order to function better in the git land.
>>>
>>> It's like expecting Linus to announce the kernel release in his blog.
>>>
>>> Not going to happen.  The official channel of this community has always
>>> been this list.
>>>
>>> I'm OK if somebody declares that he will use his blog to relay important
>>> announcements from this list, to help blog minded people to follow it
>>> instead of reading the list.
>
> There is always http://gitrss.q42.co.uk/announce.rss which extracts
> "[ANNOUNCE]" emails from git mailing list into an RSS feed, for those
> who prefer this way of watching for git news.

That's nice, although relatively unknown it seems.

>>> But that won't be me.
>>
>> I know there's no official git blog, I've tried to change that, but so
>> far that hasn't happened. IMHO for now the most popular git blog(s)
>> should announce the survey, I'll announce it at gitlog.wordpress.com
>> but it is far from being popular.
>>
>> I understand your position for not making your personal blog the
>> official one; I wouldn't do that on my personal blog either
>> (felipec.wordpress.com) that's why I created a separate blog for that,
>> where you, or anyone else, can do official git posts instead of on
>> their personal blog.
>
> 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? ;)

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.

It would be interesting to clone http://gitrss.q42.co.uk/announce.rss
into gitlog.wordpress.com... I'll see if I can find a way to do that
:)

> A propos blogs: Elijah Newren writes from time to time about git
> on http://blogs.gnome.org/newren/ ; I think this blog is in a few
> GNOME planets, so if he were so kind as put announcement there
> when the time comes...  It would be good to have such announcement
> on some blog which is in Perl blog planet (Perlsphere and/or Planet
> Perl Iron Man), and similarly for other communities which rely on
> blogs (KDE, Ruby: anyone?).
>
> There is also http://www.versioncontrolblog.com (which is currently
> off-line, so I can't check who to contact).

Yeap, posting on planets will get a lot of attention.

Cheers.

-- 
Felipe Contreras

  reply	other threads:[~2009-07-05 20:13 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 [this message]
2009-07-06  8:14               ` Andreas Ericsson
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=94a0d4530907051312u1c4bc811i4015b1eb753a8b1e@mail.gmail.com \
    --to=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).