Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
On 09.01.2015 15:43, Branko Čibej wrote: > On 09.01.2015 14:04, Ulrich Stärk wrote: >> If I'm not mistaken, SVN does the same (combine and compress all changes >> prior to sending it over >> the wire). > Not entirely; it sends deltas and will compress new files IF the server > has mod_deflate configured (but they usually don't because there was a > huge memory leak there for the longest time), but doesn't combine them. > It can't, since it doesn't have the repository available locally. > Subversion working copy state can differ substantially from repository > state, yet the commit can still succeed; this is not the case with Git. > > On 2015-01-08 10:28, Robert Metzger wrote: >>> 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 files) >>> git repo size: 58 MB (du -sh in ".git" dir) >>> git push to github : 35 seconds (using the same internet connection as with >>> the svn) > In this case, Subversion will generate a PUT request for each file, > whereas Git will, IIRC, send a single file across the wire. The problem > here is that Subversion does not (yet) pipeline PUTs, so the difference > you're seeing is the request latency. > > We've been talking about pipelining PUTs for ages ... but no-one is > currently working on that, so ... we need more incentive! :) FWIW, such commits should be a lot faster via svn:// than via http://. But we can't use svn:// at all at the ASF because the repo replication method we currently use only supports http://. -- Brane
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
On 09.01.2015 14:04, Ulrich Stärk wrote: > If I'm not mistaken, SVN does the same (combine and compress all changes > prior to sending it over > the wire). Not entirely; it sends deltas and will compress new files IF the server has mod_deflate configured (but they usually don't because there was a huge memory leak there for the longest time), but doesn't combine them. It can't, since it doesn't have the repository available locally. Subversion working copy state can differ substantially from repository state, yet the commit can still succeed; this is not the case with Git. On 2015-01-08 10:28, Robert Metzger wrote: >> 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 files) >> git repo size: 58 MB (du -sh in ".git" dir) >> git push to github : 35 seconds (using the same internet connection as with >> the svn) In this case, Subversion will generate a PUT request for each file, whereas Git will, IIRC, send a single file across the wire. The problem here is that Subversion does not (yet) pipeline PUTs, so the difference you're seeing is the request latency. We've been talking about pipelining PUTs for ages ... but no-one is currently working on that, so ... we need more incentive! :) -- Brane
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
If I'm not mistaken, SVN does the same (combine and compress all changes prior to sending it over the wire). Uli On 2015-01-08 10:28, Robert Metzger wrote: > 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 files) > git repo size: 58 MB (du -sh in ".git" dir) > git push to github : 35 seconds (using the same internet connection as with > the svn) > > I think we can achieve the same performance at apache using git for the > websites. > > I agree with you that I should probably take a closer look into the CMS > external build feature. Using svn or git for 17k files is certainly wrong. > In particular because we add generated files (javadocs, documentation) to > the VCS which doesn't have any value. > > I'll get in touch with Infra on a separate thread to resolve our website > issues. > > > > On Thu, Jan 8, 2015 at 10:01 AM, Daniel Gruno wrote: > >> >> 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 website, the upload >>> usually runs for 6+ hours. Probably because its so many files). >>> >> How is that in any way related to svn? svn or git, if you have that many >> files, it's going to take ages to upload regardless of which repository >> system you use. >> >> If it makes it easier, you might peruse http://www.apache.org/dev/ >> cmsref.html#external-build and see if you can't use an external build job >> for you site - that way, you just commit the changes to your template/raw >> docs, and the CMS system builds the javadoc for you. >> >> >> >>> Almost all incoming incubator projects are using git nowadays. Many of >>> them >>> use GitHub and the "gh-pages" hosting feature. I guess a lot of them would >>> appreciate a similar feature from the ASF infra. >>> >>> >>> >>> On Wed, Jan 7, 2015 at 9:42 PM, Daniel Gruno >>> wrote: >>> >>> Hi Jay, It sounds like you have the CMS setup that is quite common in the ASF. If you would rather have straight-up svnpubsub, you can ask for it. That way, whatever static content you push to svn will instantly be shown on your web site without having to publish through the UI first. 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 there is sufficient demand, however, that could change - the code that would make this possible does exist. With regards, Daniel. On 2015-01-07 21:29, jay vyas wrote: 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 > 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, >>> 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-ow...@community.apache.org. Acknowledgment: I have added the address jayunit100.apa...@gmail.com to the dev mailing list. Welcome to dev@co
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 to be >> visible to the 'net). The javadocs should be easily rebuildable from >> release bits and don't require version control, just VM backups. >> > With just a minimal extra effort this could be available to all our java > projects, please bear that in mind if following this route. +1 and not limited to Java since there are other systems for generating documentation from code (q.v. pydoc and Doxygen, for example). -- Brane
Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))
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 that pubsub carries it to the right places... > > Do you have URLs that show how that works? DeviceMap might be interested. > > https://github.com/apache/drill/tree/gh-pages See the README Also http://jekyllrb.com/
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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, 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. Probably because its so many files). > >> I'd be interested in seeing what kind of commit takes 6 hours, and from > >> where. Shouldn't take that long. > >> > > I think this one > > http://svn.apache.org/viewvc?view=revision&revision=r1630951 or this one > > http://svn.apache.org/viewvc?view=revision&revision=r1627056 took so > long. > > We committed from Berlin, Germany with a 100 MBit down, 12 MBit up > > connection. > > I'm frankly horrified that you push build artifacts into the repository > like this ... only because the cms system appears to require it. It's > irrelevant whether this is Git or Subversion: it's a waste of space and > time. This looks like a case of using the wrong tool for the job. > > 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 to be > visible to the 'net). The javadocs should be easily rebuildable from > release bits and don't require version control, just VM backups. > With just a minimal extra effort this could be available to all our java projects, please bear that in mind if following this route. rgds jan i. > > -- Brane >
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 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. Probably because its so many files). >> I'd be interested in seeing what kind of commit takes 6 hours, and from >> where. Shouldn't take that long. >> > I think this one > http://svn.apache.org/viewvc?view=revision&revision=r1630951 or this one > http://svn.apache.org/viewvc?view=revision&revision=r1627056 took so long. > We committed from Berlin, Germany with a 100 MBit down, 12 MBit up > connection. I'm frankly horrified that you push build artifacts into the repository like this ... only because the cms system appears to require it. It's irrelevant whether this is Git or Subversion: it's a waste of space and time. This looks like a case of using the wrong tool for the job. 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 to be visible to the 'net). The javadocs should be easily rebuildable from release bits and don't require version control, just VM backups. -- Brane
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 of svnwcsub which is the frontend for svnpubsub) for web > > sites yet. If there is sufficient demand, however, that could change - > the > > code that would make this possible does exist. > > FWIW: I see quite a bit of demand for that on the poddling side. Every > single > poddling I've onboarded in the last year opted out for Git and had to > 'grok' > why is there a bit of SVN thingy sticking out as a sore thumb in otherwise > 100% Git workflow they've picked. > > Thanks, > Roman. > Don't they also have to use SVN for pushing releases to the dists/mirrors? How do those newly onboarded projects view that? Do they understand that more, because it's less often updated than the site?
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 there is sufficient demand, however, that could change - the > code that would make this possible does exist. FWIW: I see quite a bit of demand for that on the poddling side. Every single poddling I've onboarded in the last year opted out for Git and had to 'grok' why is there a bit of SVN thingy sticking out as a sore thumb in otherwise 100% Git workflow they've picked. Thanks, Roman.
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 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. Probably because its so many files). > > I'd be interested in seeing what kind of commit takes 6 hours, and from > where. Shouldn't take that long. > I think this one http://svn.apache.org/viewvc?view=revision&revision=r1630951 or this one http://svn.apache.org/viewvc?view=revision&revision=r1627056 took so long. We committed from Berlin, Germany with a 100 MBit down, 12 MBit up connection.
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 it to be offered as a generic service in the ASF ? 2) This would allow any ASF project to publish via SVN by simply pushing to their git repo, without requiring a change to the underlying SVN infrastructure. - Is the git->svn daily cron a sensible approach ? - Has anyone tried this or setup infra to do it that we can copy? On Thu, Jan 8, 2015 at 9:31 AM, David Nalley wrote: > 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/pmcs.html#websites > > This would, to my mind, seem to eliminate folks from redirecting. > > --David > -- jay vyas
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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/pmcs.html#websites This would, to my mind, seem to eliminate folks from redirecting. --David
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 the ASF network. -Bertrand
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 our website, the upload > usually runs for 6+ hours. Probably because its so many files). I'd be interested in seeing what kind of commit takes 6 hours, and from where. Shouldn't take that long. FWIW, nothing's stopping you from hosting javadocs from the VM that they're built on and just having a link to that on your site. That's what we do at Subversion, where we have a static web site (using SSI and svnpubsub), and it avoids a large part of the asf-cms suction. > Almost all incoming incubator projects are using git nowadays. "Git's major contribution to software development is the resurrection of the world's second-worst scripting language." :) -- Brane
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 - 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. Probably because its so many files). > > > > Almost all incoming incubator projects are using git nowadays. Many of > them > > use GitHub and the "gh-pages" hosting feature. I guess a lot of them > would > > appreciate a similar feature from the ASF infra. > > > > > > The svn infrastructure we have now just works, and from the standpoint > of having to manage ~200 websites, it's relatively simple. > Replicating that functionality with Git is possible, but adds > relatively little in terms of functionality. With the projects on > folks plates right now, the contractors at least, won't have time to > begin looking at this for at least 18 months. Volunteers could of > course tackle this if wanted. > > --David > -- jay vyas
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 documentation on our website, the upload > usually runs for 6+ hours. Probably because its so many files). > > Almost all incoming incubator projects are using git nowadays. Many of them > use GitHub and the "gh-pages" hosting feature. I guess a lot of them would > appreciate a similar feature from the ASF infra. > > The svn infrastructure we have now just works, and from the standpoint of having to manage ~200 websites, it's relatively simple. Replicating that functionality with Git is possible, but adds relatively little in terms of functionality. With the projects on folks plates right now, the contractors at least, won't have time to begin looking at this for at least 18 months. Volunteers could of course tackle this if wanted. --David
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 build feature. (And would also have the added benefit of only needing to update the viewer when there's a javadoc security vulnerability, rather than require every project to patch their javadocs, as I seem to remember was recently the case.) -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Thu, Jan 8, 2015 at 4:28 AM, Robert Metzger wrote: > 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 files) > git repo size: 58 MB (du -sh in ".git" dir) > git push to github : 35 seconds (using the same internet connection as with > the svn) > > I think we can achieve the same performance at apache using git for the > websites. > > I agree with you that I should probably take a closer look into the CMS > external build feature. Using svn or git for 17k files is certainly wrong. > In particular because we add generated files (javadocs, documentation) to > the VCS which doesn't have any value. > > I'll get in touch with Infra on a separate thread to resolve our website > issues. > > > > On Thu, Jan 8, 2015 at 10:01 AM, Daniel Gruno > wrote: > > > > > 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 website, the upload > >> usually runs for 6+ hours. Probably because its so many files). > >> > > How is that in any way related to svn? svn or git, if you have that many > > files, it's going to take ages to upload regardless of which repository > > system you use. > > > > If it makes it easier, you might peruse http://www.apache.org/dev/ > > cmsref.html#external-build and see if you can't use an external build job > > for you site - that way, you just commit the changes to your template/raw > > docs, and the CMS system builds the javadoc for you. > > > > > > > >> Almost all incoming incubator projects are using git nowadays. Many of > >> them > >> use GitHub and the "gh-pages" hosting feature. I guess a lot of them > would > >> appreciate a similar feature from the ASF infra. > >> > >> > >> > >> On Wed, Jan 7, 2015 at 9:42 PM, Daniel Gruno > >> wrote: > >> > >> Hi Jay, > >>> It sounds like you have the CMS setup that is quite common in the ASF. > >>> If you would rather have straight-up svnpubsub, you can ask for it. > That > >>> way, whatever static content you push to svn will instantly be shown on > >>> your web site without having to publish through the UI first. > >>> > >>> 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 there is sufficient demand, however, that could > >>> change - the code that would make this possible does exist. > >>> > >>> With regards, > >>> Daniel. > >>> > >>> > >>> On 2015-01-07 21:29, jay vyas wrote: > >>> > >>> 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 > 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 grea
Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))
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 that works? DeviceMap might be interested. -Bertrand
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 files) git repo size: 58 MB (du -sh in ".git" dir) git push to github : 35 seconds (using the same internet connection as with the svn) I think we can achieve the same performance at apache using git for the websites. I agree with you that I should probably take a closer look into the CMS external build feature. Using svn or git for 17k files is certainly wrong. In particular because we add generated files (javadocs, documentation) to the VCS which doesn't have any value. I'll get in touch with Infra on a separate thread to resolve our website issues. On Thu, Jan 8, 2015 at 10:01 AM, Daniel Gruno wrote: > > 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 website, the upload >> usually runs for 6+ hours. Probably because its so many files). >> > How is that in any way related to svn? svn or git, if you have that many > files, it's going to take ages to upload regardless of which repository > system you use. > > If it makes it easier, you might peruse http://www.apache.org/dev/ > cmsref.html#external-build and see if you can't use an external build job > for you site - that way, you just commit the changes to your template/raw > docs, and the CMS system builds the javadoc for you. > > > >> Almost all incoming incubator projects are using git nowadays. Many of >> them >> use GitHub and the "gh-pages" hosting feature. I guess a lot of them would >> appreciate a similar feature from the ASF infra. >> >> >> >> On Wed, Jan 7, 2015 at 9:42 PM, Daniel Gruno >> wrote: >> >> Hi Jay, >>> It sounds like you have the CMS setup that is quite common in the ASF. >>> If you would rather have straight-up svnpubsub, you can ask for it. That >>> way, whatever static content you push to svn will instantly be shown on >>> your web site without having to publish through the UI first. >>> >>> 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 there is sufficient demand, however, that could >>> change - the code that would make this possible does exist. >>> >>> With regards, >>> Daniel. >>> >>> >>> On 2015-01-07 21:29, jay vyas wrote: >>> >>> 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 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, >> 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-ow...@community.apache.org. >>> >>> Acknowledgment: I have added the address >>> >>> jayunit100.apa...@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 administrativ
Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))
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 wrote: > 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 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.gard...@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.apa...@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 > >>> 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, > 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-ow...@community.apache.org. > >> > >> Acknowledgment: I have added the address > >> > >> jayunit100.apa...@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: > >> > >> > >> To remove your address from the list, send a message to: > >> > >> > >> Send mail to the following for info and FAQ for this list: > >> > >> > >> > >> Similar addresses exist for the digest list: > >> > >> > >> > >> To get messages 123 through 145 (a maximum of 100 per request), > mail: > >> > >> > >> To get an index with
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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 website, the upload usually runs for 6+ hours. Probably because its so many files). How is that in any way related to svn? svn or git, if you have that many files, it's going to take ages to upload regardless of which repository system you use. If it makes it easier, you might peruse http://www.apache.org/dev/cmsref.html#external-build and see if you can't use an external build job for you site - that way, you just commit the changes to your template/raw docs, and the CMS system builds the javadoc for you. Almost all incoming incubator projects are using git nowadays. Many of them use GitHub and the "gh-pages" hosting feature. I guess a lot of them would appreciate a similar feature from the ASF infra. On Wed, Jan 7, 2015 at 9:42 PM, Daniel Gruno wrote: Hi Jay, It sounds like you have the CMS setup that is quite common in the ASF. If you would rather have straight-up svnpubsub, you can ask for it. That way, whatever static content you push to svn will instantly be shown on your web site without having to publish through the UI first. 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 there is sufficient demand, however, that could change - the code that would make this possible does exist. With regards, Daniel. On 2015-01-07 21:29, jay vyas wrote: 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 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, 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-ow...@community.apache.org. Acknowledgment: I have added the address jayunit100.apa...@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: To remove your address from the list, send a message to: Send mail to the following for info and FAQ for this list: Similar addresses exist for the digest list: To get messages 123 through 145 (a maximum of 100 per request), mail: To get an index with subject and author for messages 123-456 , mail: 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: 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: To stop subscription for this address, mail: 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-ow...@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: Recei
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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. Probably because its so many files). Almost all incoming incubator projects are using git nowadays. Many of them use GitHub and the "gh-pages" hosting feature. I guess a lot of them would appreciate a similar feature from the ASF infra. On Wed, Jan 7, 2015 at 9:42 PM, Daniel Gruno wrote: > Hi Jay, > It sounds like you have the CMS setup that is quite common in the ASF. > If you would rather have straight-up svnpubsub, you can ask for it. That > way, whatever static content you push to svn will instantly be shown on > your web site without having to publish through the UI first. > > 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 there is sufficient demand, however, that could > change - the code that would make this possible does exist. > > With regards, > Daniel. > > > On 2015-01-07 21:29, jay vyas wrote: > >> 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 >> 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, 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-ow...@community.apache.org. > > Acknowledgment: I have added the address > > jayunit100.apa...@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: > > > To remove your address from the list, send a message to: > > > Send mail to the following for info and FAQ for this list: > > > > Similar addresses exist for the digest list: > > > > To get messages 123 through 145 (a maximum of 100 per request), mail: > > > To get an index with subject and author for messages 123-456 , mail: > > > 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: > > > 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: > > > To stop subscription for this address, mail: > > > 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-ow...@community.apache.org. Please be patient, my owner is a > l
Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))
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 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.gard...@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.apa...@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 >>> 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, 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-ow...@community.apache.org. >> >> Acknowledgment: I have added the address >> >> jayunit100.apa...@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: >> >> >> To remove your address from the list, send a message to: >> >> >> Send mail to the following for info and FAQ for this list: >> >> >> >> Similar addresses exist for the digest list: >> >> >> >> To get messages 123 through 145 (a maximum of 100 per request), mail: >> >> >> To get an index with subject and author for messages 123-456 , mail: >> >> >> 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: >> >> >> 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: >> >> >> To stop subscription for this address, mail: >> >> >> In both cases, I'll send a confirmation message t
Re: GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.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? 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.gard...@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.apa...@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 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, 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-ow...@community.apache.org. Acknowledgment: I have added the address jayunit100.apa...@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: To remove your address from the list, send a message to: Send mail to the following for info and FAQ for this list: Similar addresses exist for the digest list: To get messages 123 through 145 (a maximum of 100 per request), mail: To get an index with subject and author for messages 123-456 , mail: 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: 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: To stop subscription for this address, mail: 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-ow...@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: Received: (qmail 14748 invoked by uid 99); 7 Jan 2015 19:56:45 - 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 + 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.apa...@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 + Rec
GitHub pages for git based Apache projects (Was: Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org))
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.gard...@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.apa...@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 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, 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-ow...@community.apache.org. > >>> > >>> Acknowledgment: I have added the address > >>> > >>> jayunit100.apa...@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: > >>> > >>> > >>> To remove your address from the list, send a message to: > >>> > >>> > >>> Send mail to the following for info and FAQ for this list: > >>> > >>> > >>> > >>> Similar addresses exist for the digest list: > >>> > >>> > >>> > >>> To get messages 123 through 145 (a maximum of 100 per request), mail: > >>> > >>> > >>> To get an index with subject and author for messages 123-456 , mail: > >>> > >>> > >>> 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: > >>> > >>> > >>> 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: > >>> > >>> > >>> To stop subscription for this address, mail: > >>> > >>> > >>> 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-ow...@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: > >>> Received: (qmail 14748 invoked by uid 99); 7 Jan 2015 19:56:45 - > >>> 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 > >>> + > >>> 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
Re: Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
Hi Jay, It sounds like you have the CMS setup that is quite common in the ASF. If you would rather have straight-up svnpubsub, you can ask for it. That way, whatever static content you push to svn will instantly be shown on your web site without having to publish through the UI first. 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 there is sufficient demand, however, that could change - the code that would make this possible does exist. With regards, Daniel. On 2015-01-07 21:29, jay vyas wrote: 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 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, 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-ow...@community.apache.org. Acknowledgment: I have added the address jayunit100.apa...@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: To remove your address from the list, send a message to: Send mail to the following for info and FAQ for this list: Similar addresses exist for the digest list: To get messages 123 through 145 (a maximum of 100 per request), mail: To get an index with subject and author for messages 123-456 , mail: 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: 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: To stop subscription for this address, mail: 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-ow...@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: Received: (qmail 14748 invoked by uid 99); 7 Jan 2015 19:56:45 - 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 + 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.apa...@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 + Received: by mail-we0-f171.google.com with SMTP id u56so1794125wes.30 for ; 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/PcDTvj
Managing zyz.apache.org (was RE: WELCOME to dev@community.apache.org)
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.apa...@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 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, 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-ow...@community.apache.org. >>> >>> Acknowledgment: I have added the address >>> >>> jayunit100.apa...@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: >>> >>> >>> To remove your address from the list, send a message to: >>> >>> >>> Send mail to the following for info and FAQ for this list: >>> >>> >>> >>> Similar addresses exist for the digest list: >>> >>> >>> >>> To get messages 123 through 145 (a maximum of 100 per request), mail: >>> >>> >>> To get an index with subject and author for messages 123-456 , mail: >>> >>> >>> 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: >>> >>> >>> 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: >>> >>> >>> To stop subscription for this address, mail: >>> >>> >>> 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-ow...@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: >>> Received: (qmail 14748 invoked by uid 99); 7 Jan 2015 19:56:45 - >>> 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 >>> + >>> 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.apa...@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 >>> + >>> Received: by mail-we0-f171.google.com with SMTP id u56so1794125wes.30 >>> for >>> >> gmail@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-
