taskSavannah Administration - Tasks: task #8877, Submission of I2C Tools for Linux


task #8877: Submission of I2C Tools for Linux

Submitted by:  Jean Delvare <khali>
Submitted on:  Sat 29 Nov 2008 01:39:37 PM UTC  
Should Start On:  Fri 28 Nov 2008 11:00:00 PM UTC Should be Finished on:  Mon 08 Dec 2008 11:00:00 PM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Cancelled Privacy:  Public
Percent Complete:  0% Assigned to:  None
Open/Closed:  Closed Effort:  0.00

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


( Jump to the original submission)

Mon 21 Sep 2009 03:53:30 PM UTC, comment #8: 

Timeout--closing this submission.

Feel free to resubmit your project later when you have more time
to deal with the registration issues.


Sebastian Gerhardt <sgerhardt>
Thu 29 Jan 2009 09:02:16 AM UTC, comment #7: 

I did ask the author but am still waiting for an answer.

Writing an alternative is not possible, I don't know anything about python.

Jean Delvare <khali>
Fri 23 Jan 2009 01:08:24 AM UTC, comment #6: 

#one piece of the project
#(py-smbus) which has been specifically released by its author as
#GPL version 2 only.

Jean, can you ask the author if he is willing to release it under GPLv2-or-later?  Or, can you find or write an alternative?

Karl Berry <karl>
Site Administrator
Thu 22 Jan 2009 06:59:48 PM UTC, comment #5: 

It's possible to import SVN history, please check:

Sylvain Beucler <Beuc>
Thu 22 Jan 2009 05:42:43 PM UTC, comment #4: 


#I have clarified all files where the GPL license note was missing
#or incomplete, however there is one piece of the project
#(py-smbus) which has been specifically released by its author as
#GPL version 2 only. Not being the copyright owner, I can't
#changethis. If this is going to be a blocker, please tell me now.

- I am sorry, but this is going to be a blocker.
One of Savannah's hosting requirement is that the complete project can legally be brought to future versions of GPL.

- As far as I know, the explicit copyright dates are not such a hard requirement. I will ask around about this and the SVN history importing thing.

Sebastian Gerhardt <sgerhardt>
Thu 22 Jan 2009 09:59:56 AM UTC, comment #3: 

Hi Sebastian,

Sorry for my silence, this has been a very busy week for me.

Yes I am still interested in my projected being hosted on Savannah. I have been working in the items from comment #1 already.

- With regards to GPL license notes all having the "or any later version" clause, I am afraid I can't do that. I have clarified all files where the GPL license note was missing or incomplete, however there is one piece of the project (py-smbus) which has been specifically released by its author as GPL version 2 only. Not being the copyright owner, I can't change this. If this is going to be a blocker, please tell me now.

- Copyright years: I am in the process of updating all the files, but checking who touched the file in what year exactly takes some time. I am not even sure what years should be listed, any year the author changed something to the file, or all years from the initial commit to the last change?

I admit I don't really get the point of listing all the years one by one. As far as I know, copyright years are only useful for 2 things: prior art and end of copyright. For the former, what matters is the first year, for the latter it is the last year, so I am really curious why it matters so much to list all the years in between.

- With regards to the word "Linux", indeed these tools are tightly related to the Linux kernel, so all occurrences of "Linux" refer to the kernel itself and not the operating system and thus do not need to be changed to "GNU/Linux". I have added the sentence you suggested to the README file.

I will attach the source tree I have come up with for your reference.

I still would like to know whether it will be possible to import the SVN history into Savannah or not.

Jean Delvare <khali>
Thu 22 Jan 2009 07:53:39 AM UTC, comment #2: 


I am waiting for an answer from you.

If within two weeks I still do not get a reply, I will remove
your project.  You will still be able to register it again once
you have the time to deal with the registration issues.

Are you still willing to host your project at Savannah? If not,
please tell us--we don't bite, and it will make us gain time.


Sebastian Gerhardt <sgerhardt>
Tue 13 Jan 2009 04:33:25 PM UTC, comment #1: 


sorry for the delay -- we have quite a backlog of open items here.
Your project will be judged in regard to
so make sure every point has been met.

On a first look, I would point out these issues:

- All GPL license notes need to have the "or any later version" clause.

- The years of the copyright should be written down explicit, not as ranges (1999 -- 2002  --->  1999, 2000, 2001, 2002)

- Please help your users to distinguish the kernel from the operating system. We understand that your project is somewhat more related to a specific kernel than to the operating system, but you should make it clear in your Readme and description when you are talking about what.
For example, "This is a set of tools for the Linux kernel. They compile, run and have been tested on GNU/Linux."

You can attach an upgrade archive to this tracker item. I will automatically be noted about this and can continue the approval process then.

Sebastian Gerhardt <sgerhardt>
Sat 29 Nov 2008 01:39:37 PM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.

Registration Administration

While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):

Registration Details

  • Name: I2C Tools for Linux
  • System Name:  i2c-tools
  • Type: non-GNU software & documentation
  • License: GNU General Public License v2 or later


This package contains a heterogeneous set of I2C tools for Linux: a bus probing tool, a chip dumper, register-level access helpers, EEPROM decoding scripts, and more. Low-level I2C access tools are written in C, while EEPROM decoding scripts are written in perl.

Other Comments:

The i2c-tools project is currently hosted at lm-sensors.org. I want to move it to another host because i2c tools are useful beyond the scope of hardware monitoring, and because not all hardware monitoring chips need I2C at all. There has been a lot of confusion between i2c and lm-sensors in the past and I am trying to clear it up.

The source code of i2c-tools was maintained in a SVN tree at lm-sensors.org. I would like to import all the SVN history into the new savannah project if this is possible.

Tarball URL:


Jean Delvare <khali>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by sgerhardt (Posted a comment)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 10 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-09-21 sgerhardt StatusIn Progress => Cancelled
        Open/ClosedOpen => Closed
    2009-06-03 sgerhardt Carbon-CopyRemoved 20998 => -
    2009-06-03 sgerhardt Carbon-CopyRemoved 71290 => -
    2009-06-03 sgerhardt Carbon-CopyRemoved 12366 => -
    2009-06-03 sgerhardt Carbon-CopyRemoved 685 => -
    2009-06-03 sgerhardt Attached File#17303 => Removed
    2009-01-22 sgerhardt StatusPing-ed => In Progress
    2009-01-22 khali Attached File- => Added i2c-tools.tar.bz2, #17303
    2009-01-22 sgerhardt StatusNone => Ping-ed

    Back to the top

    Powered by Savane 3.5