Re: Q: NEW process licence requirements
Le dimanche, 1 avril 2018, 00.11:58 h CEST Adrian Bunk a écrit : > Sat, Mar 31, 2018 at 11:03:00PM +0200, Joerg Jaspert wrote: > > Like it or not, but there *is* a big difference in the project making > > something available for the big wide world (which a public NEW would > > be), or a user putting it somewhere readable for everyone even though > > the latter might be using project resources too. > > What is the big (legal) difference between distributing something > from the Debian group on the Debian machine salsa.debian.org, and > distributing the same from a different Debian machine? People are mirroring the Debian pool under a set of well-understood norms, as that's what the Debian project "produces" (think of the mirror network, people pressing CDs, etc). A .deb in a Debian suite in the Debian pool isn't comparable to a random .deb, as only the former has the Debian-seal-of- approval (DFSG & fulfills releasability criterias). Salsa is not meant to be mirrored by third-parties, and really shouldn't. Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Re: Q: NEW process licence requirements
On Sun, Apr 1, 2018 at 6:11 AM, Adrian Bunk wrote: > What is the big (legal) difference between distributing something > from the Debian group on the Debian machine salsa.debian.org, and > distributing the same from a different Debian machine? The big difference appears to be the Social Contract (and DFSG), which we generally don't seem to apply to alioth/salsa, especially because they often contain full upstream development history, which might or might not contain non-free material. -- bye, pabs https://wiki.debian.org/PaulWise
Vote status
The vote is running, you can send the emails. You will not get a ack about your vote until I can look at what's broken, which will hopefully be tomorrow evening. If you received an error message, I can reprocess your email. There is no reason to revote at the moment. If you did vote properly you should get an ack after I fixed things. Kurt
Debian Project Leader election 2018: First call for votes
Hi, This is the first call for votes on the DPL election of 2018. Voting period starts 2018-04-03 00:00:00 UTC Votes must be received by 2018-04-16 23:59:59 UTC This vote is being conducted as required by the Debian Constitution. You may see the constitution at https://www.debian.org/devel/constitution. For voting questions or problems contact secret...@debian.org. The details of the candidate's platform can be found at: https://www.debian.org/vote/2018/platforms/ Also, note that you can get a fresh ballot any time before the end of the vote by sending a mail to bal...@vote.debian.org with the subject "leader2018". To vote you need to be a Debian Developer. HOW TO VOTE First, read the full text of the platform. You might also want to read discussions with the candidates at https://lists.debian.org/debian-vote/ To cast a vote, it is necessary to send this ballot filled out to a dedicated e-mail address, in a signed message, as described below. The dedicated email address this ballot should be sent to is: leader2...@vote.debian.org The form you need to fill out is contained at the bottom of this message, marked with two lines containing the characters '-=-=-=-=-=-'. Do not erase anything between those lines, and do not change the choice names. There are 2 choices in the form, which you may rank with numbers between 1 and 2. In the brackets next to your preferred choice, place a 1. Place a 2 in the brackets next to your next choice. Continue until you reach your last choice. Do not enter a number smaller than 1 or larger than 2. You may skip numbers, leave some choices unranked, and rank options equally. Unranked choices are considered equally the least desired choices, and ranked below all ranked choices. To vote "no, no matter what", rank "None Of The Above" as more desirable than the unacceptable choices, or you may rank the "None Of The Above" choice and leave choices you consider unacceptable blank. (Note: if the "None Of The Above" choice is unranked, then it is equal to all other unranked choices, if any -- no special consideration is given to the "None Of The Above" choice by the voting software). Finally, mail the filled out ballot to: leader2...@vote.debian.org. Don't worry about spacing of the columns or any quote characters (">") that your reply inserts. NOTE: The vote must be GPG signed (or PGP signed) with your key that is in the Debian keyring. You may, if you wish, choose to send a signed, encrypted ballot: use the vote key appended below for encryption. The voting software (Devotee) accepts mail that either contains only an unmangled OpenPGP message (RFC 2440 compliant), or a PGP/MIME mail (RFC 3156 compliant). To avoid problems I suggest you use PGP/MIME. VOTING SECRECY This is a secret vote. After the voting period there will be a record of all the votes without the name of the voter. It will instead contain a cryptographic hash. You will receive a secret after you have voted that can be used to calculate that hash. This allows you to verify that your vote is in the list. - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=- 5270cc4f-e99f-419e-9cac-4792aa4c6547 [ ] Choice 1: Chris Lamb [ ] Choice 2: None Of The Above - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=- -- The responses to a valid vote shall be signed by the vote key created for this vote. The public key for the vote, signed by the Project secretary, is appended below. -BEGIN PGP PUBLIC KEY BLOCK- mQENBFrCnjIBCACpeswSNpmfTXPn5CYo9puNWcvzHS9nWRrKeiOh27A55ussBH/c W+n0Hgi/adFO5l6FVd3ZCheC5HA8HWHPsluIUTgbuDEhQdaalhYdJWVODVXgVlJt XInHYLeL8Fq2UTegzZ3HLztDCzT57vBkVs+CMv3ktV+91At9Sx9krGsF2ikaI4/4 AU1dTA+6umIJB9fwcaslpOYWdLJaJ44gKS6h+LzChlPBHAiiMKB97NE9coJzxpSQ xTslP1QRlfXDsZzjKJHEq/jJuQz2/WGfTRaTT/tWzZ3vh5zvEGJjp7M39JnX8pai qZJbRS9xHy86EzYjNyW2ncNK9cIdfi4BCKGjABEBAAG0KkRQTCB2b3RlIDIwMTgg PGxlYWRlcjIwMThAdm90ZS5kZWJpYW4ub3JnPokBVAQTAQgAPhYhBERWihyHi/aN /bWS9kzY4MZ5h+K4BQJawp4yAhsDBQkDwmcABQsJCAcCBhUICQoLAgQWAgMBAh4B AheAAAoJEEzY4MZ5h+K4P1cH/RRWnYHHtIy/6ff/kpZxIX7Lgy/Ao3NkakpmZ3UY jy1T3OsLyf0PJc90jMk+TBFaoOfMoqIOEGOHlz8DQWAdQPNTfN34ZoY+mANw2S9z VXlAdHPdiGYSnGzyi1EI/CQ0o56zTgUhmBy+6go+sJnwqRe2rXHEBC14W/o/X7rB jyfX4vvCzlXgl/XVTLu2FWkNyl2iE8wUT++uuCT/DvpFXJMnTTSJrX9rlyLFYQmk B768l+UW+8QucDbxc2IAdbg7jKMNngFFpPNAUgJfdz3lcmxT0AqnAGk78GjEDPnT a1KKA1btJVYDkXVknojEt2b3eSo1/vlWysNqlkCtYyZLoH6JAjMEEAEKAB0WIQTl 5SVg3ZHFVt29pdAgZMU2QcJeXQUCWsKeugAKCRAgZMU2QcJeXc42D/9gviD8Mi6i RsYMuzfO7wei9SoPE7z9hE33PTQazsN/Jv502KslteJ56xBgImhrNcqute+h4Fbj Ug0jqasMrCgpRpYV2omhdeOdrbpSxmsmWrUW2fXVQEAj4/QBIVwi+sE/AzsEeJJh tfGDeGBnMxPs3BHtCsexsLFivezkoOg29XklquDeTg33908YjzxP8P9vH19vzu8J 8x/WrR7E8Hlvn6YOK4jDEHkYHytUgBGDh0zOASveDIJB1VizEtYUCjfrN3USVIgS LsRtTFMLBc/3haMWmveUd6vIk79bTxw+quyz+I6qCD0u7GDDM/ZP2Tr1Bgw9znpH sUaAgf0tpIB+d65LXAgdS9oJ8bdr9NTjaGFwnZhnINoGsvV5mjvARqbKaZZwWqcZ
Ballot for the vote
Here is the ballot for the vote. Voting period starts 2018-04-03 00:00:00 UTC Votes must be received by 2018-04-16 23:59:59 UTC This vote is being conducted as required by the Debian Constitution. You may see the constitution at https://www.debian.org/devel/constitution. For voting questions or problems contact secret...@debian.org. The details of the candidate's platform can be found at: https://www.debian.org/vote/2018/platforms/ Also, note that you can get a fresh ballot any time before the end of the vote by sending a mail to bal...@vote.debian.org with the subject "leader2018". To vote you need to be a Debian Developer. HOW TO VOTE First, read the full text of the platform. You might also want to read discussions with the candidates at https://lists.debian.org/debian-vote/ To cast a vote, it is necessary to send this ballot filled out to a dedicated e-mail address, in a signed message, as described below. The dedicated email address this ballot should be sent to is: leader2...@vote.debian.org The form you need to fill out is contained at the bottom of this message, marked with two lines containing the characters '-=-=-=-=-=-'. Do not erase anything between those lines, and do not change the choice names. There are 2 choices in the form, which you may rank with numbers between 1 and 2. In the brackets next to your preferred choice, place a 1. Place a 2 in the brackets next to your next choice. Continue until you reach your last choice. Do not enter a number smaller than 1 or larger than 2. You may skip numbers, leave some choices unranked, and rank options equally. Unranked choices are considered equally the least desired choices, and ranked below all ranked choices. To vote "no, no matter what", rank "None Of The Above" as more desirable than the unacceptable choices, or you may rank the "None Of The Above" choice and leave choices you consider unacceptable blank. (Note: if the "None Of The Above" choice is unranked, then it is equal to all other unranked choices, if any -- no special consideration is given to the "None Of The Above" choice by the voting software). Finally, mail the filled out ballot to: leader2...@vote.debian.org. Don't worry about spacing of the columns or any quote characters (">") that your reply inserts. NOTE: The vote must be GPG signed (or PGP signed) with your key that is in the Debian keyring. You may, if you wish, choose to send a signed, encrypted ballot: use the vote key appended below for encryption. The voting software (Devotee) accepts mail that either contains only an unmangled OpenPGP message (RFC 2440 compliant), or a PGP/MIME mail (RFC 3156 compliant). To avoid problems I suggest you use PGP/MIME. VOTING SECRECY This is a secret vote. After the voting period there will be a record of all the votes without the name of the voter. It will instead contain a cryptographic hash. You will receive a secret after you have voted that can be used to calculate that hash. This allows you to verify that your vote is in the list. - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=- 5270cc4f-e99f-419e-9cac-4792aa4c6547 [ ] Choice 1: Chris Lamb [ ] Choice 2: None Of The Above - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=- -- The responses to a valid vote shall be signed by the vote key created for this vote. The public key for the vote, signed by the Project secretary, is appended below. -BEGIN PGP PUBLIC KEY BLOCK- mQENBFrCnjIBCACpeswSNpmfTXPn5CYo9puNWcvzHS9nWRrKeiOh27A55ussBH/c W+n0Hgi/adFO5l6FVd3ZCheC5HA8HWHPsluIUTgbuDEhQdaalhYdJWVODVXgVlJt XInHYLeL8Fq2UTegzZ3HLztDCzT57vBkVs+CMv3ktV+91At9Sx9krGsF2ikaI4/4 AU1dTA+6umIJB9fwcaslpOYWdLJaJ44gKS6h+LzChlPBHAiiMKB97NE9coJzxpSQ xTslP1QRlfXDsZzjKJHEq/jJuQz2/WGfTRaTT/tWzZ3vh5zvEGJjp7M39JnX8pai qZJbRS9xHy86EzYjNyW2ncNK9cIdfi4BCKGjABEBAAG0KkRQTCB2b3RlIDIwMTgg PGxlYWRlcjIwMThAdm90ZS5kZWJpYW4ub3JnPokBVAQTAQgAPhYhBERWihyHi/aN /bWS9kzY4MZ5h+K4BQJawp4yAhsDBQkDwmcABQsJCAcCBhUICQoLAgQWAgMBAh4B AheAAAoJEEzY4MZ5h+K4P1cH/RRWnYHHtIy/6ff/kpZxIX7Lgy/Ao3NkakpmZ3UY jy1T3OsLyf0PJc90jMk+TBFaoOfMoqIOEGOHlz8DQWAdQPNTfN34ZoY+mANw2S9z VXlAdHPdiGYSnGzyi1EI/CQ0o56zTgUhmBy+6go+sJnwqRe2rXHEBC14W/o/X7rB jyfX4vvCzlXgl/XVTLu2FWkNyl2iE8wUT++uuCT/DvpFXJMnTTSJrX9rlyLFYQmk B768l+UW+8QucDbxc2IAdbg7jKMNngFFpPNAUgJfdz3lcmxT0AqnAGk78GjEDPnT a1KKA1btJVYDkXVknojEt2b3eSo1/vlWysNqlkCtYyZLoH6JAjMEEAEKAB0WIQTl 5SVg3ZHFVt29pdAgZMU2QcJeXQUCWsKeugAKCRAgZMU2QcJeXc42D/9gviD8Mi6i RsYMuzfO7wei9SoPE7z9hE33PTQazsN/Jv502KslteJ56xBgImhrNcqute+h4Fbj Ug0jqasMrCgpRpYV2omhdeOdrbpSxmsmWrUW2fXVQEAj4/QBIVwi+sE/AzsEeJJh tfGDeGBnMxPs3BHtCsexsLFivezkoOg29XklquDeTg33908YjzxP8P9vH19vzu8J 8x/WrR7E8Hlvn6YOK4jDEHkYHytUgBGDh0zOASveDIJB1VizEtYUCjfrN3USVIgS LsRtTFMLBc/3haMWmveUd6vIk79bTxw+quyz+I6qCD0u7GDDM/ZP2Tr1Bgw9znpH sUaAgf0tpIB+d65LXAgdS9oJ8bdr9NTjaGFwnZhnINoGsvV5mjvARqbKaZZwWqcZ
Re: Question: What would you like to see {more,less} of?
Dear Bdale, > I've been startled sometimes at how other read what I wrote instead of > what I meant, and how often a very small tweak in wording was all it > took to clear up the distinction... Thank you for sharing your wisdom :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Question: What would you like to see {more,less} of?
Chris Lambwrites: > Every time I tried drafting such "loaded" opinions in the past I could > already hear the (perhaps justified…) pushback and thus decided not to > get closer involved. I think it depends a lot on how local vs general the topic is. For example, in my second (successful) run at DPL when I started pushing the "universal operating system" meme in my platform, one of the recent experiences I'd had at a conference in Mexico made it utterly clear to me that we absolutely needed to put more attention on translation of the installer... so I was eager to shine a spotlight on that in my platform and keep talking about it during my term. But I, too, struggled with the idea of how "involved" to become in smaller decisions, most of which clearly belonged in the hands of the most actively involved developers. A good step to take, which I've made heavy use of over the years, is to find a few trusted friends you can pass draft texts by for feedback. I've been startled sometimes at how other read what I wrote instead of what I meant, and how often a very small tweak in wording was all it took to clear up the distinction... Bdale signature.asc Description: PGP signature
Re: Q: NEW process licence requirements
On Mon, Apr 02, 2018 at 10:57:24AM +0100, Chris Lamb wrote: >... > The other, critical, factor nobody has raised is time. Why not > assume good faith here? After all, which is more likely - the FTP > team are sitting around doing nothing and happy/enjoying the current > state of affairs, or too busy with life/family/work and the quotidien > admin tasks & other breakages that they don't have as spare cycles as > we would like to work on this? >... This is not about assuming bad faith, more about bad priorities. There are plenty of cases where people get annoyed by the NEW handling, and when you say that the ftp team needs a thick skin that is also due to many people thinking "Why did the idiots in the ftp teams do this with my work?". >From outside copyright handling in NEW ranges from How did this package pass NEW with this copyright problem that is obvious when looking at debian/copyright? through What the legal reason that the ftp team insists on adding all author attribution to debian/copyright for GPLv2 software? to What is the legal reason that adding all author attribution is not required for src:linux to pass NEW? >From outside all this appears arbitrary and unfair, and you might be underestimating the amount of frustration it causes. Some cases might be an ftp team member making a mistake. Many cases might be people not understanding why something is required for legal reasons. Most of us have more Debian TODO items than available Debian time. Waiting for spare cycles might therefore not be a good way forward for something that causes widespread frustration. You were calling it "imposing an ultimatum", I would rather call it "agree with the ftp team on a deadline". cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Re: Q: NEW process licence requirements
On Mon, Apr 02, 2018 at 04:11:40PM +0300, Adrian Bunk wrote: > On Sun, Apr 01, 2018 at 10:36:23PM +0200, Joerg Jaspert wrote: > > If someone does go down the road, then any project creation on salsa > > would possibly end up needing to be vetted by an admin (or a new team > > doing this, or a combination of new team and NEW handling, as parts of > > this surely could be merged then). > > If someone does go down the road, the most likely result will be to > decommission salsa: > > With a bureaucratic process in place that might take weeks just for > getting a new git tree approved, most people would consider external > places like GitHub much more attractive and use these instead. And what about badly licensed or wholly copyrighted by EvilCorp patches in the BTS? Or even, whole tarballs attached to bug reports? Or the mailing list, for that matter. You also can have attachments, or put short but sensitive pieces inline, like: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > There is an argument for this having changed now, with the new setup, > > yes, but following that opens such a big can, I don't want to do this. > > Thats something the DPL might want to get some informed (ie. lawyers) > > opinion on, how free that service can be. > > > > I would love for the outcome of that to be something like "It's fine if > > open, as long as there is a contact that quickly disables reported > > $legalfoo violations". You can't have basically any user contributions if you'd require pre-approval. So, having just this one piece pre-approval rather than removal-upon-report is inconsistent. > > Also, in a way we do assume people NOT intentionally putting bad stuff > > up, though the current system does make it farely easy to play bad here. > > This a fair assumption for the DD-only NEW, but not for salsa. DDs are already trusted wrt adding extra stuff to existing packages, giving them access to this temporary holding ground is reasonable. Anyone else, even a DM, needs to seek a DD's review. Yet we allow anyone untrusted to put any crap on Salsa. Copyright is a bad enough drain on the world already, let's not suffer more due to a tight _inconsistent_ interpretation. Plus, there's already a mechanism for removing things from NEW. There's a fat button emblazoned with "REJECT" in all-caps. Meow! -- ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ
Re: Q: NEW process licence requirements
On Sun, Apr 01, 2018 at 10:36:23PM +0200, Joerg Jaspert wrote: > On 14994 March 1977, Adrian Bunk wrote: > > > Since Debian distributing whatever random people upload to salsa > > is fine for you, I fail to see the point why you would consider > > distributing what is in the DD-only NEW a huge problem. > > It is not fine. But I've chosen to not go down the road that would be > needed here. I've got enough on my plate, I can't put this on. The sensible time for anyone to bring up this topic would have been during or before the Alioth replacement sprint. I am not involved with salsa, but this kind of changes tend to be a lot less work when they are included in the planning phase, instead of changes to a heavily used running system. > If someone does go down the road, then any project creation on salsa > would possibly end up needing to be vetted by an admin (or a new team > doing this, or a combination of new team and NEW handling, as parts of > this surely could be merged then). If someone does go down the road, the most likely result will be to decommission salsa: With a bureaucratic process in place that might take weeks just for getting a new git tree approved, most people would consider external places like GitHub much more attractive and use these instead. At that point it might no longer make sense to spend scarce Debian resources on server maintainance and contents vetting. > Right now, the handling of stuff on salsa follows what was done for > alioth "It may have a .debian.org, but its not run by Debian, so the > project chose to ignore parts of the problems with it". And implicitly > either put it onto the shoulders of the alioth admins, or the individual. So in case of problems with contents on salsa, we expect that the salsa administrators will pay all legal expenses out of their own pockets without any support from Debian? > There is an argument for this having changed now, with the new setup, > yes, but following that opens such a big can, I don't want to do this. > Thats something the DPL might want to get some informed (ie. lawyers) > opinion on, how free that service can be. > > I would love for the outcome of that to be something like "It's fine if > open, as long as there is a contact that quickly disables reported > $legalfoo violations". If that's the outcome, it would be great. > Also, in a way we do assume people NOT intentionally putting bad stuff > up, though the current system does make it farely easy to play bad here. This a fair assumption for the DD-only NEW, but not for salsa. > bye, Joerg cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Re: Question: What would you like to see {more,less} of?
Hi Martin, > > Every time I tried drafting such "loaded" opinions in the past > > I could already hear the (perhaps justified…) pushback and thus > > decided not to get closer involved. > > Don't you think being a leader sometimes requires to withstand some > pushback Of course, but not if one would agree with that pushback. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Question: What would you like to see {more,less} of?
Hi Martin, > > Every time I tried drafting such "loaded" opinions in the past > > I could already hear the (perhaps justified…) pushback and thus > > decided not to get closer involved. > > Don't you think being a leader sometimes requires to withstand some > pushback Of course, but not if one would agree with that pushback. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Question: What would you like to see {more,less} of?
also sprach Chris Lamb[2018-04-02 21:41 +1200]: > Every time I tried drafting such "loaded" opinions in the past > I could already hear the (perhaps justified…) pushback and thus > decided not to get closer involved. Don't you think being a leader sometimes requires to withstand some pushback, or if justified, then this pushback ought to be included in the vision they share? -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems "i am not in favour of long engagements. they give people the opportunity of finding out each other's character before marriage, which i think is never advisable." -- oscar wilde digital_signature_gpg.asc Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Re: Q: NEW process licence requirements
Hi Adrian, > > do we really want to a culture in Debian where it is acceptable to > > publically belittle others' efforts using such emotionally loaded > > words or in such a combatitive / adversarial manner? > > you omitted the relevant part from my email I'm sorry you feel misquoted but I believe I explicitly praised you in my last mail for pointing out the potential disparity between perception & reality and even underlined my agreement with you. > > If you will permit me to exaggerate for a moment, if anybody is leaving > > the Project it is due to sustained exposure to such low-level > > toxicity. :( > > There are two orders of magnitude of people more in the project that > need a thick skin due to the toxity of the intransparent NEW handling > of the ftp team than there are members in the ftp team. Again, apologies for any miscommunication but I was referring to members of the Debian Project as a whole who perhaps do not find it satisfying to be part of generally negative interactions, rather than members of the FTP team specifically. > the only person in the project who is able to push for improvements > in this area is the DPL. Which, as I mentioned, I have been persuing in my role as DPL and as an FTP-assistant. Indeed, a glance at my mailbox suggests that things have been in motion even since your reply to me. The other, critical, factor nobody has raised is time. Why not assume good faith here? After all, which is more likely - the FTP team are sitting around doing nothing and happy/enjoying the current state of affairs, or too busy with life/family/work and the quotidien admin tasks & other breakages that they don't have as spare cycles as we would like to work on this? > The only alternative would be a GR to override the DPL decision > regarding the ftp team delegation, and no matter the outcome this > would be ugly. > > It is therefore disappointing when a DPL candidate tries to wiggle out > of making a commitment There is no wiggle; I think I already implied that a DPL passive- aggressively threatening the FTP team with a General Resolution masquerading as a schedule would not lead to the situation improving any quicker. :) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Question: What would you like to see {more,less} of?
Dear Enrico, > I wouldn't want the DPL to express their opinion with the expectation > that everyone should agree or follow their lead, but more with the idea > of giving a sense of direction Nod. There are a few situations where I would like to have liked to done this during my first term. However, would you have any concrete suggestions for phrasing or ideas for framing this that could not be interpreted as a top-down directive, yet not being "just another" voice in the mix? Every time I tried drafting such "loaded" opinions in the past I could already hear the (perhaps justified…) pushback and thus decided not to get closer involved. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-