Would the blog be available to anyone, or just CloudBees employees? On Wed, Oct 7, 2015 at 7:56 AM Daniel Beck <[email protected]> wrote:
> > On 07.10.2015, at 14:51, Christopher Simons < > [email protected]> wrote: > > >> We don't get site traffic until the site is good. > > > > Respectfully, I think this is mistaken. The way to get "traffic" is to > create a good product that people want. If people want to download > Jenkins, they aren't going to think to themselves, "Well, Jenkins is the > best open source CI server, but I'm not going to download it because their > website is ugly." The site is a means to an end, and that end is > downloading Jenkins or finding documentation. > > > > The Jenkins site should get traffic because people want to use Jenkins. > Not because they think they might find good articles or "content" there. > We all deal with enough "information overload" already. I think putting > some documentation up about best practices is a good idea, but the idea of > the Jenkin's website pushing articles in my face, trying to sell me on > stuff, asking me to subscribe, etc. makes me want to vomit and likely would > lead to me avoid visiting the website entirely, possibly even to looking > around for a different CI tool. > > We're not going to sell things. Well, except for Jenkins-related events > like the Jenkins User Conferences, but I think those have a place on the > Jenkins site. We're not going to require subscription to just consume > content. There's not going to be a pay-wall, or even a subscribe-wall. If > technically possible, any contributions will only require a GitHub account, > or a Jenkins community account, which you already have if you've edited the > wiki or filed a bug. > > However, there's still a lot left to write about in more or less regular > posts. Recent blog posts I've written include highlighting cool, lesser > known plugins, tools related to Jenkins, and news about the Jenkins project > itself. I think it would also be interesting to also link to what others > write about Jenkins. Not to garner pointless comments, but to inform people > about what's going on with Jenkins and give them new ideas what they can do > with it. > > -- > 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/0F738FB9-CC91-407D-9757-01B7855FC2B9%40beckweb.net > . > 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/CAPiUgVd1%2BwB2yd7JjA%3Dxo%3DbU6A0B5u9rMXsMHJkmiGWJ2iVvmg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
