gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manu Zhang (JIRA)" <>
Subject [jira] [Commented] (GEARPUMP-28) Transit the website to Apache
Date Sun, 01 May 2016 13:11:12 GMT


Manu Zhang commented on GEARPUMP-28:

You checked in to [] ?
I don't see any related commits.
We need to push the generated files to the content folder on "asf-site" branch.

> Transit the website to Apache
> -----------------------------
>                 Key: GEARPUMP-28
>                 URL:
>             Project: Apache Gearpump
>          Issue Type: Bug
>            Reporter: Sean Zhong
>            Assignee: Qian Xu
> Requirements:
> 1. Add links and logo, and etc to meet the hard requirements of a Apache site:
> With these must be added:
>  {quote}
>  1. Project Home Page: the primary entry point to the site; contains project description,
news, invitation to join the project.
> 2. License Page: usually, the Apache License 2.0
> 3. Downloads: many projects in incubation will release code, and this page describes
them and has links to the download pages that redirect to Apache Mirror sites.
> 4. Documentation: this page describes the project documentation, including javadoc for
Java projects; guides, tutorials, and links to external documentation.
> 5. Committers: a list of current committers on the project.
> 6. Mailing Lists: there are several mailing lists that the community might be interested
in, and this page contains mailto: links that allow easy subscription (and unsubscription)
to any of them.
> 7. FAQ: frequently asked questions are answered here.
> 8. Road Map: if the project has a vision of future community or development activities,
the road map is published here.
> 9. Source Code: links to the browsable source repository and svn commands to check out
the sources.
> 10. Coding Standards: the coding standards for submitted code by the community, along
with a description of how strict the project intends to be.
> 11. Issue Tracking: links to the JIRA or other issue tracking tool, possibly including
frequently used filters for issue lists.
> 12. Dependencies: other projects that this project depends on.
> 13. favicon: the project's icon in a format suitable for a browser's address bar. If
absent, an Apache Feather will be displayed.
>  {quote}
> 2. Refine the UI layout to be more user friendly. 
> 3. We will build the site with content from source of
>   a.   
>   b.
>   And then publish the site to  asf-site branch of repo
> 4. Create automatic script to generate the site content:
>   a. pull  version related document from docs/ folder of
>   b. Pull version irrelevant website markdown content from
>   c. Run Jekyll build, 
>   d. Publish to 
(NOTE: asf-site branch)

This message was sent by Atlassian JIRA

View raw message