Your request to join salsa's qt-kde team

[Scarlett Moore]

On Sunday, March 22, 2020 10:19:04 AM MST Pino Toscano wrote:
> In data domenica 22 marzo 2020 17:41:06 CET, Scarlett Moore ha scritto:
> > On Sunday, March 22, 2020 9:36:11 AM MST Pino Toscano wrote:
> > > In data domenica 22 marzo 2020 14:04:43 CET, Dylan Aïssi ha scritto:
> > > > Hi Lisandro,
> > > > 
> > > > Le sam. 21 mars 2020 à 16:35, Lisandro Damián Nicanor Pérez Meyer
> > > > 
> > > > <perezmeyer at gmail.com> a écrit :
> > > > > Hi Dylan! I have just saw your request to join the group. Which
> > > > > packages do you intend to help with?
> > > > > 
> > > > > Please ping me if I can be of any help, and feel free to join
> > > > > #debian-qt-kde>
> > > > 
> > > > As I maintain R packages, I am interested in rkward (IDE for R) which
> > > > is not up-to-date.
> > > 
> > > Note this group does not maintain rkward, but Thomas Friedrichsmeier
> > > does. Did you contact him?
> > > 
> > > Now that I see, there is a extras/rkward repository in our group: it
> > > appears that it was created two years ago by Scarlett, by importing the
> > > content of the unstable version at a time, without any history/tags.
> > > Considering that an upload done recently by Thomas recently simply
> > > ignored that repository, I consider that repository wrong, and most
> > > probably done without contacting the maintainer. Hence I just removed
> > > it, thanks for making us notice it.
> > > 
> > > That said: if you get approval from Thomas to work on it and agreement
> > > to maintain rkward as part of the qt-kde team, then that's perfectly
> > > OK for me. In this case, please do start from a repository containing
> > > the proper history of the rkward packaging.
> > 
> > For what it is worth, Thomas had given me permission and he was doing
> > packaging from local and only uploading binaries.
> 
> This is great, however there was no communication about this *at all*.
> Also, this is not the first time I see this situation, i.e.:
> - a repository created with no history, just "import current packaging"
>   (and once the "current packaging" was the Ubuntu one, different from
>   the Debian one at that time)
> - under the qt-kde umbrella of a package not under the team maintenance
> - no communication about maintenance switch
> 
> For example, I saw this happening twice for kdenlive a couple of years
> ago (and they were not the only examples).
> 
> > I am letting this go under the circumstances that I am clearly not
> > wanted around here.
> 
> I wrote your name above because it was the author of the 4 commits in
> that repository, no more and no less than that. It was *not* meant
> as personal attack or anything like that.
> 
> Can you please explain exactly in which ways you are "clearly not
> wanted around here"? Because now I'm starting to worry that whatever
> action me (or anyone else) will do on anything that you touched there
> will be such as snarky/demotivated answer like this.

My apologies for the emotional response. I read it as "I" did everything wrong 
in the handling of this repo. I recall asking how to handle the situation 
under the circumstances and was told this way. Thomas did apologize for doing 
the security update via the way he was doing them ( sponsored binary upload ), 
but it was holidays and I was unreachable at the time.

So moving forward, how does one handle a case like this in regards to non 
existent history to match archive?
Thank you,
Scarlett


-- 
Scarlett Moore
gpg: 7C35 920F 1CE2 899E 8EA9  AAD0 2E7C 0367 B9BF A089
Software Engineer @ Blue Systems
Debian Maintainer developer in training.
Netrunner PM
KDE Developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20200326/77eec960/attachment.sig>