From kde-devel Wed Aug 21 20:22:58 2019 From: Albert Astals Cid Date: Wed, 21 Aug 2019 20:22:58 +0000 To: kde-devel Subject: Re: SQL Query tool - incubator Message-Id: <4502057.sWrxFPPfgy () xps> X-MARC-Message: https://marc.info/?l=kde-devel&m=156641899704892 El dimecres, 14 d=E2=80=99agost de 2019, a les 14:24:09 CEST, Miroslav =C5= =A0pehar va escriure: > Hi Albert, >=20 > > El divendres, 9 d=E2=80=99agost de 2019, a les 14:45:23 CEST, Miroslav = =C5=A0pehar va escriure: > > > Hi all, > > > > > > i would like to check if there is some interest into including SQL to= ol > > > into KDE and helping with development. So far the project has (had) t= wo > > > developers, me and asw-dev (from github, do not know his actual name). > > > > > > This was started because, afaik, there is no application in Qt5 that = fits > > > into KDE that provides this functionality. > > > > > > Anyhow, the code and how it looks like is here: > > > https://github.com/mispp/goat > > > Some things are missing, some things are not working best, but overal= l it > > > does work. > > > > Your code doesn't build. > > > > CMake Error at CMakeLists.txt:19 (add_executable): > > Cannot find source file: > > > > src/ConnectionStandardItem.cpp >=20 > Probably not with cmake. I tried to convert .pro into cmake, but didnt > manage to do it since i never touched cmake before. > To be honest, i actually do not need cmake since qmake works just > fine, so i just left it for later in the state it is... The idea was > to move to cmake since kde uses it. Oh, then remove the file, or fix it, but don't leave it there for people li= ke me to try to use it, fail and then be sad. >=20 > > > Incubator requirements, per point: > > > > > > - Compliance with the KDE Manifesto -> this is currently hosted on > > > github, but it is not a problem to move it to kde infrastructure (= gitlab) > > > - Governance similar to the other KDE projects -> i cant really ju= dge > > > this since this has been a small effort. what does this exactly me= an? > > > > It means that once you joing KDE it's not yours anymore, it's ours, bec= ause you are now us. >=20 > Very clear explanation. I would suggest using this sentence in the wiki p= age. >=20 > > > - Clear product vision -> product vision is described in readme. n= ot > > > sure if this enough. > > > - Healthy team (healthy proportion of volunteers, inclusive toward= s new > > > contributors, ideally more than one developer) -> this is one of t= he > > > issues. reason for reaching out is lack of developer time. > > > > Having a small team is "ok but not great". >=20 > Not great, not terrible :) >=20 > > But what's not going to happen for you importing your code to KDE's git= lab is that suddenly you get 10 new contributors (unless you do some noise = about the app and sell it to developers) everyone here is already very busy. >=20 > Yes, i am aware of that. one can hope at least for at least some > casual commits and/or advice / internal design help.. > If not to the application itself, maybe in KPart if someone helps with > replacement of the custom component with KPart one. > But one of the reasons for joining into the community is to have support,= right? Yes, we will try to help you, but unless you have a good selling story, peo= ple are not going to show up and develop stuff. >=20 > > I see that the last "code" commit was 10 months ago, that makes me a bi= t scared to be honest. > > > > Cheers, > > Albert >=20 > Yes, this is actually an issue. I reached the point where it > more-or-less worked for me, some other design aspects i had an issue > with, so i kinda just thought to left it for a while. > I am thinking to put some effort into it once kubuntu 19.10 (plasma > 5.17?) comes out, so let's see if i get distracted with stuff like > golang/rust. >=20 > As i said, this is just a check to see what you guys think about this > idea, especially since there is no alternative for this development > tool in kde ecosystem (not considering jetlabs and java apps). > I can also keep it as it is and come back when it is more mature. This last paragraph leaves me with a "i don't know what to say" feeling, it= seems that it works for you, which is nice, but if you want to move from "= pet project" to "this is something i want people to use" you can't say "let= 's see if i get distracted" because what we don't want is to incubate proje= cts to have them just die the second after they join. So I guess the real question here is, how commit are you to make this a ser= ious project? One where you make releases and tell the world "hey there's t= his nice thing, come and use it" and then take all the [potentially negativ= e] feedback and try to make the app better, and then rinse and repeat. Cheers, Albert >=20 > Thanks for reading. >=20 > Best regards, > Miroslav. >=20