On 08.01.2015 19:01, jan i wrote:
> On 8 January 2015 at 18:51, Branko Čibej wrote:
>
>> In cases like this I'd strongly recommend that you ask Infra to set up a
>> small VM for you to build and host the Javadocs on, and link to that
>> from your web site (or proxy it; the VM itself doesn't have t
On Thu, Jan 8, 2015 at 3:29 AM, Bertrand Delacretaz
wrote:
> Hi,
>
> On Thu, Jan 8, 2015 at 10:14 AM, Ted Dunning
> wrote:
> > ...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 th
On 8 January 2015 at 18:51, Branko Čibej wrote:
> On 08.01.2015 17:12, Robert Metzger wrote:
> > Hi Brane,
> > See answer inline:
> >
> > On Thu, Jan 8, 2015 at 4:29 PM, Branko Čibej wrote:
> >
> >> On 08.01.2015 09:55, Robert Metzger wrote:
> >>> Hi,
> >>>
> If there is sufficient demand,
On 08.01.2015 17:12, Robert Metzger wrote:
> Hi Brane,
> See answer inline:
>
> On Thu, Jan 8, 2015 at 4:29 PM, Branko Čibej wrote:
>
>> On 08.01.2015 09:55, Robert Metzger wrote:
>>> Hi,
>>>
If there is sufficient demand, however, that could change - the code
>> that
>>> would make this poss
Hi Ross,
I have been teaching open source in many universities and schools in south
Asia before I came to US. I'm happy to help .
Cheers
Kanchana
On Wed, Jan 7, 2015 at 2:22 PM, Christopher wrote:
> On Wed, Jan 7, 2015 at 4:59 PM, Ross Gardler (MS OPEN TECH) <
> ross.gard...@microsoft.com> wro
On Thu, Jan 8, 2015 at 11:24 AM, Roman Shaposhnik
wrote:
> On Wed, Jan 7, 2015 at 12:42 PM, Daniel Gruno
> wrote:
> > The main reason we do not support git in this workflow is that git does
> not
> > enable single-file checkouts, and that we haven't properly tested
> gitwcsub
> > (a git version
On Wed, Jan 7, 2015 at 12:42 PM, Daniel Gruno wrote:
> The main reason we do not support git in this workflow is that git does not
> enable single-file checkouts, and that we haven't properly tested gitwcsub
> (a git version of svnwcsub which is the frontend for svnpubsub) for web
> sites yet. If
Hi Brane,
See answer inline:
On Thu, Jan 8, 2015 at 4:29 PM, Branko Čibej wrote:
> On 08.01.2015 09:55, Robert Metzger wrote:
> > Hi,
> >
> >> If there is sufficient demand, however, that could change - the code
> that
> > would make this possible does exist.
> >
> > I would like to express dema
Thanks for the feedback !
How about, then this solution : A cron job which copies all files from
site/ in xyz apache project, into /content, every day, and does a svn
commit.
1) We can try this for one of our projects (maybe i can propose it bigtop)
... and if it works Maybe even donate/broaden i
On Thu, Jan 8, 2015 at 10:24 AM, jay vyas wrote:
> IS the ASF okay with simply doing a one time commit to SVN, of a single
> HTML page which forwards to gh-pages?
>
I am pretty sure there is a brand requirement that the project's web
site is at $foo.a.o -
http://www.apache.org/foundation/marks/pm
On Thu, Jan 8, 2015 at 4:24 PM, jay vyas wrote:
> ...IS the ASF okay with simply doing a one time commit to SVN, of a single
> HTML page which forwards to gh-pages?..
You mean redirect to github which has the actual content?
That's not ok IMO, like our source code our websites have to be hosted
On 08.01.2015 09:55, Robert Metzger wrote:
> Hi,
>
>> If there is sufficient demand, however, that could change - the code that
> would make this possible does exist.
>
> I would like to express demand from the Flink project. svn is a pain to use
> (since we host javadocs and our documentation on o
IS the ASF okay with simply doing a one time commit to SVN, of a single
HTML page which forwards to gh-pages?
On Thu, Jan 8, 2015 at 9:19 AM, David Nalley wrote:
> On Thu, Jan 8, 2015 at 3:55 AM, Robert Metzger
> wrote:
> > Hi,
> >
> >> If there is sufficient demand, however, that could change
On Thu, Jan 8, 2015 at 3:55 AM, Robert Metzger wrote:
> Hi,
>
>> If there is sufficient demand, however, that could change - the code that
> would make this possible does exist.
>
> I would like to express demand from the Flink project. svn is a pain to use
> (since we host javadocs and our docume
Perhaps a better mechanism for things like javadocs, would be to support
some javadoc viewer which serves javadocs directly from javadoc jars? That
way, you just upload the jars you build with maven or ant, which are
already compressed. That should work well enough with svn or the CMS
external buil
But that then provides the ability to create a larger eco-system
of binary providers.
> On Jan 6, 2015, at 3:45 PM, Nicolas Lalevée
> wrote:
>
> I would add something about the build of the sources. Because having sources
> without having a repeatable build or having no clue about how to build
Hi,
On Thu, Jan 8, 2015 at 10:14 AM, Ted Dunning wrote:
> ...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...
Do you have URLs that show how
I think there is a performance difference between git and svn because with
git, you are syncing repositories, not files. Git is usually compressing
the repository before sending it over the network.
I did a little test with our website directory and pushed it to github:
git add : 7 seconds (17k fi
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 Gi
On 2015-01-08 09:55, Robert Metzger wrote:
Hi,
If there is sufficient demand, however, that could change - the code that
would make this possible does exist.
I would like to express demand from the Flink project. svn is a pain to use
(since we host javadocs and our documentation on our websi
Hi,
> If there is sufficient demand, however, that could change - the code that
would make this possible does exist.
I would like to express demand from the Flink project. svn is a pain to use
(since we host javadocs and our documentation on our website, the upload
usually runs for 6+ hours. Prob
2015-01-08 9:26 GMT+01:00 Sergio Fernández :
> 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
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?
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
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
24 matches
Mail list logo
