Re: Can envisage.get_application be used?
Not that this would solve the problem, but someone recommended a blog to
summarize key happenings inside Enthought. We definitely need to clarify
our communication with customers and open source contributers, a blog
could go a long way towards this goal if its properly maintained.
Dave Peterson wrote:
> I hear your complaints, and I've thought the same things myself.
> Verbally doesn't cut it because people may not have been present or
> can too easily forget. The mailing list isn't quite appropriate
> either, though it is better than anything else we have at the moment.
> Having a better form of communicating our standard coding practices is
> something I'll be working on as soon as I can roll off of P&G dev tasks.
> Once that is established though, I'll be expecting people to actually
> conform to those standard coding practices!
> -- Dave
> Peter Wang wrote:
>> Jason Sugg wrote ..
>>> so enthought-dev is now our official means of internal technology
>>> communications? i read it sometimes, but there's a lot of cruft that i
>>> skip over. if there are going to be official pronouncements like this
>>> then they need to be directed to another forum like, say,
>> I think it's appropriate to keep it on enthought-dev, but I agree that
>> such a significant change should be more visibly announced. I follow