From kde-core-devel Fri Jan 26 07:27:55 2018 From: Kevin Ottens Date: Fri, 26 Jan 2018 07:27:55 +0000 To: kde-core-devel Subject: Re: Importing kdiff3 - was - Re: Aw: Re: KDE inclusion Message-Id: <3835730.Y0EhfCH68V () wintermute> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=151695169502550 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart5794935.u37Cveo7TF" --nextPart5794935.u37Cveo7TF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Hello, On Thursday, 25 January 2018 22:35:37 CET Albert Astals Cid wrote: > El dijous, 25 de gener de 2018, a les 9:01:10 CET, Kevin Ottens va escriu= re: > > On Thursday, 25 January 2018 00:08:03 CET Albert Astals Cid wrote: > > > As I did with the last person that also was confused and annoyed by a= ll > > > this burocracy, just ask me any question you may have. > >=20 > > Oh come on... the bad mean bureaucracy argument now. Wanna look at the > > Eclipse incubation process? Or the Apache one? >=20 > Can I use the "if all your friends jump from a balcony will you do it" > defense? Not really since my point was more that what we have in place is very very = far=20 from bureaucracy not that we should replicate other's bureaucracy. If you w= ant=20 an example of bureaucracy look at those friends who jump from a balcony. ;-) =20 > > Seriously it's just about having a person already within the community > > making sure the new project needs get catered to and also making sure t= he > > new project is on the right path to put in place rules and procedures > > compatible with the rest of the community (and the Manifesto). >=20 > But how do you find that person? You're just an 'outsider', how do you fi= nd > a random person to be your incubator guy? Because as it happens, it's the > second time in a month or something that i have to volunteer. Ah! That is interesting feedback. You're correct that we're currently assum= ing=20 that someone will step in to do that and that there's enough of us and that= =20 we're responsible enough to do that when we see something we're interested = in. Personally for kdiff3, I'd have expected Kevin Funk to end up doing it, ind= eed=20 he was first responder with "I'd love to see kdiff3 being adopted by KDE=20 again". To me he sounded like a perfect sponsor. I'd like to see that fixed. Right now, I'm not sure how, but if you're the= =20 only one indeed caring about new projects getting in, we have a more genera= l=20 community problem, it's just that the incubator makes it visible... > I think it's much easier if we had guidelines and the rest was just "ask = in > kde-devel mailing list if you have further questions", It'd be easier, but not better. Because then it's no different than "ask th= e=20 GitHub support if you have further questions", and it's not what it's about. In my previous email I mentioned this is *also* for the "sponsor" to touch= =20 base with the joining project to verify it's getting into fruition to *be* = a=20 KDE project (which is not just about having a repository on our=20 infrastructure)... I know, pesky people and culture thing. > and sure if you find a dedicated person for you, great, but requiring it > feels weird, and also makes it for less scalability, as an example I alre= ady > have an email from Michael that was sent only to me but anyone else in th= is > list would have been able to answer, but he had to wait at least 14 hours > for me to have time to answer it. Maybe that needs to be made clearer in the wiki? I'd expect the sponsor to= =20 push the involved persons to ask these type of questions on public mailing= =20 lists indeed. One on one discussions are likely to happen but they must be = the=20 minority of the communication going on. The sponsor in that case is the fai= l=20 safe mechanism to make sure an answer indeed happens in those public forums= or=20 trying to solve the case if no answer happened for some reason. Regards. =2D-=20 K=E9vin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com --nextPart5794935.u37Cveo7TF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQQXFmpSdcX6bxpI/XgHS7vLjezJ4gUCWmrYewAKCRAHS7vLjezJ 4ky+AKCqFJ7ymWzZ0UiIbsMzsGmt6oVRjQCbBHNnCWtpOFXLeZY7w6EY7V/M+mU= =vr0K -----END PGP SIGNATURE----- --nextPart5794935.u37Cveo7TF--