Hi Paolo, I think collab-maint is the right place for it. Also, what did you use as an upstream source? Was it pip URL or the repo on github? I think we should move to the github repo because buildbot-www package is already a build artifact produced by build procedures from github repo. That's where nodejs and friends come in. Granted, buildbot as a standalone pip package does not need nodejs to be built.
Info on collab-maint and collaborative maintenance of the package: https://wiki.debian.org/Alioth/Git -- Best regards, Andrii Senkovych 2016-11-10 14:25 GMT+02:00 Paolo Greppi <paolo.gre...@libpf.com>: > Control: retitle 790241 please package 0.9.1 > > I have given it a try, and found that it requires RAMLfications (see the > RFP: https://bugs.debian.org/843882) > > For buildbot, I have set up a local git repo using the git-buildpackage > branch / tag standard (the VCS link pointed to by tracker.d.o is not > compatible with gbp). Assuming someone is willing to help, where would I > push the git repo ? (I would not like to host it on github) > > P >
