Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package "ocaml-linenoise":
* Package name : ocaml-linenoise
Version : 1.5-1
Upstream contact : Edgar Aroutiounian
* URL
Thanks you for the confirmation. Really appreciate it!
They have added a copyright file; so it should be all good. I was likely being
overly cautious and they might have been too. It tripped me up when they
indicated
(L)GPL might have to be treated differently, and when I looked up projects
On Tue, Mar 05, 2024 at 03:50:27AM +0530, Alan M Varghese wrote:
> What I meant was that upstream does not know where to put the copyright
> information or
> how it should be formatted. Or, to rephrase, is there a preferred format for
> a COPYRIGHT file
> in a project that uses LGPL?
There are
On Sunday, March 3, 2024 12:08:00 PM MST Loren M. Lang wrote:
> > There is certainly nothing wrong with keeping your project under your own
> > namespace, but if you would like to move it to the debian namespace, grant
> > me
> > full access to it (my Salsa username is soren) and I can then move
Your message dated Mon, 4 Mar 2024 22:58:38 +0530
with message-id
and subject line Close RFS bug for python-click
has caused the Debian Bug report #1065389,
regarding RFS: python-click/8.1.7-1 [ITA] -- Wrapper around optparse for
command line utilities - documentation
to be marked as done.
This
Hi,
Thank you for pointing this out.
I had a discussion with Peter Pentchev off-list and
we decided it would be better if I take it down from mentors so that
Peter can package it from Python Team.
I am deleting python-click package from mentors and closing the RFS bug.
Thanks,
Akash
Alan,
These are good questions.
1. Yes, there must be a copyright statement. Only the person, people, group,
or organization that holds the copyright can issue a license for other people
to use the work. So, you must have someone claiming a copyright or they do
not have the legal ability
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "shaderc":
* Package name : shaderc
Version : 2023.8-1
Upstream contact : David Neto
* URL : https://github.com/google/shaderc/
* License :
Hello Soren,
Thank you for answering my queries.
I will share this with the upstream project. The project authors are unsure how
to do this for an LGPL project. I will see tomorrow if I can find an example of
an LGPL project that includes the copyright information in the root of the
project.
What I meant was that upstream does not know where to put the copyright
information or
how it should be formatted. Or, to rephrase, is there a preferred format for a
COPYRIGHT file
in a project that uses LGPL?
This is the issue I opened upstream:
https://github.com/hyprwm/hyprlang/issues/28
On Tue, Mar 05, 2024 at 12:38:00AM +0530, Alan M Varghese wrote:
> Hello Soren,
>
> Thank you for answering my queries.
>
> I will share this with the upstream project. The project authors are unsure
> how
> to do this for an LGPL project. I will see tomorrow if I can find an example
> of
> an
11 matches
Mail list logo
