incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <joe_schae...@yahoo.com>
Subject Re: Podling website - Access Denied
Date Sat, 18 Jun 2011 00:33:11 GMT
Your commit access to ooo hasn't been activated yet. Probably will happen after the next batch
of accounts are created.

Sent from my iPhone

On Jun 17, 2011, at 8:26 PM, "Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote:

I thought I'd try adding site/ at the ooo/ tree as a test (using Tortoise SVN and having already
done an SVN checkout).  

On the commit, I was prompted for my user ID (orcmid) and my password, but I got
" Error: access to '/repos/asf/!svn/ver/1135683/incubator/ooo' forbidden"  

I am using <https://svn.apache.org/repos/asf/incubator/ooo> as the URL that my working
copy is tied to.

Is there something administrative that is yet to be done?  That I need to do? (I haven't put
an SSH cert at orcmid@people.apache.org yet.)

- Dennis

-----Original Message-----
From: Joe Schaefer [mailto:joe_schaefer@yahoo.com] 
Sent: Friday, June 17, 2011 16:31
To: ooo-dev@incubator.apache.org
Subject: Re: Podling website

I recommend using

http://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openoffice.org/

for the markdown sources.  The way to get everything
into svn is to add them to the ooo tree the way
you would any other code.  Once the basic tree is
established, file an INFRA Jira ticket to enable
the CMS webgui and publishing facilities.


----- Original Message ----
From: Rob Weir <apache@robweir.com>
To: ooo-dev@incubator.apache.org
Sent: Fri, June 17, 2011 4:18:49 PM
Subject: Re: Podling website

So I'm making some progress on the website.

I've read through the CMS  reference doc.  I also downloaded the site from
the Raven podling and  customized the markdown.

A few questions:

1) If I understand  correctly, we put out markdown in
trunk/content/$projectname.  For us,  is that trunk/content/ooo ?  or
trunk/content/openofficeorg ? Does it  matter, so long as it is unique?

I see the podling status page lists the  ultimate URL as :
http://incubator.apache.org/openofficeorg/

So I'm  assuming for now that the markdown goes  into
trunk/content/openofficeorg


2) I'm not seeing how I get these  files initially loaded into the CMS.  I
can see that once it is there, I  can use the bookmarklet to do further
edits.  But how do I bootstrap  this?

Thanks for any hints!

-Rob



On Wed, Jun 15,  2011 at 10:30 AM, Ross Gardler <rgardler@apache.org> wrote:

On 15/06/2011 15:19, Rob Weir wrote:

On Tue, Jun 14, 2011 at  8:40 PM, Greg Stein<gstein@gmail.com>   wrote:

Anakia is "sooooo last decade" technology  and has some requirements
for everybody that wants to use it  (eg. java :-)

If the new CMS can be used, then  I'd recommend going with that. It
would be nice to get the  community working with that today, as it
should be a good tool  to use in the long-term. (Anakia gets to be a
pain for larger  sites)

The CMS is newer than that documentation,  which may be why it "prefers"
anakia.

Please take a look, and I can help with  any authz bits or other setup
(just lemme know what I need to  do).

IOW, my +1 is for the CMS. If we find that  the community doesn't like
it, then we can make another choice  for the long-term site.


 With the CMS, would we also need to check in the generated site into
SVN?
Or do we deploy "live" from the CMS? I assume this is the  later, which
would
be a lot  simpler.


The markdown is in subversion. You can edit  it either offline and commit or
you can use (a fairly basic) web UI.  From the webUI you can publish the
site, but there are also scripts to  enable you to do it from the command
line.


 Can you point me to a project that uses this for their project's  website,
something that I can look at and potentially use a  boilerplate for our
site?


I recently  built the boilerplate for the Rave podling (which in turn was
stolen  from another podling, Clerrezza I think). If you checkout

http://svn.apache.org/repos/**asf/incubator/rave/site/trunk/<http://svn.apache.org/repos/asf/incubator/rave/site/trunk/>and
look over the history you'll get an idea of how we built the site up  for
that podling. The first commit is a fairly bare bones template you  could
reuse with just a little find/replace.

Once you  have this template in place you need to ask infrastructure (via a
JIRA  ticket) to turn on the site publishing features.

As an ASF  committer you can check out the UI of some of the foundation wide
sites,  such as http://community.apache.org (you need the bookmarklet from
the  bottom of https://cms.apache.org/

Ross



--
rgardler@apache.org
@rgardler





Mime
View raw message