7 Mar
2011
7 Mar
'11
12:46 a.m.
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!)
--
later, Robert Xu
7 Mar
7 Mar
1:08 a.m.
On Sun, Mar 6, 2011 at 19:46, Robert Xu <robxu9(a)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.
--
later, Robert Xu
2:05 a.m.
New subject: [trinity-devel] flooding the devel list is a bad idea - weekly meetings?
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.
2:18 a.m.
New subject: [trinity-devel] flooding the devel list is a bad idea - weekly meetings?
On Sun, Mar 6, 2011 at 9:05 PM, Darrell Anderson
<humanreadable(a)yahoo.com> wrote:
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.
--
Kris
"Piki"
Ark Linux Webmaster
Trinity Desktop Environment Packager
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.
2:26 a.m.
New subject: [trinity-devel] flooding the devel list is a bad idea - weekly meetings?
On Sun, Mar 6, 2011 at 21:18, Kristopher Gamrat <pikidalto(a)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.
--
later, Robert Xu
2:19 a.m.
New subject: [trinity-devel] flooding the devel list is a bad idea - weekly meetings?
On Sun, Mar 6, 2011 at 21:05, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
I know. It's not embarrassing to me,
but personally, I've completely lost track, and probably some other people have.
--
later, Robert Xu
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.
2:26 a.m.
New subject: [trinity-devel] flooding the devel list is a bad idea - weekly meetings?
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. 
8 Mar
8 Mar
12:36 p.m.
New subject: [trinity-devel] flooding the devel list is a bad idea - weekly meetings?
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.
4:19 p.m.
New subject: [trinity-devel] flooding the devel list is a bad idea - weekly meetings?
On Tue, Mar 8, 2011 at 07:36, Dave Williams <b12b(a)sdf.lonestar.org> wrote:
On Sunday 06 March 2011 18:46:09 Robert Xu wrote:
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.)
--
later, Robert Xu
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.
5071
days inactive
5072
days old
9 comments
5 participants
participants (5)
-
Darrell Anderson -
Dave Williams -
Kristopher Gamrat -
Robert Xu -
Timothy Pearson