-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debian/ in master and nest-3 branches #1321
Comments
@alexmyczko: does your suggestion imply your willingness to take over maintainership of the package in debian? We think that it would be good if you could join one of the next Open NEST Developer Video Conferences in order to have a proper discussion about this. |
@jougs more like, one can't take over maintainership of a package, if it's not even there yet? following links give me empty results however i've seen some other people provide binaries: i might be interested, since i have a building package: thanks for the tip on video conference, do you also use irc (internet relay chat) for development/users? |
I meant of course if you would be willing to be the maintainer, once a package exists. We will discuss this topic internally next Monday and the VC might be a good forum to get things going further. We don't currently have an IRC channel or such. Most discussions happen either here on GitHub, during our open VC, or on the public mailing list. |
what was the outcome of the discussion? |
Our current take on it is that since we provide the PPA for Ubuntu, there is not a lot of pressure to also get it into Debian. If someone is willing to do that and maintain it, we're not against that. |
I'm closing this now. Feel free to come back in case you want to become the maintainer of an official nest package in Debian. |
@jougs Didn't you want to close the issue? |
@steffengraber: Yes. Closing! |
let me suggest to drop all debian/ completely and make it the packagers work instead of shipping a heavily outdated/no more working version.
The text was updated successfully, but these errors were encountered: