Henry,

I also think that the document will be useful for committers.
After the wiki is available, could you write 'how to contribute' page?

Hyunsik



On Fri, Mar 22, 2013 at 6:29 AM, Henry Saputra <[email protected]>wrote:

> Thanks Chris, I think this will work for now.
>
> We just have to document this step somehow, maybe in the How To contribute
> section, so the generated HTML in sync with the source (updating maven
> generated HTML is not fun =P)
>
>
> - Henry
>
>
> On Thu, Mar 21, 2013 at 11:32 AM, Mattmann, Chris A (388J) <
> [email protected]> wrote:
>
> > Hey Henry,
> >
> > On 3/21/13 11:23 AM, "Henry Saputra" <[email protected]> wrote:
> >
> > >Hi Chris,
> > >
> > >Thanks for the clarification.
> >
> > NP dude.
> >
> > >
> > >But doing it this way means that I have to copy manually from git local
> > >after creating using mvn site to my other local directory that connect
> to
> > >the svn then commit to make the svn pub sub to work?
> >
> > ACK.
> >
> > 1. git local checkout of src/site for Tajo
> > 2. svn local checkout of
> > https://svn.apache.org/repos/asf/incubator/tajo/site
> > 3. In #1, dev/update site, build mvn site in tmp build directory
> > 4. Copy from #1 to #2
> > 5. svn commit in #2.
> >
> > Sorry it's this way but there is no gitpubsub, or Infra support for it
> for
> > sites,
> > and there's a requirement now for all projects to be on svnpubsub.
> >
> > Until someone helps infra finish gitpubsub :) Who could that be, no one
> > knows ^_^
> >
> > Cheers,
> > Chris
> >
> >
> > >
> > >So the steps will look like:
> > >1. Run mvn site in the incubator-tajo/tajo-project/src/site git repo
> > >2. Copy the generated HTML files from the git target dir to svn local
> dir
> > >for svn.apache.org/repos/asf/incubator/tajo/site
> > >3. svn commit
> > >4. The svn pub sub will track this change and publish to p.a.o/.../tajo/
> > >directory
> > >5. Drink beer
> > >
> > >
> > >
> > >- Henry
> > >
> > >
> > >On Wed, Mar 20, 2013 at 9:54 PM, Mattmann, Chris A (388J) <
> > >[email protected]> wrote:
> > >
> > >> Hi Henry,
> > >>
> > >>
> > >> On 3/20/13 9:41 PM, "Henry Saputra" <[email protected]> wrote:
> > >>
> > >> >Hi Chris, so I guess we should move the MVN site source files from
> > >> >incubator-tajo/tajo-project/src/site git repo to
> > >> >svn.apache.org/repos/asf/incubator/tajo/site somewhere to make it
> > >>easier
> > >> >to
> > >> >update the HTML if we want to keep using mvn to generate the website.
> > >> >
> > >> >I believe infra will target
> > >> >https://svn.apache.org/repos/asf/incubator/tajo/site as the source
> for
> > >> the
> > >>
> > >> This is a great question.
> > >>
> > >> In fact, you don't have to do that. You can define a Site:
> > >>
> > >> 1. src - the MVN source site files and lives in Git
> > >> 2. "published/build site" - this lives in SVN and is what SVN pub sub
> is
> > >> based off,
> > >> and it can be generated from the Git src in #1.
> > >>
> > >> Make sense?
> > >>
> > >> Cheers,
> > >> Chris
> > >>
> > >>
> > >> >SVN pub sub.
> > >> >
> > >> >- Henry
> > >> >
> > >> >
> > >> >On Wed, Mar 20, 2013 at 9:00 PM, Mattmann, Chris A (388J) <
> > >> >[email protected]> wrote:
> > >> >
> > >> >> Hi Henry,
> > >> >>
> > >> >> Actually the website looks like it was generated by MVN.
> > >> >>
> > >> >> The thing though is that infra moved to SVNpubsub for all sites
> > >> >> (either generated by the CMS, which naturally uses SVN pub sub,
> > >> >> or by some other client).
> > >> >>
> > >> >> However, MVN output must be checked into an SVN home, since
> > >> >> the SVN pub sub only works for svn.
> > >> >>
> > >> >> Hope that clarifies!
> > >> >>
> > >> >> Cheers,
> > >> >> Chris
> > >> >>
> > >> >>
> > >> >> On 3/20/13 8:50 PM, "Henry Saputra" <[email protected]>
> wrote:
> > >> >>
> > >> >> >So I guess we are not using mvn to generate the website?
> > >> >> >
> > >> >> >- Henry
> > >> >> >
> > >> >> >
> > >> >> >On Wed, Mar 20, 2013 at 8:02 PM, Mattmann, Chris A (388J) <
> > >> >> >[email protected]> wrote:
> > >> >> >
> > >> >> >> No probs Hyunsik!
> > >> >> >>
> > >> >> >> I've added a first draft of your site to SVN in r1459141. This
> > >>will
> > >> >>be a
> > >> >> >> nice bootstrap for when
> > >> >> >> SVN pub sub is set up in INFRA-6025.
> > >> >> >>
> > >> >> >> From here on out, to update the site, simply:
> > >> >> >>
> > >> >> >> 1. svn co https://svn.apache.org/repos/asf/incubator/tajo/site
> > >> >> >> 2. cd site
> > >> >> >> 3. modify stuff
> > >> >> >> 4. svn commit *
> > >> >> >>
> > >> >> >> And once INFRA-6025 is updated,
> http://incubator.apache.org/tajo/
> > >> >>will
> > >> >> >>be
> > >> >> >> updated automatically.
> > >> >> >>
> > >> >> >> Cheers,
> > >> >> >> Chris
> > >> >> >>
> > >> >> >>
> > >> >> >> On 3/20/13 7:47 PM, "Hyunsik Choi" <[email protected]>
> > wrote:
> > >> >> >>
> > >> >> >> >Thank you very much, Chris!
> > >> >> >> >
> > >> >> >> >
> > >> >> >> >On Thu, Mar 21, 2013 at 11:44 AM, Mattmann, Chris A (388J) <
> > >> >> >> >[email protected]> wrote:
> > >> >> >> >
> > >> >> >> >> Hi Hyunsik,
> > >> >> >> >>
> > >> >> >> >> Actually you are totally eligible.
> > >> >> >> >>
> > >> >> >> >> Daniel just wanted more information per the guide for
> > >>requesting
> > >> >> >> >> a new TLP.
> > >> >> >> >>
> > >> >> >> >> I think I've provided it in:
> > >> >> >> >>
> > >> >> >> >> https://issues.apache.org/jira/browse/INFRA-6025
> > >> >> >> >>
> > >> >> >> >>
> > >> >> >> >> Let's use that for the SVN site creation. Sorry for the
> > >>confusion.
> > >> >> >> >>
> > >> >> >> >> Cheers,
> > >> >> >> >> Chris
> > >> >> >> >>
> > >> >> >> >>
> > >> >> >> >> On 3/20/13 6:19 PM, "Hyunsik Choi" <[email protected]>
> > >> wrote:
> > >> >> >> >>
> > >> >> >> >> >
> > >> >> >> >>
> > >> >> >> >>
> > >> >> >>
> > >> >> >>
> > >> >>
> > >> >>
> > >>
> > >>
> >
> https://issues.apache.org/jira/browse/INFRA-6018?focusedCommentId=1360786
> > >> >> >> >>2
> > >> >> >> >>
> > >> >> >>
> > >> >>
> > >>
> >
> >>>>>>>>>&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabp
> > >>>>>>>>>an
> > >> >>>>>>>el
> > >> >> >>>>>#c
> > >> >> >> >>>om
> > >> >> >> >> >ment-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