taskSavannah Administration - Tasks: task #5214, Submission of DRI Configuration...

 
 

task #5214: Submission of DRI Configuration Applet

Submitter:  Felix Kuehling <fxkuehl>
Submitted:  Mon 30 Jan 2006 12:11:28 AM UTC
   
 
Should Start On:  Mon 30 Jan 2006 12:00:00 AM UTC Should be Finished on:  Thu 09 Feb 2006 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 10 Feb 2006 07:39:01 PM UTC, comment #6: 

Hello again Felix.
Maybe I missed something on that point.


The decision about the licenses of the project documentations was a bit prematurate and concerned discussions are in progress.

So nothing has changed until now. If you are still interested in hosting your project on Savananh, feel free to re-register.



We all expect a news item from the busy Savannah team pretty soon. We are currently working on it.

Have a nice weekend
Sebastian Wieseler,



Sebastian Wieseler <kickino>
Wed 08 Feb 2006 10:40:44 PM UTC, comment #5: 

Hello.

I'm really really sorry about it but we had to accept your decission, so cancel your submission...


Maybe the Debian people change their point of view because of the GNU FDL in the future or the FSF release a compatible FDL to the Debian Free Software Guidelines, we will see. :-/

Have a nice week.
Sebastian,

Sebastian Wieseler <kickino>
Wed 08 Feb 2006 10:33:10 PM UTC, comment #4: 

The GFDL is not acceptable for me. Even with the possibility of dual licensing this new GFDL requirement for documentation looks like a political and ideological battle between Debian and Savannah. I don't want to be part of it. I'm goint to look for other sites to host my project.

Regards,
  Felix

Felix Kuehling <fxkuehl>
Wed 08 Feb 2006 08:04:44 PM UTC, comment #3: 

Hello.

About the issue between Debian and the FSF and the GNU FDL I wrote shortly an entry (http://blog.kickino.org/archives/2006/01/#e2006-01-31T23_13_51.txt) into my blog, if you are interested feel free to read it.


On the other hand the official statement of Savannah is still:
If you don't like the GNU FDL and would like to follow Debian's point of view, hey, do so, we don't care.

At least you should use the GNU FDL for your documentation, and if you would like then use the GNU GPL, too. This is what is meant by "dual-licensing" - and this is what we accept in our policy, too.



So if you would like release your documentation under the GNU FDL and GNU GPL. (but only GNU GPL is what we don't allow).


At last, you should add copyright+license information into the README file, but not into the README, which states the licenses for png images and in CHANGELOG, TODO it is not neccessary, too.

Regards,

Sebastian Wieseler <kickino>
Wed 08 Feb 2006 03:56:49 PM UTC, comment #2: 

Thanks for the feedback. I have two questions about the documentation licenses.

1. I know that Debian does not consider the GFDL a free license due to an invariant sections clause (see http://www.debian.org/doc/manuals/ddp-policy/ch-common.en.html). Therefore I'd like to avoid the GFDL. (Did I mention that driconf is already included in Debian?) Debian recommends the GPL for software documentation. Would it be acceptable for you if I licensed the documentation of my project under the GPL?

2. To which documentation files should I add license statements?

- the current README file (definitely)
- the README file that states the licenses for png images (probably not)
- the CHANGELOG and TODO list? (not sure)

Regards,
  Felix

Felix Kuehling <fxkuehl>
Wed 08 Feb 2006 10:46:11 AM UTC, comment #1: 

Hi,
I'm evaluating the project you submitted for approval in Savannah.


At first, the address of the FSF has changed, and is now:

  51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA

Please update your license notices.

Updates versions of the GPL, LGPL and GFDL can also be found at:
http://www.gnu.org/licenses/gpl.txt
http://www.gnu.org/licenses/lgpl.txt
http://www.gnu.org/licenses/fdl.txt

Please update the copy of the license (usually, the 'COPYING' file) in your package as well.

You can find some background and a possible migration script at https://savannah.gnu.org/forum/forum.php?forum_id=3766



At second, for your images (.png) please include a README file in their directory and write there copyright+license notices down.
You can have an additional look at http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html

At third, for your documentation read these general instructions:

In order to release your project properly and unambiguously under the FDL,
please place copyright notices and permission-to-copy statements after the title page of each work.

In addition, if you haven't already, please add a copy of the FDL
(available from http://www.gnu.org/licenses/fdl.html in various formats)
as a section of your works , and as plain text in a file named 'COPYING' (http://www.gnu.org/licenses/fdl.txt).

For more information, see http://www.gnu.org/licenses/fdl.html#SEC4

http://www.gnu.org/licenses/fdl-howto.html also covers additional points,
including a smaller notice that you can use in auxiliary files.



And last, your setup.py lacks information about copyright+license. Please add there the GPL notices, too.

Regards,

Sebastian Wieseler <kickino>
Mon 30 Jan 2006 12:11:28 AM UTC, original submission:  

A new project has been registered at Savannah
The project account will remain inactive until a site admin approve or discard 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):

  <https://savannah.nongnu.org/admin/groupedit.php?group_id=8320>


######### REGISTRATION DETAILS #########

Full Name:
----------
  DRI Configuration Applet

System Group Name:
-----------------
  driconf

Type:
-----
  non-GNU software & documentation

License:
--------
  GNU General Public License V2 or later

Description:
------------
  DRIconf is a configuration applet for DRI (direct rendering infrastructure) drivers that support the DRI configuration infrastructure [1,2].

It automatically discovers DRI-capable screens and obtains configuration information encoded in the drivers themselves in an XML format. This information includes data types and valid ranges of available options as well as descriptions in multiple languages. The information is then used to present the available options to the user. No knowledge about drivers is built into DRIconf. Any driver that supports the DRI configuration infrastructure should be supported out of the box.

The configuration is saved in a configuration file (also an XML format) in the user's home directory that will be parsed by compliant DRI drivers. The configuration file can contain different settings for different screens and drivers as well as settings that only apply to specific applications.

DRIconf is written in Python using the PyGTK toolkit bindings.

Reference:
[1] http://dri.freedesktop.org/wiki/ConfigurationInfrastructure
[2] http://dri.freedesktop.org/~fxkuehl/driconf/dri_config_design_rev4.html

Latest release tarball: http://dri.freedesktop.org/~fxkuehl/driconf/driconf-0.9.0.tar.gz

Current project homepage: http://dri.freedesktop.org/wiki/DriConf

Other Software Required:
------------------------
  Python 2.3 or later (http://python.org/)
PyGTK 2.4 or later (http://pygtk.org/)
xdriinfo and libGL, included in Xorg 6.8 or later (http://xorg.freedesktop.org/)
DRI drivers, for example from the Mesa project (http://mesa3d.sourceforge.net)

Other Comments:
---------------
  I have managed DRIconf in a private CVS repository so far and used my freedesktop account for release tarballs and a project homepage. I used the DRI mailing lists for release announcements and feedback. The ongoing internationalization of DRIconf makes this approach impractical. A public CVS host is crucial to being able to release software with up-to-date translations.


Felix Kuehling <fxkuehl>

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 4 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-02-08 kickino StatusWait reply Cancelled
    Open/ClosedOpen Closed
2006-02-08 kickino StatusNone Wait reply
    Assigned toNone kickino

Back to the top

Powered by Savane 3.13-4b48.
Corresponding source code