Put C.Tx back into its own repo, castleproject/Castle.Transactions, because it's a top-level project.
castleproejct/Castle.Transactions will contain a working tree of Castle.IO at tags of releases. Castle.IO sub-level project. Henrik -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of hammett Sent: den 30 oktober 2011 02:11 To: [email protected] Subject: Re: New Castle.IO project? What was the conclusion of this whole discussion? What should be done with the repositories? On Tue, Oct 25, 2011 at 11:28 AM, Henrik Feldt <[email protected]> wrote: > I'm aware that I may be interpreted that way. You must understand that > this is not my intention... I will try to formulate my concerns more > clearly before disagreeing in the future. Since I know that I might be > taken this way I often suggest a phone call/skype instead, because > when I have those I don't sound as confrontational. > > At least I end it with; > Cheers, ;) > Henrik > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of hammett > Sent: den 25 oktober 2011 18:24 > To: [email protected] > Subject: Re: New Castle.IO project? > > As long as another repository is under /castleproject and abide to its > rules. > > The explanation for the veto is the whole other thread. I dont see you > making your concerns clear, instead you confront/attack. My time is > too precious to waste on these energy draining activities. It's not > the first time it happens with you and I'm sure it wont be the last. > Like I said before, if you want full control over your projects, move > it somewhere else. > > > On Tue, Oct 25, 2011 at 9:03 AM, Henrik <[email protected]> wrote: >> Do you still do that if it's a part of another *git repository* like >> I suggested in my last e-mail? >> >> Also, remember this: >> "Vetos with no explanation are void" >> >> >> >> On Oct 25, 5:51 pm, hammett <[email protected]> wrote: >>> http://www.castleproject.org/community/bylaws.html >>> >>> I veto it. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On Tue, Oct 25, 2011 at 8:39 AM, Henrik Feldt <[email protected]> wrote: >>> > @hammett: >>> >>> > But you are not backtracking from this thread. It’s a new project, >>> > by majority vote. So castle is *the* vehicle. >>> >>> > Cheers, >>> >>> > Henrik >>> >>> > From: [email protected] >>> > [mailto:[email protected]] On Behalf Of >>> > Hamilton Verissimo de Oliveira >>> > Sent: den 29 september 2011 22:44 >>> > To: Henrik Feldt; [email protected] >>> >>> > Subject: RE: New Castle.IO project? >>> >>> > Go for it >>> >>> > Sent from my Windows Phone >>> >>> > ________________________________ >>> >>> > From: Henrik Feldt >>> > Sent: 9/29/2011 12:45 PM >>> > To: [email protected] >>> > Subject: RE: New Castle.IO project? >>> >>> > What does hammett think? Green light? >>> >>> > From: [email protected] >>> > [mailto:[email protected]] On Behalf Of >>> > Sebastien Lambla >>> > Sent: den 29 september 2011 16:14 >>> > To: G. Richard Bellamy; [email protected] >>> > Cc: Bertrand Le Roy; Henrik Feldt >>> > Subject: RE: New Castle.IO project? >>> >>> > Well no because o.exe is separate from everything else, we’ve had >>> > issues before because of that. It’s all rather complicated. >>> >>> > What I discussed with Henrik was to migrate to a common codebase >>> > while preserving some of the existing assemblies and namespaces on >>> > my side, using some sort of templating. I’m gonna have to >>> > re-review those plans end of next week so maybe I’ll find a better >>> > way to solve > this. >>> >>> > From: G. Richard Bellamy [mailto:[email protected]] >>> > Sent: 29 September 2011 14:51 >>> > To: [email protected] >>> > Cc: Sebastien Lambla; Bertrand Le Roy; Henrik Feldt >>> > Subject: Re: New Castle.IO project? >>> >>> > Sebastian, >>> >>> > So, you've got a hard dependency on the OpenFileSystem namespace >>> > because you've got deployed o.exe users, and o.exe doesn't autoupdate? >>> >>> > Am I missing something here? If they're 1.0 users, then won't they >>> > just retain the assemblies used by o.exe, and when they upgrade, >>> > couldn't you change the dependency tree? Isn't this equivalent to >>> > removing an old, and then adding a new dependency? >>> >>> > -rb >>> >>> > On 9/29/2011 5:46 AM, Sebastien Lambla wrote: >>> >>> > +1 but I’m stuck with OpenFileSystem as a namespace / name, >>> > +openwrap 1.0 >>> > depends on it and the shell doesn’t auto-update, changing names >>> > would break my installed based which is not ideal. >>> >>> > From: Bertrand Le Roy [mailto:[email protected]] >>> > Sent: 28 September 2011 22:55 >>> > To: Henrik Feldt; [email protected]; Sebastien >>> > Lambla >>> > Subject: RE: New Castle.IO project? >>> >>> > +1 obviously J >>> >>> > From: Henrik Feldt [mailto:[email protected]] >>> > Sent: Wednesday, September 28, 2011 1:24 PM >>> > To: [email protected]; Bertrand Le Roy; >>> > [email protected] >>> > Subject: New Castle.IO project? >>> >>> > Hello everybody, >>> >>> > I’m merging open file system and fluent path into what was >>> > Castle.Transactions for the transactional file systems’ benefit. >>> >>> > But it’s not so smooth to have it coupled to the transactional >>> > behavior – one would have to know both projects to change one, and >>> > the IO project is becoming large. >>> >>> > Can we create a new project Castle.IO? >>> >>> > This would also involve Sebastien Lambla and Bertrand Le Roy who >>> > are the authors of openfilesystem and FluentPath respectively – it >>> > would be great if they would be allowed to push to this specific >>> > repository. I generally think it’s a good thing to work together >>> > with other OSS projects and cooperate with them, which is why I’m >>> > not re-doing their work but asking them to work with me. >>> >>> > What do you think? >>> >>> > Cheers, >>> >>> > Henrik >>> >>> > PS, features for this project: >>> >>> > * Transactional file system >>> >>> > * Non-transactional file systems on Windows >>> >>> > * Same for *nix-systems >>> >>> > * A fluent API for these systems through both interfaces and >>> > extension methods on these interfaces >>> >>> > * Long path support (no more >245 chars exceptions) >>> >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "Castle Project Development List" group. >>> > To post to this group, send email to > [email protected]. >>> > To unsubscribe from this group, send email to >>> > [email protected]. >>> > For more options, visit this group at >>> >http://groups.google.com/group/castle-project-devel?hl=en. >>> >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "Castle Project Development List" group. >>> > To post to this group, send email to > [email protected]. >>> > To unsubscribe from this group, send email to >>> > [email protected]. >>> > For more options, visit this group at >>> >http://groups.google.com/group/castle-project-devel?hl=en. >>> >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "Castle Project Development List" group. >>> > To post to this group, send email to > [email protected]. >>> > To unsubscribe from this group, send email to >>> > [email protected]. >>> > For more options, visit this group at >>> >http://groups.google.com/group/castle-project-devel?hl=en. >>> >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "Castle Project Development List" group. >>> > To post to this group, send email to > [email protected]. >>> > To unsubscribe from this group, send email to >>> > [email protected]. >>> > For more options, visit this group at >>> >http://groups.google.com/group/castle-project-devel?hl=en. >>> >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "Castle Project Development List" group. >>> > To post to this group, send email to > [email protected]. >>> > To unsubscribe from this group, send email to >>> > [email protected]. >>> > For more options, visit this group at >>> >http://groups.google.com/group/castle-project-devel?hl=en. >>> >>> -- >>> Cheers, >>> hammetthttp://hammett.castleproject.org/ >> >> -- >> You received this message because you are subscribed to the Google >> Groups > "Castle Project Development List" group. >> To post to this group, send email to > [email protected]. >> To unsubscribe from this group, send email to > [email protected]. >> For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. >> >> > > > > -- > Cheers, > hammett > http://hammett.castleproject.org/ > > -- > You received this message because you are subscribed to the Google > Groups "Castle Project Development List" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]. > For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. > > -- Cheers, hammett http://hammett.castleproject.org/ -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
