On Sun, Mar 6, 2011 at 21:18, Kristopher Gamrat pikidalto@gmail.com wrote:
We can make one long thread of cmake errors, but that could become extremely long and confusing.
agreed
We can also close the devel mailing list, but then people would go to the regular users mailing list, which would scare normal users not wanting to participate in development, and make us look very unorganized.
also agreed.
We could force those interested in devel to use IRC, but some people don't like IRC and some don't like mailing lists.
We could do a mailing list specfic to cmake, but once cmake porting is complete, that would be useless to have anyway. Cmake is a part of development anyway.
I'd rather not say useless, but not as much needed as before.
We could force people to use the forum, but some people don't like forums. We'd also open up having one long confusing cmake thread, or open up a section just for cmake and close it after, but I don't think we should for the same reason as not having a cmake mailing list.
Never saw the Trinity forum before. It's pretty hidden :-\
The fact that we are putting the cmake errors on the devel mailing list while we are porting to cmake and that our main developers are checking the devel mailing list shows that we do have some level of coordination.
But it's getting mixed in other mails, and in the end, it's showing the *some* part pretty widely.
We could see about setting up a bridge between the devel mailing list and the devel forum to further bring us together, though I don't know how active the forum is or if it would be worth it. I doubt that there is a way to bridge IRC and mailing list. It may be worth it, though, to have a bridge between the bugtracker and mailing list to make (setup to file the bug in bugzilla, but post comments via bugtracker or mailing list) may make it easier to discuss bugs.
Hm... nope.
As I suggested, weekly meetings might be the best way to ensure we're all on the same page. Tim has said he's good with it, I'd like everyone's opinion on this before we continue.