All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Felipe Contreras" <felipe.contreras@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, "git list" <git@vger.kernel.org>
Subject: Re: Git weekly news: 2008-49
Date: Fri, 5 Dec 2008 23:33:39 +0100	[thread overview]
Message-ID: <200812052333.40213.jnareb@gmail.com> (raw)
In-Reply-To: <94a0d4530812051349tff33aaan76e29402215dcae2@mail.gmail.com>

On Fri, 5 Dec 2008, Felipe Contreras wrote:
> On Fri, Dec 5, 2008 at 10:54 PM, Junio C Hamano <gitster@pobox.com> wrote:
> > Jakub Narebski <jnareb@gmail.com> writes:

> > Felipe's page currently is a random collection of links, and other than
> > their titles, there is no indication for readers to judge which link is
> > worth clicking and reading.  It does not even mention who wrote each
> > piece, let alone editorial comments (e.g. "This is worth reading") like
> > you added.  When you click one of them in order to read it, you leave the
> > "list of links".  That is not how navigation (the click and thought flow
> > for the readers) usually works in a "Planet".
> 
> Lets remember that this is the first try, and there's many more links
> that what would fit in any given week, but I just didn't want to leave
> them out.
> 
> Maybe for the next weeks I'll do a bit of explanation about each link,
> lets see. 

Not necessary a bit of explanation about _each_ link, but at least put
them in rough categories (as a kind of you did), separating praise,
explanation/documentation, web and Ruby stuff and solving, and solving
specific issue (like those on BlogPosts wiki page).
 
 
> I actually propose two things:

[...]
> b) git blog
> 
> A blog can be shared by a bunch of people, much line online news
> sites. Junio could write a post once for each release, for example,
> without having to setup his own blog, maybe somebody else can
> copy-paste "What's cooking in git.git", or any kind of semi-official
> announcement.

Junio has its own blog: http://gitster.livejournal.com

And there is RSS feed for [ANNOUNCE] posts at http://gitrss.q42.co.uk
and "What's cooking in git.git" and the like.

> And I'm sure there will be one or two developers who wouldn't mind
> sharing their frustrations and/or visions.

Would they want to write blog posts? Git is very much email driven
community...

[...]
> For b) I just need interested people to send me their emails.

To apply for accounts, isn't it?
-- 
Jakub Narebski
Poland

  reply	other threads:[~2008-12-05 22:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05  0:43 Git weekly news: 2008-49 Felipe Contreras
2008-12-05 16:02 ` Jakub Narebski
2008-12-05 17:00   ` Michael J Gruber
2008-12-05 17:46   ` Felipe Contreras
2008-12-05 19:27     ` Jakub Narebski
2008-12-05 21:12     ` Nanako Shiraishi
2008-12-05 21:44     ` Santi Béjar
2008-12-05 21:57       ` Felipe Contreras
2008-12-05 22:11         ` Santi Béjar
2008-12-05 20:54   ` Junio C Hamano
2008-12-05 21:49     ` Felipe Contreras
2008-12-05 22:33       ` Jakub Narebski [this message]
2008-12-05 22:18     ` Nanako Shiraishi
2008-12-05 22:42       ` Junio C Hamano
2008-12-06  3:53     ` Casual observers (was Re: Git weekly news: 2008-49) Jean-Rene David
2008-12-06  5:53       ` Edward Z. Yang
2008-12-06  6:52       ` Boyd Stephen Smith Jr.

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=200812052333.40213.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.