You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by Gabriel Reid <ga...@gmail.com> on 2012/09/04 21:01:59 UTC
Re: Karma for Site-SVN needed
Hi guys,
Just to check: the one thing we're waiting on for this is INFRA-5092 [1], and once the CMS is enabled then the site will automatically be up, with the next step being the committing of the site content that Matthias has done into svn under [2], and with those two things taken care of then we'll have a working site up at [3] -- is that all correct?
If there are any other points that are missing (and for which I can take some action on), anyone who can point me in the right direction?
I guess we've still got a short little while before the release for the INFRA issue to happen, but should that not happen, what do you think of just putting in a redirect to the wiki [4]? Any idea if that's technically easy/possible?
If I can help out on this, I really want to (in the last couple of days before I'm on vacation and away from internet access for a bit) -- I would also particularly like to take some of the pressure off of Matthias on this if possible (if that's ok for you Matthias!), as he's been pretty alone on taking care of this stuff so far.
- Gabriel
[1] https://issues.apache.org/jira/browse/INFRA-5092
[2] https://svn.apache.org/repos/asf/incubator/crunch
[3] http://incubator.apache.org/crunch/
[4] https://cwiki.apache.org/confluence/display/CRUNCH/Index
On Tuesday 28 August 2012 at 23:03, Josh Wills wrote:
> On Tue, Aug 28, 2012 at 1:53 PM, Gabriel Reid <gabriel.reid@gmail.com (mailto:gabriel.reid@gmail.com)>wrote:
>
> > My two cents: first of all, I think the site looks awesome -- Matthias,
> > you continue to amaze me with how good you are at getting stuff like this
> > done!
>
>
>
> +100
>
>
> >
> > I think it would be *really* good if we could have the site up before we
> > do a release, just to have a place to point people towards. On the other
> > hand, if getting the site up is going to delay things a whole lot, I'd opt
> > towards making a release without the site.
>
>
>
> I agree-- I am in the *really* wanting website camp. That said, I think we
> can start the process of crafting the release internal to the project and
> create some release candidates for our mentors to start reviewing, as I'm
> sure it will take us a few tries to get this right before we take it to
> general@incubator. I'm happy to serve as release manager for this and will
> start by getting my keys into into the Apache web of trust.
>
>
> > - Gabriel
> >
> >
> > On Tuesday 28 August 2012 at 22:01, Matthias Friedrich wrote:
> >
> > > OK. Just to be clear, in my opinion having a site is no prerequisite
> > > for releasing.
> > >
> > > On Tuesday, 2012-08-28, Josh Wills wrote:
> > > > The site looks great to me.
> > > >
> > > > On Tue, Aug 28, 2012 at 11:10 AM, Matthias Friedrich <matt@mafr.de (mailto:matt@mafr.de)(mailto:
> > matt@mafr.de (mailto:matt@mafr.de))> wrote:
> > > >
> > > > > For the site's content? I think I read something like it but now I
> > > > > can't find it on the Incubator website. If not, all the better.
> > > > >
> > > > > On Tuesday, 2012-08-28, Josh Wills wrote:
> > > > > > We need mentor approval for which piece?
> > > > > >
> > > > > > On Tue, Aug 28, 2012 at 7:44 AM, Matthias Friedrich <matt@mafr.de (mailto:matt@mafr.de)(mailto:
> > matt@mafr.de (mailto:matt@mafr.de))>
> > > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > while we're waiting for infra: Here's a new version of the
> > CMS-enabled
> > > > > > > website with fixed navigation: http://tmp.mafr.de/crunch/
> > > > > > >
> > > > > > > It turns out the CMS doesn't have support for navigation or other
> > > > > > > basic stuff, you have to implement everything yourself in Perl or
> > > > > > > using the Django-inspired templating language.
> > > > > > >
> > > > > > > I think we need mentor approval for this. Other than layout
> > changes
> > > > > > > the difference to the previous Maven-generated version is the
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > lengthy
> > > > > > > footer and the use of Bootstrap [1] which is Apache-licensed. The
> > > > > > > Fluido Skin we used previously also used Bootstrap but they
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > renamed
> > > > > > > the source files so nobody noticed.
> > > > > > >
> > > > > > > Does anyone have time for a review?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Matthias
> > > > > > >
> > > > > > > [1] http://twitter.github.com/bootstrap/index.html
> > > > > > >
> > > > > > > On Monday, 2012-08-27, Matthias Friedrich wrote:
> > > > > > > > Hi Tom,
> > > > > > > >
> > > > > > > > committing to svn works now, thanks. Now it's up to INFRA to
> > enable
> > > > > > > > CMS access (see INFRA-5092).
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Matthias
> > > > > > > >
> > > > > > > > On Monday, 2012-08-27, Tom White wrote:
> > > > > > > > > Hi Matthias,
> > > > > > > > >
> > > > > > > > > I just updated the asf-authorization-template file per [1] to
> > > > > include
> > > > > > > > > all the Crunch committers on the status page. Let me know if
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > that
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > lets
> > > > > > > > > you get further. Sorry for the delay on this.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Tom
> > > > > > > > >
> > > > > > > > > [1] http://www.apache.org/dev/pmc.html#SVNaccess
> > > > > > > > >
> > > > > > > > > On Mon, Aug 27, 2012 at 9:20 AM, Matthias Friedrich <
> > matt@mafr.de (mailto:matt@mafr.de)>
> > > > > > > wrote:
> > > > > > > > > > On Sunday, 2012-08-26, Josh Wills wrote:
> > > > > > > > > > > +jukka
> > > > > > > > > > >
> > > > > > > > > > > Did this get resolved? I (jwills) am also karmaless for
> > our SVN
> > > > > > > repo.
> > > > > > > > > >
> > > > > > > > > > Nope.
> > > > > > > > > >
> > > > > > > > > > I was able to set up the CMS page generator locally and
> > had some
> > > > > > > > > > success to port the Maven-generated site over to a
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > Bootstrap-based
> > > > > > > > > > site that we can edit online through the CMS UI [1]. But
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > even
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > without
> > > > > > > > > > this we've had a reviewed, publishable website [2] for four
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > weeks and
> > > > > > > > > > we're still not closer to getting it published. I'm
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > stopping all
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > work
> > > > > > > > > > on this, if someone cares enough to finish it I'll provide
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > a
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > patch.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Matthias
> > > > > > > > > >
> > > > > > > > > > [1]
> > http://users.mafr.de/~matthias/crunch/site3/content/crunch/
> > > > > > > > > > [2] http://users.mafr.de/~matthias/crunch/site2/
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Director of Data Science
> > > > > > Cloudera <http://www.cloudera.com>
> > > > > > Twitter: @josh_wills <http://twitter.com/josh_wills>
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Director of Data Science
> > > > Cloudera <http://www.cloudera.com>
> > > > Twitter: @josh_wills <http://twitter.com/josh_wills>
> > >
> >
>
>
>
>
> --
> Director of Data Science
> Cloudera <http://www.cloudera.com>
> Twitter: @josh_wills <http://twitter.com/josh_wills>
Re: Karma for Site-SVN needed
Posted by Matthias Friedrich <ma...@mafr.de>.
Hi,
On Wednesday, 2012-09-05, Rahul wrote:
> I am not completely sure on this but as per my understanding, when
> the ticket gets completed the the site will be published to a
> staging domain[1] and then someone would be required to deploy it to
> have a working site. Every time a commit is being done in SVN the
> staging will be updated and then someone should publish it.
Yes, you're right. But since we already tested the mechanism of creating
the site this should only require the press of a button (or two). I've
already checked that I'm able to log into the CMS, but of course,
authentication and authorization are two different things :)
Regards,
Matthias
> [1] http://www.staging.apache.org/
Re: Karma for Site-SVN needed
Posted by Rahul <rs...@xebia.com>.
Guys,
I am not completely sure on this but as per my understanding, when the
ticket gets completed the the site will be published to a staging
domain[1] and then someone would be required to deploy it to have a
working site. Every time a commit is being done in SVN the staging will
be updated and then someone should publish it.
- Rahul
[1] http://www.staging.apache.org/
On 05-09-2012 02:13, Gabriel Reid wrote:
> Hi Matthias,
>
> Ok, thanks for all the info! I'll give it a go getting the page generator running on my machine.
>
> I guess the best approach for the site is to just hope that the INFRA gets taken care of quickly.
>
>
> Regards,
>
> Gabriel
>
>
> On Tuesday 4 September 2012 at 22:29, Matthias Friedrich wrote:
>
>> Hi Gabriel,
>>
>> On Tuesday, 2012-09-04, Gabriel Reid wrote:
>>> Just to check: the one thing we're waiting on for this is INFRA-5092
>>> [1], and once the CMS is enabled then the site will automatically be
>>> up, with the next step being the committing of the site content that
>>> Matthias has done into svn under [2], and with those two things
>>> taken care of then we'll have a working site up at [3] -- is that
>>> all correct?
>>>
>>
>> Yes, that's it exactly. I could have committed the site immediately
>> but I figured it's easier to debug the almost empty default template
>> from INFRA in case there are problems. I've never seen the CMS in
>> action, just the page generator so you never know.
>>
>>> If there are any other points that are missing (and for which I can
>>> take some action on), anyone who can point me in the right
>>> direction?
>>>
>>
>> Hmm, except for a download page I think it's pretty much done. We
>> could always use a getting started page though that explains how to
>> set up a new project with Maven. But since there's no release vote
>> on the site there's no deadline on that.
>>
>> BTW, I'm currently working on an archetype that should streamline
>> project setup and make things easier to explain.
>>
>>> I guess we've still got a short little while before the release for
>>> the INFRA issue to happen, but should that not happen, what do you
>>> think of just putting in a redirect to the wiki [4]? Any idea if
>>> that's technically easy/possible?
>>>
>>
>> Technically possible yes, but a second ticket to INFRA will probably
>> take longer than getting the CMS configured. And then we'd have to
>> get the redirect removed which is going to take another ticket.
>>
>>> If I can help out on this, I really want to (in the last couple of
>>> days before I'm on vacation and away from internet access for a bit)
>>> -- I would also particularly like to take some of the pressure off
>>> of Matthias on this if possible (if that's ok for you Matthias!), as
>>> he's been pretty alone on taking care of this stuff so far.
>>>
>>
>> Thank you, Gabriel, much appreciated! As I said, I don't think there's
>> anything that really needs to be done right now, but we should
>> distribute knowlege in case I'm run over by a bus ;-)
>>
>> I have attached the site to CRUNCH-56 [5]. If you want to run INFRA's
>> page generator locally, you have to check out [6], change to the
>> directory and run the markdownd daemon (you may need to install some
>> dependencies, for me it was only python-markdown):
>>
>> export MARKDOWN_SOCKET=`pwd`/markdown.socket
>> export PYTHONPATH=`pwd`
>> python markdownd.py
>>
>> Then run the build_site.pl (http://build_site.pl) script:
>>
>> ./build_site.pl (http://build_site.pl) --source-base path/to/site/trunk/ \
>> --target /tmp/site
>>
>> Next publish the website via some HTTP server:
>>
>> cd /tmp/site/content && python -m SimpleHTTPServer
>>
>> That's it really. All documentation you might need is linked from the
>> CMS reference page [7]; the documentation for the Bootstrap CSS
>> framework is at [8].
>>
>> Regards,
>> Matthias
>>
>> [5] https://issues.apache.org/jira/browse/CRUNCH-56
>> [6] https://svn.apache.org/repos/infra/websites/cms/build
>> [7] http://www.apache.org/dev/cmsref.html#local-build
>> [8] http://twitter.github.com/bootstrap/index.html
>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-5092
>>> [2] https://svn.apache.org/repos/asf/incubator/crunch
>>> [3] http://incubator.apache.org/crunch/
>>> [4] https://cwiki.apache.org/confluence/display/CRUNCH/Index
>>>
>>
>>
>
>
Re: Karma for Site-SVN needed
Posted by Gabriel Reid <ga...@gmail.com>.
Hi Matthias,
Ok, thanks for all the info! I'll give it a go getting the page generator running on my machine.
I guess the best approach for the site is to just hope that the INFRA gets taken care of quickly.
Regards,
Gabriel
On Tuesday 4 September 2012 at 22:29, Matthias Friedrich wrote:
> Hi Gabriel,
>
> On Tuesday, 2012-09-04, Gabriel Reid wrote:
> > Just to check: the one thing we're waiting on for this is INFRA-5092
> > [1], and once the CMS is enabled then the site will automatically be
> > up, with the next step being the committing of the site content that
> > Matthias has done into svn under [2], and with those two things
> > taken care of then we'll have a working site up at [3] -- is that
> > all correct?
> >
>
>
> Yes, that's it exactly. I could have committed the site immediately
> but I figured it's easier to debug the almost empty default template
> from INFRA in case there are problems. I've never seen the CMS in
> action, just the page generator so you never know.
>
> > If there are any other points that are missing (and for which I can
> > take some action on), anyone who can point me in the right
> > direction?
> >
>
>
> Hmm, except for a download page I think it's pretty much done. We
> could always use a getting started page though that explains how to
> set up a new project with Maven. But since there's no release vote
> on the site there's no deadline on that.
>
> BTW, I'm currently working on an archetype that should streamline
> project setup and make things easier to explain.
>
> > I guess we've still got a short little while before the release for
> > the INFRA issue to happen, but should that not happen, what do you
> > think of just putting in a redirect to the wiki [4]? Any idea if
> > that's technically easy/possible?
> >
>
>
> Technically possible yes, but a second ticket to INFRA will probably
> take longer than getting the CMS configured. And then we'd have to
> get the redirect removed which is going to take another ticket.
>
> > If I can help out on this, I really want to (in the last couple of
> > days before I'm on vacation and away from internet access for a bit)
> > -- I would also particularly like to take some of the pressure off
> > of Matthias on this if possible (if that's ok for you Matthias!), as
> > he's been pretty alone on taking care of this stuff so far.
> >
>
>
> Thank you, Gabriel, much appreciated! As I said, I don't think there's
> anything that really needs to be done right now, but we should
> distribute knowlege in case I'm run over by a bus ;-)
>
> I have attached the site to CRUNCH-56 [5]. If you want to run INFRA's
> page generator locally, you have to check out [6], change to the
> directory and run the markdownd daemon (you may need to install some
> dependencies, for me it was only python-markdown):
>
> export MARKDOWN_SOCKET=`pwd`/markdown.socket
> export PYTHONPATH=`pwd`
> python markdownd.py
>
> Then run the build_site.pl (http://build_site.pl) script:
>
> ./build_site.pl (http://build_site.pl) --source-base path/to/site/trunk/ \
> --target /tmp/site
>
> Next publish the website via some HTTP server:
>
> cd /tmp/site/content && python -m SimpleHTTPServer
>
> That's it really. All documentation you might need is linked from the
> CMS reference page [7]; the documentation for the Bootstrap CSS
> framework is at [8].
>
> Regards,
> Matthias
>
> [5] https://issues.apache.org/jira/browse/CRUNCH-56
> [6] https://svn.apache.org/repos/infra/websites/cms/build
> [7] http://www.apache.org/dev/cmsref.html#local-build
> [8] http://twitter.github.com/bootstrap/index.html
>
> > [1] https://issues.apache.org/jira/browse/INFRA-5092
> > [2] https://svn.apache.org/repos/asf/incubator/crunch
> > [3] http://incubator.apache.org/crunch/
> > [4] https://cwiki.apache.org/confluence/display/CRUNCH/Index
> >
>
>
>
Re: Karma for Site-SVN needed
Posted by Matthias Friedrich <ma...@mafr.de>.
Hi Gabriel,
On Tuesday, 2012-09-04, Gabriel Reid wrote:
> Just to check: the one thing we're waiting on for this is INFRA-5092
> [1], and once the CMS is enabled then the site will automatically be
> up, with the next step being the committing of the site content that
> Matthias has done into svn under [2], and with those two things
> taken care of then we'll have a working site up at [3] -- is that
> all correct?
Yes, that's it exactly. I could have committed the site immediately
but I figured it's easier to debug the almost empty default template
from INFRA in case there are problems. I've never seen the CMS in
action, just the page generator so you never know.
> If there are any other points that are missing (and for which I can
> take some action on), anyone who can point me in the right
> direction?
Hmm, except for a download page I think it's pretty much done. We
could always use a getting started page though that explains how to
set up a new project with Maven. But since there's no release vote
on the site there's no deadline on that.
BTW, I'm currently working on an archetype that should streamline
project setup and make things easier to explain.
> I guess we've still got a short little while before the release for
> the INFRA issue to happen, but should that not happen, what do you
> think of just putting in a redirect to the wiki [4]? Any idea if
> that's technically easy/possible?
Technically possible yes, but a second ticket to INFRA will probably
take longer than getting the CMS configured. And then we'd have to
get the redirect removed which is going to take another ticket.
> If I can help out on this, I really want to (in the last couple of
> days before I'm on vacation and away from internet access for a bit)
> -- I would also particularly like to take some of the pressure off
> of Matthias on this if possible (if that's ok for you Matthias!), as
> he's been pretty alone on taking care of this stuff so far.
Thank you, Gabriel, much appreciated! As I said, I don't think there's
anything that really needs to be done right now, but we should
distribute knowlege in case I'm run over by a bus ;-)
I have attached the site to CRUNCH-56 [5]. If you want to run INFRA's
page generator locally, you have to check out [6], change to the
directory and run the markdownd daemon (you may need to install some
dependencies, for me it was only python-markdown):
export MARKDOWN_SOCKET=`pwd`/markdown.socket
export PYTHONPATH=`pwd`
python markdownd.py
Then run the build_site.pl script:
./build_site.pl --source-base path/to/site/trunk/ \
--target /tmp/site
Next publish the website via some HTTP server:
cd /tmp/site/content && python -m SimpleHTTPServer
That's it really. All documentation you might need is linked from the
CMS reference page [7]; the documentation for the Bootstrap CSS
framework is at [8].
Regards,
Matthias
[5] https://issues.apache.org/jira/browse/CRUNCH-56
[6] https://svn.apache.org/repos/infra/websites/cms/build
[7] http://www.apache.org/dev/cmsref.html#local-build
[8] http://twitter.github.com/bootstrap/index.html
> [1] https://issues.apache.org/jira/browse/INFRA-5092
> [2] https://svn.apache.org/repos/asf/incubator/crunch
> [3] http://incubator.apache.org/crunch/
> [4] https://cwiki.apache.org/confluence/display/CRUNCH/Index