community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))
Date Thu, 08 Jan 2015 09:14:56 GMT
Apache Drill has been doing something like this for some time.  They use
Jekyll from Github to render markdown as HTML and then commit the HTML to
SVN to that pubsub carries it to the right places.

By doing this in the gh-pages branch of their git repo, the get the side
effect that they can use Github as a preview of the site before publishing
to Apache infra.

Works very well and is very low maintenance burden.  It is also simple
enough to be completely predictable.



On Thu, Jan 8, 2015 at 12:43 AM, Benedikt Ritter <britter@apache.org> wrote:

> 2015-01-08 9:26 GMT+01:00 Sergio Fernández <wikier@apache.org>:
>
> > Hi Benedikt,
> >
> > what's the different between the workflow you're suggesting and using the
> > doxia-module-markdown module for building the site with Maven?
> >
>
> Probably there's no difference. I was just unaware of the
> doxia-module-markdown. Damn, every time I thing I have a good idea,
> somebody else has implemented it already ;-)
>
> Thanks!
> Benedikt
>
>
> >
> > In Marmotta we use that, but we're open to fresh ideas in case we could
> > address some minor issues (page titles, variables replacement, etc) we
> > currently have.
> >
> > Cheers,
> >
> >
> > On 08/01/15 09:20, Benedikt Ritter wrote:
> >
> >> I've been thinking about extending the maven site build so that it can
> >> create a markdown version of a projects site, which could then be
> >> committed
> >> to a gh-pages branch for git based projects. Would anybody be interested
> >> in
> >> joining such an endeavor?
> >>
> >> Benedikt
> >>
> >> 2015-01-07 21:36 GMT+01:00 Ross Gardler (MS OPEN TECH) <
> >> Ross.Gardler@microsoft.com>:
> >>
> >>  The answer to your question is different depending on what xyz is in
> >>> http://xyz.apache.org
> >>>
> >>> Probably the most common answer is
> http://www.apache.org/dev/cmsref.html
> >>>
> >>> Microsoft Open Technologies, Inc.
> >>> A subsidiary of Microsoft Corporation
> >>>
> >>> -----Original Message-----
> >>> From: jay vyas [mailto:jayunit100.apache@gmail.com]
> >>> Sent: Wednesday, January 7, 2015 12:30 PM
> >>> To: dev@community.apache.org
> >>> Subject: Re: WELCOME to dev@community.apache.org
> >>>
> >>> thanks daniel...
> >>>
> >>>   here at bigtop we are 100% git based.  so having an svn account ,
> just
> >>> to
> >>> push changes to a site, seems to slow us down alot.
> >>>
> >>> is SVN required  ? or is there another way?
> >>>
> >>> right now we have a system that uses maven, followed by svn and then we
> >>> have to approve the changes in the web ui.
> >>>
> >>> would rather just push static html pages to our git repo , the way we
> >>> push
> >>> everything else.
> >>>
> >>> are all apache projects using SVN or do some folks have an easier
> >>> workflow
> >>> ?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Jan 7, 2015 at 3:12 PM, Daniel Gruno <humbedooh@apache.org>
> >>> wrote:
> >>>
> >>>  Essentially, github uses the same method as we do with svnpubsub.
> >>>> Files are pushed to a repository and then from there pushed directly
> >>>> to the web site.
> >>>>
> >>>> Is there anything specific about the github model that you think
> >>>> differ from how we do things?
> >>>> Apart from it being git and not subversion, obviously.
> >>>>
> >>>> With regards,
> >>>> Daniel.
> >>>>
> >>>> On 2015-01-07 21:06, jay vyas wrote:
> >>>>
> >>>>  Hi apache !
> >>>>>
> >>>>> Whats the simplest way to maintain the xyz.apache.org site?  Right
> >>>>> now we push to SVN, but would be great to use something like the
> >>>>> github.io model, where the static pages are just hosted directly.
> >>>>>
> >>>>>
> >>>>> On Wed, Jan 7, 2015 at 2:56 PM, <dev-help@community.apache.org>
> wrote:
> >>>>>
> >>>>>   Hi! This is the ezmlm program. I'm managing the
> >>>>>
> >>>>>> dev@community.apache.org mailing list.
> >>>>>>
> >>>>>> I'm working for my owner, who can be reached at
> >>>>>> dev-owner@community.apache.org.
> >>>>>>
> >>>>>> Acknowledgment: I have added the address
> >>>>>>
> >>>>>>      jayunit100.apache@gmail.com
> >>>>>>
> >>>>>> to the dev mailing list.
> >>>>>>
> >>>>>> Welcome to dev@community.apache.org!
> >>>>>>
> >>>>>> Please save this message so that you know the address you are
> >>>>>> subscribed under, in case you later want to unsubscribe or change
> >>>>>> your subscription address.
> >>>>>>
> >>>>>>
> >>>>>> --- Administrative commands for the dev list ---
> >>>>>>
> >>>>>> I can handle administrative requests automatically. Please do
not
> >>>>>> send them to the list address! Instead, send your message to
the
> >>>>>> correct command address:
> >>>>>>
> >>>>>> To subscribe to the list, send a message to:
> >>>>>>      <dev-subscribe@community.apache.org>
> >>>>>>
> >>>>>> To remove your address from the list, send a message to:
> >>>>>>      <dev-unsubscribe@community.apache.org>
> >>>>>>
> >>>>>> Send mail to the following for info and FAQ for this list:
> >>>>>>      <dev-info@community.apache.org>
> >>>>>>      <dev-faq@community.apache.org>
> >>>>>>
> >>>>>> Similar addresses exist for the digest list:
> >>>>>>      <dev-digest-subscribe@community.apache.org>
> >>>>>>      <dev-digest-unsubscribe@community.apache.org>
> >>>>>>
> >>>>>> To get messages 123 through 145 (a maximum of 100 per request),
> mail:
> >>>>>>      <dev-get.123_145@community.apache.org>
> >>>>>>
> >>>>>> To get an index with subject and author for messages 123-456
, mail:
> >>>>>>      <dev-index.123_456@community.apache.org>
> >>>>>>
> >>>>>> They are always returned as sets of 100, max 2000 per request,
so
> >>>>>> you'll actually get 100-499.
> >>>>>>
> >>>>>> To receive all messages with the same subject as message 12345,
send
> >>>>>> a short message to:
> >>>>>>      <dev-thread.12345@community.apache.org>
> >>>>>>
> >>>>>> The messages should contain one line or word of text to avoid
being
> >>>>>> treated as sp@m, but I will ignore their content.
> >>>>>> Only the ADDRESS you send to is important.
> >>>>>>
> >>>>>> You can start a subscription for an alternate address, for example
> >>>>>> "john@host.domain", just add a hyphen and your address (with
'='
> >>>>>> instead of '@') after the command word:
> >>>>>> <dev-subscribe-john=host.domain@community.apache.org>
> >>>>>>
> >>>>>> To stop subscription for this address, mail:
> >>>>>> <dev-unsubscribe-john=host.domain@community.apache.org>
> >>>>>>
> >>>>>> In both cases, I'll send a confirmation message to that address.
> >>>>>> When you receive it, simply reply to it to complete your
> subscription.
> >>>>>>
> >>>>>> If despite following these instructions, you do not get the
desired
> >>>>>> results, please contact my owner at dev-owner@community.apache.org.
> >>>>>> Please be patient, my owner is a lot slower than I am ;-)
> >>>>>>
> >>>>>> --- Enclosed is a copy of the request I received.
> >>>>>>
> >>>>>> Return-Path: <jayunit100.apache@gmail.com>
> >>>>>> Received: (qmail 14748 invoked by uid 99); 7 Jan 2015 19:56:45
-0000
> >>>>>> Received: from athena.apache.org (HELO athena.apache.org)
> >>>>>> (140.211.11.136)
> >>>>>>       by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2015
> >>>>>> 19:56:45
> >>>>>> +0000
> >>>>>> X-ASF-Spam-Status: No, hits=1.5 required=5.0
> >>>>>>           tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
> >>>>>> X-Spam-Check-By: apache.org
> >>>>>> Received-SPF: pass (athena.apache.org: domain of
> >>>>>> jayunit100.apache@gmail.com designates 74.125.82.171 as permitted
> >>>>>> sender)
> >>>>>> Received: from [74.125.82.171] (HELO mail-we0-f171.google.com)
> >>>>>> (74.125.82.171)
> >>>>>>       by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2015
> >>>>>> 19:56:39
> >>>>>> +0000
> >>>>>> Received: by mail-we0-f171.google.com with SMTP id
> u56so1794125wes.30
> >>>>>>           for
> >>>>>> <dev-sc.1420660420.dnaojabgibffbmnboifj-jayunit100.apache=
> >>>>>> gmail.com@community.apache.org>; Wed, 07 Jan 2015 11:56:18
-0800
> >>>>>> (PST)
> >>>>>> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> >>>>>>           d=gmail.com; s=20120113;
> >>>>>>
> >>>>>>
> h=mime-version:in-reply-to:references:date:message-id:subject:from:to
> >>>>>>            :content-type;
> >>>>>>           bh=4OB4KLyw2fmFpQl3M1XmOX18z5O8zy+yvZghLrCCQH0=;
> >>>>>>
> >>>>>> b=XSc/5mc3l7ZxTLvKQwhwblcJ9JBklYotsWNQjg2deDzdYhR4p1icsaTjQrklu+hpk2
> >>>>>>
> >>>>>>
> >>>>>> W0Y80Uk/PcDTvjO5JSDU0IxtUsSrjV5QK6KU2H9w7H39EytqRv/lFn7QL1Yw4UYib6zo
> >>>>>>
> >>>>>>
> >>>>>> 0hNaCgxt84skf1IQm7yRWP5pxIaQuDyI1r2W8WL5Bt6d34ps80thba1ILoPz/b1htNVT
> >>>>>>
> >>>>>>
> >>>>>> huI4b35Fqf2Q8mf2rKWYL1ppgyelNXheWOwWfqerEILddc3En+r2PKqzTY6Jh5R8aoVn
> >>>>>>
> >>>>>>    BwI0pN6WhAjm59qb7WZ0vb4Aorj3G2pMIOSn4R75jTvmFRY3DlSd8q582L+
> >>>>>> JFWGC5tWd
> >>>>>>            KASw==
> >>>>>> MIME-Version: 1.0
> >>>>>> X-Received: by 10.194.88.131 with SMTP id bg3mr9420545wjb.99.
> >>>>>> 1420660578606;
> >>>>>>    Wed, 07 Jan 2015 11:56:18 -0800 (PST)
> >>>>>> Received: by 10.27.144.214 with HTTP; Wed, 7 Jan 2015 11:56:18
-0800
> >>>>>> (PST)
> >>>>>> In-Reply-To: <1420660420.2944.ezmlm@community.apache.org>
> >>>>>> References: <1420660420.2944.ezmlm@community.apache.org>
> >>>>>> Date: Wed, 7 Jan 2015 14:56:18 -0500
> >>>>>> Message-ID: <CACVCA=fV3HDyzkHn=
> >>>>>> TEhWKOSmky2vXTyiCAcstnHq4n+eerWzw@mail.gmail.com>
> >>>>>> Subject: Re: confirm subscribe to dev@community.apache.org
> >>>>>> From: jay vyas <jayunit100.apache@gmail.com>
> >>>>>> To: dev-sc.1420660420.dnaojabgibffbmnboifj-jayunit100.apache=
> >>>>>> gmail.com@community.apache.org
> >>>>>> Content-Type: multipart/alternative; boundary=
> >>>>>> 089e010d849e226317050c15515d
> >>>>>> X-Virus-Checked: Checked by ClamAV on apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>> --
> >>> jay vyas
> >>>
> >>>
> >>
> >>
> >>
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 660 2747 925
> > e: sergio.fernandez@redlink.co
> > w: http://redlink.co
> >
>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>

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