 Okay. Welcome everybody. If you're standing up, there's a bunch of empty seats so you can come sit down. This is the first talk of the DebConf proper after Debian Day. And I actually think our first speaker doesn't need very much the way of introduction. Stefano Azzacchiaroli, the Debian project leader, is going to give us bits from the DPL. Better. I hope the battery stays up with me. Okay. So thank you everybody for coming up this early in the morning. I'm glad that we did... working still. Okay. I'm glad that we did manage to enter the auditorium. So in this talk, I just want to make a kind of a health check of Debian after 17 years almost of its life. And it seems to be kind of a tradition to start the bits from the DPS talk looking back, looking at how all this started. So I went back and read for the end time the message that Ian sent to a news group, something like 17 years ago, and it was something like a fellow Linuxer. This is just an announcement to announce the imminent completion, not the completion of a brand new Linux release, which I'm calling the Debian Linux release. That was August 16, 1993. And in that message, you can find something of the original goals of Debian, and which are kind of inspiring to look at. So back then Ian was aiming at making GNU Linux competitive with the commercial operating system. Back then it was kind of completely unknown to the great public, and so the first goal was to have that operating system be competitive. So it was inspired by distribution quite popular back then called SLS, but the goal was to make it better, make it a distribution in which quality was really important. You wanted to make Debian easy to install for any user. You want to build it in a collaborative manner in which all packages were managed by experts of the specific software which was being packaged and using an open model in which everything was done in the public. And also, more importantly, you wanted Debian to be free as in freedom. So back then, there were not many distributions. Debian was one of the sole ones. Together with that, we started not far away. And today, the situation has pretty much changed. So nowadays, Debian has something like 30,000 binary packages. If you look today in the IMD64 seed main, we have spawned something like 120 derivative distributions, which are distributions which are based on our packages. And we have released 11th time and we are close to release for the 12th time. We are about 1,000 packaging contributors, of which 900 are developers and about 100 are Debian entertainers, plus thousands of other contributors of relevant work like translations, websites, and this kind of stuff. We are probably among the biggest distributions. We are the one with the largest number of ports available, and we are going to release two non-Linux ports for the first time with Squeeze. So I would say, well done. It's pretty impressive with respect to the original goal and with respect to our condition back then. However, I feel that when we talk with us and when we think about Debian, we have some kind of bad feelings in some moment. So I feel that sometimes we have the feeling and sometimes I also have the feeling that there are now a lot of other distributions. We are not alone anymore. And we feel that some other distributions are releasing more frequently than us and we feel a bit better about that. We know that other distributions have more users than Debian has and we feel a bit better about that too. We feel that some other distributions are innovating more, that some other distributions are getting more credit, more press, more relevance, all in all, than Debian. So I ask myself and I ask you, do you think Debian is better than other distributions? Why are you contributing to Debian in the first place? And even more so, do you think Debian is still relevant 17 years after its original creation? Do you think that the free software ecosystem will miss something if Debian will disappear one day from another? So my answer to that, to both of them, is yes, absolutely. But I would like, before presenting my, I mean, the reasoning for my answer, I would like to know from you. So have you ever asked yourself this question? What is your answer to that? Why do you think Debian is still relevant nowadays? I think that we have a microphone, some comments on that? Jonas? Most certainly, yes. That's the easy part. It was written there. Should I reason it or should I... So why do you think it is the case? Because the resolving above is flawed. We have the most users, because we have distribution users. Okay, fair enough. And similar with some of the others. We don't release less frequently. Release four times a day. So you're saying that Debian is relevant because it's the basis for several other distributions out there. That's your argument. Anything else, Phil? I'm kind of scared of what Phil is going to say, but... Hi there. Yes, okay. I've always thought that Debian is relevant because it does what I want. It does what? It does what I want. And there are about a thousand people who think that it does what they want enough to work on it. And even if the rest of the world goes somewhere else, there'll still be a thousand people that you'd have to kill to stop working on Debian. Anything else for us? I think it's extremely relevant because it still follows that model, wherein experts maintain packages of the software that they know. And when we were looking for a distribution to use at Stanford, we were looking for something not that we were going to consume, but something where when we came up with things at Stanford that we needed, we would be able to get them back into the distribution and then they would have the benefit of being part of the distribution and not some add-on that we have to maintain independently. Absolutely. Sam? For me, Debian is a great distribution because it's something that I can choose to contribute to. I know that there's a community aspect to it. If I am part of the Debian community and I'm working on Debian, I know that my needs and concerns are going to be one of the factors. It's not something where my contributions will be accepted as long as they're consistent with someone's commercial agenda. But whenever the person who owns the whole thing, their needs diverge from mine, I'm out on the street. Here I know that maybe someday the community will disagree with me. That's okay. It's at least a community process to understand that that disagreement has a cost. Absolutely. Take a couple more, Matt, and then... I apologize in advance for a long answer. I think in order to answer... Okay, we postponed that to the question time. I think in order to answer this question, you have to think about what Debian is and what it's for as well. I think it's not a trivial question. And I think there are at least a few different angles to look at this question from. Debian is an operating system that works very well for a lot of people. It's also a platform for developers to use to make things, whether that's a derivative distribution or an embedded system or lots of different things. And it's also a project. It's an activity that people do. And I think in each of those dimensions Debian is actually doing very well. As a platform, the extent to which other products are based on it is proof of that. And in terms of a project, I think it's important to contribute to and continues to attract contributors. So I think yes. Okay, thanks. One more? I think all these answers are great. But for me, the underrepresented really critical element in Debian is unlike any other distribution, it's the commercial or Linux. It's the only one that has maintainability through release after release after release. I call it eternally regenerative software administration. It is so awesome. And I think we should remember that and acknowledge it more often because the others that everyone mentioned seem to be the one that people think of first. But for me, it's always the regenerativity. Thank you. Okay. Just one more there and then we post on the left, the remaining for the question time. Just a brief one. First of all, we set standards. Standards in terms of documentation which documented standards which don't stink, they get updated. It's not that we drag for 17 years original documents which steal in that shape, right? And that's important. Okay, thank you. So I'm glad to have this small question time because you have done the talk for me. But not entirely. I have some answers which have not appeared yet and I would just like to go through them briefly. So one of the first reasons why I think Debian is better is because it has a focus on quality which is not there in all our distribution out there. So we have, as someone already said, package maintainers which are experts of the software they package. This interestingly enough was one of the initial goals set by Ian Marduk. So in Debian, unlike some other distribution, if you are a maintainer for a package, you most likely know this software. You do not know only the packaging aspect but you know the software. And that puts you in a better position to fix the software and more importantly to contribute back your work upstream to contribute to the free software world in general. A second reason why I think we have an important focus on quality is that we don't have any second class packages. So in principle, all packages in Debian Archive are subject to the same quality constraint and to the same quality requirements. That's not always true in practice because we know we have orphan packages but the goal we set for all packages, it is the same. Third point, our motto we release when it's ready which is something which makes us release slower than other but still it means that for us the quality of the packages is not something that we are ready to trade with some specific data or with some specific external requirement. This is something quite peculiar in the context of distribution nowadays. And I think that our user are very well aware of that so this is just a couple of recent feedback I got after becoming DPL talking with big companies, talking with part of the government which want to switch to the free software. I got feedback like we chose Debian because we need to rebuild packages because we need to change them and that's actually the essence of free software and Debian is the only one where we find packages that do not fail to build from sources constantly and this for them was really important and the second piece of feedback that I get is something like we choose that distribution Debian based which is a commercial distribution because we need some commercial guarantees but we choose that and not another commercial distribution because we trust Debian packages and we know they are based on Debian packages so we chose that instead of that other. More generally there are lots of technical reasons for which people prefer Debian so I made a quick experiment on Identica I kind of put out a meme saying why do you think Debian is better than others and I got tons of technical reasons number of ports, stability it's running anywhere people like the testing suite, the policy it's huge, we have a lot of packages and there are a lot of technical reasons we might agree upon. I don't think these are actually the most important parts of Debian, I think there are some more profound philosophical reasons for which Debian is relevant in the free software world of today is how much we care about freedom so Debian is based on some firm principles which bind together users and developers by the means of social contact so we write down very clearly what are our goals what are our commitments and we bound ourselves to respect them in front of the users in essence that means that we have been promoting the culture of free software since 1993 and that we have users which are aware of that users trust our choices in terms of free software and believe that our choices are for the greater good of free software second point about freedom is that I like to think of Debian as a distribution which is free the bottom up what does it mean? that means that we are free in the software we distribute and that starting from squeeze will be including firmware finally no GR for deciding that firmware is an exception at the last minute thanks to the amazing work of the kernel team but also it means that we are free in our infrastructure we do not have any nobody in Debian would accept to propose non-free services that developers have to use to do their packaging work and nobody will accept among our users to have to use some non-free web services in a way that integrates with the distribution so we really did a good job in pushing the culture of free software and our users are very well aware of that second point what is still on the philosophical level is that we are independent so in the so called blogosphere there have been a lot of discussion recently distinguishing corporate from non-corporate distribution and Debian is an independent distribution what does it mean? that means that there is no single company which is behind us which gives us infrastructure which gives us money which gives us hardware we live up on the donation of a lot of companies but a lot of individuals that gives us money and hardware and besides that we only have a gift economy and that puts us in a relatively independent position from money and from choices which comes from corporations and people trust that our choices are not kind of driven by commercial needs by money needs third and last point on the philosophical level is that Debian is better in decision making now I understand that we do not all agree that we are kind of completely okay at taking decisions but at least on paper we are quite good at that so if you look at our constitution so if you look at our constitution there are two very clear principles the first one is what I call doocracy even if it is not called that way in the constitution and essentially it says that anyone which is working on a specific task and it is in charge to work on a specific task it's free to take any decision regarding his own work so if you are a package maintainer you are fully entitled to take all decision on that package and either if they are technical or if they are non-technical so second point democracy so we have doocracy as the default so decision are taken by who do the job and when that does not work or when we do want to override the doocracy we have completed democratic process in which collectively we can take any kind of decision taken together the two points mean that reputation in debian follows work and that we don't have any benevolent detector we don't have any oligarchy some people claims we do not have any cabal too and essentially that means that we have no decision which are imposed from the outside the decision are all our fault if you do something good and all our merit if you do something good ok so this for me is what defines the specific role of debian in the distribution ecosystem of today and that for me also mean that we have a kind of responsibility so we have the responsibility to ensure that debian shall live long and prosper because if we one day to the other we disappear the free software world I think will suffer from our absence so what should we do to ensure that debian will live long and prosper well we should fix some problem that we do have in our project there are values I thought that how to list the problem we have there are value possibility to do that the way I chose to do that in this talk is to start from the lack of manpower so the lack of manpower is something that if you ask anything in debian what is their problem one of the thing they will say ok we don't have enough manpower we need more manpower and we are starting to I think believe that that's why other people do things better than us because they have more manpower than we do so I ask myself is it really the case and my answer is twofold well it is surely the case so we could definitely use more manpower basically everywhere in debian nevertheless we should also put into better use the manpower that we do have and which in some way we tend to waste so I go briefly about how I think we should put into better use the manpower we have and our first way to do that is to change our culture with respect to releases so right now we have a kind of culture in which releasing is the job of the release team and of a few people which do NMUs and that is something we really need to change because we cannot go on and release that way for much longer we need to realize that releasing is a shared responsibility so as a package maintainer your first task is to ensure that your package is in good shape and that it has no RC bugs and that in generally follow all the guidelines for packaging we have in debian but when you are done with that it is also your responsibility to ensure that other packages in the archive have no RC bugs because it's not tenable that only the release team should care about fixing the RC bugs in 30,000 packages in the archive that simply does not work and the way to go forward and relax and change this belief is simply to use NMUs more do NMUs welcome NMUs so my personal experience is what the initiative I called RCBW a release critical bug of the week I just tried to do one NMU per day but the point was not really the duration and the point was not even fixing as many RC bugs as possible the point was experimenting with how much people welcome or don't welcome NMUs and I was impressed by the result so I did something like 180 NMUs and I got no complaint nobody complained about a single NMU although I got a couple of override of uploads and I get a lot of thank you messages so that is impressive for me because I've always thought that we are kind of too attached to our packages we kind of don't like our package of yours and I was really impressed to see that actually people welcome that that people see that you are trying to help their work when they are overworked and we don't have time to fix the specification and even more importantly we had a buff on this topic yesterday and everyone who participated in this buff agreed with this interpretation so anyone which was at the buff and which has done NMUs reported the same experience people do welcome NMUs and NMUs as a way to collaborate and that's I think the first step to release in a more shared way second way to use better the manpower that we do have is taking responsibility so lack of manpower is something that I've been hearing whining about in volunteering everywhere so when I've been doing volunteering even in non-computer related stuff everyone cries for the lack of manpower but we have an advantage in other volunteering realities we have computers, we are geeks, we are hackers and with computers a single motivated individual can do wonder so if you take one person which is motivated and capable in one night of hacking can solve a longer standing problem which is in Damian so I know that it's easier to rent on lists about core teams which are not doing their job properly but it's even if it's more difficult it's more and more productive to actually propose yourself to join that team I don't have the feeling that we are anymore at the point where core teams are close identities which do not accept members what I do see is rather a lot of core teams or non-core teams looking for volunteers and not finding volunteers so think about it try to say okay I'm ready to do this experiment I want to be part of that team and just show that you are capable of doing the job you really can and if you look at the core teams in Damian you will find out that we have some relatively young DD we joined some important teams and started doing some wonderful job there and that's something you can do too we all can do that third and last point about using in a better way the manpower we do have is trying to reduce the inertia of the project so folklore says that large changes are impossible in Damian that we have too much inertia on how we take decisions this is true when you look from the outside but it's something that is easy changeable it is enough to realize that in a project as big as Damian you simply will never have unanimity in a project with 1,000 developers and in which the Damian Development mailing list is open for posting to anyone out there in the world who want to say his opinion on Damian you will never have unanimity so looking for consensus is good when you are doing a big change which can affect a lot of packages we will never have unanimity because we will never have that on any single subject one of the most funny question I've been asking the first interviews after becoming DPL it was something like how do you think about being the DPL in a project which have 1,000 developers and 10,000 opinions this is true so that simply means that we will never have unanimity so look for consensus but at some point it is the one who is ready to do the job and decide so if I can like paraphrasing Linus I would like to say talk is cheap show me the NMUs we find our way decision which is kind of prominent and someone has just to start doing the job and so this is it for what concern using better than Empower we do have and if I had to summarize it I would use this quote from Sam that comes from Sam which said be bold and this is true we have computers if you do mistake most of them we can undo them so it just take you to go ahead and do the work okay so this what I had to say about using better what we have so how do we reach out to find more manpower so a first way to to have more manpower is to be able to retain the offer of help that we get so that it's very very much needed to have a welcoming community so look at what this distro watch to say about Debian you will find something like discussions on developer mailing list and blogs can be uncultured at times and it is full glory that to join Debian you need to grow a thick skin so you need to be able to withstand steps from people which are not related to your technical work you need to be able to withstand a community in which people are grumpy in which people hardly acknowledge the good you did and just look at the bad you did people sometimes fail to give credit people rarely thank other people we see insults on mailing list sometimes so this is simply not acceptable not because we want to have a happy family but because this way we are losing manpower every time you do one of these things you are probably killing a potential contributor maybe not the one to which you are applying but someone else which is lurking which is looking at the exchange on the mailing list and thinks you know what I don't think I want to be part of this so I simply don't buy the argument that the requirement of having a thick skin is a guarantee of hacking abilities it is not it is just a requirement of having something which has a thick skin and which will probably perpetrate the need of having a thick skin to stay in Debian so for me the requirement of having a thick skin is just a way to lose potential contributors so another way to get more manpower is getting more users so recently I've been reading on mailing list arguments like we don't need more users we don't need more bug reports we just want full grown experts from day one okay the last one is for me but that's not the way it works in free software free software for me is participation and participation starts with some initial involvement and involvement is something that goes bit by bit starting from the first bug report so if we want to have more manpower we should be also be more welcome into noobs that doesn't mean that we should accept bogus bug report but we need it to be kind of tolerant from people which are starting and which potentially can become some very valuable Debian hacker like one year later as a bonus point on this we want to be the universal operating system well the universal operating system is everywhere of every kind okay last point on how to get more manpower for me is working more with derivatives so we saw that we have kind of more than 100 derivatives out there some of them has more than 10 times the user base of Debian and in an ideal free software world that means that every contributor of a derivative distribution is also a Debian contributor but in that ideal free software world we also have that every Debian patch is pushed upstream so I think we agree that not every Debian, sorry I think that we agree that it is not yet the case that every contributor derivative is also a contributor of Debian because sometimes the work doesn't get forwarded to us but it's also the case that it is not true that everything we do in Debian gets forwarded upstream so I think we should work better in both ways and as a first way to do that I've tried to reaching out about derivatives and explaining to them what we do and I was impressed by the result people in derivatives distribution care about Debian, care about our free software principle and are simply kind of scared of us so it's just enough to show really I mean I get to reply like are you sure you want us to work for you so it is really easy just a way to go there and get other people to know you and as a first step I'm very happy to have the initiative of the derivatives fund desk we just started recently for the moment it has a wiki page and a couple of contact points and that is the contact point you can give to any developer of a Debian based distribution for if he wants to contribute his work back to Debian so this is the place where we can reach out to us and say okay I have this kind of work I would like it to be in Debian because I care in free software and how it works how can I do to put into Debian who should I contact so if you want to join this list this is a place where we can really attract more manpower from our derivative distribution and improving the way patches flows between us and them okay so this was equal on let's say some of the outstanding problem that I see in Debian I just have a couple of final slides to throw out some discussion subject that we would like to discuss with you later on so the first potential direction I think we should think about is quality so Debian started with the focus on quality it still has a focus on quality but we can't be happy for the status quo quality doesn't wait for us so other people are starting to focus more and more on quality Lucas does not only rebuild packages for Debian it rebuilds packages also for other distributions so we cannot hope to have enough quality just because we care about FTBFS quality is something we should try to get more and more every day and the potential direction in that is having more testing but with testing here I do not mean only the PU part stuff so not only on the package itself but also in the software so having more unique test suites for the software repackage and suites which are not only runnable at the end of the build process but we should be able to find a way to test packages as they are used by users so sometime ago we had some proposal to do that in DPKG but that's really a direction we should take and that ultimately will mean more RC bugs and more RC bug fixing so second potential direction so Joy will probably kill me for this slide so I think it's the time to start having a serious discussion about a proposal called CUT and the reason is that it is a fact that we have a lot of users which do love our release cycle but it is also a fact that some users don't and as a consequence of this too we have a lot of users which are using the testing distribution which initially was not meant to be used by users but in fact it's something which is really peculiar it's something that it is not there in any other distribution out there it is a mix of recent software and tested packages which is really really peculiar so the question is do we need or want to bless that suite I'm not saying we do I'm saying that we need to discuss that because it's a potential improvement of Debian which will be quite peculiar and quite interesting for a lot of users out there so if you're interested in that here is a proposal of Joy there will be a buff here but the timing is completely wrong so Daniel will say when it is the actual buff which is Friday at 5pm in inter-school thanks so the buff will be actually we change it because people which are not at the conference would like to participate and there will be so video streaming which is not possible to have in this room final slide on another direction I think we should take known package known developer project members so this is a quote from my platform is there just because a lot of people seems to have liked it and it says the best operating system is mainly but not only made of software it is also made of translations, graphics, music etc etc etc so what those are all software okay okay documentation is software okay it is made by a more varied kind of software than what we take today so we are already benefiting from a lot of work of these people we have a lot of people working on some ancillary part around the Debian operating system also people doing marketing which is hardly software I found one so we are already benefiting from work of these people and I think we should reward them more so something which is kind of very hard to do because it is hard to mix it properly with the bureaucracy which is at the basis of Debian but we need to think about how to have project members which are known packages so that's it for me and I would like to add your thoughts on all this matter thanks are you going to argue that marketing is software? no no not that allow me just for a second to stick my neck out and put together a straw man for you one of your arguments up there was that in order to get more manpower we need to have more users because developers don't start out as full developers they start out as users and progress and gain skills now you also point out that there are derivatives of Debian today that have 10 times as many users as Debian and I've observed the trend that a number of people who start out as users of those derivatives go on to become developers in those derivatives and then move on as well to be contributors in Debian as well when you couple this with the fact that Debian today does not have the infrastructure to accommodate orders of magnitude more bug reports from users sent to our BTS does it make sense to offload that particular task to the derivatives or is it something that Debian should focus on directly okay that's a pretty interesting question so let me point out that what you said in the beginning it's already happening so for instance we already have an important flow of developers in Debian which came from Ubuntu they started to know Ubuntu they became user of Ubuntu, developer of Ubuntu I believe at some point they become more interested in the relation between Ubuntu and Debian and they end up being developers in Debian this is a service which derivatives and for sure Ubuntu is the most important one among them in that respect it's already offering this service to Debian so I don't think we should have as a goal to offload users to derivative distribution I mean if it happens okay but I don't think we should abide to our we should reject our responsibility of having direct users for this reason so you talked about teams needing manpower and every team wishing for more, teams wishing for more members but not having volunteers I haven't looked at the whole DevCon schedule yet but is there somewhere where teams can come up in front of us and say I want help it's really not that hard to join us please join me and wherever you can hear about all the work, all the teams that need people so I smell like this is kind of subliminal advertisement of open hatch right so yes I completely agree and I think we are so another argument to get more manpower is surely communicate better so communicate better not only in what we are because I don't think we are doing yet a particular good job in pushing out our values and but we are I think we are improving significantly but also communicate more about what we need and in fact I think it's a kind of a meta problem so because we also need in Debian people which is able to do this kind of communication and I don't think we have much of those people in Debian yet so there is a kind of a chicken and egg problem sorry he volunteers to do it talk with him afterwards okay I do there is a question here from Matt hi I'm Matt stand up hi I'm Matt Zimmerman I had a comment on releasing when it's ready I think it's a great ideal for Debian to have and it's not right for every project not right for every user but having that option and having a project that's standing up for that I think it's a great thing for free software I think though when we talk about releasing when Debian is ready we can do a better job of defining what that means when is Debian ready we say it's ready when there aren't any RC bugs for example so when no packages are flawed in a fundamental way and I think that's a little bit it's looking at a little bit in the wrong direction rather it should be considered ready when Debian is suitable to be used for its intended purpose it should be defined in terms of what you can do with it Debian is ready when you can do all of these things with it it's more of a user centric definition rather than saying it's ready based on a mathematical formula of how many bugs there are so I think by turning that around we could change the dynamic of releasing when it's ready it wouldn't seem quite as cumbersome as it is if it meant something more specific yeah so I have the impression that yeah I mean you alright it seems something cumbersome at the moment something difficult to achieve it can be defined in other ways but I have the impression that the one you suggested a bit more blurry so you will then need someone deciding whether you have met the criteria you put forward and that is on paper so go ahead yeah I'm someone that has used Debian for quite a while and I do develop open source software I've never participated and I think one thing that would greatly increase participation is a hello world if Debian had the equivalent of a hello world for participation in terms of okay let's say that you want to create your own binary package or your own source package and just have a path do this do this do this all the way to here is the joke package that actually makes it up and you can actually see your joke package like with Wikipedia you know there's very little barrier to entry you can just do your thing and oh my god you're live like you can see it right there and it's very exciting if there were a way to go all the way from start to finish with a pretty well paved path where it's not like well go to the you know get a mentor oh geez what's a men now I'm going to join that now I'm going to do this and here's the file system hierarchy sprawling document here's the you know it gets exhausting so if there were a nice cleaner way to do that hello world is good just a comment on that I think we used to have a hello package I have no idea if it exists any longer but okay and beside that so what is really good is a packaging guide which comes from Ubuntu actually and which you have been discussing on the Debian derivatives mailing list to promote as more general like Debian derivative packaging guide and that's kind of good and I've heard that there are also work in progress at this conference to actually improve the our current packaging document I think what we need is kind of the experience of someone outside because we are all people that know how to do the packaging so we are not any longer really good at looking if a document for beginning packaging for scratch is good or not so this is something that for instance someone like you can contribute to so letting us know whether what we have right now is good or not and how to improve it so I've got the five minutes time anything else? Steve? Hi yeah Steve McIntyre just a quick question I guess not so much for you Zach but for the rest of the audience can we have a quick show of hands who's at the first Debian conference this year wow and how many people do we have here who are just going through new maintainer or just become new Debian developers or Debian maintainers cool okay thanks for coming along and volunteering really echoing what Zach was saying earlier I said something about this last year as well please don't be scared of getting involved in these scary core teams there's lots of people out there who would love to talk to you would love to share beer with you and have you help them with their work don't be intimidated there's lots and lots of cool stuff that you can do to make a difference yeah thanks for this comment Steve there's one question here I believe it will be the last one Hi I'm CJ in addition to more manpower we need a lot more women power so just in case that was not a sexist remark English word for available power so thank you I enjoy that