From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>,
Paul Goyette <paul-3orOWTcw9wBWk0Htik3J/w@public.gmane.org>
Subject: New home for i2c-tools (RFC)
Date: Thu, 29 Jan 2009 10:37:17 +0100 [thread overview]
Message-ID: <20090129103717.025661db@hyperion.delvare> (raw)
Hi all,
I am in the process of moving i2c-tools away from lm-sensors.org to a
new home. My reasons for doing this are:
* The i2c tools are useful way beyond lm-sensors, and on the other hand
lm-sensors works fine on many recent systems without I2C support at
all. There has been a lot of confusion about i2c and lm-sensors in
the past and I hope that moving i2c-tools somewhere else will help
put an end to it.
* Administration of lm-sensors.org isn't always as good as I would
like. I am not blaming our host, we get everything for free and it
isn't that bad, but apparently our admin is busy with more important
things so I don't want to put additional load on him.
* I hope that a clean, simple, standalone project will more easily
attract extra developers.
Now the question is: where do we go? At first I had considered Savannah
[1], essentially because I have other projects hosted there. One
problem though is that they are rather strict when it comes to
licenses. In particular, GPL v2 only code isn't good enough for them,
while one piece of i2c-tools is released under that license.
[1] https://savannah.nongnu.org/
An alternative I have considered since then is to put the code on
kernel.org. After all, i2c-tools are tightly linked to the Linux
kernel at the moment.
There are pros and cons both ways. At Savannah we'd have a Subversion
tree, which is what we already have for i2c-tools at the moment so
importing the code should be easy. Creating accounts for extra
contributors is easy. We get a bug tracking system and web space.
At kernel.org, we would have a git tree. More powerful than Subversion,
but also a little more complicated, and we probably don't need that
much power for such a small project. I'm not sure how easy it is to
import a Subversion repository into a git tree. No bug tracking system.
No accounts for contributors. The web pages would probably go in
i2c.wiki.kernel.org. Might become a little confusing if i2c-tools ever
supports another OS than Linux.
And there are other options available, such as Gna! or BerliOS. Never
used these myself though.
[2] https://gna.org/
[3] http://developer.berlios.de/
As far as I am concerned, I can live with all options, but what I
really want to know is: which option would potential future
contributors prefer? Please speak up if you care!
Thanks,
--
Jean Delvare
next reply other threads:[~2009-01-29 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 9:37 Jean Delvare [this message]
[not found] ` <20090129103717.025661db-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-29 11:15 ` New home for i2c-tools (RFC) Wolfram Sang
2009-01-29 15:56 ` Mike Frysinger
[not found] ` <200901291056.12963.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-01-29 16:00 ` Paul Goyette
2009-01-29 16:28 ` Jean Delvare
[not found] ` <20090129172812.22c3d301-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-29 16:30 ` Wolfram Sang
[not found] ` <20090129163039.GF32057-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-01-29 16:38 ` Tony Lindgren
[not found] ` <20090129163845.GC32148-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2009-01-29 16:48 ` Mike Frysinger
[not found] ` <200901291148.06805.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-01-29 16:56 ` Tony Lindgren
[not found] ` <20090129165615.GJ32148-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2009-01-29 17:10 ` Mike Frysinger
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=20090129103717.025661db@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=paul-3orOWTcw9wBWk0Htik3J/w@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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