exactly. I think that would be greatly valuable to a lot of people. ....so long as the browse and search interface of the site can handle the volume of content, and the volume of content is great enough that people think to look for it.
On Wed, Oct 7, 2015 at 8:35 AM, Slide <[email protected]> wrote: > That sounds great then. I like the idea of community members being able to > blog about something they are doing or some plugin they found interesting. > > On Wed, Oct 7, 2015 at 8:33 AM Gus Reiber <[email protected]> wrote: > >> To my mind, anyone with something to say should be encouraged to blog on >> the site. >> It should be easy for them. >> And that is the sort of traffic, I think we should seek to encourage. >> >> I like Christopher's comments quite a bit, so I think I should clarify my >> own position a bit. I don't think Jenkins-ci.org needs to be adding new >> types of content, like tech briefs or newsish content, but the content that >> is there now is both difficult to find and not particularly fresh. >> >> Correct me if I am wrong, but navigating the documentation on the site is >> pretty rough. First, it is hard to tell you are looking at product doc vs. >> a blog vs. the plugin list, and more importantly, it is really hard to tell >> if a piece of doc is current or what version of Jenkins it was written >> against. For events, there is no direct tie between what shows up on the >> calendar and event listed in blog posts or in the office hours page. >> >> ...also, it is hard to find this mailing group and know that this is >> actually where the meat of the community interactions happens if you are >> starting from Jenkins-ci.org. >> >> As far as traffic growth goes, I believe if a site is well assembled and >> managed, more visitors == better site, because those visitors contribute. >> It is also a good way to assess the health and size of the community. I >> think a big and growing community is something we all want. We don't have >> this problem, but communities sometimes shrink in size and participation. >> When that happens, it becomes a lot harder to find help and support for >> your own needs. >> >> ...so I stand by the statement growth is good. >> And it is good for everyone. >> >> >> >> On Wed, Oct 7, 2015 at 8:05 AM, Slide <[email protected]> wrote: >> >>> 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 a topic in the >>> Google Groups "Jenkins Developers" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-dev/EMbE3a4u8nA/unsubscribe. >>> To unsubscribe from this group and all its topics, 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 >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVd1%2BwB2yd7JjA%3Dxo%3DbU6A0B5u9rMXsMHJkmiGWJ2iVvmg%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/CAOcHHXyFtYGHL-JL4MHyp9CNLqmtpPB-MPWs9-Dfm_W%2BsWzbeQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAOcHHXyFtYGHL-JL4MHyp9CNLqmtpPB-MPWs9-Dfm_W%2BsWzbeQ%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 a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/EMbE3a4u8nA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVeJasgUb_zsMykTPZtvVwS4Bxee8ZYDSgM%2BnmxgUMrKSw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVeJasgUb_zsMykTPZtvVwS4Bxee8ZYDSgM%2BnmxgUMrKSw%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/CAOcHHXy0uh5n-ee0KQD-Mx5fZT5JLutXpfwwGTfKTKAyeSnYbw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
