You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Emmanuel Venisse <em...@venisse.net> on 2007/03/30 21:06:35 UTC
Re: confluence
Jason van Zyl a écrit :
>
> On 30 Mar 07, at 10:49 AM 30 Mar 07, Brett Porter wrote:
>
>> While you make plenty of valid points about Contegix, it's completely
>> unrelated to what I'm arguing for.
>
> How is starting to move things away from Contegix, which is you
> suggestion, not related? The subsequent argument would then be made that
> we already started this process so why not move the rest. Of course it's
> related.
>
>> If you are successful in bringing them in to the ASF infrastructure as
>> you've proposed, it should be a no-brainer to move a cwiki space to
>> that infrastructure. So that's a non-issue as far as this discussion
>> is concerned.
>>
>> We're better off on cwiki than where we are now. We have no admin
>> privileges (I'm currently locked out of editing the CONTINUUM space)
>
> Did you ask? I asked Ben for JIRA privs and that took 5 minutes.
>
>> , and the setup is not conducive to deploying into the Apache site.
>> cwiki is already running the stuff we need. People I trust recommend it.
>>
>
> The stuff is a plugin which can be installed in any Confluence instance.
> So that's not an onerous task.
>
>> We've wanted to do this for months, and this is an avenue that
>> actually makes it easier for us - I continue to suggest we take it.
>>
>
> I'm simply not in favour of moving anything away from Contegix. Taking
> the output from the export plugin and scp'ing it to people is not hard
> either.
If Ben is ok to install the plugin and if we can manage the scp to people, it's ok for me. But I don't know how we'll can manage it, we don't have shell access to codehaus.
Emmanuel
>
> Jason.
>
>> - Brett
>>
>> On 31/03/2007, at 12:23 AM, Jason van Zyl wrote:
>>
>>> On 28 Mar 07, at 5:22 PM 28 Mar 07, Brett Porter wrote:
>>>
>>>> (moving to main dev list as scope has increased)
>>>>
>>>> On 29/03/2007, at 12:28 AM, Jason van Zyl wrote:
>>>>
>>>> Similar to what Emmanuel suggested, how about we move *all* the
>>>> current spaces to cwiki, avoiding any further fragmentation, and in
>>>> fact removing the current fragmentation between the apache site and
>>>> the codehaus confluence, as well as getting all of the above benefits?
>>>>
>>>> Before biting the bullet we can do a trial with this single SCM page.
>>>>
>>>> What do folks think?
>>>>
>>>
>>> I think it's a bad idea to move from a stable setup we have with
>>> great support from people who have helped us at every turn. I would
>>> like to suggest we stay with Contegix wherever possible and this
>>> discussion is still ongoing with infra and they have yet to get back
>>> with SLA policies. I believe it is in the best interest of users and
>>> the community to provide the best infrastructure as possible and
>>> there is no doubt in my mind that is Contegix. For anything we have
>>> ever done for JIRA, Confluence or the Central Repository they have
>>> been there for us. We gain nothing by moving any of this to Apache.
>>>
>>> Contegix has run JIRA and Confluence for us when these services were
>>> not available at Apache and they have been more than accommodating
>>> when we needed a new repository infrastructure.
>>>
>>> I have been trying to incorporate Contegix officially into the
>>> infrastructure at Apache so that we can keep everyone happy. I am not
>>> willing, nor do I support any move to Apache without infra deciding
>>> their policies, nor am I overly excited about the possibility of any
>>> of our infrastructure being moved to a place where no one is really
>>> accountable. Contegix is responsible, accountable, a pleasure to work
>>> with and they have bent over backward to help us. We are relying on
>>> Jeff Turner who is already overworked in trying to manage our setup
>>> whereas at Contegix we have a team who are very knowledgeable about
>>> Atlassian products because they resell them. We also have people here
>>> who's first response is a derisive comment about the tools we use.
>>>
>>> My vote is for Contegix to continue the great job they have done and
>>> seeing as infra has not decided anything or contacted me after I
>>> attended the last board meeting, I am going to go ahead with an
>>> official proposal starting with our PMC to let each PMC decide on
>>> their infrastructure needs and use whomever they like working on the
>>> integration strategies and policies that will make everyone
>>> comfortable. Until that time I don't think it's prudent because you
>>> will potentially jeopardize the infrastructure used by everyone
>>> using Maven.
>>>
>>> Jason.
>>>
>>>> Cheers,
>>>> Brett
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: confluence
Posted by Jason Dillon <ja...@planet57.com>.
There are some issues with autoexport, you guys might want to take a
peek at the HokeyPokey's exportspace command:
http://svn.apache.org/repos/asf/geronimo/sandbox/hokeypokey/trunk/
Its still a work in progress, but it basically exports a space via
xmlrpc and applies a velocity template and then does some massaging
of urls. Currently the massaging is hardcoded... the rules need to
be externalized. And the multi-space exporter needs to be hooked up
too.
But, the idea is to have a regular cron job execute the exporter
using templates and resources that are checked into svn, which makes
it easier to manage and allows for better oversight of template changes.
And by using this method pages with dynamic tags (like include or
jiraissues, etc) will also get refreshed.
Anyways... its a work in progress, but worth a look if you are just
getting started.
--jason
On Mar 30, 2007, at 12:19 PM, Jason van Zyl wrote:
>
> On 30 Mar 07, at 3:06 PM 30 Mar 07, Emmanuel Venisse wrote:
>
>>
>>
>> Jason van Zyl a écrit :
>>> On 30 Mar 07, at 10:49 AM 30 Mar 07, Brett Porter wrote:
>>>> While you make plenty of valid points about Contegix, it's
>>>> completely unrelated to what I'm arguing for.
>>> How is starting to move things away from Contegix, which is you
>>> suggestion, not related? The subsequent argument would then be
>>> made that we already started this process so why not move the
>>> rest. Of course it's related.
>>>> If you are successful in bringing them in to the ASF
>>>> infrastructure as you've proposed, it should be a no-brainer to
>>>> move a cwiki space to that infrastructure. So that's a non-issue
>>>> as far as this discussion is concerned.
>>>>
>>>> We're better off on cwiki than where we are now. We have no
>>>> admin privileges (I'm currently locked out of editing the
>>>> CONTINUUM space)
>>> Did you ask? I asked Ben for JIRA privs and that took 5 minutes.
>>>> , and the setup is not conducive to deploying into the Apache
>>>> site. cwiki is already running the stuff we need. People I trust
>>>> recommend it.
>>>>
>>> The stuff is a plugin which can be installed in any Confluence
>>> instance. So that's not an onerous task.
>>>> We've wanted to do this for months, and this is an avenue that
>>>> actually makes it easier for us - I continue to suggest we take it.
>>>>
>>> I'm simply not in favour of moving anything away from Contegix.
>>> Taking the output from the export plugin and scp'ing it to people
>>> is not hard either.
>>
>> If Ben is ok to install the plugin and if we can manage the scp to
>> people, it's ok for me. But I don't know how we'll can manage it,
>> we don't have shell access to codehaus.
>>
>
> The plugin will be installed and the PMC will have access:
>
> http://jira.codehaus.org/browse/HAUS-1489
>
> Jason.
>
>> Emmanuel
>>
>>> Jason.
>>>> - Brett
>>>>
>>>> On 31/03/2007, at 12:23 AM, Jason van Zyl wrote:
>>>>
>>>>> On 28 Mar 07, at 5:22 PM 28 Mar 07, Brett Porter wrote:
>>>>>
>>>>>> (moving to main dev list as scope has increased)
>>>>>>
>>>>>> On 29/03/2007, at 12:28 AM, Jason van Zyl wrote:
>>>>>>
>>>>>> Similar to what Emmanuel suggested, how about we move *all*
>>>>>> the current spaces to cwiki, avoiding any further
>>>>>> fragmentation, and in fact removing the current fragmentation
>>>>>> between the apache site and the codehaus confluence, as well
>>>>>> as getting all of the above benefits?
>>>>>>
>>>>>> Before biting the bullet we can do a trial with this single
>>>>>> SCM page.
>>>>>>
>>>>>> What do folks think?
>>>>>>
>>>>>
>>>>> I think it's a bad idea to move from a stable setup we have
>>>>> with great support from people who have helped us at every
>>>>> turn. I would like to suggest we stay with Contegix wherever
>>>>> possible and this discussion is still ongoing with infra and
>>>>> they have yet to get back with SLA policies. I believe it is in
>>>>> the best interest of users and the community to provide the
>>>>> best infrastructure as possible and there is no doubt in my
>>>>> mind that is Contegix. For anything we have ever done for JIRA,
>>>>> Confluence or the Central Repository they have been there for
>>>>> us. We gain nothing by moving any of this to Apache.
>>>>>
>>>>> Contegix has run JIRA and Confluence for us when these services
>>>>> were not available at Apache and they have been more than
>>>>> accommodating when we needed a new repository infrastructure.
>>>>>
>>>>> I have been trying to incorporate Contegix officially into the
>>>>> infrastructure at Apache so that we can keep everyone happy. I
>>>>> am not willing, nor do I support any move to Apache without
>>>>> infra deciding their policies, nor am I overly excited about
>>>>> the possibility of any of our infrastructure being moved to a
>>>>> place where no one is really accountable. Contegix is
>>>>> responsible, accountable, a pleasure to work with and they have
>>>>> bent over backward to help us. We are relying on Jeff Turner
>>>>> who is already overworked in trying to manage our setup whereas
>>>>> at Contegix we have a team who are very knowledgeable about
>>>>> Atlassian products because they resell them. We also have
>>>>> people here who's first response is a derisive comment about
>>>>> the tools we use.
>>>>>
>>>>> My vote is for Contegix to continue the great job they have
>>>>> done and seeing as infra has not decided anything or contacted
>>>>> me after I attended the last board meeting, I am going to go
>>>>> ahead with an official proposal starting with our PMC to let
>>>>> each PMC decide on their infrastructure needs and use whomever
>>>>> they like working on the integration strategies and policies
>>>>> that will make everyone comfortable. Until that time I don't
>>>>> think it's prudent because you will potentially jeopardize the
>>>>> infrastructure used by everyone using Maven.
>>>>>
>>>>> Jason.
>>>>>
>>>>>> Cheers,
>>>>>> Brett
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> ----
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: confluence
Posted by Jason van Zyl <ja...@maven.org>.
On 30 Mar 07, at 3:06 PM 30 Mar 07, Emmanuel Venisse wrote:
>
>
> Jason van Zyl a écrit :
>> On 30 Mar 07, at 10:49 AM 30 Mar 07, Brett Porter wrote:
>>> While you make plenty of valid points about Contegix, it's
>>> completely unrelated to what I'm arguing for.
>> How is starting to move things away from Contegix, which is you
>> suggestion, not related? The subsequent argument would then be
>> made that we already started this process so why not move the
>> rest. Of course it's related.
>>> If you are successful in bringing them in to the ASF
>>> infrastructure as you've proposed, it should be a no-brainer to
>>> move a cwiki space to that infrastructure. So that's a non-issue
>>> as far as this discussion is concerned.
>>>
>>> We're better off on cwiki than where we are now. We have no admin
>>> privileges (I'm currently locked out of editing the CONTINUUM space)
>> Did you ask? I asked Ben for JIRA privs and that took 5 minutes.
>>> , and the setup is not conducive to deploying into the Apache
>>> site. cwiki is already running the stuff we need. People I trust
>>> recommend it.
>>>
>> The stuff is a plugin which can be installed in any Confluence
>> instance. So that's not an onerous task.
>>> We've wanted to do this for months, and this is an avenue that
>>> actually makes it easier for us - I continue to suggest we take it.
>>>
>> I'm simply not in favour of moving anything away from Contegix.
>> Taking the output from the export plugin and scp'ing it to people
>> is not hard either.
>
> If Ben is ok to install the plugin and if we can manage the scp to
> people, it's ok for me. But I don't know how we'll can manage it,
> we don't have shell access to codehaus.
>
The plugin will be installed and the PMC will have access:
http://jira.codehaus.org/browse/HAUS-1489
Jason.
> Emmanuel
>
>> Jason.
>>> - Brett
>>>
>>> On 31/03/2007, at 12:23 AM, Jason van Zyl wrote:
>>>
>>>> On 28 Mar 07, at 5:22 PM 28 Mar 07, Brett Porter wrote:
>>>>
>>>>> (moving to main dev list as scope has increased)
>>>>>
>>>>> On 29/03/2007, at 12:28 AM, Jason van Zyl wrote:
>>>>>
>>>>> Similar to what Emmanuel suggested, how about we move *all* the
>>>>> current spaces to cwiki, avoiding any further fragmentation,
>>>>> and in fact removing the current fragmentation between the
>>>>> apache site and the codehaus confluence, as well as getting all
>>>>> of the above benefits?
>>>>>
>>>>> Before biting the bullet we can do a trial with this single SCM
>>>>> page.
>>>>>
>>>>> What do folks think?
>>>>>
>>>>
>>>> I think it's a bad idea to move from a stable setup we have with
>>>> great support from people who have helped us at every turn. I
>>>> would like to suggest we stay with Contegix wherever possible
>>>> and this discussion is still ongoing with infra and they have
>>>> yet to get back with SLA policies. I believe it is in the best
>>>> interest of users and the community to provide the best
>>>> infrastructure as possible and there is no doubt in my mind that
>>>> is Contegix. For anything we have ever done for JIRA, Confluence
>>>> or the Central Repository they have been there for us. We gain
>>>> nothing by moving any of this to Apache.
>>>>
>>>> Contegix has run JIRA and Confluence for us when these services
>>>> were not available at Apache and they have been more than
>>>> accommodating when we needed a new repository infrastructure.
>>>>
>>>> I have been trying to incorporate Contegix officially into the
>>>> infrastructure at Apache so that we can keep everyone happy. I
>>>> am not willing, nor do I support any move to Apache without
>>>> infra deciding their policies, nor am I overly excited about the
>>>> possibility of any of our infrastructure being moved to a place
>>>> where no one is really accountable. Contegix is responsible,
>>>> accountable, a pleasure to work with and they have bent over
>>>> backward to help us. We are relying on Jeff Turner who is
>>>> already overworked in trying to manage our setup whereas at
>>>> Contegix we have a team who are very knowledgeable about
>>>> Atlassian products because they resell them. We also have people
>>>> here who's first response is a derisive comment about the tools
>>>> we use.
>>>>
>>>> My vote is for Contegix to continue the great job they have done
>>>> and seeing as infra has not decided anything or contacted me
>>>> after I attended the last board meeting, I am going to go ahead
>>>> with an official proposal starting with our PMC to let each PMC
>>>> decide on their infrastructure needs and use whomever they like
>>>> working on the integration strategies and policies that will
>>>> make everyone comfortable. Until that time I don't think it's
>>>> prudent because you will potentially jeopardize the
>>>> infrastructure used by everyone using Maven.
>>>>
>>>> Jason.
>>>>
>>>>> Cheers,
>>>>> Brett
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org