[sword-devel] [modules] Problems with gitlab project

[Cyrille]

Dears,
Please I'm still waiting for problem of permission on gitlab, i can't
neither remove the project or change the permission.

Le 04/10/2019 à 21:29, Cyrille a écrit :
>
>
> On 04/10/2019 21:27, Troy A. Griffitts wrote:
>> Ah, yes. So, we run the software package 'gitlab' which serves
>> git.crosswire.org. When you said "our gitlab repository," I
>> understood "our" to mean git.crosswire.org. Things are clear now.
> Ok nice :) Excuse me for being confused. Now who can do something?
>>
>> Thank you, Cyrille,
>>
>> Troy
>>
>> On October 4, 2019 4:06:39 PM MST, Cyrille <lafricain79 at gmail.com>
>> wrote:
>>
>>     On 04/10/2019 18:06, Troy A. Griffitts wrote:
>>
>>         Hi Fr. Cyrille, What new project are you attempting to
>>         create?  I am not sure you understand our policy on versioned
>>         source repositories.  We do not host any text development in
>>         a versioned repository on our servers.  
>>
>>     Are you speaking about gitlab or about git.crosswire?
>>     I create all the project without copyright on the gitlab repo and I want
>>     to add the lingala project and Kikongo. I created already the lingala
>>     but private, but I want it public.
>>     We changed our mind about the opportunity to push on gitlab?
>>     https://gitlab.com/crosswire-bible-society or
>>     https://gitlab.com/lafricain79/LinVB is almost the same no? But it's
>>     easier if all is grouped together.
>>     Then if it is a mistake than just remove the current lingala-verbumbible
>>     repo.
>>
>>         I don't know if this is what you are attempting to do, but
>>         this seemed likely due to your email being sent to
>>         modules at crosswire.org.  Scripts and tools are fine, but not
>>         text itself.  You can use public github or other repos for
>>         this.  The reasoning behind this is that we have a clear
>>         distinction between workspace areas which are not backed up,
>>         and source code, which is backed up.  If we started storing
>>         all of our texts in version control just because it is
>>         convenient to share and publish files with others, it would
>>         require enormous amounts of backup space.  i.e., if you are
>>         using git simply because it helps you collaborate and the
>>         work you are doing really doesn't require versioning by
>>         CrossWire or would be considered Intellectual property, then
>>         please consider using other freely available public options
>>         with seemingly unlimited resources sponsored or owned by
>>         large corporations :)  I agree git is convenient for sharing
>>         data between teams, but including terabytes of text data
>>         which doesn't really need to be versioned and preserved for
>>         posterity is something we are trying to avoid.  This may
>>         change in the future, but is currently the case right now. Troy 
>>
>>     PS: Please someone can upload the myanmar new module?
>>
>>         On 10/4/19 6:01 AM, Cyrille wrote:
>>
>>             Hello, I create a new project on our gitlab repository.
>>             But I did a mistake, I choose Private despite public, now
>>             I can't change private to public, and I can't delete the
>>             project to create an new one. Please help me. Thank you.
>>             Br Cyrille
>>             ------------------------------------------------------------------------
>>             modules mailing list modules at crosswire.org
>>             http://www.crosswire.org/mailman/listinfo/modules 
>>
>>         ------------------------------------------------------------------------
>>         modules mailing list modules at crosswire.org
>>         http://www.crosswire.org/mailman/listinfo/modules 
>>
>>
>>
>> -- 
>> Sent from my Android device with K-9 Mail. Please excuse my brevity. 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20191024/59e8a5ac/attachment.html>