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

[Jed Brown]

I think it's just links and screenshots.

Barry Smith <bsmith at petsc.dev> writes:

>   Crap, do you have any documents you used in the submission process so I can reuse them?
>
>
>> On Jun 20, 2022, at 3:41 PM, Jed Brown <jed at jedbrown.org> wrote:
>> 
>> I submitted in February and never heard back. Feel free to submit again.
>> 
>> Barry Smith <bsmith at petsc.dev <mailto:bsmith at petsc.dev>> writes:
>> 
>>> 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/ <https://about.gitlab.com/blog/2022/02/04/ultimate-perks-for-open-source-projects/> <https://about.gitlab.com/blog/2022/02/04/ultimate-perks-for-open-source-projects/ <https://about.gitlab.com/blog/2022/02/04/ultimate-perks-for-open-source-projects/>>