www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-3228) New TLP: ZooKeeper
Date Tue, 23 Nov 2010 18:55:15 GMT

    [ https://issues.apache.org/jira/browse/INFRA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934971#action_12934971

Patrick Hunt commented on INFRA-3228:

Conversation on IRC btw me and Joe:

10:21 < joes4> infrabot: comment jira 3228
10:21 < infrabot> <phunt> For our website we currently use Forrest and are exploring
"mvn site" for generating our website & docs instead:
10:21 < infrabot> <phunt> https://issues.apache.org/jira/browse/ZOOKEEPER-925
10:21 < infrabot> <phunt> I've heard a bit about CMS, but honestly I'm not very
familiar with it. Is it ready for general use? I see this
10:21 < infrabot> <phunt> http://wiki.apache.org/general/ApacheCms2010
10:21 < infrabot> <phunt> but it's not very clear to me what the tradeoffs will
be from a user perspective. In particular how does the content generation workflow compare
to "mvn site". In my experience that's what our contrib...
10:21 < infrabot> <phunt> What would you suggest, say maven site plugin vs this
10:29 < infrabot> Joe Schaefer Commented: (INFRA-3228) New TLP: ZooKeeper
10:30 < joes4> phunt: the cms is way better. give it a spin for www.apache.org and i'll
walk you through the featureset
10:32 < joes4> phunt: to get started go to https://cms.apache.org/ and install the bookmarklet
10:32 < joes4> let me know when you've done that
10:33 < phunt> joes4: on page, bookmarklet installed
10:34 < joes4> ok now go to http://www.apache.org/foundation/thanks.html and click on
the bookmarklet
10:35 < phunt> https://cms.apache.org/www/wc/browse/phunt-9fkfTv/trunk/content/foundation/thanks.mdtext
10:35 < joes4> now click on Edit
10:36 < joes4> the left-hand pane is a markdown editor
10:36 < joes4> the right-hand pane is a preview of the resulting html
10:36 < phunt> Ok. got it.
10:37 < phunt> editing. markdown, good.
10:37 < joes4> ok lets try to find a page you can actually edit.  Go Back
10:37 < phunt> joes4: what are the other links, staging, static, prod
10:37 < phunt> publish
10:38 < phunt> joes4: also, this is committer only? what about regular contributors?
(I had to login iirc)
10:38 < joes4> committer only yes
10:38 < joes4> contributors can check out the site via svn and submit patches
10:39 < phunt> joes4: the pages are just markdown in svn? each page.
10:39 < joes4> yes
10:39 < phunt> Ok.
10:39 < phunt> How does that work? they submit patch, we commit to svn, it's in staging
for review?
10:39 < joes4> yes.
10:39 < phunt> we == committer
10:39 < joes4> if you like it you publish it
10:39 < phunt> Ok.
10:40 < phunt> this is the indiv page, what about site nav and skinning?
10:40 < joes4> you write templates
10:40 < phunt> ok.
10:40 < joes4> the www site uses django
10:40 < joes4> (perl port of)
10:40 < phunt> all this is just in svn right? we can checkout the zookeeper site/docs
via svn if we don't want to use the gui?
10:40 < joes4> yes
10:41 < phunt> ok. so we can also generate the site and view locally in django if we
want to do it that way too?
10:41 < joes4> the only thing you need to do with the webgui is publish
10:41 < joes4> yes
10:41 < phunt> Great.
10:41 < phunt> Plus all the commits are in svn with logs. Nice.
10:42 < phunt> Not having what you just told me in a doc makes it tough for me to get
this out to the rest of the team for their approval though.
10:42 < phunt> Should be a no brainer though.
10:44 < joes4> http://www.apache.org/dev/infra-site.html
10:44 < joes4> usage docs go there
10:44 < phunt> with RTC process we just put it on staging, then have someone review?
10:45 < joes4> just commit it and it'll get built to staging
10:45 < phunt> we usually do site releases with the release, this gives us more flexibility
(cms) but I'll have to think through some of the implications.
10:45 < phunt> anyone that's a committer can publish? by clicking the link.
10:45 < joes4> you can write a simple webclient for publishing too if you want to completely
avoid the webui
10:45 < joes4> phunt: up to you who can publish
10:46 < phunt> I assume that emails are sent out to the list on changes, same as regular
10:46 < joes4> normally we restrict to proj committers
10:46 < joes4> yes
10:46 < phunt> Ok. great.
10:46 < phunt> Alright. this looks awesome. Great job guys!
10:47 < curcuru> quick question: does the new CMS mean that now all committers have
write access to the a.o site?  In the past it was just members.
10:47 < phunt> Gentlemen and Ladies. :-)
10:47 < joes4> all committers can commit changes
10:47 < joes4> only members and infra can publish
10:48 < phunt> joes4: I'll update 3228 - we should go ahead with CMS for the site. I'll
work out the details with the ZK community.
10:48 < phunt> joes4: thanks!
10:48 < joes4> just give me the svn url of a conforming layout and i'll do the rest
10:49 < phunt> joes4: ah, we we use the default apache one to start?

> New TLP: ZooKeeper
> ------------------
>                 Key: INFRA-3228
>                 URL: https://issues.apache.org/jira/browse/INFRA-3228
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: TLP Admin
>            Reporter: Patrick Hunt
> The board voted to promote ZooKeeper to a TLP from Hadoop subproject. This issue will
track the infrastructure changes required to implement this. 
> I, phunt@apache.org, am the PMC Chair of the ZooKeeper TLP.
> I believe we need the following: 
> (1) create 'zookeeper' unix user group containing zookeeper committers 
> (2) create zookeeper subversion repository. we'll move the code later 
> (3) create /www/zookeeper.apache.org/. we'll add content & redirects later. (And
anything else that needed to move our site) 
> (4) rename zookeeper-*@hadoop.apache.org to *.zookeeper.apache.org, forwarding old addresses,
adding phunt & mahadev as moderators. 
> (5) create private@zookeeper.apache.org with phunt & mahadev as moderators 
> Initial PMC are: 
>         * Patrick Hunt         <phunt@apache.org>
>         * Flavio Junqueira     <fpj@apache.org>
>         * Mahadev Konar        <mahadev@apache.org>
>         * Benjamin Reed        <breed@apache.org>
>         * Henry Robinson       <henry@apache.org>
> Initial Committers are:  (notice 1 more than pmc - Andrew)
>         * Andrew Kornev	<akornev@apache.org>
>         * Patrick Hunt         <phunt@apache.org>
>         * Flavio Junqueira     <fpj@apache.org>
>         * Mahadev Konar        <mahadev@apache.org>
>         * Benjamin Reed        <breed@apache.org>
>         * Henry Robinson       <henry@apache.org>
> Thank you!

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message