Hi all,
Because the trinity-devel list is flooded so much with cmake problems and such, we're showing the lack of coordination within the project. Therefore, I am proposing a weekly meeting:
* Takes place on irc.freenode.net, although I do not have a meetbot to wire up, so this may be a bad idea (i do not think tbottu can do meetbot) * Takes place on something like iEtherpad, where we can chat and create a checklist for the week. (trinity.ietherpad.com is taken, but we can come up with something)
This way, the coordination is here, and there are weekly tasks. Most importantly, we'll be able to see who is working on what and such. (hehe! remember due dates? >:P)
I would really like your suggestions. (if you are wondering about iEtherpad, go check it out!)
On Sun, Mar 6, 2011 at 19:46, Robert Xu robxu9@gmail.com wrote:
Hi all,
Because the trinity-devel list is flooded so much with cmake problems and such, we're showing the lack of coordination within the project. Therefore, I am proposing a weekly meeting:
- Takes place on irc.freenode.net, although I do not have a meetbot to
wire up, so this may be a bad idea (i do not think tbottu can do meetbot)
- Takes place on something like iEtherpad, where we can chat and
create a checklist for the week. (trinity.ietherpad.com is taken, but we can come up with something)
This way, the coordination is here, and there are weekly tasks. Most importantly, we'll be able to see who is working on what and such. (hehe! remember due dates? >:P)
I would really like your suggestions. (if you are wondering about iEtherpad, go check it out!)
To coordinate this, please visit http://lincom.ietherpad.com/8 and add your vote there. The password to access it is "helloworld". Only reason it's password-protected is to keep away spammers.
Because the trinity-devel list is flooded so much with cmake problems and such, we're showing the lack of coordination within the project.
That's not embarassing to me. Or bothersome.
You folks do what you want. I'm still posting here when I have problems.
On Sun, Mar 6, 2011 at 9:05 PM, Darrell Anderson humanreadable@yahoo.com wrote:
Because the trinity-devel list is flooded so much with cmake problems and such, we're showing the lack of coordination within the project.
That's not embarassing to me. Or bothersome.
You folks do what you want. I'm still posting here when I have problems.
We can make one long thread of cmake errors, but that could become extremely long and confusing.
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.
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.
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.
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.
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.
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.
On Sun, Mar 6, 2011 at 21:05, Darrell Anderson humanreadable@yahoo.com wrote:
Because the trinity-devel list is flooded so much with cmake problems and such, we're showing the lack of coordination within the project.
That's not embarassing to me. Or bothersome.
You folks do what you want. I'm still posting here when I have problems.
I know. It's not embarrassing to me, but personally, I've completely lost track, and probably some other people have.
Because the trinity-devel list is flooded so much with cmake problems and such, we're showing the lack of coordination within the project.
That's not embarassing to me. Or bothersome.
You folks do what you want. I'm still posting here when I have problems.
Perfectly fine with me. I think the discussion on the meetings will be more geared towards planning/direction/who does what/making sure people stay on task.
Tim
On Sunday 06 March 2011 18:46:09 Robert Xu wrote:
Because the trinity-devel list is flooded so much with cmake problems and such, we're showing the lack of coordination within the project.
Perhaps it might be worthwhile to create a temporary mailing list, something like "trinity-conversion" to handle the cmake-related traffic during the conversion process, (and perhaps rebranding traffic) and then close the list when those tasks are completed.
Development, patches, bugfixes, etc. could remain here.
On Tue, Mar 8, 2011 at 07:36, Dave Williams b12b@sdf.lonestar.org wrote:
On Sunday 06 March 2011 18:46:09 Robert Xu wrote:
Because the trinity-devel list is flooded so much with cmake problems and such, we're showing the lack of coordination within the project.
Perhaps it might be worthwhile to create a temporary mailing list, something like "trinity-conversion" to handle the cmake-related traffic during the conversion process, (and perhaps rebranding traffic) and then close the list when those tasks are completed.
Development, patches, bugfixes, etc. could remain here.
That would be a good idea... We do have other patches and development talk as well :) However, that decision is up to Tim; He manages everything.
(This was added as a topic for the upcoming meeting.)
-
Darrell Anderson -
Dave Williams -
Kristopher Gamrat -
Robert Xu -
Timothy Pearson