[petsc-dev] Upgrade to Gitlab Open source project must be done ASAP?

[Jed Brown]

Note this from the FAQ:

Can I also use this license for projects that aren't open source, or to host private projects?  <https://about.gitlab.com/solutions/open-source/join/#requirements> 
No. You may use the GitLab license you receive from the GitLab for Open Source Program only for the publicly visible open source projects for which it was approved. In some cases, we allow program members to host a small number of private projects if those projects contain sensitive data. Please email us at `opensource at gitlab.com` to ask about your case. You must obtain written permission from us in order to use the license outside of program requirements.


On Mon, Jun 20, 2022, at 6:50 PM, Barry Smith wrote:
> 
>   Thanks. Looks like we have some cleaning up to do and can't treat the petsc group as a trash dump :-)
> 
> 
>> On Jun 20, 2022, at 7:40 PM, Ham, David A <david.ham at imperial.ac.uk> wrote:
>> 
>> The front page you link to below contains the following:
>>  
>> Requirements include:
>> · *OSI-approved open source license*: All of the code you host in this GitLab group must be published under OSI-approved open source licenses <https://opensource.org/licenses/category>
>> I believe https://gitlab.com/petsc is the group (it has a Group ID) and hence everything under https://gitlab.com/petsc would need to have an OSI licence.
>>  
>> Cheers,
>>  
>> David
>>  
>> --
>> Dr David A. Ham
>> Reader in Computational Mathematics
>> Department of Mathematics
>> Imperial College London
>>  
>>  
>>  
>> *From: *petsc-dev <petsc-dev-bounces at mcs.anl.gov> on behalf of Barry Smith <bsmith at petsc.dev>
>> *Date: *Tuesday, 21 June 2022 at 05:35
>> *To: *petsc-dev <petsc-dev at mcs.anl.gov>
>> *Subject: *Re: [petsc-dev] Upgrade to Gitlab Open source project must be done ASAP?
>>  
>>  * Benefits of the GitLab for Open Source Program apply to a namespace. To qualify, every project in an applicant’s namespace must carry an OSI-approved open source license.
>>  
>> Again, GitLab when you use language that a reasonable person may not understand you provide a link to its meaning. Is the entire petsc/* the namespace? If so we have to be careful about all the packages and oddballs in petsc/* that may not have license information etc. Or is petsc/petsc a name space and this all we care about?
>> 
>>> On Jun 20, 2022, at 3:31 PM, Barry Smith <bsmith at petsc.dev> wrote:
>>>  
>>>  
>>>    Did we drop the ball on this?  I cannot find out what "tier" PETSc is currently in, I hunt around the settings pages for PETSc and cannot find this information. GitLab should provide a link to how to check this for your project in all their nagging to get people to do something, please at least be informative in your nagging, don't expect me to read your mind.
>>>  
>>>  
>>>  
>>> https://about.gitlab.com/blog/2022/02/04/ultimate-perks-for-open-source-projects/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20220620/28d10f38/attachment.html>