Hi -

I think that a brand compliant initial podling page would not be hard to create 
using the Apache CMS.

This could have two simple pages that would show a compliant examples:

(1) Index page with all of the appropriate links to both podling Mailing lists, 
Download placeholder, Apache Branding [1][2], and following Site instructions 
on [3]
(2) Download page that shows how to both refer to pre-Incubation legacy 
releases and how to properly use Apache Dist and closer.lua.

By giving a simple example we get projects going. Not all projects are going to 
want to spend much time on the website so a start is important.


[1] https://www.apache.org/foundation/marks/pmcs#navigation 
[2] https://www.apache.org/foundation/marks/pmcs#attributions 
[3] http://www.apache.org/dev/project-site.html 

> On Apr 15, 2018, at 9:25 AM, John D. Ament <johndam...@apache.org> wrote:
> 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 <kmcgr...@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 <johndam...@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?

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to