Re: Feedback on iProjects - good, bad and ugly

I wanted something like a member filter, to group source members together,
but to show me members that no longer existed in the development library,
because they were promoted to production. i Projects was not well suited
to this task. I couldn't really figure out what it was supposed to be used
for, so I abandoned it. If it is for managing open source type projects,
then that explains it, as we don't do any of that here.

I understand that I may be like an ignorant customer complaining that my
car didn't work well as a submarine, but you seem to be asking why i
Projects isn't more widely adopted, so I though it pertinent to say that
for us, it doesn't seem designed for what we need.


___________________________________
Darren Strong
Dekko





From: "Edmund Reinhardt" <edmund.reinhardt@xxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Cc: Rob Cecco <cecco@xxxxxxxxxx>
Date: 04/19/2017 06:21 PM
Subject: [WDSCI-L] Feedback on iProjects - good, bad and ugly
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



As RDi architect, I want to make sure that I don't get out of touch with
your experience in using RDi in the trenches.
For example, I might think that i Projects are a perfect way for people to
be able to use Git on IBM i and maybe I am missing some reason why people
are not adopting i Projects.
So please set me straight.
Who is using i Projects and if so how do you like it?
If you have tried i Projects and abandoned them, let me know why?

I am very thankful to have access to such a vocal group of customers that
I
can get unfiltered, immediate feedback from.

Thanks
Edmund