incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <johndam...@apache.org>
Subject Re: Default webpages for new podlings
Date Sun, 15 Apr 2018 16:25:38 GMT
I don't believe that linking to the status page would satisfy the website
requirement, but solves the 404 issue.  At least in my mind it wouldn't get
them out of needing a website.  I put out three months because that's
that's the longest I've seen the bootstrapping to take.  To make sure I'm
being clear - I'm only trying to help solve the 404 issue.

I think what we need to offer though is a complete solution.  From the
podlings I've dealt with, keeping revision history on websites is usually
not helpful.  If we had a way to retain it great, and may end up being part
of their on boarding.  Seeding them though with a website repository + the
necessary branches to maintain the website would be helpful in kick
starting that process.  They then have a base to build from.  It could be
that we create this skeleton and some tips (I may have already written them
down somewhere).

John

On Sun, Apr 15, 2018 at 11:39 AM Kevin A. McGrail <kmcgrail@apache.org>
wrote:

> I think this is a great day one idea but by 3 months,.the project should be
> having a website to start that ball rolling.  This might be too much of a
> crutch.
>
> On Sun, Apr 15, 2018, 11:10 John D. Ament <johndament@apache.org> wrote:
>
> > Based on some of the on going discussions, wanted to get opinions on how
> to
> > get podling websites bootstrapped a bit easier.
> >
> > When I review https://incubator.apache.org/guides/sites.html it seems
> > pretty clear what we expect on a podling website.  I'm wondering if
> during
> > the bootstrapping phase (first 3 months or so of the project at Apache,
> in
> > my mind at least) it would be OK if the podlings website just redirected
> to
> > their status page.
> >
> > This avoid unnecessary 404's for the project, and gives them some time to
> > move their infrastructure over.  Once they have their website up and
> > running (either migrated or created from scratch) then they can switch
> the
> > redirect to point to their actual content.
> >
> > I would imagine this can be done with a .htaccess file, similar to what's
> > done for retired podlings.
> >
> > Thoughts?
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message