← Back to team overview

rednotebook-users team mailing list archive

Re: Fwd: rednotebook removed from Debian Stable?

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sat, 2018-01-20 at 05:43 +0000, Phil Wyett wrote:
> On Fri, 2018-01-19 at 18:42 -0600, Lukasz Szybalski wrote:
> > Hello
> > What does need a sponsor mean? Do I need to reach out to somebody in
> > Debian.Org and tell them to accept the package because it's ready and build
> > and passed all necessary prerequisites? 
> > Or 
> > It you need a sponsor (person that actually builds ) /create a .Deb and src
> > repos. And of yes what I need to do?
> > 
> > Sponsor vs maintainer?
> > 
> > Thank you
> > Lucas
> > 
> 
> Hi Lucas,
> 
> All new packages into debian require a sponsor. A sponsor is a debian
> developer
> with upload rights that takes on and validates the new package to be of the
> quality to enter debian. The sponsor should work with the submitter to work
> out
> any issues and once the developer is happy, they would then upload to the
> debian
> archive for build and inclusion within the OS proper and close all related ITP
> (Intent To Package) and RFS (Request For Sponsorship) bugs reports[1].
> 
> Sponsor vs Maintainer ...
> 
> As I said a sponsor is an existing debian developer with upload rights.
> 
> The maintainer (day to day) of a package is usually the submitter of the
> package. In this case the day to day maintainer of the package once accepted
> back into debian would be me. Every time Jendrik pushes out a release, I would
> pick it up, build and test it, debianize it and then upload it.
> 
> When the package was submitted to debian, developers for the project wanted
> some
> changes as a seperate 'debian' folder that was not part of upstream and the
> changelog should be a continuation of the one that was in debian previously
> back
> in the rednotebook 1.x days. All fixes went to Jendrik and upstream and all
> external 'debian' folder data is hosted by me at:
> 
> https://gitlab.com/kathenas_external/debian/rednotebook
> 
> I am going to reach out to certain debian developers over this weekend and try
> and push for someone to look at it. If I get no joy by early next week, I will
> email you guys and maybe go for a more public 'What does it take to get into
> debian, the sponsorship process is flawed?' type of campaign. :-)
> 
> [1] All package submissions are organised via the debian bug tracking system.
> 
> Regards
> 
> Phil
> 
> P.S. Can we please do bottom posting for better conversation flow. Thanks.
> 

Hi all,

In follow up to my message above.

The package now has a sponsor I am working with.

Actions:

* Perform a few fixes.
* Update debian related files to match new project policies.
* Move my rednotebook debianized tree onto debians new salsa gitlab instance.
* Have sponsor process package into debian and close associated bug reports.

Estimated time for the above is around two weeks. I am busy at present, so do
not all start screaming at me if we are a few days out. :-)

Regards

Phil

- -- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

GitLab: https://gitlab.com/kathenas

Twitter: kathenasorg

Instagram: kathenasorg

GPG: A0C3 4C6A AC2B B8F4 F1E5 EDF4 333F 60DC B0B9 BB77
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCgAGBQJaagX/AAoJEDM/YNywubt3bu8P/ivnuJVKsMHY4k3qGBZDWTIm
WG8GVum1I4Z9HgZubfAZLJLgrzL7bFFxll1jxI5hvCs9cHiOERbVuy/ZkrWd8uHo
VpVt1835Ws5TzDlvWzTYbFFCCIaM5mHcDy7X19o3kQp5ZYrcf4dZWvCcRmNPYxvt
8lvBlWGJQmjWnq2ryRRMo6SSb/ZGqjYYOlQlQfxvgENMrtqpYX40GKoqlgXpnliw
EbG/3urSXT42wUTV5yKFJMnx8b79WCFWMc3h15KYC/v3VGcWKjGfHbDZMktJXSLH
cAfsNE+ApfHbjnM/STOdiT0lgoatKsL0peMU//h5ezClAu+Wv9JQQLTB2OWNozMY
XWY850S0Jih7zbPxPPKZ1V2TATMBuVEO/1ih4WH4lfnzB1v+qccZ6cdyt1KftB34
gJTU3l4ckBL4GKcJ6pF+n2lQhhiR/zGif5/oKG3Mp+G04ROvLBxnjZHKseZHoys1
GDKCdppL93XGhD2mCRz7MuR0852rai8ruuBQfjX1plTfgvb68Hpa7EMD6opRH8AL
JntqZP9dFYsD4fPKLoETzc/URA5Xk3nfjjzaIzKhA5gIiljGn1JkZRwRhvkS/pUp
zpfe9QWe55aMNbRwf3NrpmJzmgfTYAcxUvIbbOYCXHPBmGolFeNcwlFXHj9q09Nx
5gIs6ZFLuU/DK9zvV1mW
=2XWs
-----END PGP SIGNATURE-----



Follow ups

References