> From: [email protected]
> Date: Wed, 14 Nov 2012 15:10:29 +0100
> CC: [email protected]; [email protected]
> To: [email protected]
> Subject: Re: [fw-general] Events vs. EventManager
>
> Hello Gerry,
>
>
> > > > That's an interesting approach. I'm not sure. Discussions on issues
> > > > like this can go on for ever. I think it will be better to disable the
> > > > discussion in the issue tracker and just link to relating resources
> > > > instead.
> > >
> > > From what, though?
> >
> > ???
> >
> > How do you mean "from what"?
> You said that one should just link to the relating sources. But where should
> the link be placed - e.g. from where shall one link to the related resources?
>
> And, what would a related resource be - a link to Nabble?
>
>
> Best regards,
>
> Andreas
>
Ah, yes. I'm not sure.
What I am sure about is this: I don't want to waste my time debating issues
like coding standards. I
have an opinion on what I like so I'll vote and sometimes even throw in
my 2cents about which side of the fench I sit on. Some people do like
discussing these things though. Trying to convince us all that their way
is the best. I'm fine with that. Convince me I'll vote for it. At the same
time, that
doesn't mean discussing things like coding standards is a
waste of time. It is counter productive to allow
discussions like this to be open indefinitly though. They should be closed and
only open for short periods of time when a decision needs to be made. I'd like
to be notified too i.e. when
discussions for a particular topic of interest are open and active.
I guess the github issue tracker will probably works best for this kind of
thing. Not ideal, but close.
* You can keep the
dicussion part of the issue closed and then open it at the appropriate
time.
* You can watch an issue in github, so that kinda notifies you
when it opens.
If duplicates open on nabble or anywhere else. Close them. Post a link to the
github issue. And a link in the issue back to the duplicate. The issue should
explain why the dicussion is currently closed and when it will be opened.
... or something like that. :)
Regards,
Gerard
