RE: [dsdp-pmc] FW: [cross-project-issues-dev] Reminder andinstructions t

["Sandin Diego-WDS057" <wds057@xxxxxxxxxxxx>]

Hi,

The MTJ team is tracking our Galileo Status at
http://wiki.eclipse.org/DSDP/MTJ/Galileo_Train_Gap

Diego

-----Original Message-----
From: dsdp-pmc-bounces@xxxxxxxxxxx [mailto:dsdp-pmc-bounces@xxxxxxxxxxx]
On Behalf Of Kurzke Christian-E11581
Sent: Friday, April 03, 2009 6:17 PM
To: DSDP PMC list; Paula Gustavo-WGP010
Subject: Re: [dsdp-pmc] FW: [cross-project-issues-dev] Reminder
andinstructions to completeG-bugs

Hi Doug,

the MTJ team is actively tracking our Galileo Status, and we're "good to

go" in all mandatory areas.
We have a few open questions on the "optional" items:

Branding (DSDP Logo?)
       Should MTJ use the DSDP Logo in the About screen?

"Provider Name"
       What should we use as the Provider name? Eclipse.org


"Contribute to Welcome Screen"
       Typically only the "top level projects" are expected to 
contribute to the welcome screen.
       In the case of MTJ, (esp. with light of Pulsar), should we have 
our own Welcome Screen entry?


your thoughts?

Christian


Gaff, Doug wrote:
> Martin, Christian, Eric -
>
> I know you guys are actively looking at this, but I want to ask if you
> have any concerns with the remaining Galileo requirements.
>
> Doug
>
>
>
> -----Original Message-----
> From: cross-project-issues-dev-bounces@xxxxxxxxxxx
> [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of
David
> M Williams
> Sent: Friday, April 03, 2009 12:53 AM
> To: cross-project-issues-dev@xxxxxxxxxxx
> Subject: [cross-project-issues-dev] Reminder and instructions to
> completeG-bugs
>
> G-bugs: those celestial canaries describing our progress towards
> nirvana. 
> Or, in other words, the bugs listed in our Galileo status chart: 
> http://www.eclipse.org/projects/galileo_status.php
>
> As you can see in the chart, the canaries are telling us to get out
> while 
> we still can! I exaggerate ... more than half are green or have some 
> status ... though it should be about 80% by now. 
>
> But I wanted to remind people to complete them and get them to some 
> resolved state, especially, obviously, for those past due for past 
> milestones. From reading some of the yellow ones, they either say
> nothing, 
> or say something that sounds like maybe they should be marked
'fixed'?! 
>
> Maybe it would help if I gave some instructions on how to make
progress.
>
>
> For one, if you don't think you'll be able to do something ... or, you

> think maybe there is a 50/50 chance you'll be able to pull it off at
the
>
> last minute, then don't wait, just mark is "won't fix" and give some 
> explanation as to why. Almost any reason will do, "not enough time",
> "not 
> enough people", "we don't know what this means", "doesn't apply to us"
> ... 
> what ever. (And if a miracle happens and you do it later, you can
change
>
> the status then). 
>
> This at least allows others in the community (planners and adopters)
to 
> get a better idea of what's coming. 
>
> One prime example, that many adopters are very interested in, is the 
> "accessibility" item. Due at M4! And only half the projects have
marked 
> anything. And it's so easy, do you design and test for accessibility
or 
> not? [am I missing some complication that makes this hard to say? If
you
>
> don't know what accessibility means, mark it as "won't fix" and just 
> explain you don't know what accessibility means. Then we'll know to
work
>
> on that for next year!]
>
> Here's another tip ... next year we'll be more explicit ... in bugs
such
>
> as the one for "builds reproducible by others", nearly everyone just
> said 
> "yes" and marked fixed. Why not give a link to instructions for how to
> do 
> it? I'm pretty sure none are so easily reproducible that it's just 
> intuitive. 
>
> And, don't forget, if there's every any questions or issues, feel free
> to 
> ask here on this list ... someone will know the answer or be able to
> help. 
>
>
> I guess you get the idea if you've read this far ... which is that
I'll 
> keep sending nag notes until it's done! :) 
>
> Thank you all very much! Seriously! 
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> _______________________________________________
> dsdp-pmc mailing list
> dsdp-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-pmc
>   

_______________________________________________
dsdp-pmc mailing list
dsdp-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-pmc