On 3/22/07, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
Nice idea and I can see the benefit of it to you and I don't mean to be a wet blanket on it, I just wonder about the legality of it. People may find it and think it is the official Apache Lucene, since it is branded that way. I'm not a lawyer, so I don't know for sure. I think you have the right to store and use the code, even create a whole other search product based solely on Lucene (I think), I just don't know about this kind of thing. In some sense it is like mirroring, but that fact that you can commit w/ out going through the
NO NO!! I don't make any commits to apache trunk. Nor any one else for that matter. The repo at launchpad is just a pure mirror and will always be a mirror. Just to clarify what I meant by commit. Basically you "pull" the Lucene branch from launchpad to your local machine and that becomes a complete copy of the trunk and you make another local branch from that branch. Example bzr branch http://bazaar.launchpad.net/~vcs-imports/lucene/trunk local.copy bzr branch local.copy local.customerx then you do all your work on local.customerx and make commits there. Cos you want to keep the local.copy exactly identical to lanuchpad version which in turns a mirror like any other mirror that apache have thats all. If I were to commit things to the launchpad version I loose the whole point of mirroring and getting changes from trunk.
Apache process makes me think that others coming upon the code will be mislead about what's in it. The site _definitely_ makes it look like Launchpad is the home for Lucene with the intro and the bug tracking, etc, even though we all know this site will rank further down in the SERPs than the main site.
I am not a lawyer or branding expert. But if you want me to edit the description text with something like "A mirrored copy of Apache Lucene.. original site at..." No problem Please provide me the exact text so I can edit it to avoid confusion etc.. Last thing I want to do is create confusion. Moreover if such need like mine exist maybe Apache Infrastructure should consider a DRCS system then a RCS system .. SVN doesn't provide the flexibility that I need. In apache there is CVS and SVN co-exist as well as there are mirrors of such all over the world so.. why not have a bzr branch? if Launchpad want to host it great if other mirror wants to host it great. I hope it clarifies misunderstanding.. Please do provide an exact text so we don't get into some lawyer trouble :-) I don't want to take a stab on the text its better you provide me exact instructions. Regards.
On Mar 22, 2007, at 7:42 AM, rubdabadub wrote: > On 3/22/07, Grant Ingersoll <[EMAIL PROTECTED]> wrote: >> Is the point of this that you can make "commits" to Lucene so that >> you don't lose your changes on trunk? > > Not only that. But I can make as many local branch as I like ..for > example > customer X, customer Y. This way I can support X and Y as they have > separate features .. All of the above can be done with SVN but its > a pain > at least for me. > > And off course work off line .. during summer .. under trees :-) > and then update > the whole branch with main repo without loosing any changes. It > just seems easy, > I have also had a case where I need to bake some part of Nutch and > some part > Solr under one tree i.e. new project and still maintain that tree with > the original > repo. and i could do that just fine. Bazaar commands are like SVN > commands > so its not much to learn either :-) > > Regards >> On Mar 22, 2007, at 7:14 AM, rubdabadub wrote: >> >> > Hi: >> > >> > First of all apology to those friends who follow all the list. >> > >> > Often times I work offline and I do not have any commit rights >> to any >> > of the projects. All the modifications I make for various >> clients and >> > trying to keep up to date with latest trunk somehow makes it >> difficult >> > for me to just stick with "subversion". I have heard many things >> about >> > distributed >> > revision control system and I am sure there are tricks/fixes for >> the >> > subversion problem i mentioned above, but I also wanted to learn >> > something new :-) So after some trial with many DRCS I have >> decided to >> > go for Bazaar! Its really cool DRCS.. you got try it. >> > >> > http://bazaar-vcs.org/. >> > >> > Now due to the fact that SVN is RCS and bzr is DRCS one need to >> > convert SVN repos to bzr repos. and cool enough.. there is a >> free vcs >> > mirroring service at Launchpad >> > >> > https://launchpad.net/ >> > >> > So now the following projects are available via bzr branch. You can >> > access them here. >> > >> > Nutch - https://launchpad.net/nutch >> > Solr - https://launchpad.net/solr >> > Lucene - https://launchpad.net/lucene >> > Hadoop - https://launchpad.net/hadoop >> > >> > It only mirrors "trunk". Thats what I need to follow thats why >> and I >> > don't see any reason to mirror releases. >> > >> > Regards >> >> -------------------------- >> Grant Ingersoll >> Center for Natural Language Processing >> http://www.cnlp.org >> >> Read the Lucene Java FAQ at http://wiki.apache.org/jakarta-lucene/ >> LuceneFAQ >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > ------------------------------------------------------ Grant Ingersoll http://www.grantingersoll.com/ http://lucene.grantingersoll.com http://www.paperoftheweek.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]