search for: brockmeier

On Thu, May 14, 2015 at 7:35 AM, Joe Brockmeier <jzb at redhat.com> wrote: > On 05/12/2015 06:13 AM, Karanbir Singh wrote: >> Hi, >> >> I've created http://wiki.centos.org/ContainerPipleline as a placeholder >> to start populating about the pipeline. Although this will run from >> ci.centos.org hosted i...

Howdy - Was trying to revive the CentOS Newsletter and went to edit this page: http://wiki.centos.org/Newsletter/Contributing And was told I don't have access. Can I get access to that page / pages related to the Newsletter, please? Thanks! jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

Hey all, Is there better documentation on setting up ACLs for the wiki than what's here? (http://wiki.centos.org/SyntaxReference?action=show&redirect=centoswiki%2FSyntaxReference) Thanks, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP dig...

Hi all, Requesting edit permissions for the wiki. I'm going to be involved in planning some of the dojos and possibly working on the cloud instance SIG, and would like to be able to edit the wiki as needed. Username: JoeBrockmeier Thanks! jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

Hi, I've created http://wiki.centos.org/ContainerPipleline as a placeholder to start populating about the pipeline. Although this will run from ci.centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it will form a sort of ecocystem test + release process, I think it deserves scope beyond being just under the CI namespace. - KB -- Karanbir Singh, Project Lead, The CentOS

...centos.org hosted infra ( http://wiki.centos.org/QaWiki/CI ) - and it > will form a sort of ecocystem test + release process, I think it > deserves scope beyond being just under the CI namespace. Pipleline? :-) Should that be: http://wiki.centos.org/ContainerPipeline ? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb at redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP dig...

hi, wondering if we should setup a twitter account for seven.centos.org and have it linked into the blog code to auto tweet on new posts ? There is a lot of great content on the blog now, and I suspect its not getting a lot of air time. Could we do something similar for the centos facebook groups as well ? Regards -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 |

This past Wed., 9/28/05, NewsForge [a website property of the Open Source Technology Group ((OSTG))], published a review of John Terpstra's new Second Edition, of "Samba-3 by Example: Practical Exercises to Successful Deployment". The review, written by Joe 'Zonker' Brockmeier, opens with this paragraph: "Too many technical books provide superficial coverage of their subject matter. Samba-3 by Example by John H. Terpstra, a long-time member of the Samba Team, is one of the rare titles that actually delivers the goods." To read the full review, please link to:...

...Case studies, best practices, tips and tricks, etc. What we avoid at Dojos are product pitches or 101-type presentations that won't be useful for experienced admins / users. Please let me know if you have any questions. Thanks! [1] http://lists.centos.org/mailman/listinfo/centos-promo -- Joe Brockmeier jzb at zonker.net Twitter: @jzb http://www.dissociatedpress.net/

Long story short, the core team doesn't need to be in the business of micro-managing wiki permissions. We've not been that good at it during the best of times, and as the 6.6 build process is showing we've clearly let some stuff slip without following up on it appropriately here. What I'd propose is that 3-4 people who have been around the distribution a while (perhaps John