taskSavannah Administration - Tasks: task #15757, Submission of Guix Translations

 
 

task #15757: Submission of Guix Translations

Submitted by:  julien lepiller <roptat>
Submitted on:  Sun 23 Aug 2020 06:58:33 PM UTC  
 
Should Start On:  Sun 23 Aug 2020 12:00:00 AM UTC Should be Finished on:  Wed 02 Sep 2020 12:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  In Progress Privacy:  Public
Percent Complete:  0% Assigned to:  None
Open/Closed:  Open 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)

Tue 08 Sep 2020 03:08:10 PM UTC, comment #7: 

comment #6:

> comment #5:
> >
> > I'm inclined to think that as of now, "Official GNU software" is the
> > best choice for guix-i18n, given that Guix itself is "Official GNU
> > software" and translations are most often considered part of the same
> > project.
>
> Well, a part of an official GNU package isn't necessarily also a GNU
> package (in most cases it isn't). for example, we don't want all
> possible parts of GNU packages to be listed on https://www.gnu.org/s
> as GNU packages (that would be neither feasible nor useful).
>


Okay I think I see your point.

>
> > However, if we'd like to add new group types for translations, the
> > possible candidates could be "Translations of official GNU software"
> > and "Translations of non-GNU software and documentation".
> >
> > If we are aiming to be more general than just translations, we could
> > perhaps do "Extras for official GNU software" and "Extras for non-GNU
> > software and documentation"?
>
> "Extras" or "portions" look good to me; I'm not sure we'll need the
> "non-GNU" counterpart: likewise, we have no "nongnu translation teams"
> or "non-GNU user groups".


Either of those would work for me as well.  And sure, we can only add
what we need right now, and only add the others at some point in the
future if there is an actual need for them.

Amin Bandali <bandali>
Site Administrator
Tue 08 Sep 2020 01:55:35 PM UTC, comment #6: 

comment #5:

>
> I'm inclined to think that as of now, "Official GNU software" is the
> best choice for guix-i18n, given that Guix itself is "Official GNU
> software" and translations are most often considered part of the same
> project.


Well, a part of an official GNU package isn't necessarily also a GNU package (in most cases it isn't). for example, we don't want all possible parts of GNU packages to be listed on https://www.gnu.org/s as GNU packages (that would be neither feasible nor useful).

> However, if we'd like to add new group types for translations, the
> possible candidates could be "Translations of official GNU software"
> and "Translations of non-GNU software and documentation".
>
> If we are aiming to be more general than just translations, we could
> perhaps do "Extras for official GNU software" and "Extras for non-GNU
> software and documentation"?


"Extras" or "portions" look good to me; I'm not sure we'll need the "non-GNU" counterpart: likewise, we have no "nongnu translation teams" or "non-GNU user groups".

Ineiev <ineiev>
Site Administrator
Mon 07 Sep 2020 01:17:24 PM UTC, comment #5: 

comment #3:

> Another thought: this type of group, "Official GNU Software", is reserved for GNU packages; probably we'll want to use something different, like "www.gnu.org translation teams", or create a new group type.


I'm inclined to think that as of now, "Official GNU software" is the
best choice for guix-i18n, given that Guix itself is "Official GNU
software" and translations are most often considered part of the same
project.

However, if we'd like to add new group types for translations, the
possible candidates could be "Translations of official GNU software"
and "Translations of non-GNU software and documentation".

If we are aiming to be more general than just translations, we could
perhaps do "Extras for official GNU software" and "Extras for non-GNU
software and documentation"?

Amin Bandali <bandali>
Site Administrator
Mon 07 Sep 2020 01:09:01 PM UTC, comment #4: 

Hi Julien,

comment #2:

> Hi Amin,
>
> thanks for taking a look at this. I have simply copied the po and pot files as they are present or generated in the guix repository, so the issue is with these files. I've sent a message to the development list at https://lists.gnu.org/archive/html/guix-devel/2020-08/msg00195.html to collect more thoughts on what to do. I agree with you that they should be copyrighted the authors of guix. You'll see that po files also have a copyright line for each individual translator who worked on it.


Thank you for your reply.  I will keep an eye on that thread and see
what comes of it, so we could all act accordingly.

Amin Bandali <bandali>
Site Administrator
Mon 07 Sep 2020 09:12:25 AM UTC, comment #3: 

Another thought: this type of group, "Official GNU Software", is reserved for GNU packages; probably we'll want to use something different, like "www.gnu.org translation teams", or create a new group type.

Ineiev <ineiev>
Site Administrator
Tue 01 Sep 2020 02:15:34 PM UTC, comment #2: 

Hi Amin,

thanks for taking a look at this. I have simply copied the po and pot files as they are present or generated in the guix repository, so the issue is with these files. I've sent a message to the development list at https://lists.gnu.org/archive/html/guix-devel/2020-08/msg00195.html to collect more thoughts on what to do. I agree with you that they should be copyrighted the authors of guix. You'll see that po files also have a copyright line for each individual translator who worked on it.

julien lepiller <roptat>
Mon 31 Aug 2020 10:33:11 AM UTC, comment #1: 

Hi Julien,

Thanks for the submission.

I had a quick look through the attached tarball.  I have a couple of
questions regarding the copyright headers, in both pot files and po
files.

I see that all of the pot files have the following copyright notice,
with Ludo’ listed as the only copyright holder:

    Copyright (C) YEAR Ludovic Courtès

Since Ludo’ isn't the only copyright holder and contributor to Guix
(anymore :-)), wouldn't it be more appropriate to have something like
the following?

    Copyright (C) YEAR the authors of Guix (msgids)

Which is what I see is used in some of the po files.  Would that be more
in line with <https://translationproject.org/html/whydisclaim.html>?

Also, I see some of the po files mention the Free Software Foundation as
the copyright holder.  Is that indeed the case?  I'm curious since Guix
itself is not copyright FSF and does not requirement assignment from
contributors.

For what it's worth, I ask these questions both as a reviewer and on a
personal level (I have been looking into translating Guix recently).

Thanks,
amin

Amin Bandali <bandali>
Site Administrator
Sun 23 Aug 2020 06:58:33 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: Guix Translations
  • System Name:  guix-i18n
  • Type: Official GNU software
  • License: GNU General Public License v3 or later

Description:

This project contains the translation files for GNU Guix, a transactional package manager and an advanced distribution of the GNU system that respects user freedom. Our translation interface uses this repository to pick up new translation work, as well as commit translation done by our translators. This needs to be done in a separate repository, so that we don't need to give access to an external tool to our own repositories.

Other Comments:

The purpose of this separate project, instead of using a separate repository in the Guix project, is to prevent our tool from having access to the repository. Even though it would be configured to access only that separate repository, but the public key would still able to push to other parts of the project, and we don't want that.

Note that I'm not a maintainer of Guix, but I'm a member of it, and more or less responsible for NLS stuff. We have discussed this in our ML, see https://lists.gnu.org/archive/html/guix-devel/2020-02/msg00360.html (yeah, I know it was some time ago ^^')

Tarball URL:

https://savannah.gnu.org/submissions_uploads/guix-translations.tar.gz

julien lepiller <roptat>

 

(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

 

Carbon-Copy List
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by bandali (Posted a comment)
  • -email is unavailable- added by roptat (Submitted the item)
  •  

    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.

     

     

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-08-31 bandali StatusNone => In Progress

    Back to the top


    Powered by Savane 3.5