[ANN] Registration for C++Now 2013 is now open

[Boris Kolpackov]

The seventh annual C++Now Conference (formerly BoostCon) will be held at the
Aspen Center for Physics in Aspen, Colorado, May 12th to 17th, 2013.

"We are thrilled to announce the second annual C++Now conference,
the whole-language edition of BoostCon covering all the coolest topics
in C++," said Dave Abrahams, Conference Co-Chair. "In 2012, we broadened the
conference scope by adding a third track and offering more C++11 coverage
than any other event, and the community responded with an unprecedented
number of registrations. In 2013, we are going to build on that success
with foundational sessions integrating what we've all learned about using
C++11 during the past year, while continuing the exploration of cutting-edge
topics that BoostCon attendees have come to expect."

Early Bird Savings Deadlines!

Early Bird conference registration, which ends April 14th, 2013, costs
$599.  After that date, the registration fee is $699. Register now at our
registration page .

Early Bird hotel registration ends December 31st, 2012 and saves $20 per
night. Please reserve your room using the Aspen Meadows online reservation
system 

Speakers

If you are interested in presenting, we are currently accepting proposals
. Registration fee is waived
for one speaker of every standard session presentation. Shorter sessions are
prorated.

Student/Volunteers

Registration fees will be waived for a limited number of individuals that
wish to attend as volunteers. Volunteer work consists of helping to run the
conference and will not prevent volunteers from attending sessions. This is
the first year this opportunity is being offered. If you are interested in
applying to attend as a volunteer, contact us at .

Sponsors

For a copy of the conference Sponsorship Prospectus contact
sponsors...@cppnow.org.

C++Now is presented by Boost in-cooperation with ACM.

Permanent link for this announcement is:

http://cppnow.org/2013-registration-announcement/


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Developers and KDE Brainstorm

[Anne Wilson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/12/12 07:28, Frank Reininghaus wrote:
> Hi Anne,
> 
> 2012/12/10 Anne Wilson:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>> 
>> On 10/12/12 09:50, Frank Reininghaus wrote:
 There is a perception that devs don't listen.  This is not a
> complaint, on my part, but a statement of fact.
>>> Well, I can't speak for all developers, but on my side, there
>>> is a perception that some people believe "If I have a good
>>> idea, it will either be implemented by the maintainer of the
>>> application, or it will not be implemented at all, and then the
>>> maintainer has to provide an explanation why he/she won't
>>> implement it". This is confirmed by...
>>> 
>> I agree - there is a lot of misunderstanding.  That's why I
>> think that if we can come up with a simple acknowledgement
>> (that's why I suggested something boilerplate) some of the
>> misunderstanding can be avoided.
> 
> Yes, I think that we all agree that the frustration that results 
> from such misunderstandings should be avoided. However, I would
> say that the average wishlist report on bugs.kde.org can usually
> not be responded to with a standard reply. But this might of course
> be different for ideas which have already been discussed thoroughly
> at KDE Brainstorm.
> 
One thing I have wondered about is whether it is worth adding some
flag to show which are brainstorm wishes, making it easier to assess
whether they are in fact of a higher standard.

A point that comes to mind, is that I have seen wishes that are
complex, being in reality a combination of several ideas, which may or
may not work together.  When such an idea comes up in brainstorm the
writer is told that that is invalid.  A brainstorm idea must be about
a single issue.  That makes it easier to direct discussion in a
meaningful way, and helps the mods to see whether it is something
worth passing upstream.

If we could prove that brainstorm works better for all concerned we
could make that the *normal* way of submitting wishes :-)

Anne

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDHE4EACgkQj93fyh4cnBeDnACeNSWilA+qOTWi5ZnzXIF9d6e2
atsAnR0LDAwjp6r+kQE2t70PANJe7ZiQ
=Zsn9
-END PGP SIGNATURE-

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Developers and KDE Brainstorm

[David Jarvie]

> On Saturday 08 December 2012 23:57:35 Dion Moult wrote:
> > Every so often, I will pick the users top choices that seem plausible and
> > will bring them to _you_, and discuss how to evolve the idea into
something
> > that could be implemented. Then we can open up an enhancement bug
report in
> > BKO, and start getting some brainstorm ideas along the Submitted->In
> > progress->Done chain.
> The problem here is that nobody in the brainstorm section can know what
"could
> be implemented" without feedback from the developers. And I don't think it
> makes any sense to just move the wishes from brainstorm to bko. Happened
for
> kwin a few times and actually it was always a "meh, that's too complex" or
> "meh, that doesn't fit at all our design". Ending in that the proper
response
> would have been to directly close as WONTFIX. I cannot remember to have
ever
> gotten any user feedback that I implemented (either on bko or on
brainstorm).
> Also I do not accept that a few users voting for a feature represent the
> opinion of the user base.
>
> So my suggestion would be to get the developers' feedback into
brainstorm to
> figure out what the developers think about it. Let them tell the users what
> they think about it. I think it's more honest to say that "this would
require
> at least a person month of work, so don't expect it ever to happen" then to
> give users the feeling that they are ignored.
>
> Another general problem is that developers probably have their own
agenda and
> have their own ideas on how to take the software further. Personally I
doubt
> that anyone is waiting for users to come up with new ideas. So I see user
> suggested features at max as something for new developers.

It probably depends on the type of project as to whether users' ideas are
useful, but for KAlarm I've implemented quite a number of feature
suggestions from users. So I don't think you can generalise your own
experience in suggesting that user ideas are very unlikely to be useful.

-- 
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Developers and KDE Brainstorm

[Martin Graesslin]

On Tuesday 11 December 2012 11:05:40 Anne Wilson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 11/12/12 07:28, Frank Reininghaus wrote:
> > Hi Anne,
> > 
> > 2012/12/10 Anne Wilson:
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
> >> 
> >> On 10/12/12 09:50, Frank Reininghaus wrote:
>  There is a perception that devs don't listen.  This is not a
>  
> > complaint, on my part, but a statement of fact.
> >>> 
> >>> Well, I can't speak for all developers, but on my side, there
> >>> is a perception that some people believe "If I have a good
> >>> idea, it will either be implemented by the maintainer of the
> >>> application, or it will not be implemented at all, and then the
> >>> maintainer has to provide an explanation why he/she won't
> >>> implement it". This is confirmed by...
> >> 
> >> I agree - there is a lot of misunderstanding.  That's why I
> >> think that if we can come up with a simple acknowledgement
> >> (that's why I suggested something boilerplate) some of the
> >> misunderstanding can be avoided.
> > 
> > Yes, I think that we all agree that the frustration that results
> > from such misunderstandings should be avoided. However, I would
> > say that the average wishlist report on bugs.kde.org can usually
> > not be responded to with a standard reply. But this might of course
> > be different for ideas which have already been discussed thoroughly
> > at KDE Brainstorm.
> 
> One thing I have wondered about is whether it is worth adding some
> flag to show which are brainstorm wishes, making it easier to assess
> whether they are in fact of a higher standard.
This sounds very good. For me it would be a help to see which wish list items 
come from brainstorm as I know that this is an evaluated and discussed idea 
and not a random thought. It's also easier than to point to a list of valid 
ideas when new developers join.

Cheers
Martin

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<