That explains it well - thanks KK. I think the key thing, especially since a lot of the people around here seem to be CloudBee employees (or employees of other companies who have a commercial interest in Jenkins), is to ensure that things are called out clearly to avoid any potential conflict of interest. Probably best to avoid using the word "we" unless the context is clear and instead spell it "CloudBees is looking to sponsor a designer" and "The Community is discussing" type thing.
I do think that perhaps people within the community should also call out where they are representing a company like CloudBees, some-other-company, etc. to make sure that people are aware of their affiliation. Email address is probably a very minimum as on some UIs (e.g. Google Inbox) email addresses don't show up that easily. Richard. On Thu, 8 Oct 2015 at 12:55 Kohsuke Kawaguchi <[email protected]> wrote: > I'm worried that what Gus is saying here comes across wrong. It's > certainly not something he and I had discussed. > > So let me try my version. > > The website renewal project is a fairly significant community project, in > an area where we failed to have enough volunteers. So while the whole > project will be done in the community (with all emails, discussions, > meetings, etc) as it should be, I felt that we needed someone who can do > some heavy lifting over a relatively short period of time, such as design, > content schema, etc. > > So I asked my boss to see if we can fund somebody like that instead of > waiting for a volunteer to show up, and he said yes. I hadn't thought about > how to do it --- maybe we'd have CloudBees donate money to the project and > have the project contract somebody. Or maybe it's easier if we have > CloudBees directly deal with somebody to handle such annoyance like > contracts, payment, etc. > > But the intent is for that person to work directly for the community. It'd > be a failure if the whole effort comes across like CloudBees is doing the > project and turning over the result to the community. There's no hidden > string attached between CloudBees and that designer in question. > > Similarly, I was going to ask somebody from CloudBees to program manage > this project. > > I thought we can keep this all kosher by making sure that every > conversation happens in the community. > > If anyone has any suggestions to make sure more kosher, that'd be greatly > appreciated. > > 2015-10-07 13:05 GMT-07:00 Richard Bywater <[email protected]>: > >> Hi - quick question: >> Re "*We are hiring! *I am looking for a contract based web designer with >> a nice portfolio to show to help author new site templates and do some >> information architecture for Jenkins-ci.org. If you know someone, you can >> reach me on Twitter @gusreiber, or email me >> gusreiber(at-symb)cloudbees(dot-com) >> or find me on IRC, freenode/#jenkins/gusreiber. You would be part of a >> fairly tight 3 person team that would include myself, R Tyler Croy (whom >> you might know from such places as this list) and yourself. Daniel Beck, >> and KK and the will of the community will also be dropping their input >> along the way." >> >> Out of interest, who is "we" is this paragraph? Is it the Jenkins >> Community or CloudBees? >> >> Richard. >> >> On Wed, 7 Oct 2015 at 12:02 Gus Reiber <[email protected]> wrote: >> >>> Hey all, >>> So a related thread exists here >>> <https://groups.google.com/forum/#!topic/jenkinsci-dev/EMbE3a4u8nA>, >>> but I have a couple of bits I didn't want lost in a thread. They are: >>> >>> - *We are hiring! *I am looking for a contract based web designer >>> with a nice portfolio to show to help author new site templates and do >>> some >>> information architecture for Jenkins-ci.org. If you know someone, you can >>> reach me on Twitter @gusreiber, or email me >>> gusreiber(at-symb)cloudbees(dot-com) or find me on IRC, >>> freenode/#jenkins/gusreiber. You would be part of a fairly tight 3 person >>> team that would include myself, R Tyler Croy (whom you might know from >>> such >>> places as this list) and yourself. Daniel Beck, and KK and the will of >>> the >>> community will also be dropping their input along the way. >>> >>> - *We are discussing!* Even if you don't feel you have the time or >>> qualifications to join the team in exchange for money, we still want to >>> hear from you. >>> >>> With those two little action items out of the way, here is the gist of >>> the discussion so far.... >>> >>> Jenkins.org has a website (http://jenkins-ci.org/), but it isn't very >>> good, (made evident in part by the fact that I am posting this message to >>> you through this site instead of that one). It contains some documentation, >>> a few blog articles, the Jenkins bits (most importantly), and the plugins >>> directory (next most importantly). It is my belief that this site needs to >>> have more of a social, 2-way communication aspect to it such that it can >>> truly be the mecca to which Jenkins developers turn when they want their >>> soules to be filled with the light of CI/CD knowledge. >>> >>> To that ends, I have posted a proposal for what that might look here: >>> >>> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0+Website+vision+from+Gus+Reiber >>> >>> https://wiki.jenkins-ci.org/download/attachments/82673948/knowledge-site.pdf?version=1&modificationDate=1443574130000 >>> >>> ...also, the plugin browsing experience really should be a lot better. >>> To that ends, here is a related video: >>> http://youtu.be/pMwsZRo5He8 >>> >>> If you've got $.02.... >>> ...drop-em. >>> >>> >>> -- >>> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/ee6cd9be-cf19-4630-b5c9-f61fc6263ecf%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/ee6cd9be-cf19-4630-b5c9-f61fc6263ecf%40googlegroups.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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAMui946doJd3h2Wf%2BMWy6e4qSOLHQqpDVOf9LKO1LB3EQ7qkAw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMui946doJd3h2Wf%2BMWy6e4qSOLHQqpDVOf9LKO1LB3EQ7qkAw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . > > >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4zemrWS7zeSm0v3frX2OWjoqnX27Ry-Uo%3D-194ev99HGw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4zemrWS7zeSm0v3frX2OWjoqnX27Ry-Uo%3D-194ev99HGw%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMui947%2BWz%2Bj_R6M3AMZRcLCpniMM1xwRZbJ_uMo5BaxeXoatQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
