|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
|
|
Neo Lives!I took the plunge, and created http://code.google.com/p/neo2/. It
contains all my Neo related source code, including Paul Gielens generic modifications, the SqlToNeo GUI, SharpDevelop integration, unit tests for generic and non-generic classes, and a template library. Any input, blessings or curses, are welcome. Love live Neo! Michael --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Neo Lives!Hi list,
Monday, September 3, 2007, 11:57:51 PM, you wrote: > I took the plunge, and created http://code.google.com/p/neo2/. It > contains all my Neo related source code, including Paul Gielens > generic modifications, the SqlToNeo GUI, SharpDevelop integration, > unit tests for generic and non-generic classes, and a template > library. > Any input, blessings or curses, are welcome. > Love live Neo! > Michael This is fantastic! Just two questions. First, how to submit patches? (Actually, it raises another question, who's to deal with them?) And second, shouldn't we switch to the dev mailing list? Artem --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Neo Lives!Thanks. I'd like to make you an owner or member, at your choice. All
it requires is a gmail account. Members get read/write access to svn, the issues log and the wiki. Owners can, additionally, reconfigure the project. Once you're a member, patch away. Please make sure that the unit tests still pass before you commit. As soon as we feel we have some consensus on a release we'll create a tag. Yes, let's use the dev list as it was intended. Thanks again. Michael On 9/4/07, Artem <gamma@...> wrote: > Hi list, > > Monday, September 3, 2007, 11:57:51 PM, you wrote: > > > I took the plunge, and created http://code.google.com/p/neo2/. It > > contains all my Neo related source code, including Paul Gielens > > generic modifications, the SqlToNeo GUI, SharpDevelop integration, > > unit tests for generic and non-generic classes, and a template > > library. > > > Any input, blessings or curses, are welcome. > > > Love live Neo! > > > Michael > > This is fantastic! > > Just two questions. First, how to submit patches? (Actually, it raises > another question, who's to deal with them?) And second, shouldn't we > switch to the dev mailing list? > > Artem > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Neo Lives!Hi guys,
Good to know my .NET 2.0 support release added value for Neo users. The Codehaus server went down around the time I wanted to branch and submit this code. Unfortunate enough for Neo I never found the time nor motivation to continue my work. I will certainly check out the trunk every now and then. Erik will be pleased to see that Neo is in the hands where it belongs - the community -
Cheers,
Paul Gielens
On 9/5/07, PC Bender <pcbender@...> wrote:
Thanks. I'd like to make you an owner or member, at your choice. All |
|
|
|
|
|
|
|
|
|
|
|
Re: Neo Lives!Hi guys,
sorry for my prolonged silence. I had some technical problems with this mailing list. First off, I'm really happy to see renewed interest in Neo, and this includes a few more people who have contacted me offline. It's ever better to see that there is active development again. As you have noticed, Arjen and I had less and less time for Neo and, additionally, neither of us is currently working on a .NET project, which makes it really hard for us to contribute in a meaningful way. The issues at the Codehaus haven't helped either. So, in the interest of the project, what do you think is the best way forward? I could see the following possibilities: * Move the project back to SourceForge. This would fix issues with the mailing lists, the website, and it would be much easier to add new committers. * Move the project to Codeplex. This seems to become a more natural home for .NET projects but it would mean that we'd have to use that horrendous source code management system, and Neo would have its third home. * Move the project to Google. (I actually hold the 'neo' project name there.) I'm not to keen on this, as that would be the third home for Neo and I've yet to find a compelling reason for Google Code. * If we move back to SourceForge, we could switch to Subversion and import the CVS history from the Codehaus repository into that, which would give full access to all history in one place. No matter where we move, I'm happy to make Michael a committer so he can add the improvements directly into the "official" repository. I don't think we have to fork Neo. Thanks again for your interest and energy and let me know what you think. I'll have some time over the next few weeks to set this up. erik On 06/09/07, PCBender <pcbender@...> wrote: > That's great news. Thanks. > > Michael > > -----Original Message----- > From: Jim Arnold [mailto:JArnold@...] > Sent: Thursday, September 06, 2007 7:23 AM > To: user@... > Subject: Re: [neo-user] Neo Lives! > > Hello list, > > I am not Erik, but I know and work with him. He hasn't been getting emails > from this list recently, which is why he remained silent on the issue. He > is happy that Neo is being supported by the community, and will get in > touch with you guys soon to talk about admin stuff. > > Jim > > -----"Paul Gielens" <pgielens@...> wrote: ----- > > > To: user@... > From: "Paul Gielens" <pgielens@...> > Date: 09/05/2007 04:54PM > Subject: Re: [neo-user] Neo Lives! > > > Hi guys, > Good to know my .NET 2.0 support release added value for Neo users. The > Codehaus server went down around the time I wanted to branch and submit > this code. Unfortunate enough for Neo I never found the time nor motivation > to continue my work. I will certainly check out the trunk every now and > then. Erik will be pleased to see that Neo is in the hands where it belongs > - the community - > Cheers, > Paul Gielens > > > On 9/5/07, PC Bender < pcbender@... > wrote: > Thanks. I'd like to make you an owner or member, at your choice. All > it requires is a gmail account. Members get read/write access to svn, > the issues log and the wiki. Owners can, additionally, reconfigure the > project. > > Once you're a member, patch away. Please make sure that the unit tests > still pass before you commit. As soon as we feel we have some > consensus on a release we'll create a tag. > > Yes, let's use the dev list as it was intended. > > Thanks again. > > Michael > > > On 9/4/07, Artem < gamma@... > wrote: > > Hi list, > > > > Monday, September 3, 2007, 11:57:51 PM, you wrote: > > > > > I took the plunge, and created http://code.google.com/p/neo2/ . It > > > contains all my Neo related source code, including Paul Gielens > > > generic modifications, the SqlToNeo GUI, SharpDevelop integration, > > > unit tests for generic and non-generic classes, and a template > > > library. > > > > > Any input, blessings or curses, are welcome. > > > > > Love live Neo! > > > > > Michael > > > > This is fantastic! > > > > Just two questions. First, how to submit patches? (Actually, it raises > > another question, who's to deal with them?) And second, shouldn't we > > switch to the dev mailing list? > > > > Artem > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
RE: Neo Lives!It's great to hear from you. My only reason for choosing google, was the
pain factor. Almost none at all. I'm not fond of codeplex. SourceForge is a good choice, of course, but I guess I'll defer to others with a more firm opinion. I'm glad to use just Neo, and not fork to Neo2. Thanks, Michael -----Original Message----- From: edoernenburg@... [mailto:edoernenburg@...] On Behalf Of Erik Doernenburg Sent: Thursday, September 06, 2007 9:05 AM To: user@... Subject: Re: [neo-user] Neo Lives! Hi guys, sorry for my prolonged silence. I had some technical problems with this mailing list. First off, I'm really happy to see renewed interest in Neo, and this includes a few more people who have contacted me offline. It's ever better to see that there is active development again. As you have noticed, Arjen and I had less and less time for Neo and, additionally, neither of us is currently working on a .NET project, which makes it really hard for us to contribute in a meaningful way. The issues at the Codehaus haven't helped either. So, in the interest of the project, what do you think is the best way forward? I could see the following possibilities: * Move the project back to SourceForge. This would fix issues with the mailing lists, the website, and it would be much easier to add new committers. * Move the project to Codeplex. This seems to become a more natural home for .NET projects but it would mean that we'd have to use that horrendous source code management system, and Neo would have its third home. * Move the project to Google. (I actually hold the 'neo' project name there.) I'm not to keen on this, as that would be the third home for Neo and I've yet to find a compelling reason for Google Code. * If we move back to SourceForge, we could switch to Subversion and import the CVS history from the Codehaus repository into that, which would give full access to all history in one place. No matter where we move, I'm happy to make Michael a committer so he can add the improvements directly into the "official" repository. I don't think we have to fork Neo. Thanks again for your interest and energy and let me know what you think. I'll have some time over the next few weeks to set this up. erik On 06/09/07, PCBender <pcbender@...> wrote: > That's great news. Thanks. > > Michael > > -----Original Message----- > From: Jim Arnold [mailto:JArnold@...] > Sent: Thursday, September 06, 2007 7:23 AM > To: user@... > Subject: Re: [neo-user] Neo Lives! > > Hello list, > > I am not Erik, but I know and work with him. He hasn't been getting > from this list recently, which is why he remained silent on the issue. He > is happy that Neo is being supported by the community, and will get in > touch with you guys soon to talk about admin stuff. > > Jim > > -----"Paul Gielens" <pgielens@...> wrote: ----- > > > To: user@... > From: "Paul Gielens" <pgielens@...> > Date: 09/05/2007 04:54PM > Subject: Re: [neo-user] Neo Lives! > > > Hi guys, > Good to know my .NET 2.0 support release added value for Neo users. The > Codehaus server went down around the time I wanted to branch and submit > this code. Unfortunate enough for Neo I never found the time nor > to continue my work. I will certainly check out the trunk every now and > then. Erik will be pleased to see that Neo is in the hands where it belongs > - the community - > Cheers, > Paul Gielens > > > On 9/5/07, PC Bender < pcbender@... > wrote: > Thanks. I'd like to make you an owner or member, at your choice. All > it requires is a gmail account. Members get read/write access to svn, > the issues log and the wiki. Owners can, additionally, reconfigure the > project. > > Once you're a member, patch away. Please make sure that the unit tests > still pass before you commit. As soon as we feel we have some > consensus on a release we'll create a tag. > > Yes, let's use the dev list as it was intended. > > Thanks again. > > Michael > > > On 9/4/07, Artem < gamma@... > wrote: > > Hi list, > > > > Monday, September 3, 2007, 11:57:51 PM, you wrote: > > > > > I took the plunge, and created http://code.google.com/p/neo2/ . It > > > contains all my Neo related source code, including Paul Gielens > > > generic modifications, the SqlToNeo GUI, SharpDevelop integration, > > > unit tests for generic and non-generic classes, and a template > > > library. > > > > > Any input, blessings or curses, are welcome. > > > > > Love live Neo! > > > > > Michael > > > > This is fantastic! > > > > Just two questions. First, how to submit patches? (Actually, it raises > > another question, who's to deal with them?) And second, shouldn't we > > switch to the dev mailing list? > > > > Artem > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
Re[2]: Neo Lives!Hi Erik,
Thursday, September 6, 2007, 8:04:35 PM, you wrote: > Hi guys, > So, in the interest of the project, what do you think is the best way forward? But the source is already at Google (neo2), together with accompanying projects. Do you have any reason to prefer SourceForge? I've never dealt with Google Code, looks like it doesn't support mailing lists, but we already have these, don't we? Artem > I could see the following possibilities: > * Move the project back to SourceForge. This would fix issues with the > mailing lists, the website, and it would be much easier to add new > committers. > * Move the project to Codeplex. This seems to become a more natural > home for .NET projects but it would mean that we'd have to use that > horrendous source code management system, and Neo would have its third > home. > * Move the project to Google. (I actually hold the 'neo' project name > there.) I'm not to keen on this, as that would be the third home for > Neo and I've yet to find a compelling reason for Google Code. > * If we move back to SourceForge, we could switch to Subversion and > import the CVS history from the Codehaus repository into that, which > would give full access to all history in one place. > No matter where we move, I'm happy to make Michael a committer so he > can add the improvements directly into the "official" repository. I > don't think we have to fork Neo. > Thanks again for your interest and energy and let me know what you > think. I'll have some time over the next few weeks to set this up. > erik --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
RE: Re[2]: Neo Lives!Google expects you to create a google group for the project. There is some
mailing list functionality provided by a google group. Michael -----Original Message----- From: Artem [mailto:gamma@...] Sent: Friday, September 07, 2007 1:16 PM To: Erik Doernenburg Subject: Re[2]: [neo-user] Neo Lives! Hi Erik, Thursday, September 6, 2007, 8:04:35 PM, you wrote: > Hi guys, > So, in the interest of the project, what do you think is the best way forward? But the source is already at Google (neo2), together with accompanying projects. Do you have any reason to prefer SourceForge? I've never dealt with Google Code, looks like it doesn't support mailing lists, but we already have these, don't we? Artem > I could see the following possibilities: > * Move the project back to SourceForge. This would fix issues with the > mailing lists, the website, and it would be much easier to add new > committers. > * Move the project to Codeplex. This seems to become a more natural > home for .NET projects but it would mean that we'd have to use that > horrendous source code management system, and Neo would have its third > home. > * Move the project to Google. (I actually hold the 'neo' project name > there.) I'm not to keen on this, as that would be the third home for > Neo and I've yet to find a compelling reason for Google Code. > * If we move back to SourceForge, we could switch to Subversion and > import the CVS history from the Codehaus repository into that, which > would give full access to all history in one place. > No matter where we move, I'm happy to make Michael a committer so he > can add the improvements directly into the "official" repository. I > don't think we have to fork Neo. > Thanks again for your interest and energy and let me know what you > think. I'll have some time over the next few weeks to set this up. > erik --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Re[2]: Neo Lives!I hear what you say, but Neo is also already at Codehaus and, from
before that, at SourceForge. My reasoning for going back to SF was that we have everything in place, SF is a very accepted platform and services there have become quite good over the years. (This wasn't always the case, which is why we moved Neo to the Codehaus a few years ago.) We could stay at Codehaus but due to their platform the website keeps breaking, and it's somewhat more difficult to add more committers. Ultimately, it's up to you guys as you will be working on Neo the most, but I could offer the following to keep some continuity in the development of Neo, which I think is good from an end-user perspective; forks are always treated with a bit of suspicion. 1) Import the CVS history from Codehaus to the SVN repository on the SourceForge neo project. Or would you guys prefer to stick with CVS? 2) Add Michael as a committer and moderate a discussion on this mailing list who else should be a committer to be added. Michael, do you have a SourceForge account? 3) Move to neo website to SourceForge servers and set up a redirect from neo.codehaus.org to neo.sourceforge.net. How does that sound? erik On 07/09/2007, Artem <gamma@...> wrote: > Hi Erik, > > Thursday, September 6, 2007, 8:04:35 PM, you wrote: > > > Hi guys, > > > So, in the interest of the project, what do you think is the best way forward? > > But the source is already at Google (neo2), together with accompanying > projects. Do you have any reason to prefer SourceForge? I've never > dealt with Google Code, looks like it doesn't support mailing lists, > but we already have these, don't we? > > Artem > > > I could see the following possibilities: > > > * Move the project back to SourceForge. This would fix issues with the > > mailing lists, the website, and it would be much easier to add new > > committers. > > > * Move the project to Codeplex. This seems to become a more natural > > home for .NET projects but it would mean that we'd have to use that > > horrendous source code management system, and Neo would have its third > > home. > > > * Move the project to Google. (I actually hold the 'neo' project name > > there.) I'm not to keen on this, as that would be the third home for > > Neo and I've yet to find a compelling reason for Google Code. > > > * If we move back to SourceForge, we could switch to Subversion and > > import the CVS history from the Codehaus repository into that, which > > would give full access to all history in one place. > > > No matter where we move, I'm happy to make Michael a committer so he > > can add the improvements directly into the "official" repository. I > > don't think we have to fork Neo. > > > Thanks again for your interest and energy and let me know what you > > think. I'll have some time over the next few weeks to set this up. > > > erik > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
RE: Re[2]: Neo Lives!SourceForge is okay by me. I do not have an account, but I will get one. SVN
is almost a must for me. Last time I checked, googling 'Neo' brought up the codehaus site on the first page, so a redirect from there to SF would be a good thing. I'll let you know when I have an SF account. -----Original Message----- From: edoernenburg@... [mailto:edoernenburg@...] On Behalf Of Erik Doernenburg Sent: Thursday, September 13, 2007 9:47 AM To: user@... Subject: Re: Re[2]: [neo-user] Neo Lives! I hear what you say, but Neo is also already at Codehaus and, from before that, at SourceForge. My reasoning for going back to SF was that we have everything in place, SF is a very accepted platform and services there have become quite good over the years. (This wasn't always the case, which is why we moved Neo to the Codehaus a few years ago.) We could stay at Codehaus but due to their platform the website keeps breaking, and it's somewhat more difficult to add more committers. Ultimately, it's up to you guys as you will be working on Neo the most, but I could offer the following to keep some continuity in the development of Neo, which I think is good from an end-user perspective; forks are always treated with a bit of suspicion. 1) Import the CVS history from Codehaus to the SVN repository on the SourceForge neo project. Or would you guys prefer to stick with CVS? 2) Add Michael as a committer and moderate a discussion on this mailing list who else should be a committer to be added. Michael, do you have a SourceForge account? 3) Move to neo website to SourceForge servers and set up a redirect from neo.codehaus.org to neo.sourceforge.net. How does that sound? erik On 07/09/2007, Artem <gamma@...> wrote: > Hi Erik, > > Thursday, September 6, 2007, 8:04:35 PM, you wrote: > > > Hi guys, > > > So, in the interest of the project, what do you think is the best way forward? > > But the source is already at Google (neo2), together with accompanying > projects. Do you have any reason to prefer SourceForge? I've never > dealt with Google Code, looks like it doesn't support mailing lists, > but we already have these, don't we? > > Artem > > > I could see the following possibilities: > > > * Move the project back to SourceForge. This would fix issues with the > > mailing lists, the website, and it would be much easier to add new > > committers. > > > * Move the project to Codeplex. This seems to become a more natural > > home for .NET projects but it would mean that we'd have to use that > > horrendous source code management system, and Neo would have its third > > home. > > > * Move the project to Google. (I actually hold the 'neo' project name > > there.) I'm not to keen on this, as that would be the third home for > > Neo and I've yet to find a compelling reason for Google Code. > > > * If we move back to SourceForge, we could switch to Subversion and > > import the CVS history from the Codehaus repository into that, which > > would give full access to all history in one place. > > > No matter where we move, I'm happy to make Michael a committer so he > > can add the improvements directly into the "official" repository. I > > don't think we have to fork Neo. > > > Thanks again for your interest and energy and let me know what you > > think. I'll have some time over the next few weeks to set this up. > > > erik > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |