Bug#823052: ITP: python-mkdocs-bootswatch -- Bootswatch themes for MkDocs

[Piotr Ożarowski]

[Brian May, 2016-05-01]
> > please don't use python- prefix, use mkdocs-bootswatch. Note that binary
> > package is "mkdocs"
> 
> Ok, so I just call both source *and* binary packages mkdocs-bootswatch
> and mkdocs-bootstrap then?

yes please

> mkdocs was required for a DPMT package - django-rest-framework - and
> this is the only reason I bother to package it. It is already in DPMT.

we do not add libfoo package to DPMT (written in C/Perl/whatever) if its
Python wrapper "foo" module requires it. We do not maintain gcc even
though it's required by a lot of our packages. I'm sorry, but IMO one of
the main reason of having teams in Debian is to group people interested
in similar topics. I don't want to touch Perl or JavaScript and I'm
grateful to people who maintain libraries for these languages for me.
Someone long time ago decided to create a team to maintain Python
modules, this team already has so many packages that almost nobody
reads -team mailing list so I don't want to make it even worse (and
scare these few people who still read it) and add Python applications or
$UGLYLANG libraries there. If someone wants to package python-bar that
requires bar-perl, IMO the best way (especially when you don't have that
great Perl knowledge) is to join Perl team to help you maintain bar-perl
and encourage Perl Team guys to maintain python-baz within our team if
their baz-perl needs python-baz

> I tried to get access to PAPT (so I could fix another package), however
> so far haven't got a response.

I guess I missed your request email on this mailing list, sorry. Let me
know if you're still interested

> I would sooner maintain them in collab-maint rather then PAPT, because I
> don't really want to have to convert my git repositories to
> subversion. I believe subversion is still required by PAPT.

it is
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Bug#823052: ITP: python-mkdocs-bootswatch -- Bootswatch themes for MkDocs

[Brian May]

> please don't use python- prefix, use mkdocs-bootswatch. Note that binary
> package is "mkdocs"

Ok, so I just call both source *and* binary packages mkdocs-bootswatch
and mkdocs-bootstrap then?

>> I plan to maintain this as part of the DPMT - Debian Python Modules
>> Team.
>
> I think PAPT is more appropriate for mkdocs. I don't think it is also
> appropriate for themes, but since mkdocs-bootswatch/mkdocs-bootstrap are
> tightly related to another DPMT^W PAPT package, IMHO we can make an
> exception in PAPT for them (but I'd prefer to have them outside the
> team, TBH - DPMT/PAPT are not collab-maint replacements).

mkdocs was required for a DPMT package - django-rest-framework - and
this is the only reason I bother to package it. It is already in DPMT.

Recent mkdocs has split up, and now requires these packages too.

I tried to get access to PAPT (so I could fix another package), however
so far haven't got a response.

I would sooner maintain them in collab-maint rather then PAPT, because I
don't really want to have to convert my git repositories to
subversion. I believe subversion is still required by PAPT.
-- 
Brian May 

Bug#823052: ITP: python-mkdocs-bootswatch -- Bootswatch themes for MkDocs

[Piotr Ożarowski]

[Brian May, 2016-04-30]
> This is a requirement for python-mkdocs.
> 
> Not sure if this prefix of python- is appropriate or not because this
> package doesn't contain any python, however it is part mkdocs, and the
> source of mkdocs which has been named python-mkdocs in Debian.

please don't use python- prefix, use mkdocs-bootswatch. Note that binary
package is "mkdocs"

> I plan to maintain this as part of the DPMT - Debian Python Modules
> Team.

I think PAPT is more appropriate for mkdocs. I don't think it is also
appropriate for themes, but since mkdocs-bootswatch/mkdocs-bootstrap are
tightly related to another DPMT^W PAPT package, IMHO we can make an
exception in PAPT for them (but I'd prefer to have them outside the
team, TBH - DPMT/PAPT are not collab-maint replacements).
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Bug#823052: ITP: python-mkdocs-bootswatch -- Bootswatch themes for MkDocs

[Guillem Jover]

Hi!

On Sat, 2016-04-30 at 21:57:47 +1000, Brian May wrote:
> Would appreciate it if somebody could confirm that the license is BSD
> and if so what version of the BSD license this is.
> 
> https://github.com/mkdocs/mkdocs-bootswatch/blob/master/LICENSE

That looks like a BSD-2 clause license but w/o the clauses itemized.
Of course BSD-style licenses have slight text variations in their
warranty and liability paragraph, but this one seems one of the
common ones that I've seen.

Thanks,
Guillem

Bug#823052: ITP: python-mkdocs-bootswatch -- Bootswatch themes for MkDocs

[Brian May]

Would appreciate it if somebody could confirm that the license is BSD
and if so what version of the BSD license this is.

https://github.com/mkdocs/mkdocs-bootswatch/blob/master/LICENSE

setup.py declares the license as BSD, however in my current sleep
deprived state it looks different to the BSD licenses that I can see
here:

https://en.wikipedia.org/wiki/BSD_licenses
-- 
Brian May 

Bug#823052: ITP: python-mkdocs-bootswatch -- Bootswatch themes for MkDocs

[Brian May]

Package: wnpp
Severity: wishlist
Owner: Brian May 

* Package name: python-mkdocs-bootswatch
  Version : 0.4.0
  Upstream Author : Dougal Matthews 
* URL : https://pypi.python.org/pypi/mkdocs-bootswatch/
* License : BSD
  Programming Lang: HTML/CSS
  Description : Bootswatch themes for MkDocs

No idea what to put here for long description.

This is a requirement for python-mkdocs.

Not sure if this prefix of python- is appropriate or not because this
package doesn't contain any python, however it is part mkdocs, and the
source of mkdocs which has been named python-mkdocs in Debian.

I plan to maintain this as part of the DPMT - Debian Python Modules
Team.

Also see discussion on mailing
list: https://lists.debian.org/debian-python/2016/04/msg00042.html