I'd be happy to assist as well, though I don't have much spare time outside of work. I have intermediate experience packaging internal software for our company, and I've always done my best to follow Debian's packaging guidelines there. I am, however, also unfamiliar with the contribution process for Debian itself.
On Mon, 7 Jun 2021 at 18:25, Paul Levy <[email protected]> wrote: > > Sorry for the late reply. Yes, we are interested in working to get osgEarth > back into Debian and collaboratively maintaining the package. > > As I mentioned last time, we do not understand the process, even the basics > of the process as in who builds the package. I apologize for the lack of > knowledge and we are certainly willing to address the previous concerns, but > we do need some pointers or a partner who knows the process. > > Thank you > > -- > Paul Levy : Pelican Mapping > > > On Sat, May 15, 2021 at 7:18 AM Sebastiaan Couwenberg <[email protected]> > wrote: >> >> On 5/15/21 12:12 PM, Aymeric Agon-Rambosson wrote: >> > I am writing you to ask whether it would be possible to >> > put osgearth back in debian unstable. >> >> You should get in touch with the other who want osgearth back in Debian, >> and collaboratively maintain the package. See: >> >> https://lists.debian.org/debian-gis/2020/11/msg00008.html >> https://lists.debian.org/debian-gis/2020/12/msg00003.html >> >> https://alioth-lists.debian.net/pipermail/pkg-grass-devel/2021-March/089100.html >> >> As I don't use osgearth, I won't be working on getting it back into >> Debian. That's the responsibility of the people that have an actual need >> for the package. >> >> The people who have expressed interest in getting the osgearth package >> back into Debian have been CCed. Please work together to get it done. >> >> Kind Regards, >> >> Bas >> >> -- >> GPG Key ID: 4096R/6750F10AE88D4AF1 >> Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
