You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2014/03/14 05:57:11 UTC
pre-graduation action items
The incubator-general list has pointed out several areas where we should
improve our online presence. I will be traveling tomorrow - could folks
jump in and help make these adjustments ASAP? (If we can complete them
soon and get a green light to put graduation on the Board's Wednesday
agenda, then we'll be in a very good position for Wayne and me when
presenting Allura at ApacheCon in a few weeks).
See http://markmail.org/message/rghh5epojmgplb2e for my response where I
mention all the things I think we can & should change. Can we make all
those changes, and then respond on that thread when complete?
For our doc hosting, I was thinking we could just configure apache on
forge-allura.a.o to serve /p/allura/docs from a static directory instead
of sending it through to the allura webapp. Automated publishing of our
docs is currently on a SourceForge-internal jenkins job. We should
remove that, and set up the current/old docs location to redirect to the
new. If time allows automated publishing for the new location could be
done as part of the deploy.sh cron job on forge-allura, but that's
secondary to actually just moving the docs.
I am not sure how to make http://incubator.apache.org/allura redirect.
I believe the source is
http://svn.apache.org/repos/asf/incubator/allura/site/ but it's using a
CMS system. May have to do some research or ask around if there's a way
to not use the CMS and redirect. At a minimum I suppose it should be
possible to make it the page be nothing but a single link.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: pre-graduation action items
Posted by Cory Johns <jo...@gmail.com>.
Ok, the news section of the status page (
http://incubator.apache.org/projects/allura.html) has been updated as well.
Unless anyone sees anything that we missed, I'm going to update the
graduation thread on incubator-general.
On Fri, Mar 14, 2014 at 3:18 PM, Cory Johns <jo...@gmail.com> wrote:
>
> On Fri, Mar 14, 2014 at 12:57 AM, Dave Brondsema <da...@brondsema.net>wrote:
>
>> See http://markmail.org/message/rghh5epojmgplb2e for my response where I
>> mention all the things I think we can & should change. Can we make all
>> those changes, and then respond on that thread when complete?
>>
>>
> All of the naming, trademark, copyright, and linking issues raised in the
> thread should now be resolved. I'm also going to add our releases to the
> News section of the status page (
> http://incubator.apache.org/projects/allura.html) so that it is more
> complete.
>
Re: pre-graduation action items
Posted by Cory Johns <jo...@gmail.com>.
On Fri, Mar 14, 2014 at 12:57 AM, Dave Brondsema <da...@brondsema.net> wrote:
> See http://markmail.org/message/rghh5epojmgplb2e for my response where I
> mention all the things I think we can & should change. Can we make all
> those changes, and then respond on that thread when complete?
>
>
All of the naming, trademark, copyright, and linking issues raised in the
thread should now be resolved. I'm also going to add our releases to the
News section of the status page (
http://incubator.apache.org/projects/allura.html) so that it is more
complete.
Re: pre-graduation action items
Posted by Tim Van Steenburgh <tv...@gmail.com>.
On Friday, March 14, 2014 at 12:57 AM, Dave Brondsema wrote:
> The incubator-general list has pointed out several areas where we should
> improve our online presence. I will be traveling tomorrow - could folks
> jump in and help make these adjustments ASAP? (If we can complete them
> soon and get a green light to put graduation on the Board's Wednesday
> agenda, then we'll be in a very good position for Wayne and me when
> presenting Allura at ApacheCon in a few weeks).
>
> See http://markmail.org/message/rghh5epojmgplb2e for my response where I
> mention all the things I think we can & should change. Can we make all
> those changes, and then respond on that thread when complete?
>
> For our doc hosting, I was thinking we could just configure apache on
> forge-allura.a.o to serve /p/allura/docs from a static directory instead
> of sending it through to the allura webapp. Automated publishing of our
> docs is currently on a SourceForge-internal jenkins job. We should
> remove that, and set up the current/old docs location to redirect to the
> new. If time allows automated publishing for the new location could be
> done as part of the deploy.sh (http://deploy.sh) cron job on forge-allura, but that's
> secondary to actually just moving the docs.
>
>
I’ll get started setting up the docs on forge-allura.a.o.
>
> I am not sure how to make http://incubator.apache.org/allura redirect.
> I believe the source is
> http://svn.apache.org/repos/asf/incubator/allura/site/ but it's using a
> CMS system. May have to do some research or ask around if there's a way
> to not use the CMS and redirect. At a minimum I suppose it should be
> possible to make it the page be nothing but a single link.
>
> --
> Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
>
Re: pre-graduation action items
Posted by Tim Van Steenburgh <tv...@gmail.com>.
On Friday, March 14, 2014 at 12:57 AM, Dave Brondsema wrote:
> The incubator-general list has pointed out several areas where we should
> improve our online presence. I will be traveling tomorrow - could folks
> jump in and help make these adjustments ASAP? (If we can complete them
> soon and get a green light to put graduation on the Board's Wednesday
> agenda, then we'll be in a very good position for Wayne and me when
> presenting Allura at ApacheCon in a few weeks).
>
> See http://markmail.org/message/rghh5epojmgplb2e for my response where I
> mention all the things I think we can & should change. Can we make all
> those changes, and then respond on that thread when complete?
>
> For our doc hosting, I was thinking we could just configure apache on
> forge-allura.a.o to serve /p/allura/docs from a static directory instead
> of sending it through to the allura webapp.
>
>
Done. I left the /p/allura/docs Link tool installed, but repointed it to /docs, which is served statically.
> Automated publishing of our
> docs is currently on a SourceForge-internal jenkins job. We should
> remove that, and set up the current/old docs location to redirect to the
> new.
>
>
Done. Disabled SF jenkins allura-docs build and installed an .htaccess redirect from allura.sourceforge.net/docs to forge-allura.a.o/p/allura/docs.
> If time allows automated publishing for the new location could be
> done as part of the deploy.sh (http://deploy.sh) cron job on forge-allura, but that's
> secondary to actually just moving the docs.
>
>
Done. `deploy.sh` has been updated to build and deploy docs when new commits are pushed.
>
> I am not sure how to make http://incubator.apache.org/allura redirect.
> I believe the source is
> http://svn.apache.org/repos/asf/incubator/allura/site/ but it's using a
> CMS system. May have to do some research or ask around if there's a way
> to not use the CMS and redirect. At a minimum I suppose it should be
> possible to make it the page be nothing but a single link.
>
> --
> Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
>