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
This fork seems to be huge waste of open-source development limited
resources.
I do'nt see reason for it.
Andrus.
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
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.
Hi Marcos,
You realize that dbl...@googlegroups.com is an open mailing list that
anybody can join, right? It seems to be pretty active with
discussions.
I think if nobody monitors the issue tracking system, it might be best
to shut it down entirely:
http://alumnit.ca/~apenwarr/log/?m=200806#28
Have fun,
Avery
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
No problem.
"admin (that magical at sign) yuniti dot com" has been added as a
committer, so whenever you get time again feel free to merge your
changes.
- Jon