taskSavannah Administration - Tasks: task #5176, Submission of Qualification and...

 
 

task #5176: Submission of Qualification and Selection of Opensourc

Submitter:  Raphaël Semeteys <rsemeteys>
Submitted:  Fri 20 Jan 2006 05:06:42 PM UTC
   
 
Should Start On:  Fri 20 Jan 2006 12:00:00 AM UTC Should be Finished on:  Mon 30 Jan 2006 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 08 Feb 2006 08:24:22 PM UTC, comment #9: 

Very good news !!!
Thanks a lot for your help and your time.
I really hope that the QSOS method will help people to better understand the nature of free software (and differences with open source software) and thus promote the movement.

Anonymous
Wed 08 Feb 2006 10:24:09 AM UTC, comment #8: 

Hi,

I have approved your project.  You will receive an automated e-mail containing detailed information about the approval.

Regards.

Sebastian Wieseler <kickino>
Mon 06 Feb 2006 09:50:16 AM UTC, comment #7: 

the Tarball is here : http://qsos.free.fr/download/qsos-1.5.tar.gz

Regards,

        Gonéri

Goneri Le Bouder <goneri>
Mon 06 Feb 2006 09:48:17 AM UTC, comment #6: 

Hi,

I've just put a tarball of QSOS-1.5 silently updated.

Cheers,


        Gonéri Le Bouder (QSOS team)

Goneri Le Bouder <goneri>
Wed 01 Feb 2006 02:49:12 PM UTC, comment #5: 

Hello.

images/* lack information about copyright and license. Please include a README file in this directory and include there such notices for the files.
See also http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html

Regards,

Sebastian Wieseler <kickino>
Fri 27 Jan 2006 03:42:33 PM UTC, comment #4: 

Hi there,

We updated the web site to better fullfill FDL instructions :
- Official version of FDL in english
- Sources of the QSOS document (tex, Makefile, ...) in a tarball
- Licence notices in every source and document

Regards,

Raphaël

Raphaël Semeteys <rsemeteys>
Thu 26 Jan 2006 11:07:12 PM UTC, comment #3: 

Hello.

At first, I saw that you use a french license text on your website.
Please have a look at http://www.gnu.org/licenses/gpl-faq.html#GPLTranslations which says:

"This translation of the GPL is informal, and not officially approved by the Free Software Foundation as valid.  To be completely sure of what is permitted, refer to the original GPL (in English)."

... the same things for the GNU FDL.



At second, I found .dvi and .pdf links on your website but no link to the source code (.tex or something like that). You must provide such resources for your project, too.


So I list the general instructions for the GNU FDL:

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 (of your source code and the notices should be printed out in the resulted file format [pdf] as well).

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.


Since OOo file format is not plaintext you should write the notices in OOo on your own in there, too.

Hope that helps. Regards,

Sebastian Wieseler <kickino>
Tue 24 Jan 2006 04:44:17 PM UTC, comment #2: 

Hello,

Here are the answers to your questions.

Point 1:
The current website is available on http://www.qsos.org. I also attach a tarball containing folowing documents :
- The QSOS Method itself (French, Latex and PDF formats)
- Samples of QSOS Evaluations (French, OOo format)
- Slides presenting QSOS (French, OOo format)

QSOS is not software but a method to evaluate, compare and select Free & opensource software. Therefore it
consists in no source code but only documents.

Points 2 and 3:
QSOS, as a method, addresses Free AND Opensource software. The name should have been QSFOS but it seems
difficult to change its name now since the method is already used and known under that name.

Previous versions were released under the CreativeCommons by-nc-sa licence, which is not free. We were finally
able to publish the 1.5 release under the GFDL, but we had to do it in two steps in order to convince our management,
this is why previous releases of QSOS were released under the CC by-nc-sa. FDL is what we wanted since the early
beginning as it is for us the only way to freely share transparent and objective knowledge about free and opensource software.
This also is the reason of our submission to Savannah hosting, in order to label the QSOS methodological project as a free one,
compliant with the free movement ethics (as stated in the "Manifeste QSOS" invariant section in the method).

Point 4:
Sorry I wasn't exhaustive in QSOS dependencies:
QSOS method depends on:
- For edition : latex, insckape
- For opaque format generation: make, latex2html, hevea, imagen, perl, pdflatex

QSOS Evaluation documents (ID cards and Evaluation sheets) depend on OOo


I hope this answer to your questions.

Best regards,

Raphaël Semeteys

Raphaël Semeteys <rsemeteys>
Mon 23 Jan 2006 08:32:19 AM UTC, comment #1: 

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


At first, p

lease include a (perhaps temporary) URL pointing to the source code.
The description you gave when registering will not be read by the general public.
If you are still concerned with privacy, however, you can forward the code to me by email.

We wish to review your source code, even if it is not functional, to catch potential legal issues early.

For example, to release your program properly under the GPL you must include a copyright notice and
permission-to-copy statements at the beginning of every file of source code.  This is explained in
http://www.gnu.org/licenses/gpl-howto.html.  Our review would help catch potential omissions such as these.



At second, Savannah's mission is to host free software projects, and we want the public to think of them
as free software projects.  A project name that says "open" will tend to lead people to think
of the project as "open source" instead of "free software".

We would be glad if you accept to use "free" instead of "open" in your project name.


At third, note that Savannah supports projects of the Free Software movement, not projects of the Open Source movement.

We are careful about ethical issues and insist on producing software that is not dependent on proprietary software.

While Open Source as defined by its founders means something pretty close to Free Software, it's frequently
misunderstood.
For more information, please see http://www.gnu.org/philosophy/free-software-for-freedom.html.


At fourth, does your project rely on other programs than OOo?

Regards,

Sebastian Wieseler <kickino>
Fri 20 Jan 2006 05:06:42 PM 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.gnu.org/admin/groupedit.php?group_id=8299>


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

Full Name:
----------
  Qualification and Selection of Opensourc

System Group Name:
-----------------
  qsos

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

License:
--------
  GNU Free Documentation License

Other License:
--------------
  GFDL is also applied to documents produced when using QSOS :
- ID card
- Evaluation sheet
- Software Domain synthesis

The objective is to let anybody the opportunity to improve QSOS documents and thus obtain objectivity and transparancy.

Description:
------------
  The Qualification and Selection of Opensource Software (QSOS) method has being design to evaluate, qualify, select and compare free and open source software and projects with a formalized and traceable approach.

For the time being the method only exist in French but is under English translation.

QSOS assessement model is organized in 4 hierachical levels.
3 major assessment axis grouping several assessment areas :
      - functionnal coverage: assessment areas depend on the software family considered
      - risks from the user perspective: with 5 predifined assessment areas
            - Intrisic robustness
            - Industrialised solution
            - Integration
            - Technical adaptability
            - Strategy
      - risks from service provider perspective (regarding level of support we can provide on the software)
            - Maintainability
            - Source code mastery (I'me not sure of the translation here)

Each assessment is then composed of criteria and under-criteria.

Other Software Required:
------------------------
  Evaluations and templates to produce evaluation are in OpenDocument format and rely on OpenOffice.org v2.

Other Comments:
---------------
  "Opensource software" is included QSOS and not Free Software for historical reasons anf it is difficult for us to rename the method (QSFOS for instance). I really hope it is ok and won't be a problem...


Raphaël Semeteys <rsemeteys>

 

(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 Done
    Open/ClosedOpen Closed
2006-01-23 kickino StatusNone Wait reply
    Assigned toNone kickino

Back to the top

Powered by Savane 3.13-d3ae.
Corresponding source code