<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">Mads Kiilerich <<a href="mailto:mads@kiilerich.com">mads@kiilerich.com</a>> schrieb am Do., 15. Juni 2017 um 03:32 Uhr:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 06/12/2017 05:41 PM, Dominik Ruf wrote:<br>
> Hello everyone,<br>
><br>
> this mail is overdue, but I always hoped it would get better. :-/<br>
> I know this is a community project and we all have other<br>
> responsibilities. So I understand that a request does not get answered<br>
> instantly.<br>
<br>
I understand and see your frustration.<br>
<br>
Not that it really answer your questions, but for what it's worth, some<br>
comments to your examples:<br>
<br>
> But for example my pull requests about 'repository settings' is now<br>
> literally waiting for YEARS.<br>
<br>
Yes. Also, the latest changesets in the PR still say WIP, suggesting<br>
that it not really is considered ready yet. The previous iteration got<br>
review feedback 2 weeks ago. I haven't had time to follow up on the<br>
latest one, having spent time on ...<br></blockquote><div>Yes I got some feedback from a USER about the UI related (WIP) parts.</div><div>And I'm thankful for that.</div><div>It is WIP because I still got no feedback from any 'developer'.</div><div>For the non-WIP parts I still got no review/feedback. And after 2 years</div><div>'I haven't had time...' is not longer a proper argument :-(</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> Or lately my 'Port Kallithea theme to Bootstrap' pull request. I asked<br>
> multiple times for some feedback, but since 2 MONTH I got nothing. I<br>
> understand that reviewing takes time, but at least some kind of<br>
> comment is not too much to ask.<br>
<br>
Bootstrap has been very hard to land. Mainly because my initial requests<br>
for splitting things up with clean history so they were reviewable were<br>
refused or ignored.</blockquote><div>And I said I will not do it because I consider it a colossal waist of time.</div><div>You on the other hand never explained that you'll split it up anyway.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have thus spent a lot of time trying to<br>
extract/redo and land parts that I could review and so I knew what was<br>
changed and why.</blockquote><div>And why the hell did you not rebase it properly after that? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The latest iteration of the Bootstrap PR is much better<br>
and we are making progress - thanks!<br>
<br>
> And some pull request like 'catch MemoryErrors when calling git diff'<br>
> are really trivial.<br>
<br>
Unfortunately, I also have the feeling that the approach in that PR is<br>
wrong. </blockquote><div>Then why the hell did you not say so? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If we push the system so much that we get MemoryErrors, the<br>
system might start swapping and other things might fail too. Instead, we<br>
should make sure we don't use crazy amounts of memory but fail<br>
gracefully.</blockquote><div>I don't think that is possible with the way we use git at the moment.</div><div>But that discussion belongs in the PR. So add a comment to the PR already. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> But I haven't had time to investigate and propose a better<br>
solution.<br></blockquote><div>'<a title="frequency: 0" href="http://www.dict.cc/englisch-deutsch/A+bird+in+the+hand+is+worth+two+in+the+bush.html" style="font-size:13px;color:black;text-decoration-line:none;font-family:arial,helvetica,sans-serif;background-color:rgb(238,238,238)">A bird in the hand is worth two in the bush.</a>'</div><div>So even though there is a bigger problem we need to solve in the FUTURE,</div><div>why the hell can we not solve a small part of the problem NOW?</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> This can not continue in this way. This project is now almost 3 years<br>
> old and we have very little to show for ourselves. In fact there were<br>
> questions if this project is actually alive (can't find the link right<br>
> now). And I can't blame anybody to think so. Kallithea has improved<br>
> very little. Version 0.3 is 20 month ago.<br>
><br>
> So my questions to you guys is this:<br>
> What are your future plans for this project?<br>
<br>
My plan is to keep improving it, as contributions, time and priorities<br>
allow it.<br>
<br>
> Are there any chances that this project will start moving more quickly?<br>
<br>
Yes, if more people help by adding more resources and by helping us<br>
utilize resources better.<br>
<br>
Contributors can help reviewing, testing and improving contributions<br>
from others to the point where they are willing to put it in production<br>
right away and support it long term.<br>
<br>
Code contributors can also help by following the contributor guidelines<br>
and structure the code changes in such a way that they are easy to<br>
review and maintain.<br>
<br>
/Mads<br>
<br>
</blockquote></div></div>