You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@any23.apache.org by Lewis John Mcgibbney <le...@gmail.com> on 2012/01/09 15:03:25 UTC
Any23 Roadmap [WAS] Re: Googlegroup or Apache SVN
Hi tomasso. Thanks for your comments. I am happy to progress with the
website task [1] but I think it would be beneficial to consider a few
points at this stage.
1) We discussed briefly moving the existing site documentation out of the
trunk codebase to its own separate directory within our Any23 SVN area.
Does anyone have any thoughts on running this over the ASF CMS? I have been
trying to get up to speed with it but to be honest I'm a bit unclear as to
where to get started with this... I'm waiting on hearing back from some
people I've asked but if anyone is up to speed with this then please say
so.
So just to clarify...
Michele,
Can you confirm that all recent changes made to the Googlecode can be
ported to the ASF Any23 code residing in our SVN area?
Thank you Lewis
[1] https://issues.apache.org/jira/browse/ANY23-9
On Saturday, January 7, 2012, Tommaso Teofili <to...@apache.org> wrote:
> Hi all,
>
> first of all thanks Michele and Lewis for your efforts and Chris for doing
> your role of champion and mentor much better than me so far :)
>
> I think Chris clarified things well and I agree with his points,
especially
> the project needs all the committers to get up to speed here so if any of
> you feels like needing any clarifications and/or support on doing
something
> then just let me know and I'll be happy to help out.
>
> By the way, I think that one thing that may be help users (especially when
> switching from GC to Apache) is having our website published; in fact
> incubator.apache.org/any23 is still "empty" while one thing that help us
as
> PPMC members to let the project develop is a roadmap.
>
> My 2 cents.
> Tommaso
>
> 2012/1/7 Mattmann, Chris A (388J) <ch...@jpl.nasa.gov>
>
>> Hi Michele,
>>
>> On Jan 7, 2012, at 11:34 AM, Michele Mostarda wrote:
>>
>> >>
>> >>
>> >> 1. Who are the Sindice team?
>> >>
>> >
>> > Giovanni Tummarello, Michele Mostarda, Davide Palmisano, Szymon
>> Danielczyk.
>>
>> Gotcha, thanks.
>>
>> >
>> >
>> >> 2. When was it agreed that they would or could even approve of
>> >> moving the code *after* the 0.7.0 release?
>> >>
>> >
>> > We didn't find an agreement, we continued developing on Any23 while
>> waiting
>> > for
>> > the initial code import on the Apache repository.
>>
>> Well the "we" here is important. The only one of those folks you listed
>> above
>> that I've seen make any effort towards the code import at the ASF has
been
>> you. Hats
>> off to you. But things don't get done in Apache by waiting for things to
>> get done.
>> They get done by volunteers like yourself stepping it up and pushing for
>> stuff
>> to get done. I don't have a ton of time (or understanding) to do a lot of
>> the code
>> importing or development myself here, and that's fine, b/c what I do have
>> time
>> to do is to help you guys learn the Apache way and become familiar with
the
>> community. That's the role I'm trying to play here as mentor and as
>> Champion
>> for the project at the Apache Software Foundation. But others in the
Apache
>> Any23 community need to step up here too and do their work at the ASF.
>>
>> >
>> > The Any23 Incubation proposal was accepted when the 0.7.0 release was
>> ready
>> > at
>> > 60%, we didn't expect an instant freeze of the code base, out of a
>> > milestone.
>>
>> The Any23 (prior to Apache) team didn't have to freeze anything and it
>> probably
>> should have been better clarified where you guys were in terms of the
code
>> base as part of your Incubator proposal. But regardless, once the
proposal
>> was accepted in the Incubator there needed to be steps taken to start
>> getting the code to Apache. The process steps were taken (Software Code
>> Grant, etc.), but only recently over the past few months has there been
>> effort (led primarily by you and Daniel Shahaf by me minimally via my
>> nudging)
>> to get the code in to the ASF SVN.
>>
>> Even if the code wasn't fully imported yet, I would expect development
>> towards
>> any releases outside of Apache to stop -- it's just easier. Why develop
in
>> both
>> places when nothing is stopping anyone from developing here at the ASF?
If
>> there is something stopping anyone on the Any23 team, please speak up?
>>
>> >
>> >
>> >> It is my understanding that when you guys proposed for this to be
>> >> an Apache project, and when you filed a proposal to join the Incubator
>> >> that all of the parallel development at Google Code would stop,
period.
>> >>
>> >> To be blunt:
>> >>
>> >> 1. There shouldn't be any parallel development release going on, or
>> >> code work going on at Google Code anymore.
>> >>
>> >
>> > Let's interrupt all the development on Any23. I will update the
>> > announcement,
>> > the 0.7.0 release will be done within the ASF.
>>
>> OK great, but I wouldn't characterize anything as an interrupt -
>> what are we interrupting by saying that the 0.7.0 release will
>> occur at the ASF?
>>
>> Are we not talking simply about:
>>
>> 1. updated link to where to download the release tarball from
>> 2. updated package names in the code
>> 3. updated docs on the website
>>
>> Correct?
>>
>> >
>> > What we have to do with the releases from r1548 (we imported on the ASF
>> SVN
>> > the revisions
>> > from r0 to 1547) to r1607 (the latest commit on the Google SVN related
to
>> > the milestone 0.7.0) ?
>> > I would provide an incremental dump to be applied on the initial
import.
>> > Please let me know.
>>
>> That would work fine, but would involve ASF infrastructure as well, and
>> they
>> are also time limited. If you or any one of the other guys on Apache
Any23
>> want to spearhead it yourself, just create a JIRA issue here at the Any23
>> ASF JIRA to
>> track the provenance, and then do the svn import yourself. You should
have
>> the n
Re: Any23 Roadmap [WAS] Re: Googlegroup or Apache SVN
Posted by Michele Mostarda <mi...@gmail.com>.
On 10 January 2012 17:14, Lewis John Mcgibbney <le...@gmail.com>wrote:
> Yeah +1 Michele to your patch. I think whatever makes life easiest for us
> whilst maintaining some level of traceability should be implemented.
>
Well, the patch has been applied as tracked on issue ANY23-23.
Please confirm next steps:
1. Update packages (ANY23-21)
2. Update headers (ANY23-21 or a dedicated issue ?)
3. Bug fixing (opening some issues to report possible bugs that need to be
verified)
4. Plan release
I created an issue (ANY23-29) to link all the tasks related to the code
base migration.
The best.
Mic
>
> On Tue, Jan 10, 2012 at 3:39 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
> > Hey Michele,
> >
> > On Jan 10, 2012, at 3:46 AM, Michele Mostarda wrote:
> >
> > > On 10 January 2012 11:19, Michele Mostarda <michele.mostarda@gmail.com
> > >wrote:
> > >
> > >>
> > >>
> > >> On 9 January 2012 15:03, Lewis John Mcgibbney <
> > lewis.mcgibbney@gmail.com>wrote:
> > >>
> > >>> Hi tomasso. Thanks for your comments. I am happy to progress with
> the
> > >>> website task [1] but I think it would be beneficial to consider a few
> > >>> points at this stage.
> > >>>
> > >>
> > >> Thanks Lewis,
> > >>
> > >>
> > >>> 1) We discussed briefly moving the existing site documentation out of
> > the
> > >>> trunk codebase to its own separate directory within our Any23 SVN
> area.
> > >>> Does anyone have any thoughts on running this over the ASF CMS? I
> have
> > >>> been
> > >>> trying to get up to speed with it but to be honest I'm a bit unclear
> > as to
> > >>> where to get started with this... I'm waiting on hearing back from
> some
> > >>> people I've asked but if anyone is up to speed with this then please
> > say
> > >>> so.
> > >>>
> > >>> So just to clarify...
> > >>>
> > >>> Michele,
> > >>>
> > >>> Can you confirm that all recent changes made to the Googlecode can be
> > >>> ported to the ASF Any23 code residing in our SVN area?
> > >>>
> > >>
> > >> Not yet, we still miss on the ASF repo the revisions from r1548 to
> > r1607.
> > >> I just opened an issue: [1].
> > >>
> > >> Which is the best way to synch the repositories without producing an
> > >> incremental svn dump? (Chris asked to avoid the ASF INFRA guys
> further).
> > >> I can try with 'svn sync' but I'm not sure it works (1). This would
> > allow
> > >> to preserve also the SVN logs.
> > >> The other solution is to produce a patch and apply it on the ASF SVN
> > (2).
> > >> This will cause the lost of the SVN logs.
> > >> The definitive solution would be to import patch by patch all the
> > >> revisions (3), but it is really time consuming.
> > >>
> > >> Attempting with (1) first.
> > >>
> > >
> > > Solution (1) is not applicable with standard SVN tools, may be somebody
> > > knows some python-ish script that can be used for this purpose.
> > > Meanwhile I attempted with solution (2), I have merged the
> modifications
> > in
> > > a single patch ready to be committed.
> > > Waiting for your confirmation.
> > >
> > > Chris, do you agree?
> >
> > I'm fine either way. If you want to ask infra@ that's OK too I was just
> > saying that
> > it might take them too long in case you wanted to get going or this is
> > holding us
> > up. In that case, a patch is fine IMO. We're not too too far off in
> > revisions and
> > even if it's a big patch, we still have the history, just not
> > incrementally.
> >
> > +1 for patch, or whatever you (who is doing the work) decides :)
> >
> > Cheers,
> > Chris
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: chris.a.mattmann@nasa.gov
> > WWW: http://sunset.usc.edu/~mattmann/
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Adjunct Assistant Professor, Computer Science Department
> > University of Southern California, Los Angeles, CA 90089 USA
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
>
>
> --
> *Lewis*
>
--
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com
Re: Any23 Roadmap [WAS] Re: Googlegroup or Apache SVN
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Yeah +1 Michele to your patch. I think whatever makes life easiest for us
whilst maintaining some level of traceability should be implemented.
On Tue, Jan 10, 2012 at 3:39 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hey Michele,
>
> On Jan 10, 2012, at 3:46 AM, Michele Mostarda wrote:
>
> > On 10 January 2012 11:19, Michele Mostarda <michele.mostarda@gmail.com
> >wrote:
> >
> >>
> >>
> >> On 9 January 2012 15:03, Lewis John Mcgibbney <
> lewis.mcgibbney@gmail.com>wrote:
> >>
> >>> Hi tomasso. Thanks for your comments. I am happy to progress with the
> >>> website task [1] but I think it would be beneficial to consider a few
> >>> points at this stage.
> >>>
> >>
> >> Thanks Lewis,
> >>
> >>
> >>> 1) We discussed briefly moving the existing site documentation out of
> the
> >>> trunk codebase to its own separate directory within our Any23 SVN area.
> >>> Does anyone have any thoughts on running this over the ASF CMS? I have
> >>> been
> >>> trying to get up to speed with it but to be honest I'm a bit unclear
> as to
> >>> where to get started with this... I'm waiting on hearing back from some
> >>> people I've asked but if anyone is up to speed with this then please
> say
> >>> so.
> >>>
> >>> So just to clarify...
> >>>
> >>> Michele,
> >>>
> >>> Can you confirm that all recent changes made to the Googlecode can be
> >>> ported to the ASF Any23 code residing in our SVN area?
> >>>
> >>
> >> Not yet, we still miss on the ASF repo the revisions from r1548 to
> r1607.
> >> I just opened an issue: [1].
> >>
> >> Which is the best way to synch the repositories without producing an
> >> incremental svn dump? (Chris asked to avoid the ASF INFRA guys further).
> >> I can try with 'svn sync' but I'm not sure it works (1). This would
> allow
> >> to preserve also the SVN logs.
> >> The other solution is to produce a patch and apply it on the ASF SVN
> (2).
> >> This will cause the lost of the SVN logs.
> >> The definitive solution would be to import patch by patch all the
> >> revisions (3), but it is really time consuming.
> >>
> >> Attempting with (1) first.
> >>
> >
> > Solution (1) is not applicable with standard SVN tools, may be somebody
> > knows some python-ish script that can be used for this purpose.
> > Meanwhile I attempted with solution (2), I have merged the modifications
> in
> > a single patch ready to be committed.
> > Waiting for your confirmation.
> >
> > Chris, do you agree?
>
> I'm fine either way. If you want to ask infra@ that's OK too I was just
> saying that
> it might take them too long in case you wanted to get going or this is
> holding us
> up. In that case, a patch is fine IMO. We're not too too far off in
> revisions and
> even if it's a big patch, we still have the history, just not
> incrementally.
>
> +1 for patch, or whatever you (who is doing the work) decides :)
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
--
*Lewis*
Re: Any23 Roadmap [WAS] Re: Googlegroup or Apache SVN
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Michele,
On Jan 10, 2012, at 3:46 AM, Michele Mostarda wrote:
> On 10 January 2012 11:19, Michele Mostarda <mi...@gmail.com>wrote:
>
>>
>>
>> On 9 January 2012 15:03, Lewis John Mcgibbney <le...@gmail.com>wrote:
>>
>>> Hi tomasso. Thanks for your comments. I am happy to progress with the
>>> website task [1] but I think it would be beneficial to consider a few
>>> points at this stage.
>>>
>>
>> Thanks Lewis,
>>
>>
>>> 1) We discussed briefly moving the existing site documentation out of the
>>> trunk codebase to its own separate directory within our Any23 SVN area.
>>> Does anyone have any thoughts on running this over the ASF CMS? I have
>>> been
>>> trying to get up to speed with it but to be honest I'm a bit unclear as to
>>> where to get started with this... I'm waiting on hearing back from some
>>> people I've asked but if anyone is up to speed with this then please say
>>> so.
>>>
>>> So just to clarify...
>>>
>>> Michele,
>>>
>>> Can you confirm that all recent changes made to the Googlecode can be
>>> ported to the ASF Any23 code residing in our SVN area?
>>>
>>
>> Not yet, we still miss on the ASF repo the revisions from r1548 to r1607.
>> I just opened an issue: [1].
>>
>> Which is the best way to synch the repositories without producing an
>> incremental svn dump? (Chris asked to avoid the ASF INFRA guys further).
>> I can try with 'svn sync' but I'm not sure it works (1). This would allow
>> to preserve also the SVN logs.
>> The other solution is to produce a patch and apply it on the ASF SVN (2).
>> This will cause the lost of the SVN logs.
>> The definitive solution would be to import patch by patch all the
>> revisions (3), but it is really time consuming.
>>
>> Attempting with (1) first.
>>
>
> Solution (1) is not applicable with standard SVN tools, may be somebody
> knows some python-ish script that can be used for this purpose.
> Meanwhile I attempted with solution (2), I have merged the modifications in
> a single patch ready to be committed.
> Waiting for your confirmation.
>
> Chris, do you agree?
I'm fine either way. If you want to ask infra@ that's OK too I was just saying that
it might take them too long in case you wanted to get going or this is holding us
up. In that case, a patch is fine IMO. We're not too too far off in revisions and
even if it's a big patch, we still have the history, just not incrementally.
+1 for patch, or whatever you (who is doing the work) decides :)
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: Any23 Roadmap [WAS] Re: Googlegroup or Apache SVN
Posted by Michele Mostarda <mi...@gmail.com>.
On 10 January 2012 11:19, Michele Mostarda <mi...@gmail.com>wrote:
>
>
> On 9 January 2012 15:03, Lewis John Mcgibbney <le...@gmail.com>wrote:
>
>> Hi tomasso. Thanks for your comments. I am happy to progress with the
>> website task [1] but I think it would be beneficial to consider a few
>> points at this stage.
>>
>
> Thanks Lewis,
>
>
>> 1) We discussed briefly moving the existing site documentation out of the
>> trunk codebase to its own separate directory within our Any23 SVN area.
>> Does anyone have any thoughts on running this over the ASF CMS? I have
>> been
>> trying to get up to speed with it but to be honest I'm a bit unclear as to
>> where to get started with this... I'm waiting on hearing back from some
>> people I've asked but if anyone is up to speed with this then please say
>> so.
>>
>> So just to clarify...
>>
>> Michele,
>>
>> Can you confirm that all recent changes made to the Googlecode can be
>> ported to the ASF Any23 code residing in our SVN area?
>>
>
> Not yet, we still miss on the ASF repo the revisions from r1548 to r1607.
> I just opened an issue: [1].
>
> Which is the best way to synch the repositories without producing an
> incremental svn dump? (Chris asked to avoid the ASF INFRA guys further).
> I can try with 'svn sync' but I'm not sure it works (1). This would allow
> to preserve also the SVN logs.
> The other solution is to produce a patch and apply it on the ASF SVN (2).
> This will cause the lost of the SVN logs.
> The definitive solution would be to import patch by patch all the
> revisions (3), but it is really time consuming.
>
> Attempting with (1) first.
>
Solution (1) is not applicable with standard SVN tools, may be somebody
knows some python-ish script that can be used for this purpose.
Meanwhile I attempted with solution (2), I have merged the modifications in
a single patch ready to be committed.
Waiting for your confirmation.
Chris, do you agree?
The best.
Mic
> The best.
>
> Mic
>
>
>>
>> Thank you Lewis
>>
>
>
> [1] https://issues.apache.org/jira/browse/ANY23-27
>
>
>>
>> [1] https://issues.apache.org/jira/browse/ANY23-9
>>
>> On Saturday, January 7, 2012, Tommaso Teofili <to...@apache.org> wrote:
>> > Hi all,
>> >
>> > first of all thanks Michele and Lewis for your efforts and Chris for
>> doing
>> > your role of champion and mentor much better than me so far :)
>> >
>> > I think Chris clarified things well and I agree with his points,
>> especially
>> > the project needs all the committers to get up to speed here so if any
>> of
>> > you feels like needing any clarifications and/or support on doing
>> something
>> > then just let me know and I'll be happy to help out.
>> >
>> > By the way, I think that one thing that may be help users (especially
>> when
>> > switching from GC to Apache) is having our website published; in fact
>> > incubator.apache.org/any23 is still "empty" while one thing that help
>> us
>> as
>> > PPMC members to let the project develop is a roadmap.
>> >
>> > My 2 cents.
>> > Tommaso
>> >
>> > 2012/1/7 Mattmann, Chris A (388J) <ch...@jpl.nasa.gov>
>> >
>> >> Hi Michele,
>> >>
>> >> On Jan 7, 2012, at 11:34 AM, Michele Mostarda wrote:
>> >>
>> >> >>
>> >> >>
>> >> >> 1. Who are the Sindice team?
>> >> >>
>> >> >
>> >> > Giovanni Tummarello, Michele Mostarda, Davide Palmisano, Szymon
>> >> Danielczyk.
>> >>
>> >> Gotcha, thanks.
>> >>
>> >> >
>> >> >
>> >> >> 2. When was it agreed that they would or could even approve of
>> >> >> moving the code *after* the 0.7.0 release?
>> >> >>
>> >> >
>> >> > We didn't find an agreement, we continued developing on Any23 while
>> >> waiting
>> >> > for
>> >> > the initial code import on the Apache repository.
>> >>
>> >> Well the "we" here is important. The only one of those folks you listed
>> >> above
>> >> that I've seen make any effort towards the code import at the ASF has
>> been
>> >> you. Hats
>> >> off to you. But things don't get done in Apache by waiting for things
>> to
>> >> get done.
>> >> They get done by volunteers like yourself stepping it up and pushing
>> for
>> >> stuff
>> >> to get done. I don't have a ton of time (or understanding) to do a lot
>> of
>> >> the code
>> >> importing or development myself here, and that's fine, b/c what I do
>> have
>> >> time
>> >> to do is to help you guys learn the Apache way and become familiar with
>> the
>> >> community. That's the role I'm trying to play here as mentor and as
>> >> Champion
>> >> for the project at the Apache Software Foundation. But others in the
>> Apache
>> >> Any23 community need to step up here too and do their work at the ASF.
>> >>
>> >> >
>> >> > The Any23 Incubation proposal was accepted when the 0.7.0 release was
>> >> ready
>> >> > at
>> >> > 60%, we didn't expect an instant freeze of the code base, out of a
>> >> > milestone.
>> >>
>> >> The Any23 (prior to Apache) team didn't have to freeze anything and it
>> >> probably
>> >> should have been better clarified where you guys were in terms of the
>> code
>> >> base as part of your Incubator proposal. But regardless, once the
>> proposal
>> >> was accepted in the Incubator there needed to be steps taken to start
>> >> getting the code to Apache. The process steps were taken (Software Code
>> >> Grant, etc.), but only recently over the past few months has there been
>> >> effort (led primarily by you and Daniel Shahaf by me minimally via my
>> >> nudging)
>> >> to get the code in to the ASF SVN.
>> >>
>> >> Even if the code wasn't fully imported yet, I would expect development
>> >> towards
>> >> any releases outside of Apache to stop -- it's just easier. Why develop
>> in
>> >> both
>> >> places when nothing is stopping anyone from developing here at the ASF?
>> If
>> >> there is something stopping anyone on the Any23 team, please speak up?
>> >>
>> >> >
>> >> >
>> >> >> It is my understanding that when you guys proposed for this to be
>> >> >> an Apache project, and when you filed a proposal to join the
>> Incubator
>> >> >> that all of the parallel development at Google Code would stop,
>> period.
>> >> >>
>> >> >> To be blunt:
>> >> >>
>> >> >> 1. There shouldn't be any parallel development release going on, or
>> >> >> code work going on at Google Code anymore.
>> >> >>
>> >> >
>> >> > Let's interrupt all the development on Any23. I will update the
>> >> > announcement,
>> >> > the 0.7.0 release will be done within the ASF.
>> >>
>> >> OK great, but I wouldn't characterize anything as an interrupt -
>> >> what are we interrupting by saying that the 0.7.0 release will
>> >> occur at the ASF?
>> >>
>> >> Are we not talking simply about:
>> >>
>> >> 1. updated link to where to download the release tarball from
>> >> 2. updated package names in the code
>> >> 3. updated docs on the website
>> >>
>> >> Correct?
>> >>
>> >> >
>> >> > What we have to do with the releases from r1548 (we imported on the
>> ASF
>> >> SVN
>> >> > the revisions
>> >> > from r0 to 1547) to r1607 (the latest commit on the Google SVN
>> related
>> to
>> >> > the milestone 0.7.0) ?
>> >> > I would provide an incremental dump to be applied on the initial
>> import.
>> >> > Please let me know.
>> >>
>> >> That would work fine, but would involve ASF infrastructure as well, and
>> >> they
>> >> are also time limited. If you or any one of the other guys on Apache
>> Any23
>> >> want to spearhead it yourself, just create a JIRA issue here at the
>> Any23
>> >> ASF JIRA to
>> >> track the provenance, and then do the svn import yourself. You should
>> have
>> >> the n
>>
>
>
>
> --
> Michele Mostarda
> Senior Software Engineer
> skype: michele.mostarda
> twitter: micmos
> mail: me@michelemostarda.com
> site : http://www.michelemostarda.com
>
>
--
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com
Re: Any23 Roadmap [WAS] Re: Googlegroup or Apache SVN
Posted by Michele Mostarda <mi...@gmail.com>.
On 9 January 2012 15:03, Lewis John Mcgibbney <le...@gmail.com>wrote:
> Hi tomasso. Thanks for your comments. I am happy to progress with the
> website task [1] but I think it would be beneficial to consider a few
> points at this stage.
>
Thanks Lewis,
> 1) We discussed briefly moving the existing site documentation out of the
> trunk codebase to its own separate directory within our Any23 SVN area.
> Does anyone have any thoughts on running this over the ASF CMS? I have been
> trying to get up to speed with it but to be honest I'm a bit unclear as to
> where to get started with this... I'm waiting on hearing back from some
> people I've asked but if anyone is up to speed with this then please say
> so.
>
> So just to clarify...
>
> Michele,
>
> Can you confirm that all recent changes made to the Googlecode can be
> ported to the ASF Any23 code residing in our SVN area?
>
Not yet, we still miss on the ASF repo the revisions from r1548 to r1607.
I just opened an issue: [1].
Which is the best way to synch the repositories without producing an
incremental svn dump? (Chris asked to avoid the ASF INFRA guys further).
I can try with 'svn sync' but I'm not sure it works (1). This would allow
to preserve also the SVN logs.
The other solution is to produce a patch and apply it on the ASF SVN (2).
This will cause the lost of the SVN logs.
The definitive solution would be to import patch by patch all the revisions
(3), but it is really time consuming.
Attempting with (1) first.
The best.
Mic
>
> Thank you Lewis
>
[1] https://issues.apache.org/jira/browse/ANY23-27
>
> [1] https://issues.apache.org/jira/browse/ANY23-9
>
> On Saturday, January 7, 2012, Tommaso Teofili <to...@apache.org> wrote:
> > Hi all,
> >
> > first of all thanks Michele and Lewis for your efforts and Chris for
> doing
> > your role of champion and mentor much better than me so far :)
> >
> > I think Chris clarified things well and I agree with his points,
> especially
> > the project needs all the committers to get up to speed here so if any of
> > you feels like needing any clarifications and/or support on doing
> something
> > then just let me know and I'll be happy to help out.
> >
> > By the way, I think that one thing that may be help users (especially
> when
> > switching from GC to Apache) is having our website published; in fact
> > incubator.apache.org/any23 is still "empty" while one thing that help us
> as
> > PPMC members to let the project develop is a roadmap.
> >
> > My 2 cents.
> > Tommaso
> >
> > 2012/1/7 Mattmann, Chris A (388J) <ch...@jpl.nasa.gov>
> >
> >> Hi Michele,
> >>
> >> On Jan 7, 2012, at 11:34 AM, Michele Mostarda wrote:
> >>
> >> >>
> >> >>
> >> >> 1. Who are the Sindice team?
> >> >>
> >> >
> >> > Giovanni Tummarello, Michele Mostarda, Davide Palmisano, Szymon
> >> Danielczyk.
> >>
> >> Gotcha, thanks.
> >>
> >> >
> >> >
> >> >> 2. When was it agreed that they would or could even approve of
> >> >> moving the code *after* the 0.7.0 release?
> >> >>
> >> >
> >> > We didn't find an agreement, we continued developing on Any23 while
> >> waiting
> >> > for
> >> > the initial code import on the Apache repository.
> >>
> >> Well the "we" here is important. The only one of those folks you listed
> >> above
> >> that I've seen make any effort towards the code import at the ASF has
> been
> >> you. Hats
> >> off to you. But things don't get done in Apache by waiting for things to
> >> get done.
> >> They get done by volunteers like yourself stepping it up and pushing for
> >> stuff
> >> to get done. I don't have a ton of time (or understanding) to do a lot
> of
> >> the code
> >> importing or development myself here, and that's fine, b/c what I do
> have
> >> time
> >> to do is to help you guys learn the Apache way and become familiar with
> the
> >> community. That's the role I'm trying to play here as mentor and as
> >> Champion
> >> for the project at the Apache Software Foundation. But others in the
> Apache
> >> Any23 community need to step up here too and do their work at the ASF.
> >>
> >> >
> >> > The Any23 Incubation proposal was accepted when the 0.7.0 release was
> >> ready
> >> > at
> >> > 60%, we didn't expect an instant freeze of the code base, out of a
> >> > milestone.
> >>
> >> The Any23 (prior to Apache) team didn't have to freeze anything and it
> >> probably
> >> should have been better clarified where you guys were in terms of the
> code
> >> base as part of your Incubator proposal. But regardless, once the
> proposal
> >> was accepted in the Incubator there needed to be steps taken to start
> >> getting the code to Apache. The process steps were taken (Software Code
> >> Grant, etc.), but only recently over the past few months has there been
> >> effort (led primarily by you and Daniel Shahaf by me minimally via my
> >> nudging)
> >> to get the code in to the ASF SVN.
> >>
> >> Even if the code wasn't fully imported yet, I would expect development
> >> towards
> >> any releases outside of Apache to stop -- it's just easier. Why develop
> in
> >> both
> >> places when nothing is stopping anyone from developing here at the ASF?
> If
> >> there is something stopping anyone on the Any23 team, please speak up?
> >>
> >> >
> >> >
> >> >> It is my understanding that when you guys proposed for this to be
> >> >> an Apache project, and when you filed a proposal to join the
> Incubator
> >> >> that all of the parallel development at Google Code would stop,
> period.
> >> >>
> >> >> To be blunt:
> >> >>
> >> >> 1. There shouldn't be any parallel development release going on, or
> >> >> code work going on at Google Code anymore.
> >> >>
> >> >
> >> > Let's interrupt all the development on Any23. I will update the
> >> > announcement,
> >> > the 0.7.0 release will be done within the ASF.
> >>
> >> OK great, but I wouldn't characterize anything as an interrupt -
> >> what are we interrupting by saying that the 0.7.0 release will
> >> occur at the ASF?
> >>
> >> Are we not talking simply about:
> >>
> >> 1. updated link to where to download the release tarball from
> >> 2. updated package names in the code
> >> 3. updated docs on the website
> >>
> >> Correct?
> >>
> >> >
> >> > What we have to do with the releases from r1548 (we imported on the
> ASF
> >> SVN
> >> > the revisions
> >> > from r0 to 1547) to r1607 (the latest commit on the Google SVN related
> to
> >> > the milestone 0.7.0) ?
> >> > I would provide an incremental dump to be applied on the initial
> import.
> >> > Please let me know.
> >>
> >> That would work fine, but would involve ASF infrastructure as well, and
> >> they
> >> are also time limited. If you or any one of the other guys on Apache
> Any23
> >> want to spearhead it yourself, just create a JIRA issue here at the
> Any23
> >> ASF JIRA to
> >> track the provenance, and then do the svn import yourself. You should
> have
> >> the n
>
--
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com