djencks commented on issue #673: URL: https://github.com/apache/camel-kamelets/issues/673#issuecomment-1007203040
Thanks for fixing the source links. I don’t see an update for 0.5.x? I’m a bit surprised the link checker didn’t find the problems. I’m really glad to discover my fears about the kamelet dependencies linking to unreleased code are unfounded, although since the 0.6.x branch doesn’t appear to have been updated after release the kamelet dependencies on the branch currently do point to snapshots… but the poms also say the version is main-snapshot. I apologize for repeatedly discovering something about the processes here that worries me and, after not being able to discover what the actual process is, expressing my doubts that it’s in line with apache polices. I can see that that’s probably rather infuriating. I’ll see if I can find another way of asking for information; what I’ve been doing is bad for everyone. If there’s something else I’ve said that you are offended about, please let me know what it is. I’m trying to contribute, not cause problems. I think camel is a pretty amazing thing, which is why I’m spending so much time working on the docs and trying to get them to make the relationship between the different parts clearer. David Jencks > On Jan 6, 2022, at 9:46 PM, Andrea Cosentino ***@***.***> wrote: > > > You weren't asking for this fix, but for something else, using the extract action for setting the indexId from the json routing in the integration. This is not a solution, it's just a workaround. > > Thanks for reporting about the links, I'll take care of fixing them. Maybe there were some updates when we changed the way the documentation generation with some PRs from David. > > I will always speak up when the work from this community and from the oldest contributors will be underrated and I really wish that members of this PMC do the same, because in the last weeks I just seen attempts to criticize the work done and find faults in what it is done (if someone feel I'm talking about him, yes, I'm talking about you, David). > > 20 hours ago I couldn't answer about the fix, because your problem was and it's still different. > > The 100's hours of time you consumed, it's 500 hours of work done from contributors around Kamelets and camel-k. The fact that you don't know the code or you have troubles finding where the code is or how it is working, it's part of the game. Camel is a really complex ecosystem, documenting everything will always be impossible, given the number of real contributors working regularly and with passion on this. > > I'll take comments like yours as offence, because you and many others, consider, ALWAYS, our time for granted, which it's wrong and unpleasant to read. > > That say, thanks for your feedback and I'll trying to improve the upstream documentation, in my spare time, as always. > > — > Reply to this email directly, view it on GitHub <https://github.com/apache/camel-kamelets/issues/673#issuecomment-1007157005>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAELDXXJQ5NBY6C4NA4RGODUUZ42HANCNFSM5LLAMB2A>. > You are receiving this because you commented. > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
