https://issues.apache.org/jira/browse/INFRA-6018?focusedCommentId=13607862&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13607862

http://www.apache.org/dev/infra-contact#requesting-podling

I'm not eligible to request the site creation.

Jakob,
Could you please request the site creation?

Thanks,
Hyunsik



On Thu, Mar 21, 2013 at 12:43 AM, Hyunsik Choi <[email protected]>wrote:

> Henry,
>
> I've just read the guide (http://www.apache.org/dev/cms.html). As you
> mentioned, CMS looks recommended. It seems to work with maven site.
>
> Since I don't have any experience to use CMS, I've just surveyed some jira
> issues to request CMS. According to them, the website in CMS must remain in
> SVN. So, I've just asked the infra team to create an additional SVN
> repository for CMS.
>
> https://issues.apache.org/jira/browse/INFRA-6018
>
> Thanks,
> Hyunsik
>
>
>
> On Wed, Mar 20, 2013 at 9:17 PM, Henry Saputra <[email protected]>wrote:
>
>> HI Hyunksik, thanks for taking stab at the homepage. Just update that I am
>> also in PST which is -8 Time Zone
>>
>> This is a good start. One consideration is whether we want to use svn pub
>> sub or CMS for website management?
>> I believe most projects are encouraged to move to Apache CMS style of home
>> page.
>>
>> - Henry
>>
>>
>> On Wed, Mar 20, 2013 at 3:55 AM, Hyunsik Choi <[email protected]> wrote:
>>
>> > Hi folks,
>> >
>> > I'm working on the tajo homepage. Here is the first draft.
>> > http://people.apache.org/~hyunsik/tajo/site/index.html
>> >
>> > This draft is based on the original tajo home at github (
>> > http://tajo-project.github.com/tajo). I've modified the following
>> things:
>> >
>> > * The first page (removed long and boring descriptions)
>> > * Team list (added all committers and mentors)
>> > * Menu layout
>> > * getting started page completed
>> > * Apache Incubator logo and Disclaimer added
>> >
>> > I don't know all of the members's updated affiliations and time zones.
>> So,
>> > some of the entries remain blank or may include wrong information. If
>> you
>> > find wrong information, please let me know.
>> >
>> > In addition, I'm not a native English speaker. Some descriptions may
>> need
>> > improvement. So, you could suggest me more elegant expressions.
>> >
>> > I'm looking forward to your feedback.
>> >
>> > Thanks,
>> > Hyunsik
>> >
>>
>
>

Reply via email to