Re: [eclipse.org-architecture-council] 8-Sep AC Meeting Notes

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

> The user story
that Working Sets aims to address, isn't it better served with different
workspaces and/or nested projects?

OK. I'll check with MikeM. He told me
that he has some UX designer that could do some FEEP work. Just getting
rid of the dust in the guidelines would be worthwhile in my opinion.

Dani



From:      
 Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
To:      
 "eclipse.org-architecture-council"
<eclipse.org-architecture-council@xxxxxxxxxxx>
Date:      
 09.09.2016 15:15
Subject:    
   Re: [eclipse.org-architecture-council]
8-Sep AC Meeting Notes
Sent by:    
   eclipse.org-architecture-council-bounces@xxxxxxxxxxx

---

From: <eclipse.org-architecture-council-bounces@xxxxxxxxxxx>
on behalf of Daniel Megert <daniel_megert@xxxxxxxxxx>
Reply-To: Eclipse Architecture Council
<eclipse.org-architecture-council@xxxxxxxxxxx>
Date: Friday, September 9, 2016 at 4:50 AM
To: Eclipse Architecture Council <eclipse.org-architecture-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-architecture-council] 8-Sep AC Meeting Notes

Hi Doug

I suggest to have the discussions for the UI guidelines on https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group.
Those from the Architecture Council and IDE mailing lists can join there.

Excellent! Thank you.



As for my AI regarding FEEP: I see two choices: have a UI designer just
clean up what we have already, e.g. replace outdated examples and screenshots
with what we shipped in Neon. That way it won't look like a dead document
anymore. Or we wait until we have some concrete changes that we want to
see applied to the document.





Dani



From:        Doug
Schaefer <dschaefer@xxxxxxxxxxxxxx>
To:        "eclipse.org-architecture-council"
<eclipse.org-architecture-council@xxxxxxxxxxx>
Date:        08.09.2016
20:49
Subject:        Re:
[eclipse.org-architecture-council] 8-Sep AC Meeting Notes
Sent by:        eclipse.org-architecture-council-bounces@xxxxxxxxxxx

---

Hey gang, as Martin noted, I’ll be driving a renewed effort with a committee
studying and providing UI Guidelines and more generally User Experience
Guidelines that we would want all projects, internal and third party, to
follow when contributing to the Eclipse IDE User Interface.

I need to figure out a couple of logistics but look for an e-mail here
where I will ask for volunteers to help contribute ideas to the effort.
This really needs to be a community effort so we can maximize peer pressure
to help projects do the right thing, so I may expand it to more than just
the Architecture Council at least for input. At times, making decisions
will be hard, but we need to have a strong front to make a difference and
not everyone will be happy as individuals. Hopefully we can all rise above
that and focus on the end goal of making the Eclipse IDE a world leader
again.

More when I figure out how to proceed. But really looking forward to what
we can achieve.

Doug.

From: <eclipse.org-architecture-council-bounces@xxxxxxxxxxx>
on behalf of "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
Reply-To: Eclipse Architecture Council <eclipse.org-architecture-council@xxxxxxxxxxx>
Date: Thursday, September 8, 2016 at 12:50 PM
To: Eclipse Architecture Council <eclipse.org-architecture-council@xxxxxxxxxxx>
Subject: [eclipse.org-architecture-council] 8-Sep AC Meeting Notes

Hi all,
 
Notes of today’s meeting are now online:
https://wiki.eclipse.org/Architecture_Council/Meetings/September_8_2016
 
Interesting follow-up to expect – read the notes for details J
 
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind
River
direct +43.662.457915.85  fax +43.662.457915.6
 _______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxxto request removal.
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.