mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] kernel traczilla: tracking active kernel development
Date: Mon, 7 Apr 2008 22:51:20 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0804072235470.8933@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.0803171613310.4997@axis700.grange>

On Mon, 17 Mar 2008, Guennadi Liakhovetski wrote:

> The first thing one normally does before starting a new development is 
> research whether and what has already been done in this area. Unless, of 
> course, one knows it beforehand:-)
> 
> This research might sometimes be quite time-consuming and might not always 
> deliver expected results. Wouldn't it be good to have a central page for 
> tracking such hot kernel projects _before_ they get submitted into 
> mainline. One would just decide "now I am prepared to tell the world about 
> my work", go to this site, register, enter a description of his project in 
> an appropriate section with some contact information (a mailing list that 
> the developer is regularly reading should be enough). The site could be 
> just organized in a hierarchial manner. For example, to add a new ARM 
> XScale port one would go
> 
> top -> Processor architectures -> ARM -> XScale -> ...
> 
> I am no designer, no web-administrator, and no content-provider, but 
> knowing that LKML loves action above words, I put up a sceleton trac wiki 
> site at
> 
> http://gross-embedded.homelinux.org/trac.fcgi
> 
> so everybody could have a look, play with it, and decide if they think 
> something like this could be useful. This is not intended as a final 
> solution, so, don't take it too seriously. It is hosted on a 500MHz ARM 
> system, so, be patient:-)

Ok, in about 3 weeks there have been maybe 100 or 200 connections to the 
server, most of them from google and yahoo bots and from other less 
pleasant scanners:-) And - not a single new entry. I've modified the 
layout a bit to exactly reproduce the kernel tree, so on the top level I 
have arch/, block/, drivers/, net/, etc. So it should even be easier to 
find a suitable place to enter ones work and to find previous 
developments. I'll leave this site for another 2-3 days running, but if 
it still doesn't attract any contributors and / or feadback, I'll just 
take it down.

I certainly can understand why there wasn't much interest in it. If a 
development is payed, one often is not allowed to disclose it before the 
completion. I've hoped that "free" developers might get attracted by this 
idea, but this seems to be not the case either, or just not many of them 
read LKML:-)

Anyway, this is just to document the intention to close the page.

Thanks
Guennadi
---
Guennadi Liakhovetski

      reply	other threads:[~2008-04-07 20:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 15:30 Guennadi Liakhovetski
2008-04-07 20:51 ` Guennadi Liakhovetski [this message]

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=Pine.LNX.4.64.0804072235470.8933@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®