Good score: the word "codeplex" appears 5 times in your message.
:)

On Mon, May 18, 2009 at 23:45, yuniti <[email protected]> wrote:

>
> Again no offense at all taken and I was in no way upset - I simply
> figured as I got no response and I had these changes locally that I
> didn't want to go to waste, that I may as well go to a different
> medium where I knew I could get some work submitted.
>
> The prolem I have with "convnention" is that, clearly, someone new
> won't know what the convention is, and someone not new is "useless" as
> they are already part of the project heh.  The idea here is we want to
> make it really easy/simple for new users to join in, and convention
> won't help us there.
>
> That's the nice thing about Codeplex - no convention.  You just click
> on a developer's name, and you're taken to a page where you can send
> them a message.  Unfortunately, Google Code doesn't have this option.
> I realized after the fact (after having already created my group in
> Codeplex) that all the activity happens here in the group - but there
> isn't a strong linking between the forum posts and the google code
> page (as opposed to Codeplex, where it's all inter-connected).
>
> Again, I'd recommend you guys have a look at Codeplex.  I have no
> problem submitting my code changes here, but if you have a look over
> there, you'll see the interface is quite nicer than Google Code +
> Google Groups (at least, for the purpose of working on an open-source
> project where we want other developers to join in).
>
> I realize that an MIT license allows us to branch the source any time
> we see fit, but that's somewhat pointless here as we all want the same
> thing.  I just get a feeling that it's a lot more difficult to
> maintain this project and to get attention (and other developers)
> using Google Code instead of Codeplex.
>
> On May 14, 10:23 am, Jonathan Pryor <[email protected]> wrote:
> > I don't think it's possible to use a custom prefix for issues, so I've
> > create a new dblinq-bugs group at Google Groups, which should now
> > receive issue emails.  Sign up at:
> >
> >    http://groups.google.com/group/dblinq-bugs
> >
> >  - Jon
> >
> >
> >
> > On Thu, 2009-05-14 at 09:29 +0200, Giacomo Tesio wrote:
> > > I agree for a different group.
> > > Alternativelly we should allow some tagging for email coming from
> > > issue tracker (a [ISSUE] prefix in the subject or the so).
> >
> > > Giacomo
> >
> > > On Wed, May 13, 2009 at 8:49 PM, Jonathan Pryor <[email protected]>
> > > wrote:
> >
> > >         On Wed, 2009-05-13 at 13:39 -0400, Adam Tauno Williams wrote:
> > >         > Possibly a dumb question; but can the Google Issues "app"
> > >         notify the
> > >         > mailing list when something is created/commented/etc...
> > >          This list is
> > >         > fairly low volume [and generally very interesting] so it
> > >         doesn't seem
> > >         > like the "extra" traffic would be a problem.
> >
> > >         Yes it can.  Alas, it can only be sent to one email address
> > >         (odd, that).
> >
> > >         So we could either send the issue emails to this list, or we
> > >         could
> > >         create a new Google group specifically for the issue emails
> > >         (and then
> > >         anyone could subscribe to that group if they want to receive
> > >         Issue
> > >         emails).
> >
> > >         I'm inclined to create a new group for issue emails, and will
> > >         do so
> > >         unless a majority of people responding by tomorrow would
> > >         rather use this
> > >         list.
> >
> > >          - Jon- Hide quoted text -
> >
> > - Show quoted text -
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to