Hi Marcos, I'm one of the two project admins (the other one being Jiri Moudry, DbLinq's original developper). We always accept suggestions, patches, and contributors. I've always, even if my professional activity doesn't allow me to be as available as I would, answered to people willing to help the project.
It is understable, that maybe guided by some disappointment you forked the project, and I think no one has to object against this. The license allows it, and you are free. I just took a look at the google group and searched for "yuniti". I found only 3 messages from you, and 2 of them are dated from today. So this leaves you only one unsuccessful try before getting the project forked... Patience is something to learn :) So - we're all working on DbLinq for free, following different purposes, going from fun to real production needs. - if you submit patches on the group, we'll review and commit them. - if you want to become a contributor, just say the magic words: "I want to be a contributor, because... " (and fill in the blank) - if you want to carry on alone on codeplex, no problem, we'll also review your patches and apply them to DbLinq on google code if we like them (since your license also has to be MIT). Cheers (and by advance, welcome to contributors :)), Pascal. On Wed, May 13, 2009 at 13:14, Marcos Boyington <[email protected]> wrote: > > Hi Jonathan! Sorry if my "branching" at codeplex was taken as an offense, > that was in no way my intention! I definitely have nothing against the > direction you guys have taken - as a matter of fact, I wanted some of your > direction with my bug fixes! I very much wanted to help you guys with the > project - problem was, I had no way of contacting you! I tried getting > email addresses for the most active developers (yourself included), but > Google Code does not have it available. > > I also tried posting bug reports on the google code page (saying I had a > fix > and if I could be added as a developer), and again, no response! That was > actually my main reason for going with CodePlex - not because I wanted to > branch from your guys' amazing work (in fact, I'd love to combine it all), > but because google code was a huge discouragement in having me be part of > your group/effort. > > The beauty of CodePlex is it's quite easy to contact the > developers/administrators of the project to be added to the project. I > think this could greatly help in having other developers such as myself > help > out, even if only little bits. > > I'm not sure where to go from here - I could/would gladly closedown the > CodePlex project and submit my changes to the Google Code group, but as I > said, I really do think it's a major detriment to the project as it's quite > difficult to join in the effort. I assumed that you guys were in contact > via mailing list or personal email (As I saw your check-ins), but that > doesn't help much when someone new wants to join in. > > Let me know how you'd like to proceed. I definitely do not want to branch > and want all of us working on the same thing. If you're up for trying > CodePlex, I can add you all as managers there and also would gladly do the > integration of the efforts from the google group. > > - Marcos Boyington > > -----Original Message----- > From: Jonathan Pryor [mailto:[email protected]] > Sent: Tuesday, May 12, 2009 11:45 PM > To: [email protected] > Cc: yuniti > Subject: Re: New project at CodePlex for DbLinq > > On Tue, 2009-05-12 at 19:30 -0700, yuniti wrote: > > I've started a new project over at CodePlex for DbLinq. I've noticed > > the Google project has come to a crawl and has gotten very little > > support lately. > > I understand that the Google project seems like it's slow, but the > mailing list is still somewhat responsive, and we're quite willing to > add new commiters to the project. I don't understand why you felt the > need to fork the project at codeplex. (It's not like we've had any > major discussions on the list about intractable differences of opinion > on how to manage and run the project. To the contrary, when it isn't > quiet there's been no flaming of late to speak of...) > > Rephrased another way, why place your fixes at codeplex instead of > contributing them back here? This will only increase maintenance burden > if we try to keep the two projects in sync with each other (and at > present, why shouldn't we try to keep them in sync?), and increase the > likelihood that fixes made in one branch won't make it to the other. > > Would you be interesting in merging your changes back into the Google > repository so that we don't split our efforts? > > Thanks, > - Jon > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" 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/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
