You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commonsrdf.apache.org by Lewis John Mcgibbney <le...@gmail.com> on 2015/03/11 21:31:26 UTC
[VOTE] CommonsRDF Website Format
Hi Folks,
Based on Geoffrey Core's request on INFRA-9260 [0], I would like to open an
VOTE for the website build layout. The VOTE will be open for at least 72
hours.
Options are
0 svnpubsub
1 CMS (default-Perl-build)
2 CMS (Maven-build)
3 CMS (Ant-build)
4 CMS (Shell-build)
[ ] +1 I VOTE for option ${insert option here}
[ ] +/-0 I don't care either way but would rather see ${insert option here}
[ ] -1 I hate them all and I am not having a good day
Thanks
Lewis
[0] https://issues.apache.org/jira/browse/INFRA-9260
--
*Lewis*
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
On Tue, Apr 21, 2015 at 12:57 PM, Stian Soiland-Reyes <st...@apache.org>
wrote:
> Great - I added some basic package-info.java files.
>
Cool!
> I had to massage the mycila license-plugin as the /* style license
> header in package-info.java was not recognized - it seems very picky -
> is ther any reason to keep both this and the rat plugin? (Raised as
> https://issues.apache.org/jira/browse/COMMONSRDF-18 )
>
Already fixed.
I tried to deploy using mvn site-deploy. I got these errors:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-scm-publish-plugin:1.1:publish-scm
> (scm-publish) on project commons-rdf-api: Failed to check-in files to
> SCM: The svn command failed. svn: E155011: Commit failed (details
> follow):
> [ERROR] svn: E155011: Directory
>
> '/home/stain/src/commons-rdf/api/target/site-content/apidocs/org/apache/commons/rdf/simple'
> is out of date
> [ERROR] svn: E170004: Item
>
> '/websites/production/commonsrdf/content/apidocs/org/apache/commons/rdf/simple'
> is out of date
>
Well, as I commented on COMMONSRDF-9, I have issues with that workflow, and
I had to manually commit the built site. Let's discuss the details there.
Cheers,
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: CommonsRDF Website Format
Posted by Stian Soiland-Reyes <st...@apache.org>.
Great - I added some basic package-info.java files.
I didn't do it as a pull request as these didn't exist/work - feel
free to tweak further!
I had to massage the mycila license-plugin as the /* style license
header in package-info.java was not recognized - it seems very picky -
is ther any reason to keep both this and the rat plugin? (Raised as
https://issues.apache.org/jira/browse/COMMONSRDF-18 )
I tried to deploy using mvn site-deploy. I got these errors:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:1.1:publish-scm
(scm-publish) on project commons-rdf-api: Failed to check-in files to
SCM: The svn command failed. svn: E155011: Commit failed (details
follow):
[ERROR] svn: E155011: Directory
'/home/stain/src/commons-rdf/api/target/site-content/apidocs/org/apache/commons/rdf/simple'
is out of date
[ERROR] svn: E170004: Item
'/websites/production/commonsrdf/content/apidocs/org/apache/commons/rdf/simple'
is out of date
.. probably because someone else deployed something somewhere while
the build was running?
(can't wait for that gitpub2pubsublub without svn..)
So I try again, getting:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:1.1:publish-scm
(scm-publish) on project commons-rdf-api: Failed to delete files from
SCM: The svn command failed. svn: E200005: Use --force to override
this restriction (local modifications may be lost)
[ERROR] svn: E200005:
'/home/stain/src/commons-rdf/api/target/site-content/source-repository.html.mine'
is not under version control
so it turns you have to do a few repeated runs of
mvn clean site-deploy
as random SVN files are spread about the file system.
This seems to work, except it deleted everything except the simple/
javadocs! Sorry!
-- is it because simple is the last module built?
I fixed this manually with svn co and cp from target/site
On 20 April 2015 at 18:45, Gary Gregory <ga...@gmail.com> wrote:
> OK, I can see the Javadocs. cool. Can someone add package-level Javdocs?
> That would help to get the difference between the API and whatever "simple"
> is supposed to be.
>
> Gary
>
> On Mon, Apr 20, 2015 at 10:27 AM, Sergio Fernández <wi...@apache.org>
> wrote:
>
>> Hi Gary,
>>
>> On Mon, Apr 20, 2015 at 5:05 PM, Gary Gregory <ga...@gmail.com>
>> wrote:
>>
>> > On Mon, Apr 20, 2015 at 1:47 AM, Sergio Fernández <wi...@apache.org>
>> > wrote:
>> >
>> > > Content online at: http://commonsrdf.incubator.apache.org/ :-)
>> > >
>> >
>> > Nice start for this site! :-)
>> >
>>
>> All the merits to infrastructure that the Commons project has put in place,
>> with a nice skin and many required things already configured in the parent.
>>
>> The first thing I wanted to do though is browse the Javadocs, which is not
>> > there.
>> >
>>
>> Also the first on my list, already added there.
>>
>>
>> > Please see any recent Apache Commons site and POM for what most Commons
>> > project sites looks like, in particular the project reports section which
>> > include Javdocs, for example:
>> > http://commons.apache.org/proper/commons-lang/project-reports.html
>>
>>
>> I'd need to take a look to those reports. Thanks for the pointer.
>>
>> For those who do not follow the Jira updates of COMMONSRDF-9, I'll try to
>> summarize here the latest work on the site: Basically working on that issue
>> I've realized that Commons project does not uses the CMS (see
>> https://commons.apache.org/site-publish.html for further details), but
>> they
>> use the site plugin to publish the site (using site-deploy to be more
>> precisely). So that means that the site could be moved to git, and that's
>> already done. It also means that INFRA-9260 is not required anymore. I also
>> included the SITE.md file with the most useful things to know to manage the
>> site. We still have some minor issues to solve, but all those minor details
>> be discussed on COMMONSRDF-9.
>>
>> Cheers,
>>
>> --
>> Sergio Fernández
>> Partner Technology Manager
>> Redlink GmbH
>> m: +43 6602747925
>> e: sergio.fernandez@redlink.co
>> w: http://redlink.co
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718
Re: CommonsRDF Website Format
Posted by Gary Gregory <ga...@gmail.com>.
OK, I can see the Javadocs. cool. Can someone add package-level Javdocs?
That would help to get the difference between the API and whatever "simple"
is supposed to be.
Gary
On Mon, Apr 20, 2015 at 10:27 AM, Sergio Fernández <wi...@apache.org>
wrote:
> Hi Gary,
>
> On Mon, Apr 20, 2015 at 5:05 PM, Gary Gregory <ga...@gmail.com>
> wrote:
>
> > On Mon, Apr 20, 2015 at 1:47 AM, Sergio Fernández <wi...@apache.org>
> > wrote:
> >
> > > Content online at: http://commonsrdf.incubator.apache.org/ :-)
> > >
> >
> > Nice start for this site! :-)
> >
>
> All the merits to infrastructure that the Commons project has put in place,
> with a nice skin and many required things already configured in the parent.
>
> The first thing I wanted to do though is browse the Javadocs, which is not
> > there.
> >
>
> Also the first on my list, already added there.
>
>
> > Please see any recent Apache Commons site and POM for what most Commons
> > project sites looks like, in particular the project reports section which
> > include Javdocs, for example:
> > http://commons.apache.org/proper/commons-lang/project-reports.html
>
>
> I'd need to take a look to those reports. Thanks for the pointer.
>
> For those who do not follow the Jira updates of COMMONSRDF-9, I'll try to
> summarize here the latest work on the site: Basically working on that issue
> I've realized that Commons project does not uses the CMS (see
> https://commons.apache.org/site-publish.html for further details), but
> they
> use the site plugin to publish the site (using site-deploy to be more
> precisely). So that means that the site could be moved to git, and that's
> already done. It also means that INFRA-9260 is not required anymore. I also
> included the SITE.md file with the most useful things to know to manage the
> site. We still have some minor issues to solve, but all those minor details
> be discussed on COMMONSRDF-9.
>
> Cheers,
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
Hi Gary,
On Mon, Apr 20, 2015 at 5:05 PM, Gary Gregory <ga...@gmail.com>
wrote:
> On Mon, Apr 20, 2015 at 1:47 AM, Sergio Fernández <wi...@apache.org>
> wrote:
>
> > Content online at: http://commonsrdf.incubator.apache.org/ :-)
> >
>
> Nice start for this site! :-)
>
All the merits to infrastructure that the Commons project has put in place,
with a nice skin and many required things already configured in the parent.
The first thing I wanted to do though is browse the Javadocs, which is not
> there.
>
Also the first on my list, already added there.
> Please see any recent Apache Commons site and POM for what most Commons
> project sites looks like, in particular the project reports section which
> include Javdocs, for example:
> http://commons.apache.org/proper/commons-lang/project-reports.html
I'd need to take a look to those reports. Thanks for the pointer.
For those who do not follow the Jira updates of COMMONSRDF-9, I'll try to
summarize here the latest work on the site: Basically working on that issue
I've realized that Commons project does not uses the CMS (see
https://commons.apache.org/site-publish.html for further details), but they
use the site plugin to publish the site (using site-deploy to be more
precisely). So that means that the site could be moved to git, and that's
already done. It also means that INFRA-9260 is not required anymore. I also
included the SITE.md file with the most useful things to know to manage the
site. We still have some minor issues to solve, but all those minor details
be discussed on COMMONSRDF-9.
Cheers,
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: CommonsRDF Website Format
Posted by Gary Gregory <ga...@gmail.com>.
On Mon, Apr 20, 2015 at 1:47 AM, Sergio Fernández <wi...@apache.org> wrote:
> Content online at: http://commonsrdf.incubator.apache.org/ :-)
>
Nice start for this site! :-)
The first thing I wanted to do though is browse the Javadocs, which is not
there.
Please see any recent Apache Commons site and POM for what most Commons
project sites looks like, in particular the project reports section which
include Javdocs, for example:
http://commons.apache.org/proper/commons-lang/project-reports.html
Thank you,
Gary
>
> CMS workflow is broken. build work on staging, but it does not work the
> copying. Talking with INFRA to get it solved. But at least there is an
> alternative workflow in case the release. I'll keep you posted.
>
>
>
>
>
> On Wed, Apr 8, 2015 at 8:47 AM, Sergio Fernández <wi...@apache.org>
> wrote:
>
> > Still dealing with some issues at INFRA-9260. I'll keep you posted when
> > the site is actually working.
> >
> > On Tue, Apr 7, 2015 at 8:08 PM, Sergio Fernández <wi...@apache.org>
> > wrote:
> >
> >> Cool! Thanks Andy for the bureaucracy.
> >> On Apr 7, 2015 7:00 PM, "Andy Seaborne" <an...@apache.org> wrote:
> >>
> >>> Now working thanks to infra.
> >>>
> >>> Andy
> >>>
> >>> On 07/04/15 14:56, Andy Seaborne wrote:
> >>>
> >>>> At the moment, it responds with a different 404 to a site that
> >>>> definitely does not exist.
> >>>>
> >>>> http://commonsrdf.incubator.apache.org/
> >>>> ("Server at commonsrdf.incubator.apache.org Port 80" line)
> >>>>
> >>>> cf
> >>>>
> >>>> http:/qwertyuiop.incubator.apache.org
> >>>> (no such line)
> >>>>
> >>>> /x1/www/commonsrdf.apache.org does not exist but other incubating
> sites
> >>>> seem to exists in that form.
> >>>>
> >>>> Infra/hipchat attempted.
> >>>>
> >>>> Andy
> >>>>
> >>>>
> >>>> On 01/04/15 10:36, Andy Seaborne wrote:
> >>>>
> >>>>> On 01/04/15 05:53, Sergio Fernández wrote:
> >>>>>
> >>>>>> I think after a week it's time to ping back infra about this, isn't
> >>>>>> it?
> >>>>>>
> >>>>>
> >>>>> Yes.
> >>>>>
> >>>>> From what I can tell it's not there (rather than a config problem
> >>>>> meaning / is returning 404)
> >>>>>
> >>>>> All the websites are at people:/x1/www/ (under their final name -
> e.g.
> >>>>> /x1/www/taverna.apache.org)
> >>>>>
> >>>>> Level 1 : INFRA-9260 pinged.
> >>>>>
> >>>>> Andy
> >>>>>
> >>>>>
> >>>>>> Sergio Fernández
> >>>>>> Partner Technology Manager
> >>>>>> Redlink GmbH
> >>>>>> m: +43 6602747925
> >>>>>> e: sergio.fernandez@redlink.co
> >>>>>> w: http://redlink.co
> >>>>>>
> >>>>>> On Mon, Mar 30, 2015 at 11:39 AM, Andy Seaborne <an...@apache.org>
> >>>>>> wrote:
> >>>>>>
> >>>>>> The "submitted request" goes onto a work queue for infra ... I
> >>>>>>> believe it
> >>>>>>> gets checked by a person, not simply automatically done.
> >>>>>>>
> >>>>>>> Andy
> >>>>>>>
> >>>>>>>
> >>>>>>> On 29/03/15 18:25, Sergio Fernández wrote:
> >>>>>>>
> >>>>>>> any update on this?
> >>>>>>>> both http://commonsrdf.incubator.apache.org/ and
> >>>>>>>> http://cms.apache.org/commonsrdf/ still return 404...
> >>>>>>>>
> >>>>>>>> On 25/03/15 14:36, Sergio Fernández wrote:
> >>>>>>>>
> >>>>>>>> On 25/03/15 14:26, Andy Seaborne wrote:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Done ::
> >>>>>>>>>>
> >>>>>>>>>> -----------------
> >>>>>>>>>> Submitted request
> >>>>>>>>>>
> >>>>>>>>>> {
> >>>>>>>>>> "version": 2,
> >>>>>>>>>> "source": "/incubator/commonsrdf/site/",
> >>>>>>>>>> "project": "commonsrdf",
> >>>>>>>>>> "backend": "cms",
> >>>>>>>>>> "message": "Project discussion:
> >>>>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
> >>>>>>>>>> commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org
> %3E",
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> "build": "maven"
> >>>>>>>>>> }
> >>>>>>>>>> -----------------
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Cool!
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernandez@redlink.co
> > w: http://redlink.co
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
Content online at: http://commonsrdf.incubator.apache.org/ :-)
CMS workflow is broken. build work on staging, but it does not work the
copying. Talking with INFRA to get it solved. But at least there is an
alternative workflow in case the release. I'll keep you posted.
On Wed, Apr 8, 2015 at 8:47 AM, Sergio Fernández <wi...@apache.org> wrote:
> Still dealing with some issues at INFRA-9260. I'll keep you posted when
> the site is actually working.
>
> On Tue, Apr 7, 2015 at 8:08 PM, Sergio Fernández <wi...@apache.org>
> wrote:
>
>> Cool! Thanks Andy for the bureaucracy.
>> On Apr 7, 2015 7:00 PM, "Andy Seaborne" <an...@apache.org> wrote:
>>
>>> Now working thanks to infra.
>>>
>>> Andy
>>>
>>> On 07/04/15 14:56, Andy Seaborne wrote:
>>>
>>>> At the moment, it responds with a different 404 to a site that
>>>> definitely does not exist.
>>>>
>>>> http://commonsrdf.incubator.apache.org/
>>>> ("Server at commonsrdf.incubator.apache.org Port 80" line)
>>>>
>>>> cf
>>>>
>>>> http:/qwertyuiop.incubator.apache.org
>>>> (no such line)
>>>>
>>>> /x1/www/commonsrdf.apache.org does not exist but other incubating sites
>>>> seem to exists in that form.
>>>>
>>>> Infra/hipchat attempted.
>>>>
>>>> Andy
>>>>
>>>>
>>>> On 01/04/15 10:36, Andy Seaborne wrote:
>>>>
>>>>> On 01/04/15 05:53, Sergio Fernández wrote:
>>>>>
>>>>>> I think after a week it's time to ping back infra about this, isn't
>>>>>> it?
>>>>>>
>>>>>
>>>>> Yes.
>>>>>
>>>>> From what I can tell it's not there (rather than a config problem
>>>>> meaning / is returning 404)
>>>>>
>>>>> All the websites are at people:/x1/www/ (under their final name - e.g.
>>>>> /x1/www/taverna.apache.org)
>>>>>
>>>>> Level 1 : INFRA-9260 pinged.
>>>>>
>>>>> Andy
>>>>>
>>>>>
>>>>>> Sergio Fernández
>>>>>> Partner Technology Manager
>>>>>> Redlink GmbH
>>>>>> m: +43 6602747925
>>>>>> e: sergio.fernandez@redlink.co
>>>>>> w: http://redlink.co
>>>>>>
>>>>>> On Mon, Mar 30, 2015 at 11:39 AM, Andy Seaborne <an...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>> The "submitted request" goes onto a work queue for infra ... I
>>>>>>> believe it
>>>>>>> gets checked by a person, not simply automatically done.
>>>>>>>
>>>>>>> Andy
>>>>>>>
>>>>>>>
>>>>>>> On 29/03/15 18:25, Sergio Fernández wrote:
>>>>>>>
>>>>>>> any update on this?
>>>>>>>> both http://commonsrdf.incubator.apache.org/ and
>>>>>>>> http://cms.apache.org/commonsrdf/ still return 404...
>>>>>>>>
>>>>>>>> On 25/03/15 14:36, Sergio Fernández wrote:
>>>>>>>>
>>>>>>>> On 25/03/15 14:26, Andy Seaborne wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Done ::
>>>>>>>>>>
>>>>>>>>>> -----------------
>>>>>>>>>> Submitted request
>>>>>>>>>>
>>>>>>>>>> {
>>>>>>>>>> "version": 2,
>>>>>>>>>> "source": "/incubator/commonsrdf/site/",
>>>>>>>>>> "project": "commonsrdf",
>>>>>>>>>> "backend": "cms",
>>>>>>>>>> "message": "Project discussion:
>>>>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
>>>>>>>>>> commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> "build": "maven"
>>>>>>>>>> }
>>>>>>>>>> -----------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Cool!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
Still dealing with some issues at INFRA-9260. I'll keep you posted when the
site is actually working.
On Tue, Apr 7, 2015 at 8:08 PM, Sergio Fernández <wi...@apache.org> wrote:
> Cool! Thanks Andy for the bureaucracy.
> On Apr 7, 2015 7:00 PM, "Andy Seaborne" <an...@apache.org> wrote:
>
>> Now working thanks to infra.
>>
>> Andy
>>
>> On 07/04/15 14:56, Andy Seaborne wrote:
>>
>>> At the moment, it responds with a different 404 to a site that
>>> definitely does not exist.
>>>
>>> http://commonsrdf.incubator.apache.org/
>>> ("Server at commonsrdf.incubator.apache.org Port 80" line)
>>>
>>> cf
>>>
>>> http:/qwertyuiop.incubator.apache.org
>>> (no such line)
>>>
>>> /x1/www/commonsrdf.apache.org does not exist but other incubating sites
>>> seem to exists in that form.
>>>
>>> Infra/hipchat attempted.
>>>
>>> Andy
>>>
>>>
>>> On 01/04/15 10:36, Andy Seaborne wrote:
>>>
>>>> On 01/04/15 05:53, Sergio Fernández wrote:
>>>>
>>>>> I think after a week it's time to ping back infra about this, isn't it?
>>>>>
>>>>
>>>> Yes.
>>>>
>>>> From what I can tell it's not there (rather than a config problem
>>>> meaning / is returning 404)
>>>>
>>>> All the websites are at people:/x1/www/ (under their final name - e.g.
>>>> /x1/www/taverna.apache.org)
>>>>
>>>> Level 1 : INFRA-9260 pinged.
>>>>
>>>> Andy
>>>>
>>>>
>>>>> Sergio Fernández
>>>>> Partner Technology Manager
>>>>> Redlink GmbH
>>>>> m: +43 6602747925
>>>>> e: sergio.fernandez@redlink.co
>>>>> w: http://redlink.co
>>>>>
>>>>> On Mon, Mar 30, 2015 at 11:39 AM, Andy Seaborne <an...@apache.org>
>>>>> wrote:
>>>>>
>>>>> The "submitted request" goes onto a work queue for infra ... I
>>>>>> believe it
>>>>>> gets checked by a person, not simply automatically done.
>>>>>>
>>>>>> Andy
>>>>>>
>>>>>>
>>>>>> On 29/03/15 18:25, Sergio Fernández wrote:
>>>>>>
>>>>>> any update on this?
>>>>>>> both http://commonsrdf.incubator.apache.org/ and
>>>>>>> http://cms.apache.org/commonsrdf/ still return 404...
>>>>>>>
>>>>>>> On 25/03/15 14:36, Sergio Fernández wrote:
>>>>>>>
>>>>>>> On 25/03/15 14:26, Andy Seaborne wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Done ::
>>>>>>>>>
>>>>>>>>> -----------------
>>>>>>>>> Submitted request
>>>>>>>>>
>>>>>>>>> {
>>>>>>>>> "version": 2,
>>>>>>>>> "source": "/incubator/commonsrdf/site/",
>>>>>>>>> "project": "commonsrdf",
>>>>>>>>> "backend": "cms",
>>>>>>>>> "message": "Project discussion:
>>>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
>>>>>>>>> commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> "build": "maven"
>>>>>>>>> }
>>>>>>>>> -----------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Cool!
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
Cool! Thanks Andy for the bureaucracy.
On Apr 7, 2015 7:00 PM, "Andy Seaborne" <an...@apache.org> wrote:
> Now working thanks to infra.
>
> Andy
>
> On 07/04/15 14:56, Andy Seaborne wrote:
>
>> At the moment, it responds with a different 404 to a site that
>> definitely does not exist.
>>
>> http://commonsrdf.incubator.apache.org/
>> ("Server at commonsrdf.incubator.apache.org Port 80" line)
>>
>> cf
>>
>> http:/qwertyuiop.incubator.apache.org
>> (no such line)
>>
>> /x1/www/commonsrdf.apache.org does not exist but other incubating sites
>> seem to exists in that form.
>>
>> Infra/hipchat attempted.
>>
>> Andy
>>
>>
>> On 01/04/15 10:36, Andy Seaborne wrote:
>>
>>> On 01/04/15 05:53, Sergio Fernández wrote:
>>>
>>>> I think after a week it's time to ping back infra about this, isn't it?
>>>>
>>>
>>> Yes.
>>>
>>> From what I can tell it's not there (rather than a config problem
>>> meaning / is returning 404)
>>>
>>> All the websites are at people:/x1/www/ (under their final name - e.g.
>>> /x1/www/taverna.apache.org)
>>>
>>> Level 1 : INFRA-9260 pinged.
>>>
>>> Andy
>>>
>>>
>>>> Sergio Fernández
>>>> Partner Technology Manager
>>>> Redlink GmbH
>>>> m: +43 6602747925
>>>> e: sergio.fernandez@redlink.co
>>>> w: http://redlink.co
>>>>
>>>> On Mon, Mar 30, 2015 at 11:39 AM, Andy Seaborne <an...@apache.org>
>>>> wrote:
>>>>
>>>> The "submitted request" goes onto a work queue for infra ... I
>>>>> believe it
>>>>> gets checked by a person, not simply automatically done.
>>>>>
>>>>> Andy
>>>>>
>>>>>
>>>>> On 29/03/15 18:25, Sergio Fernández wrote:
>>>>>
>>>>> any update on this?
>>>>>> both http://commonsrdf.incubator.apache.org/ and
>>>>>> http://cms.apache.org/commonsrdf/ still return 404...
>>>>>>
>>>>>> On 25/03/15 14:36, Sergio Fernández wrote:
>>>>>>
>>>>>> On 25/03/15 14:26, Andy Seaborne wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Done ::
>>>>>>>>
>>>>>>>> -----------------
>>>>>>>> Submitted request
>>>>>>>>
>>>>>>>> {
>>>>>>>> "version": 2,
>>>>>>>> "source": "/incubator/commonsrdf/site/",
>>>>>>>> "project": "commonsrdf",
>>>>>>>> "backend": "cms",
>>>>>>>> "message": "Project discussion:
>>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
>>>>>>>> commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> "build": "maven"
>>>>>>>> }
>>>>>>>> -----------------
>>>>>>>>
>>>>>>>>
>>>>>>>> Cool!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
Now working thanks to infra.
Andy
On 07/04/15 14:56, Andy Seaborne wrote:
> At the moment, it responds with a different 404 to a site that
> definitely does not exist.
>
> http://commonsrdf.incubator.apache.org/
> ("Server at commonsrdf.incubator.apache.org Port 80" line)
>
> cf
>
> http:/qwertyuiop.incubator.apache.org
> (no such line)
>
> /x1/www/commonsrdf.apache.org does not exist but other incubating sites
> seem to exists in that form.
>
> Infra/hipchat attempted.
>
> Andy
>
>
> On 01/04/15 10:36, Andy Seaborne wrote:
>> On 01/04/15 05:53, Sergio Fernández wrote:
>>> I think after a week it's time to ping back infra about this, isn't it?
>>
>> Yes.
>>
>> From what I can tell it's not there (rather than a config problem
>> meaning / is returning 404)
>>
>> All the websites are at people:/x1/www/ (under their final name - e.g.
>> /x1/www/taverna.apache.org)
>>
>> Level 1 : INFRA-9260 pinged.
>>
>> Andy
>>
>>>
>>> Sergio Fernández
>>> Partner Technology Manager
>>> Redlink GmbH
>>> m: +43 6602747925
>>> e: sergio.fernandez@redlink.co
>>> w: http://redlink.co
>>>
>>> On Mon, Mar 30, 2015 at 11:39 AM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>>> The "submitted request" goes onto a work queue for infra ... I
>>>> believe it
>>>> gets checked by a person, not simply automatically done.
>>>>
>>>> Andy
>>>>
>>>>
>>>> On 29/03/15 18:25, Sergio Fernández wrote:
>>>>
>>>>> any update on this?
>>>>> both http://commonsrdf.incubator.apache.org/ and
>>>>> http://cms.apache.org/commonsrdf/ still return 404...
>>>>>
>>>>> On 25/03/15 14:36, Sergio Fernández wrote:
>>>>>
>>>>>> On 25/03/15 14:26, Andy Seaborne wrote:
>>>>>>
>>>>>>>
>>>>>>> Done ::
>>>>>>>
>>>>>>> -----------------
>>>>>>> Submitted request
>>>>>>>
>>>>>>> {
>>>>>>> "version": 2,
>>>>>>> "source": "/incubator/commonsrdf/site/",
>>>>>>> "project": "commonsrdf",
>>>>>>> "backend": "cms",
>>>>>>> "message": "Project discussion:
>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
>>>>>>> commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> "build": "maven"
>>>>>>> }
>>>>>>> -----------------
>>>>>>>
>>>>>>>
>>>>>> Cool!
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
At the moment, it responds with a different 404 to a site that
definitely does not exist.
http://commonsrdf.incubator.apache.org/
("Server at commonsrdf.incubator.apache.org Port 80" line)
cf
http:/qwertyuiop.incubator.apache.org
(no such line)
/x1/www/commonsrdf.apache.org does not exist but other incubating sites
seem to exists in that form.
Infra/hipchat attempted.
Andy
On 01/04/15 10:36, Andy Seaborne wrote:
> On 01/04/15 05:53, Sergio Fernández wrote:
>> I think after a week it's time to ping back infra about this, isn't it?
>
> Yes.
>
> From what I can tell it's not there (rather than a config problem
> meaning / is returning 404)
>
> All the websites are at people:/x1/www/ (under their final name - e.g.
> /x1/www/taverna.apache.org)
>
> Level 1 : INFRA-9260 pinged.
>
> Andy
>
>>
>> Sergio Fernández
>> Partner Technology Manager
>> Redlink GmbH
>> m: +43 6602747925
>> e: sergio.fernandez@redlink.co
>> w: http://redlink.co
>>
>> On Mon, Mar 30, 2015 at 11:39 AM, Andy Seaborne <an...@apache.org> wrote:
>>
>>> The "submitted request" goes onto a work queue for infra ... I
>>> believe it
>>> gets checked by a person, not simply automatically done.
>>>
>>> Andy
>>>
>>>
>>> On 29/03/15 18:25, Sergio Fernández wrote:
>>>
>>>> any update on this?
>>>> both http://commonsrdf.incubator.apache.org/ and
>>>> http://cms.apache.org/commonsrdf/ still return 404...
>>>>
>>>> On 25/03/15 14:36, Sergio Fernández wrote:
>>>>
>>>>> On 25/03/15 14:26, Andy Seaborne wrote:
>>>>>
>>>>>>
>>>>>> Done ::
>>>>>>
>>>>>> -----------------
>>>>>> Submitted request
>>>>>>
>>>>>> {
>>>>>> "version": 2,
>>>>>> "source": "/incubator/commonsrdf/site/",
>>>>>> "project": "commonsrdf",
>>>>>> "backend": "cms",
>>>>>> "message": "Project discussion:
>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
>>>>>> commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>>>>>>
>>>>>>
>>>>>>
>>>>>> "build": "maven"
>>>>>> }
>>>>>> -----------------
>>>>>>
>>>>>>
>>>>> Cool!
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
On 01/04/15 05:53, Sergio Fernández wrote:
> I think after a week it's time to ping back infra about this, isn't it?
Yes.
From what I can tell it's not there (rather than a config problem
meaning / is returning 404)
All the websites are at people:/x1/www/ (under their final name - e.g.
/x1/www/taverna.apache.org)
Level 1 : INFRA-9260 pinged.
Andy
>
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>
> On Mon, Mar 30, 2015 at 11:39 AM, Andy Seaborne <an...@apache.org> wrote:
>
>> The "submitted request" goes onto a work queue for infra ... I believe it
>> gets checked by a person, not simply automatically done.
>>
>> Andy
>>
>>
>> On 29/03/15 18:25, Sergio Fernández wrote:
>>
>>> any update on this?
>>> both http://commonsrdf.incubator.apache.org/ and
>>> http://cms.apache.org/commonsrdf/ still return 404...
>>>
>>> On 25/03/15 14:36, Sergio Fernández wrote:
>>>
>>>> On 25/03/15 14:26, Andy Seaborne wrote:
>>>>
>>>>>
>>>>> Done ::
>>>>>
>>>>> -----------------
>>>>> Submitted request
>>>>>
>>>>> {
>>>>> "version": 2,
>>>>> "source": "/incubator/commonsrdf/site/",
>>>>> "project": "commonsrdf",
>>>>> "backend": "cms",
>>>>> "message": "Project discussion:
>>>>> http://mail-archives.apache.org/mod_mbox/incubator-
>>>>> commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>>>>>
>>>>>
>>>>>
>>>>> "build": "maven"
>>>>> }
>>>>> -----------------
>>>>>
>>>>>
>>>> Cool!
>>>>
>>>>
>>>>
>>>
>>
>
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
I think after a week it's time to ping back infra about this, isn't it?
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
On Mon, Mar 30, 2015 at 11:39 AM, Andy Seaborne <an...@apache.org> wrote:
> The "submitted request" goes onto a work queue for infra ... I believe it
> gets checked by a person, not simply automatically done.
>
> Andy
>
>
> On 29/03/15 18:25, Sergio Fernández wrote:
>
>> any update on this?
>> both http://commonsrdf.incubator.apache.org/ and
>> http://cms.apache.org/commonsrdf/ still return 404...
>>
>> On 25/03/15 14:36, Sergio Fernández wrote:
>>
>>> On 25/03/15 14:26, Andy Seaborne wrote:
>>>
>>>>
>>>> Done ::
>>>>
>>>> -----------------
>>>> Submitted request
>>>>
>>>> {
>>>> "version": 2,
>>>> "source": "/incubator/commonsrdf/site/",
>>>> "project": "commonsrdf",
>>>> "backend": "cms",
>>>> "message": "Project discussion:
>>>> http://mail-archives.apache.org/mod_mbox/incubator-
>>>> commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>>>>
>>>>
>>>>
>>>> "build": "maven"
>>>> }
>>>> -----------------
>>>>
>>>>
>>> Cool!
>>>
>>>
>>>
>>
>
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
The "submitted request" goes onto a work queue for infra ... I believe
it gets checked by a person, not simply automatically done.
Andy
On 29/03/15 18:25, Sergio Fernández wrote:
> any update on this?
> both http://commonsrdf.incubator.apache.org/ and
> http://cms.apache.org/commonsrdf/ still return 404...
>
> On 25/03/15 14:36, Sergio Fernández wrote:
>> On 25/03/15 14:26, Andy Seaborne wrote:
>>>
>>> Done ::
>>>
>>> -----------------
>>> Submitted request
>>>
>>> {
>>> "version": 2,
>>> "source": "/incubator/commonsrdf/site/",
>>> "project": "commonsrdf",
>>> "backend": "cms",
>>> "message": "Project discussion:
>>> http://mail-archives.apache.org/mod_mbox/incubator-commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>>>
>>>
>>>
>>> "build": "maven"
>>> }
>>> -----------------
>>>
>>
>> Cool!
>>
>>
>
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
any update on this?
both http://commonsrdf.incubator.apache.org/ and
http://cms.apache.org/commonsrdf/ still return 404...
On 25/03/15 14:36, Sergio Fernández wrote:
> On 25/03/15 14:26, Andy Seaborne wrote:
>>
>> Done ::
>>
>> -----------------
>> Submitted request
>>
>> {
>> "version": 2,
>> "source": "/incubator/commonsrdf/site/",
>> "project": "commonsrdf",
>> "backend": "cms",
>> "message": "Project discussion:
>> http://mail-archives.apache.org/mod_mbox/incubator-commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>>
>>
>> "build": "maven"
>> }
>> -----------------
>>
>
> Cool!
>
>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: CommonsRDF Website Format
Posted by Benedikt Ritter <br...@apache.org>.
Hello,
2015-03-29 19:32 GMT+02:00 Sergio Fernández <wi...@apache.org>:
> Well, I guess here we are bound to whatever Commons PMC decides to this
> respect.
>
> The introduction of gitpubsub is definitely great news, since many
> projects are currently using svn just for their sites.
>
> But I think (I hope) a pure Maven site would be supported in the new
> infrastructure, so we could keep what we already have.
>
We have some documentation about site publication on our website [1]. For
simple components you only have to call mvn site-deploy and it will do the
trick. I've heard from people that multi-module projects are some how more
tricky to setup with commons parent pom, but I'll have to look into that
tomorrow (I haven't worked on any of our multi-module projects so far).
Benedikt
[1] http://commons.apache.org/site-publish.html
>
> Those are my two cents.
>
>
>
> On 29/03/15 03:02, John D. Ament wrote:
>
>> So anyone have any questions/comments about the infra discussions around
>> retiring CMS?
>>
>> I'm also curious, what format for the site were you planning to use?
>> Storing asciidoc/markdown in git and publishing via maven site?
>>
>> John
>>
>> On Thu, Mar 26, 2015 at 5:58 AM Andy Seaborne <an...@apache.org> wrote:
>>
>> And then:
>>> https://cwiki.apache.org/confluence/display/INFRA/CMS+
>>> Decommissioning+RFC+-+Frequently+Asked+Questions
>>>
>>>
>>
> --
> 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
Re: CommonsRDF Website Format
Posted by "John D. Ament" <jo...@apache.org>.
On Sun, Mar 29, 2015 at 1:33 PM Sergio Fernández <wi...@apache.org> wrote:
> Well, I guess here we are bound to whatever Commons PMC decides to this
> respect.
>
> The introduction of gitpubsub is definitely great news, since many
> projects are currently using svn just for their sites.
> But I think (I hope) a pure Maven site would be supported in the new
> infrastructure, so we could keep what we already have.
>
That's basically what gitpubsub is supposed to be. The difference is that
to publish to the website, we need to push to a repo. We can probably
start tinkering with the idea of publishing the website based on pushes to
our git repo, but I think the intention is that we could use site-deploy to
push to a git repo, and then boom, the site's live.
If we think we want to try that route, I can get the ball rolling and
request the infra resources required to allow us to push that way.
John
>
> Those are my two cents.
>
>
> On 29/03/15 03:02, John D. Ament wrote:
> > So anyone have any questions/comments about the infra discussions around
> > retiring CMS?
> >
> > I'm also curious, what format for the site were you planning to use?
> > Storing asciidoc/markdown in git and publishing via maven site?
> >
> > John
> >
> > On Thu, Mar 26, 2015 at 5:58 AM Andy Seaborne <an...@apache.org> wrote:
> >
> >> And then:
> >> https://cwiki.apache.org/confluence/display/INFRA/CMS+
> >> Decommissioning+RFC+-+Frequently+Asked+Questions
> >>
> >
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 660 2747 925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co
>
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
Well, I guess here we are bound to whatever Commons PMC decides to this
respect.
The introduction of gitpubsub is definitely great news, since many
projects are currently using svn just for their sites.
But I think (I hope) a pure Maven site would be supported in the new
infrastructure, so we could keep what we already have.
Those are my two cents.
On 29/03/15 03:02, John D. Ament wrote:
> So anyone have any questions/comments about the infra discussions around
> retiring CMS?
>
> I'm also curious, what format for the site were you planning to use?
> Storing asciidoc/markdown in git and publishing via maven site?
>
> John
>
> On Thu, Mar 26, 2015 at 5:58 AM Andy Seaborne <an...@apache.org> wrote:
>
>> And then:
>> https://cwiki.apache.org/confluence/display/INFRA/CMS+
>> Decommissioning+RFC+-+Frequently+Asked+Questions
>>
>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: CommonsRDF Website Format
Posted by "John D. Ament" <jo...@apache.org>.
So anyone have any questions/comments about the infra discussions around
retiring CMS?
I'm also curious, what format for the site were you planning to use?
Storing asciidoc/markdown in git and publishing via maven site?
John
On Thu, Mar 26, 2015 at 5:58 AM Andy Seaborne <an...@apache.org> wrote:
> And then:
> https://cwiki.apache.org/confluence/display/INFRA/CMS+
> Decommissioning+RFC+-+Frequently+Asked+Questions
>
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
And then:
https://cwiki.apache.org/confluence/display/INFRA/CMS+Decommissioning+RFC+-+Frequently+Asked+Questions
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
On 25/03/15 14:26, Andy Seaborne wrote:
>
> Done ::
>
> -----------------
> Submitted request
>
> {
> "version": 2,
> "source": "/incubator/commonsrdf/site/",
> "project": "commonsrdf",
> "backend": "cms",
> "message": "Project discussion:
> http://mail-archives.apache.org/mod_mbox/incubator-commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
>
> "build": "maven"
> }
> -----------------
>
Cool!
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
On 03/25/15 13:19, Sergio Fernández wrote:
> Sorry, I think we have two threads open about this, and I replied the
> less important one.
>
> Well, source site draft is at the expected location, so please move
> ahead requesting the cms build.
>
> On 21/03/15 21:35, Andy Seaborne wrote:
>> On 20/03/15 17:49, Andy Seaborne wrote:
>>> Hoping we can wrap this up:
>>>
>>> CMS/Maven seems to be the preferred so I'll ask for that, in at least 24
>>> hours time.
>>>
>>> (Note - we didn't clear up the XML config file sub-thread so if you see
>>> that as an issue to check first, please say so)
>>>
>>> Andy
>>
>> Slight hiccup. The webreq process requires there to be
>> https://svn.apache.org/repos/asf/incubator/commonsrdf/site/trunk/pom.xml
>> in place for the request to be received.
>>
>> Currently /commonsrdf/site/ exists but no more.
>>
>> Andy
>>
>
Done ::
-----------------
Submitted request
{
"version": 2,
"source": "/incubator/commonsrdf/site/",
"project": "commonsrdf",
"backend": "cms",
"message": "Project discussion:
http://mail-archives.apache.org/mod_mbox/incubator-commonsrdf-dev/201503.mbox/%3C550C5DA6.7060205%40apache.org%3E",
"build": "maven"
}
-----------------
Re: CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
Sorry, I think we have two threads open about this, and I replied the
less important one.
Well, source site draft is at the expected location, so please move
ahead requesting the cms build.
On 21/03/15 21:35, Andy Seaborne wrote:
> On 20/03/15 17:49, Andy Seaborne wrote:
>> Hoping we can wrap this up:
>>
>> CMS/Maven seems to be the preferred so I'll ask for that, in at least 24
>> hours time.
>>
>> (Note - we didn't clear up the XML config file sub-thread so if you see
>> that as an issue to check first, please say so)
>>
>> Andy
>
> Slight hiccup. The webreq process requires there to be
> https://svn.apache.org/repos/asf/incubator/commonsrdf/site/trunk/pom.xml
> in place for the request to be received.
>
> Currently /commonsrdf/site/ exists but no more.
>
> Andy
>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
On 20/03/15 17:49, Andy Seaborne wrote:
> Hoping we can wrap this up:
>
> CMS/Maven seems to be the preferred so I'll ask for that, in at least 24
> hours time.
>
> (Note - we didn't clear up the XML config file sub-thread so if you see
> that as an issue to check first, please say so)
>
> Andy
Slight hiccup. The webreq process requires there to be
https://svn.apache.org/repos/asf/incubator/commonsrdf/site/trunk/pom.xml
in place for the request to be received.
Currently /commonsrdf/site/ exists but no more.
Andy
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
Hoping we can wrap this up:
CMS/Maven seems to be the preferred so I'll ask for that, in at least 24
hours time.
(Note - we didn't clear up the XML config file sub-thread so if you see
that as an issue to check first, please say so)
Andy
On 18/03/15 21:29, Andy Seaborne wrote:
> Gary - I don't know in detail what Commons use - could you expand
> please? or is there a descriptive link somewhere?
>
> It's some kind of maven generated site but I also understood some amount
> of XML control files are used (e.g. changes.xml) which need manually
> coordinating with, say, JIRA.
>
> Andy
>
> On 18/03/15 16:09, Stian Soiland-Reyes wrote:
> > Shall we not just go with option 2 then? It's not like we can't change
>> our mind if it doesn't work.
>>
>> I assume this does not require a formal release to update the website :)
>
> Surely option 2 is the one that connects the website to releases in
> someway?
>
>>
>> On 18 March 2015 at 16:03, Gary Gregory <ga...@gmail.com> wrote:
>>> Unless someone want to do double work, or not end up with this
>>> component in
>>> Apache Commons, it seems simpler to me to just follow what Apache
>>> Commons
>>> components do.
>>>
>>> Gary
>>>
>>> On Wed, Mar 18, 2015 at 3:46 AM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>>> Moving this onwards:
>>>>
>>>> tl;dr:
>>>>
>>>> proposal:
>>>> ask for svnpubsub now
>>>> not CMS
>>>> worry about the production of the site later.
>>>>
>>>> ------
>>>> Assumption:
>>>>
>>>> I'm assuming that the site is small (what it is, download this, maven
>>>> that, contribute, support) so for me the choice is a bit "whatever"
>>>> and low
>>>> running cost is important. Adding any steps to the release process
>>>> discourages "release early, release often".
>>>>
>>>> [This is an entirely personal and forward looking statement etc etc.]
>>>>
>>>> CMS is *possibly* not an option long term (it costs infra to
>>>> maintain, not
>>>> all projects use it, it conflicts with gitpubsub.)
>>>>
>>>> As CMS hooks into the VCS, gitpubsub is non-zero work so my guess is
>>>> that
>>>> some time down the line, there will be a choice for ASF between CMS or
>>>> gitpubsub on resource grounds.
>>>>
>>>> [/]
>>>>
>>>> Options, and some pros and cons:
>>>>
>>>> Publishing: svnpubsub
>>>> (and gitpubsub might arrive)
>>>>
>>>> then a choice of how the site is made:
>>>>
>>>> * Take the CMS perl magic independently
>>>> Don't see anyone here keen on doing that.
>>>> The only advantage is not wandering to far from CMS.
>>>>
>>>> * Maven plugin (probably many plugin choices)
>>>> The maven site plugin is too focused inwardly on process.
>>>> Familiar, in usage and to even to some visitors
>>>>
>>>> * Jekyll (c.f. github pages)
>>>> It's a ruby gem. Needs local setup even if run by maven (?)
>>>> MSWindows is not 1st class.
>>>> Jekyll is first-amongst-equals on github.
>>>>
>>>> * HTML and whatever you want to do locally to produce that
>>>> Minimal project implications.
>>>>
>>>> * one of the zillions of other templating systems.
>>>> Baseline should be "obviously better than Jekyll for the project"
>>>>
>>>> I know there has been some talk of projects using github pages. I don't
>>>> know the state of that or what the full implications are.
>>>>
>>>> Andy
>>>>
>>>> On 12/03/15 16:10, Stian Soiland-Reyes wrote:
>>>>
>>>>> The Maven build is also more easily open for Github pull requests -
>>>>> and if
>>>>> you can use Markdown files they would reasonably render also on
>>>>> Github.
>>>>>
>>>>> Commons seems however to use an XML based template system..? (I
>>>>> looked at
>>>>> Commons Math)
>>>>>
>>>>> (note: we can also github mirror the cms from svn - see for example
>>>>> https://github.com/apache/incubator-taverna-site - its just harder to
>>>>> apply
>>>>> patches and to render it)
>>>>>
>>>>> With CMS Maven build - can you still use the cms.apache.org "UI" to
>>>>> edit
>>>>> files?
>>>>> On 12 Mar 2015 13:03, "Andy Seaborne" <an...@apache.org> wrote:
>>>>>
>>>>> On 12/03/15 07:36, Sergio Fernández wrote:
>>>>>>
>>>>>> My vote goes to option 2, mainly because the compatibility with the
>>>>>>> Apache Commons project site.
>>>>>>>
>>>>>>> On 11/03/15 23:27, Gary Gregory wrote:
>>>>>>>
>>>>>>> On Wed, Mar 11, 2015 at 3:02 PM, Stian Soiland-Reyes
>>>>>>> <stain@apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>> Gary, how would we fit into Commons website-wise while
>>>>>>>> incubating?
>>>>>>>>> Could we
>>>>>>>>> still use the same system, but publish to
>>>>>>>>> commonsrdf.incubator.apache.org
>>>>>>>>> ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Good question! I know you can override a bunch of settings in
>>>>>>>> your POM
>>>>>>>> but
>>>>>>>> I am not sure about publishing the site to a different host.
>>>>>>>>
>>>>>>>>
>>>>>>> I have quite experience with that setup. So I'll check if we can
>>>>>>> build a
>>>>>>> subsite in our temporal web space, and I'll be back with conclusions
>>>>>>> during the weekend.
>>>>>>>
>>>>>>>
>>>>>> I'm assuming the website will be quite small and relatively stable
>>>>>> once
>>>>>> it's all set up.
>>>>>>
>>>>>> The choice should be whatever makes the long term running costs
>>>>>> low if
>>>>>> the
>>>>>> setup is all about the same.
>>>>>>
>>>>>> I have only used CMS/perl for real; the CMS ability edit a page in
>>>>>> the
>>>>>> browser to quickly fix the small things is great and anyone can do
>>>>>> it.
>>>>>>
>>>>>> If all the CMS choices have that, then I think I'm just -0.5 on raw
>>>>>> svnpubsub. ant - don't use it myself anymore. shell - not (easy on)
>>>>>> windows.
>>>>>>
>>>>>> Which leaves:
>>>>>>
>>>>>> 1 CMS (default-Perl-build)
>>>>>> 2 CMS (Maven-build)
>>>>>>
>>>>>> Andy
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> <http://www.manning.com/bauer3/>
>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>> Spring Batch in Action <http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>
>>
>>
>
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
Gary - I don't know in detail what Commons use - could you expand
please? or is there a descriptive link somewhere?
It's some kind of maven generated site but I also understood some amount
of XML control files are used (e.g. changes.xml) which need manually
coordinating with, say, JIRA.
Andy
On 18/03/15 16:09, Stian Soiland-Reyes wrote:
> Shall we not just go with option 2 then? It's not like we can't change
> our mind if it doesn't work.
>
> I assume this does not require a formal release to update the website :)
Surely option 2 is the one that connects the website to releases in someway?
>
> On 18 March 2015 at 16:03, Gary Gregory <ga...@gmail.com> wrote:
>> Unless someone want to do double work, or not end up with this component in
>> Apache Commons, it seems simpler to me to just follow what Apache Commons
>> components do.
>>
>> Gary
>>
>> On Wed, Mar 18, 2015 at 3:46 AM, Andy Seaborne <an...@apache.org> wrote:
>>
>>> Moving this onwards:
>>>
>>> tl;dr:
>>>
>>> proposal:
>>> ask for svnpubsub now
>>> not CMS
>>> worry about the production of the site later.
>>>
>>> ------
>>> Assumption:
>>>
>>> I'm assuming that the site is small (what it is, download this, maven
>>> that, contribute, support) so for me the choice is a bit "whatever" and low
>>> running cost is important. Adding any steps to the release process
>>> discourages "release early, release often".
>>>
>>> [This is an entirely personal and forward looking statement etc etc.]
>>>
>>> CMS is *possibly* not an option long term (it costs infra to maintain, not
>>> all projects use it, it conflicts with gitpubsub.)
>>>
>>> As CMS hooks into the VCS, gitpubsub is non-zero work so my guess is that
>>> some time down the line, there will be a choice for ASF between CMS or
>>> gitpubsub on resource grounds.
>>>
>>> [/]
>>>
>>> Options, and some pros and cons:
>>>
>>> Publishing: svnpubsub
>>> (and gitpubsub might arrive)
>>>
>>> then a choice of how the site is made:
>>>
>>> * Take the CMS perl magic independently
>>> Don't see anyone here keen on doing that.
>>> The only advantage is not wandering to far from CMS.
>>>
>>> * Maven plugin (probably many plugin choices)
>>> The maven site plugin is too focused inwardly on process.
>>> Familiar, in usage and to even to some visitors
>>>
>>> * Jekyll (c.f. github pages)
>>> It's a ruby gem. Needs local setup even if run by maven (?)
>>> MSWindows is not 1st class.
>>> Jekyll is first-amongst-equals on github.
>>>
>>> * HTML and whatever you want to do locally to produce that
>>> Minimal project implications.
>>>
>>> * one of the zillions of other templating systems.
>>> Baseline should be "obviously better than Jekyll for the project"
>>>
>>> I know there has been some talk of projects using github pages. I don't
>>> know the state of that or what the full implications are.
>>>
>>> Andy
>>>
>>> On 12/03/15 16:10, Stian Soiland-Reyes wrote:
>>>
>>>> The Maven build is also more easily open for Github pull requests - and if
>>>> you can use Markdown files they would reasonably render also on Github.
>>>>
>>>> Commons seems however to use an XML based template system..? (I looked at
>>>> Commons Math)
>>>>
>>>> (note: we can also github mirror the cms from svn - see for example
>>>> https://github.com/apache/incubator-taverna-site - its just harder to
>>>> apply
>>>> patches and to render it)
>>>>
>>>> With CMS Maven build - can you still use the cms.apache.org "UI" to edit
>>>> files?
>>>> On 12 Mar 2015 13:03, "Andy Seaborne" <an...@apache.org> wrote:
>>>>
>>>> On 12/03/15 07:36, Sergio Fernández wrote:
>>>>>
>>>>> My vote goes to option 2, mainly because the compatibility with the
>>>>>> Apache Commons project site.
>>>>>>
>>>>>> On 11/03/15 23:27, Gary Gregory wrote:
>>>>>>
>>>>>> On Wed, Mar 11, 2015 at 3:02 PM, Stian Soiland-Reyes <stain@apache.org
>>>>>>>>
>>>>>>>
>>>>>>> Gary, how would we fit into Commons website-wise while incubating?
>>>>>>>> Could we
>>>>>>>> still use the same system, but publish to
>>>>>>>> commonsrdf.incubator.apache.org
>>>>>>>> ?
>>>>>>>>
>>>>>>>>
>>>>>>> Good question! I know you can override a bunch of settings in your POM
>>>>>>> but
>>>>>>> I am not sure about publishing the site to a different host.
>>>>>>>
>>>>>>>
>>>>>> I have quite experience with that setup. So I'll check if we can build a
>>>>>> subsite in our temporal web space, and I'll be back with conclusions
>>>>>> during the weekend.
>>>>>>
>>>>>>
>>>>> I'm assuming the website will be quite small and relatively stable once
>>>>> it's all set up.
>>>>>
>>>>> The choice should be whatever makes the long term running costs low if
>>>>> the
>>>>> setup is all about the same.
>>>>>
>>>>> I have only used CMS/perl for real; the CMS ability edit a page in the
>>>>> browser to quickly fix the small things is great and anyone can do it.
>>>>>
>>>>> If all the CMS choices have that, then I think I'm just -0.5 on raw
>>>>> svnpubsub. ant - don't use it myself anymore. shell - not (easy on)
>>>>> windows.
>>>>>
>>>>> Which leaves:
>>>>>
>>>>> 1 CMS (default-Perl-build)
>>>>> 2 CMS (Maven-build)
>>>>>
>>>>> Andy
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> Java Persistence with Hibernate, Second Edition
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>
>
>
Re: CommonsRDF Website Format
Posted by Stian Soiland-Reyes <st...@apache.org>.
Shall we not just go with option 2 then? It's not like we can't change
our mind if it doesn't work.
I assume this does not require a formal release to update the website :)
On 18 March 2015 at 16:03, Gary Gregory <ga...@gmail.com> wrote:
> Unless someone want to do double work, or not end up with this component in
> Apache Commons, it seems simpler to me to just follow what Apache Commons
> components do.
>
> Gary
>
> On Wed, Mar 18, 2015 at 3:46 AM, Andy Seaborne <an...@apache.org> wrote:
>
>> Moving this onwards:
>>
>> tl;dr:
>>
>> proposal:
>> ask for svnpubsub now
>> not CMS
>> worry about the production of the site later.
>>
>> ------
>> Assumption:
>>
>> I'm assuming that the site is small (what it is, download this, maven
>> that, contribute, support) so for me the choice is a bit "whatever" and low
>> running cost is important. Adding any steps to the release process
>> discourages "release early, release often".
>>
>> [This is an entirely personal and forward looking statement etc etc.]
>>
>> CMS is *possibly* not an option long term (it costs infra to maintain, not
>> all projects use it, it conflicts with gitpubsub.)
>>
>> As CMS hooks into the VCS, gitpubsub is non-zero work so my guess is that
>> some time down the line, there will be a choice for ASF between CMS or
>> gitpubsub on resource grounds.
>>
>> [/]
>>
>> Options, and some pros and cons:
>>
>> Publishing: svnpubsub
>> (and gitpubsub might arrive)
>>
>> then a choice of how the site is made:
>>
>> * Take the CMS perl magic independently
>> Don't see anyone here keen on doing that.
>> The only advantage is not wandering to far from CMS.
>>
>> * Maven plugin (probably many plugin choices)
>> The maven site plugin is too focused inwardly on process.
>> Familiar, in usage and to even to some visitors
>>
>> * Jekyll (c.f. github pages)
>> It's a ruby gem. Needs local setup even if run by maven (?)
>> MSWindows is not 1st class.
>> Jekyll is first-amongst-equals on github.
>>
>> * HTML and whatever you want to do locally to produce that
>> Minimal project implications.
>>
>> * one of the zillions of other templating systems.
>> Baseline should be "obviously better than Jekyll for the project"
>>
>> I know there has been some talk of projects using github pages. I don't
>> know the state of that or what the full implications are.
>>
>> Andy
>>
>> On 12/03/15 16:10, Stian Soiland-Reyes wrote:
>>
>>> The Maven build is also more easily open for Github pull requests - and if
>>> you can use Markdown files they would reasonably render also on Github.
>>>
>>> Commons seems however to use an XML based template system..? (I looked at
>>> Commons Math)
>>>
>>> (note: we can also github mirror the cms from svn - see for example
>>> https://github.com/apache/incubator-taverna-site - its just harder to
>>> apply
>>> patches and to render it)
>>>
>>> With CMS Maven build - can you still use the cms.apache.org "UI" to edit
>>> files?
>>> On 12 Mar 2015 13:03, "Andy Seaborne" <an...@apache.org> wrote:
>>>
>>> On 12/03/15 07:36, Sergio Fernández wrote:
>>>>
>>>> My vote goes to option 2, mainly because the compatibility with the
>>>>> Apache Commons project site.
>>>>>
>>>>> On 11/03/15 23:27, Gary Gregory wrote:
>>>>>
>>>>> On Wed, Mar 11, 2015 at 3:02 PM, Stian Soiland-Reyes <stain@apache.org
>>>>>> >
>>>>>>
>>>>>> Gary, how would we fit into Commons website-wise while incubating?
>>>>>>> Could we
>>>>>>> still use the same system, but publish to
>>>>>>> commonsrdf.incubator.apache.org
>>>>>>> ?
>>>>>>>
>>>>>>>
>>>>>> Good question! I know you can override a bunch of settings in your POM
>>>>>> but
>>>>>> I am not sure about publishing the site to a different host.
>>>>>>
>>>>>>
>>>>> I have quite experience with that setup. So I'll check if we can build a
>>>>> subsite in our temporal web space, and I'll be back with conclusions
>>>>> during the weekend.
>>>>>
>>>>>
>>>> I'm assuming the website will be quite small and relatively stable once
>>>> it's all set up.
>>>>
>>>> The choice should be whatever makes the long term running costs low if
>>>> the
>>>> setup is all about the same.
>>>>
>>>> I have only used CMS/perl for real; the CMS ability edit a page in the
>>>> browser to quickly fix the small things is great and anyone can do it.
>>>>
>>>> If all the CMS choices have that, then I think I'm just -0.5 on raw
>>>> svnpubsub. ant - don't use it myself anymore. shell - not (easy on)
>>>> windows.
>>>>
>>>> Which leaves:
>>>>
>>>> 1 CMS (default-Perl-build)
>>>> 2 CMS (Maven-build)
>>>>
>>>> Andy
>>>>
>>>>
>>>>
>>>
>>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718
Re: CommonsRDF Website Format
Posted by Gary Gregory <ga...@gmail.com>.
Unless someone want to do double work, or not end up with this component in
Apache Commons, it seems simpler to me to just follow what Apache Commons
components do.
Gary
On Wed, Mar 18, 2015 at 3:46 AM, Andy Seaborne <an...@apache.org> wrote:
> Moving this onwards:
>
> tl;dr:
>
> proposal:
> ask for svnpubsub now
> not CMS
> worry about the production of the site later.
>
> ------
> Assumption:
>
> I'm assuming that the site is small (what it is, download this, maven
> that, contribute, support) so for me the choice is a bit "whatever" and low
> running cost is important. Adding any steps to the release process
> discourages "release early, release often".
>
> [This is an entirely personal and forward looking statement etc etc.]
>
> CMS is *possibly* not an option long term (it costs infra to maintain, not
> all projects use it, it conflicts with gitpubsub.)
>
> As CMS hooks into the VCS, gitpubsub is non-zero work so my guess is that
> some time down the line, there will be a choice for ASF between CMS or
> gitpubsub on resource grounds.
>
> [/]
>
> Options, and some pros and cons:
>
> Publishing: svnpubsub
> (and gitpubsub might arrive)
>
> then a choice of how the site is made:
>
> * Take the CMS perl magic independently
> Don't see anyone here keen on doing that.
> The only advantage is not wandering to far from CMS.
>
> * Maven plugin (probably many plugin choices)
> The maven site plugin is too focused inwardly on process.
> Familiar, in usage and to even to some visitors
>
> * Jekyll (c.f. github pages)
> It's a ruby gem. Needs local setup even if run by maven (?)
> MSWindows is not 1st class.
> Jekyll is first-amongst-equals on github.
>
> * HTML and whatever you want to do locally to produce that
> Minimal project implications.
>
> * one of the zillions of other templating systems.
> Baseline should be "obviously better than Jekyll for the project"
>
> I know there has been some talk of projects using github pages. I don't
> know the state of that or what the full implications are.
>
> Andy
>
> On 12/03/15 16:10, Stian Soiland-Reyes wrote:
>
>> The Maven build is also more easily open for Github pull requests - and if
>> you can use Markdown files they would reasonably render also on Github.
>>
>> Commons seems however to use an XML based template system..? (I looked at
>> Commons Math)
>>
>> (note: we can also github mirror the cms from svn - see for example
>> https://github.com/apache/incubator-taverna-site - its just harder to
>> apply
>> patches and to render it)
>>
>> With CMS Maven build - can you still use the cms.apache.org "UI" to edit
>> files?
>> On 12 Mar 2015 13:03, "Andy Seaborne" <an...@apache.org> wrote:
>>
>> On 12/03/15 07:36, Sergio Fernández wrote:
>>>
>>> My vote goes to option 2, mainly because the compatibility with the
>>>> Apache Commons project site.
>>>>
>>>> On 11/03/15 23:27, Gary Gregory wrote:
>>>>
>>>> On Wed, Mar 11, 2015 at 3:02 PM, Stian Soiland-Reyes <stain@apache.org
>>>>> >
>>>>>
>>>>> Gary, how would we fit into Commons website-wise while incubating?
>>>>>> Could we
>>>>>> still use the same system, but publish to
>>>>>> commonsrdf.incubator.apache.org
>>>>>> ?
>>>>>>
>>>>>>
>>>>> Good question! I know you can override a bunch of settings in your POM
>>>>> but
>>>>> I am not sure about publishing the site to a different host.
>>>>>
>>>>>
>>>> I have quite experience with that setup. So I'll check if we can build a
>>>> subsite in our temporal web space, and I'll be back with conclusions
>>>> during the weekend.
>>>>
>>>>
>>> I'm assuming the website will be quite small and relatively stable once
>>> it's all set up.
>>>
>>> The choice should be whatever makes the long term running costs low if
>>> the
>>> setup is all about the same.
>>>
>>> I have only used CMS/perl for real; the CMS ability edit a page in the
>>> browser to quickly fix the small things is great and anyone can do it.
>>>
>>> If all the CMS choices have that, then I think I'm just -0.5 on raw
>>> svnpubsub. ant - don't use it myself anymore. shell - not (easy on)
>>> windows.
>>>
>>> Which leaves:
>>>
>>> 1 CMS (default-Perl-build)
>>> 2 CMS (Maven-build)
>>>
>>> Andy
>>>
>>>
>>>
>>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
Moving this onwards:
tl;dr:
proposal:
ask for svnpubsub now
not CMS
worry about the production of the site later.
------
Assumption:
I'm assuming that the site is small (what it is, download this, maven
that, contribute, support) so for me the choice is a bit "whatever" and
low running cost is important. Adding any steps to the release process
discourages "release early, release often".
[This is an entirely personal and forward looking statement etc etc.]
CMS is *possibly* not an option long term (it costs infra to maintain,
not all projects use it, it conflicts with gitpubsub.)
As CMS hooks into the VCS, gitpubsub is non-zero work so my guess is
that some time down the line, there will be a choice for ASF between CMS
or gitpubsub on resource grounds.
[/]
Options, and some pros and cons:
Publishing: svnpubsub
(and gitpubsub might arrive)
then a choice of how the site is made:
* Take the CMS perl magic independently
Don't see anyone here keen on doing that.
The only advantage is not wandering to far from CMS.
* Maven plugin (probably many plugin choices)
The maven site plugin is too focused inwardly on process.
Familiar, in usage and to even to some visitors
* Jekyll (c.f. github pages)
It's a ruby gem. Needs local setup even if run by maven (?)
MSWindows is not 1st class.
Jekyll is first-amongst-equals on github.
* HTML and whatever you want to do locally to produce that
Minimal project implications.
* one of the zillions of other templating systems.
Baseline should be "obviously better than Jekyll for the project"
I know there has been some talk of projects using github pages. I don't
know the state of that or what the full implications are.
Andy
On 12/03/15 16:10, Stian Soiland-Reyes wrote:
> The Maven build is also more easily open for Github pull requests - and if
> you can use Markdown files they would reasonably render also on Github.
>
> Commons seems however to use an XML based template system..? (I looked at
> Commons Math)
>
> (note: we can also github mirror the cms from svn - see for example
> https://github.com/apache/incubator-taverna-site - its just harder to apply
> patches and to render it)
>
> With CMS Maven build - can you still use the cms.apache.org "UI" to edit
> files?
> On 12 Mar 2015 13:03, "Andy Seaborne" <an...@apache.org> wrote:
>
>> On 12/03/15 07:36, Sergio Fernández wrote:
>>
>>> My vote goes to option 2, mainly because the compatibility with the
>>> Apache Commons project site.
>>>
>>> On 11/03/15 23:27, Gary Gregory wrote:
>>>
>>>> On Wed, Mar 11, 2015 at 3:02 PM, Stian Soiland-Reyes <st...@apache.org>
>>>>
>>>>> Gary, how would we fit into Commons website-wise while incubating?
>>>>> Could we
>>>>> still use the same system, but publish to
>>>>> commonsrdf.incubator.apache.org
>>>>> ?
>>>>>
>>>>
>>>> Good question! I know you can override a bunch of settings in your POM
>>>> but
>>>> I am not sure about publishing the site to a different host.
>>>>
>>>
>>> I have quite experience with that setup. So I'll check if we can build a
>>> subsite in our temporal web space, and I'll be back with conclusions
>>> during the weekend.
>>>
>>
>> I'm assuming the website will be quite small and relatively stable once
>> it's all set up.
>>
>> The choice should be whatever makes the long term running costs low if the
>> setup is all about the same.
>>
>> I have only used CMS/perl for real; the CMS ability edit a page in the
>> browser to quickly fix the small things is great and anyone can do it.
>>
>> If all the CMS choices have that, then I think I'm just -0.5 on raw
>> svnpubsub. ant - don't use it myself anymore. shell - not (easy on)
>> windows.
>>
>> Which leaves:
>>
>> 1 CMS (default-Perl-build)
>> 2 CMS (Maven-build)
>>
>> Andy
>>
>>
>
Re: [VOTE] CommonsRDF Website Format
Posted by Stian Soiland-Reyes <st...@apache.org>.
The Maven build is also more easily open for Github pull requests - and if
you can use Markdown files they would reasonably render also on Github.
Commons seems however to use an XML based template system..? (I looked at
Commons Math)
(note: we can also github mirror the cms from svn - see for example
https://github.com/apache/incubator-taverna-site - its just harder to apply
patches and to render it)
With CMS Maven build - can you still use the cms.apache.org "UI" to edit
files?
On 12 Mar 2015 13:03, "Andy Seaborne" <an...@apache.org> wrote:
> On 12/03/15 07:36, Sergio Fernández wrote:
>
>> My vote goes to option 2, mainly because the compatibility with the
>> Apache Commons project site.
>>
>> On 11/03/15 23:27, Gary Gregory wrote:
>>
>>> On Wed, Mar 11, 2015 at 3:02 PM, Stian Soiland-Reyes <st...@apache.org>
>>>
>>>> Gary, how would we fit into Commons website-wise while incubating?
>>>> Could we
>>>> still use the same system, but publish to
>>>> commonsrdf.incubator.apache.org
>>>> ?
>>>>
>>>
>>> Good question! I know you can override a bunch of settings in your POM
>>> but
>>> I am not sure about publishing the site to a different host.
>>>
>>
>> I have quite experience with that setup. So I'll check if we can build a
>> subsite in our temporal web space, and I'll be back with conclusions
>> during the weekend.
>>
>
> I'm assuming the website will be quite small and relatively stable once
> it's all set up.
>
> The choice should be whatever makes the long term running costs low if the
> setup is all about the same.
>
> I have only used CMS/perl for real; the CMS ability edit a page in the
> browser to quickly fix the small things is great and anyone can do it.
>
> If all the CMS choices have that, then I think I'm just -0.5 on raw
> svnpubsub. ant - don't use it myself anymore. shell - not (easy on)
> windows.
>
> Which leaves:
>
> 1 CMS (default-Perl-build)
> 2 CMS (Maven-build)
>
> Andy
>
>
Re: [VOTE] CommonsRDF Website Format
Posted by Andy Seaborne <an...@apache.org>.
On 12/03/15 07:36, Sergio Fernández wrote:
> My vote goes to option 2, mainly because the compatibility with the
> Apache Commons project site.
>
> On 11/03/15 23:27, Gary Gregory wrote:
>> On Wed, Mar 11, 2015 at 3:02 PM, Stian Soiland-Reyes <st...@apache.org>
>>> Gary, how would we fit into Commons website-wise while incubating?
>>> Could we
>>> still use the same system, but publish to
>>> commonsrdf.incubator.apache.org
>>> ?
>>
>> Good question! I know you can override a bunch of settings in your POM
>> but
>> I am not sure about publishing the site to a different host.
>
> I have quite experience with that setup. So I'll check if we can build a
> subsite in our temporal web space, and I'll be back with conclusions
> during the weekend.
I'm assuming the website will be quite small and relatively stable once
it's all set up.
The choice should be whatever makes the long term running costs low if
the setup is all about the same.
I have only used CMS/perl for real; the CMS ability edit a page in the
browser to quickly fix the small things is great and anyone can do it.
If all the CMS choices have that, then I think I'm just -0.5 on raw
svnpubsub. ant - don't use it myself anymore. shell - not (easy on)
windows.
Which leaves:
1 CMS (default-Perl-build)
2 CMS (Maven-build)
Andy
Re: [VOTE] CommonsRDF Website Format
Posted by Sergio Fernández <wi...@apache.org>.
My vote goes to option 2, mainly because the compatibility with the
Apache Commons project site.
On 11/03/15 23:27, Gary Gregory wrote:
> On Wed, Mar 11, 2015 at 3:02 PM, Stian Soiland-Reyes <st...@apache.org>
>> Gary, how would we fit into Commons website-wise while incubating? Could we
>> still use the same system, but publish to commonsrdf.incubator.apache.org
>> ?
>
> Good question! I know you can override a bunch of settings in your POM but
> I am not sure about publishing the site to a different host.
I have quite experience with that setup. So I'll check if we can build a
subsite in our temporal web space, and I'll be back with conclusions
during the weekend.
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: [VOTE] CommonsRDF Website Format
Posted by Gary Gregory <ga...@gmail.com>.
On Wed, Mar 11, 2015 at 3:02 PM, Stian Soiland-Reyes <st...@apache.org>
wrote:
> +1 for the Maven approach, it was straightforward for me to try when
> attempting to modify a Commons webpage, I like that you can just build it
> locally, and unlike stuff like Jekyll or the default perl CMS, no strange
> system libraries to install.
>
> Gary, how would we fit into Commons website-wise while incubating? Could we
> still use the same system, but publish to commonsrdf.incubator.apache.org
> ?
>
Good question! I know you can override a bunch of settings in your POM but
I am not sure about publishing the site to a different host.
You can at least build the whole site with Maven.
Gary
> On 11 Mar 2015 21:01, "Gary Gregory" <ga...@gmail.com> wrote:
>
> > I do not think this VOTE is needed.
> >
> > If this component is to live in the Commons project, we already have all
> > that set up. Just see the site for any the recent components like
> > https://commons.apache.org/proper/commons-codec/. We have a parent POM
> to
> > handle common stuff between components. There are some variations between
> > the sites for components, sure, but nothing major.
> >
> > Gary
> >
> > On Wed, Mar 11, 2015 at 1:31 PM, Lewis John Mcgibbney <
> > lewis.mcgibbney@gmail.com> wrote:
> >
> > > Hi Folks,
> > > Based on Geoffrey Core's request on INFRA-9260 [0], I would like to
> open
> > an
> > > VOTE for the website build layout. The VOTE will be open for at least
> 72
> > > hours.
> > >
> > > Options are
> > >
> > > 0 svnpubsub
> > > 1 CMS (default-Perl-build)
> > > 2 CMS (Maven-build)
> > > 3 CMS (Ant-build)
> > > 4 CMS (Shell-build)
> > >
> > > [ ] +1 I VOTE for option ${insert option here}
> > > [ ] +/-0 I don't care either way but would rather see ${insert option
> > here}
> > > [ ] -1 I hate them all and I am not having a good day
> > >
> > > Thanks
> > > Lewis
> > >
> > > [0] https://issues.apache.org/jira/browse/INFRA-9260
> > >
> > > --
> > > *Lewis*
> > >
> >
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > Java Persistence with Hibernate, Second Edition
> > <http://www.manning.com/bauer3/>
> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > Spring Batch in Action <http://www.manning.com/templier/>
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [VOTE] CommonsRDF Website Format
Posted by Stian Soiland-Reyes <st...@apache.org>.
+1 for the Maven approach, it was straightforward for me to try when
attempting to modify a Commons webpage, I like that you can just build it
locally, and unlike stuff like Jekyll or the default perl CMS, no strange
system libraries to install.
Gary, how would we fit into Commons website-wise while incubating? Could we
still use the same system, but publish to commonsrdf.incubator.apache.org?
On 11 Mar 2015 21:01, "Gary Gregory" <ga...@gmail.com> wrote:
> I do not think this VOTE is needed.
>
> If this component is to live in the Commons project, we already have all
> that set up. Just see the site for any the recent components like
> https://commons.apache.org/proper/commons-codec/. We have a parent POM to
> handle common stuff between components. There are some variations between
> the sites for components, sure, but nothing major.
>
> Gary
>
> On Wed, Mar 11, 2015 at 1:31 PM, Lewis John Mcgibbney <
> lewis.mcgibbney@gmail.com> wrote:
>
> > Hi Folks,
> > Based on Geoffrey Core's request on INFRA-9260 [0], I would like to open
> an
> > VOTE for the website build layout. The VOTE will be open for at least 72
> > hours.
> >
> > Options are
> >
> > 0 svnpubsub
> > 1 CMS (default-Perl-build)
> > 2 CMS (Maven-build)
> > 3 CMS (Ant-build)
> > 4 CMS (Shell-build)
> >
> > [ ] +1 I VOTE for option ${insert option here}
> > [ ] +/-0 I don't care either way but would rather see ${insert option
> here}
> > [ ] -1 I hate them all and I am not having a good day
> >
> > Thanks
> > Lewis
> >
> > [0] https://issues.apache.org/jira/browse/INFRA-9260
> >
> > --
> > *Lewis*
> >
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
Re: [VOTE] CommonsRDF Website Format
Posted by Gary Gregory <ga...@gmail.com>.
I do not think this VOTE is needed.
If this component is to live in the Commons project, we already have all
that set up. Just see the site for any the recent components like
https://commons.apache.org/proper/commons-codec/. We have a parent POM to
handle common stuff between components. There are some variations between
the sites for components, sure, but nothing major.
Gary
On Wed, Mar 11, 2015 at 1:31 PM, Lewis John Mcgibbney <
lewis.mcgibbney@gmail.com> wrote:
> Hi Folks,
> Based on Geoffrey Core's request on INFRA-9260 [0], I would like to open an
> VOTE for the website build layout. The VOTE will be open for at least 72
> hours.
>
> Options are
>
> 0 svnpubsub
> 1 CMS (default-Perl-build)
> 2 CMS (Maven-build)
> 3 CMS (Ant-build)
> 4 CMS (Shell-build)
>
> [ ] +1 I VOTE for option ${insert option here}
> [ ] +/-0 I don't care either way but would rather see ${insert option here}
> [ ] -1 I hate them all and I am not having a good day
>
> Thanks
> Lewis
>
> [0] https://issues.apache.org/jira/browse/INFRA-9260
>
> --
> *Lewis*
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory