Show me the beef. Where's the repo? On Tue, Oct 6, 2015 at 11:39 PM, Gus Reiber <[email protected]> wrote: > Fair enough. > Let's see the pull requests, then. It has been a long time and they haven't > come. > > ...10 years as you point out for the product GUI. I am not sure when the > Jenkins-ci.org website was last overhauled, but I am guessing at least 5 > years ago. > > On Tue, Oct 6, 2015 at 8:34 PM, jieryn <[email protected]> wrote: >> >> Seriously, this idea is so obvious I almost hate to mention it. >> >> Make the site a repository and accept pull requests. How hard is that? >> I bet the site would improve drastically with small and simple pull >> requests, but also large changes which let users really go wild. >> >> Jenkins was made great by Kohsuke and the community, in probably equal >> measures. Let the community carry the rain water on this. Make the >> site a git repo and start accepting pull requests.. This leading by >> singular people is not working out at all. I'm sorry. I really >> appreciate your efforts, but I consider them not good and/or >> misguided. >> >> Let's let the community decide it with pull requests. >> >> On Tue, Oct 6, 2015 at 6:17 PM, Gus Reiber <[email protected]> wrote: >> > That's fair. >> > Moderating a sight can get to be a lot of work. >> > >> > ...although, at the point at which you have so much externally >> > contributed >> > content that the task of moderating the site becomes a big burden, the >> > site >> > is almost by definition a big success. The current website doesn't >> > generate >> > a lot of comments or article contribution so this problem doesn't exist. >> > The >> > bigger problem of not so great website exists, instead. >> > >> > The way I see it is this... to be a good site, the site needs to have a >> > lot >> > of fresh and quality content. If you write all that content yourself, >> > you >> > have a lot of work to do all the time, because the content always needs >> > to >> > be updating. If your visitors write some of that content for you, you >> > have >> > somewhat less work, but you also have somewhat different work. But >> > again, >> > what makes the site good is quantity of material (and quality, but >> > quality >> > comes from quantity). >> > >> > We don't get site traffic until the site is good. >> > >> > ...so step 1 is write a lot of good content. >> > ...step 2 is let other people augment that content. >> > >> > ...repeat and edit as necessary. >> > >> > >> > >> > On Friday, October 2, 2015 at 5:58:47 PM UTC-7, Daniel Beck wrote: >> >> >> >> >> >> On 02.10.2015, at 20:17, Kohsuke Kawaguchi <[email protected]> wrote: >> >> >> >> > My key take away is that we can drive participation more by >> >> > encouraging >> >> > people to sign up and create an account, which converts them from >> >> > anonymous >> >> > drive-by visitors into a "card carrying member of the Jenkins >> >> > community", >> >> > which makes a lot of sense. >> >> >> >> It's definitely in interesting concept. >> >> >> >> The major problem I see with this is the need for moderation when >> >> everyone >> >> is allowed to post everywhere. And that doesn't even consider the >> >> manual >> >> work needed to correlate the work of numerous individual contributors >> >> as >> >> mentioned at the bottom. This requires that the moderator tools are >> >> exceptionally strong to not take up a lot of time. >> >> >> >> One other issue that concerns me is that the vision requires a lot of >> >> participation to take off. Maybe I'm too pessimistic here, but I see a >> >> similar situation like those small business web sites with a section >> >> called >> >> 'special offers' or 'news' that is never updated. It just looks sad if >> >> e.g. >> >> you can vote on things in a list, and nothing has been voted on. A site >> >> should grow towards the described level of participation rather than go >> >> from >> >> basically nothing to that level. What do others think? >> >> >> > -- >> > 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/cc4e2251-3fd0-44dd-90e1-6e38d685cccb%40googlegroups.com. >> > >> > 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/CAArU9iYeyxfiA-E2Lr1Pepfo1xVf1RRxtC0KKdkXvzVa3%3D7-NQ%40mail.gmail.com. >> 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/CAOcHHXxpzB2A666w-vApB1AUEQ%2BxFTWaBVc9O9Ja6xpo2_P6Dg%40mail.gmail.com. > > 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/CAArU9iZSi7me_HnAqWDr-MZz_kuN4jcWi1PXWcUonfiK912Lxg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
