@Slide, they can block my jenkinsci account, github account and google groups. Not sure how i will be able continue development on some plugins that i wrote and maintain in such case.
@KK you publicly exposed this complain and my name. You want judge me with some unknown to me persons. That’s why I’m answering why this happened also publicly. *> **has repeatedly overstepped the threshold of what is generally accepted as being “good conduct” in an open-source community.* I know debian, gentoo and bit linux kernel community. This communities also has “if you screw up, take responsibility for your actions” and rules. I can say that some persons also overstepped them in jenkins (that caused such my reaction). *Pre-history* I like FOSS and always trying to use it instead of closed-source SW. I started using Jenkins 4 ago and found that it has too many bugs, so decided to start improving it. I started from bug wrangling in JIRA, reading docs, started learning sources and finally started opening PRs with different fixes 3 years ago. I never had to many issues/bugs with any other SW and still sure that Jenkins has low quality. (I tired protecting Jenkins quality and it’s other issues on conferences when people asking why it impossible to do this or this in jenkins). *Timeline* * So what happened before April, i finally tired with ancient uncomfortable JIRA/Confluence and tried to help with INFRA. I have deep experience with linux, distros, administrating linux servers, automation (9 years for everything). Hardly get response from KK (or rtyler, don’t remember exactly) what to do and started puppetizing jira. https://github.com/jenkins-infra/jenkins-infra/pull/66 So, my summary about infra: - it was locked on two persons, that had no time for this - they think that it better to migrate to hosted solutions instead of supporting jenkins INFRA because they have no time for support and doesn’t want provide access to somebody else or change something. - i hurt KK feelings with phrase that “jenkins infra sucks" - after this KK reacted and it was possible to provide access to infra for new persons like Daniel B., Oleg N., @aheritier. Now this helps restarting services, but still no real work on infra enhancements (excluding finally updated JIRA). - no INFRA work, just fill INFRA issues in JIRA to show how they are all not resolved. * The second case is https://github.com/jenkinsci/parameterized-trigger-plugin/pull/83 i think i provided enough arguments in comments. Summary: experienced(?) dev didn’t followed existed rules and KK likes it. For me it just one more situation that leads to lower jenkins quality. * Will try to not take personalities, but, please, think about it in general. KK points to this comment https://github.com/jenkinsci/build-pipeline-plugin/pull/81#issuecomment-139033384 and this https://github.com/jenkinsci/jenkins/pull/1815#issuecomment-137709017 CB joined people for jenkins development (that’s of course excellent). But it happens that nobody guiding them into existed jenkins rules. And they are trying to take maintainership https://groups.google.com/d/msg/jenkinsci-dev/NL2wLBjIV5A/gDv9UkCNCgAJ https://github.com/jenkinsci/build-pipeline-plugin/pull/81#issuecomment-139033384 / https://groups.google.com/forum/#!searchin/jenkinsci-dev/recena/jenkinsci-dev/6Eqz7Z9QbNE/tMOt44t-AQAJ without following existed rules (seems can provide more links). Btw Stephen C. describes very well how communication should work, but unfortunately it wasn’t followed. * One more situation. I’m working on docker-plugin enhancements (plus docker-java library), there is existed open for everybody plan https://github.com/jenkinsci/docker-plugin/issues/235. Nobody asked or joined development. In the same time CloudBees releases numerous number of docker-plugins and makes different presentations on JUC. (Obviously, every company should do PR with docker). * KK references to https://github.com/jenkinsci/jenkins/pull/1827 if it not obvious, then i can say that i never tried to personally insult somebody. I operate with work and it’s quality and just want to see Jenkins better. This is what i get from CB developer (comments in PR was deleted by somebody): <https://lh3.googleusercontent.com/-6knUo9cWp3A/VgcLaq5la1I/AAAAAAAAJgk/w77pUVn7ZQc/s1600/Screenshot%2B2015-09-25%2B14.51.01.png> I always open to facts and arguments, feel free to blame my code or help make something better. *What i can say today.* I think i got good experience with seen how FOSS project transformed to single vendor FOSS project. I want share statement that i got from KK at meeting (this can be useful for any new comer) and what i see now: - "Project organised as bazaar”. So your free to do what ever you want (excluding when somebody decided to enforce his invented rules like: 1) filtering plugins from Update Center, 2) enforcing everybody to not use GH issues or wiki, etc.). Plus such <https://github.com/jenkinsci/email-ext-plugin/commit/985892a861802c5ad0accd3d8e93abfcc4e1f48d#commitcomment-8432933> - About 2). KK uses for UI improvement Trello and gogledocs. For me it proves fact that INFRA is not suitable for comfortable development. It abusively require from everybody things that you can’t follow yourself. ( This <https://issues.jenkins-ci.org/browse/INFRA-342> and this <https://issues.jenkins-ci.org/browse/INFRA-346>) - CloudBees developers always suggesting people to merge new plugins into existed to have better usability for end-users (and i also suggesting the same), while they do tones of docker plugins. Where is logic? - Right now CloudBees hijacks features planned/existed in docker-plugin by creating new and new docker-* plugins. (I’m not taking personalities, plugin is written under CloudBees license headers and CB packages). Is this how CB works with FOSS? Answer from “KK”: ~“project is organised in such way, no problems”. - IMHO all hired jenkins devs not working on their plugins anymore like before. Example: role-strategy-plugin that was well maintained by Oleg is not really maintained now. (Oleg, didn’t i hurt you with such message?) - According to comments CB employees using model that allows them to do merges in plugins where they are maintainers without reviews and during working day only with reviews. Nice hole to merge anything you want and nobody can follow what work and where happens, because nobody uses company emails. As experiment i grepped logs for @cloudbees.com and found that CB contribution into jenkins measured only by Jesse Glick commits ;) - KK wants join more developers. My eyes blows when i open remoting, core code or some plugins: most plugins is stupid copy-paste, @jglick personally invented annotation styling (in the same time i very respect his experience), mess of letters without any spaces or brackets produced by KK and all this continue be copy-pasted to other places. How can I add workflow support in plugin when it impossible to follow changes or read this monster code? Commit history in core was more clear and clean 1 year ago. I tried join new developers into plugins and they run away with not polite words. - Company that says everybody how to do CI/CD and integrate code analysers, not using them in newly created plugins. In old plugins coding style can’t be touched because (?) it should stay for centuries with mixed tabs and spaces, and in new …? What impression do you expect from new-comers? - If plugin has some number of open PRs, and has no maintainer, and one company wants merge something they do it. Such approach kills previously opened from FOSS people PRs and real maintaining is not happening. If you work under plugin according to some plan and @reviewbybees PR appears, you will be forced to switch and merge it either they will annoy every day with questions when will it be merged (like “Zombie vs Plants”). - And of course there is a big cultural difference. If you want to see the insult, you will see it everywhere instead of resolving technical moments. On Friday, September 25, 2015 at 3:27:20 AM UTC+3, slide wrote: > > Just out of curiosity, what are the possible outcomes of such an > investigation? > > On Thu, Sep 24, 2015, 17:02 Kohsuke Kawaguchi <k...@kohsuke.org> wrote: > >> >> We have received complaints from multiple people that the conduct of >> Kanstantsin Shautsou (also known in the community as “KostyaSha”) has >> repeatedly overstepped the threshold of what is generally accepted as being >> “good conduct” in an open-source community. >> >> I have personally witnessed some of them as they have happened for more >> than half a year, and a number of people, including myself, had private >> conversations with him about the matter. As additional complaints have come >> in despite all those efforts, the board feels we have no options but to >> formally launch an investigation to look into this. We are approaching >> several prominent contributors in the community to join us to form a >> committee in order to look into this from all angles. Once we receive >> confirmations from them, we will share their names. >> >> While we have not formally adopted any code of conduct, our governance >> document >> <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Lowerbarrierofentry> >> >> does lay out the vision of the community we thrive to be. This project >> derives a lot of power from constant influx of contributors, and >> maintaining a healthy and respectful environment is of utmost importance. >> >> The board will refrain from going into the details of the matter in a >> public forum to avoid a public circus, and the committee will not publicly >> discuss the matter for the same reason. If you have inputs to the matter, >> please send them to jenkinsci-bo...@googlegroups.com, and we will pass >> them all on to the committee. >> >> I’m hoping that the committee will come to a resolution in a week or so. >> We’ll publish the resolution when it concludes. >> >> I do not take a step like this lightly, and I do this with a heavy heart. >> However, given the duration in which this has been going on, the number of >> people impacted, and the failed attempts to resolve this issue less >> formally, I feel it is a duty of the board to act on the situation. >> >> The situation also shows that the project needs to formally bless a code >> of conduct. I’m going to work with Daniel Beck to propose one for us, and >> we will take it to the developers mailing list and project meeting for the >> discussion. >> >> -- >> Kohsuke Kawaguchi >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z_X-Jcpvxz_%3DVV085XKJNZhodREf1tZPHT-3Ge_wEEUA%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z_X-Jcpvxz_%3DVV085XKJNZhodREf1tZPHT-3Ge_wEEUA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/aed320c9-6e6e-4062-b334-729b27652083%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
