Bug#914577: fixed in dropwatch 1.5.1-1
On Wed, Nov 13, 2019 at 9:35 PM Dmitry Smirnov wrote: > > On Thursday, 14 November 2019 3:33:42 AM AEDT Alexandros Kosiaris wrote: > > Thanks, I 'll take up on your offer. If anything I 'll manage to learn > > more about the bureaucracy aspects of package maintainer ship and > > avoid such mistakes in the future. > > That's not a bureaucracy but important aspects of cooperation. Notion of > ownership matters only as long as you have something to deliver. Therefore > transparency (not bureaucracy) is crucial. Even when the work is unfinished, > announce that you are on the task and where your work-in-progress repository > is. That's precisely what ITP bugs are about - cooperation and coordination. I think I might have used the term bureaucracy a bit too liberally. What I meant is the administrative processes governing this (which I clearly am not familiar with yet). But otherwise, fully agreed. > > -- > All the best, > Dmitry Smirnov. > > --- > > Success consists of going from failure to failure without loss of enthusiasm. > -- Winston Churchill
Bug#914577: fixed in dropwatch 1.5.1-1
On Thursday, 14 November 2019 3:33:42 AM AEDT Alexandros Kosiaris wrote: > Thanks, I 'll take up on your offer. If anything I 'll manage to learn > more about the bureaucracy aspects of package maintainer ship and > avoid such mistakes in the future. That's not a bureaucracy but important aspects of cooperation. Notion of ownership matters only as long as you have something to deliver. Therefore transparency (not bureaucracy) is crucial. Even when the work is unfinished, announce that you are on the task and where your work-in-progress repository is. That's precisely what ITP bugs are about - cooperation and coordination. -- All the best, Dmitry Smirnov. --- Success consists of going from failure to failure without loss of enthusiasm. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#914577: fixed in dropwatch 1.5.1-1
Hello, On Wed, Nov 13, 2019 at 1:38 AM Dmitry Smirnov wrote: > > On Wednesday, 13 November 2019 9:09:30 AM AEDT Moritz Mühlenhoff wrote: > > Why did you take over that ITP without even syncing up with the person > > (CCed) who indicated to be working on it in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914577#10 ? > > Excuse me, I was taking over "RFP" and there was nothing to sync about as > there were no publicly visible progress whatsoever. > That's probably my fault for not knowing I should have also CCed cont...@bugs.debian.org in my email. > Alexandros, you are most welcome to co-maintain this package. > Next time please ensure to re-title the bug properly and keep it updated on > your progress. > Thanks, I 'll take up on your offer. If anything I 'll manage to learn more about the bureaucracy aspects of package maintainer ship and avoid such mistakes in the future.
Bug#914577: fixed in dropwatch 1.5.1-1
On Wed, Nov 13, 2019 at 10:38:39AM +1100, Dmitry Smirnov wrote: > On Wednesday, 13 November 2019 9:09:30 AM AEDT Moritz Mühlenhoff wrote: > > Why did you take over that ITP without even syncing up with the person > > (CCed) who indicated to be working on it in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914577#10 ? > > Excuse me, I was taking over "RFP" and there was nothing to sync about as > there were no publicly visible progress whatsoever. Ah yes, you're right, the "owner" was in fact posted to the BTS, but there were no BTS commands sent to cont...@bugs.debian.org, which would have renamed the RFP appropriately. Cheers, Moritz
Bug#914577: fixed in dropwatch 1.5.1-1
On Wednesday, 13 November 2019 9:09:30 AM AEDT Moritz Mühlenhoff wrote: > Why did you take over that ITP without even syncing up with the person > (CCed) who indicated to be working on it in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914577#10 ? Excuse me, I was taking over "RFP" and there was nothing to sync about as there were no publicly visible progress whatsoever. > https://salsa.debian.org/akosiaris-guest/dropwatch had a package > waiting for sponsorship/upload. How am I suppose to know about that? There were no updates to RFP, no sponsorship-requests, no uploads to mentors.debian.net (that I'm aware of), nothing. As far as I knew there was nothing to indicate work in progress or even proper ownership of an RFP. Sometimes people comment to RFPs without contributing any work... Alexandros, you are most welcome to co-maintain this package. Next time please ensure to re-title the bug properly and keep it updated on your progress. -- Cheers, Dmitry Smirnov. --- The surest way to corrupt a youth is to instruct him to hold in higher esteem those who think alike than those who think differently. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part.
Bug#914577: fixed in dropwatch 1.5.1-1
On Tue, Nov 12, 2019 at 11:02:13AM +, Dmitry Smirnov wrote: > Maintainer: Dmitry Smirnov > Changed-By: Dmitry Smirnov > Description: > dropwatch - tool for detecting and diagnosing dropped network packets > Closes: 914577 > Changes: > dropwatch (1.5.1-1) unstable; urgency=medium > . >* Initial release (Closes: #914577). Why did you take over that ITP without even syncing up with the person (CCed) who indicated to be working on it in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914577#10 ? https://salsa.debian.org/akosiaris-guest/dropwatch had a package waiting for sponsorship/upload. Cheers, Moritz
