I would assert that Greg’s statement is correct “in general”, but it is VERY incorrect for IBM i and IBM Power Systems.
While we tend to focus on IBM i, there is A LOT of important PowerSystems information out there.
The IBM i development team embraced the developerWorks community as a way to get information available to the user community outside of formal documentation venues (aka Knowledge Center).
The Technology Updates pages are important - but there are A LOT of wikis that the development team put together on specific topics.
Want the best BRMS tips? Some PowerHA secrets? IBM i Wiki (which I personally spent a lot of time getting current)? The PowerVM blog? P9 EnergyScale? PowerSystems VUG? HMC Scanner?
The list goes on and on and on and on…
Have you noticed there is not an “IBM i” or “Power Systems” Community in IBM Communities?
Go to this page: https://www.ibm.com/community/
Where am I supposed to migrate my IBM i information?
(I included this in my feedback to IBM).
I want to believe the IBM i development team is very concerned and doing their best to address this issue …. but ….
Do we really want IBM i development spending their important time on migrating existing documentation?
No! We want them focusing on developing new software!
I strongly think IBM needs to find a way to migrate the existing content without requiring the development team to do it.
I understand there are issues with the software being used, but to discard the content because of the underlying infrastructure is the most brain-dead approach possible.
I use the dW content every day - it is not “nice to have” information, but critical to almost everything I do.
On Nov 1, 2019, at 11:47 AM, DrFranken <midrange@xxxxxxxxxxxx<mailto:midrange@xxxxxxxxxxxx>> wrote:
And that's pretty much spot on with what Ranga and I are telling them.
I have also been observing the URLs as I get data and yeah it's WAY up there. What's worse is their insentience that 'The Community' will just deal with it by migrating their content to the new community or perhaps somewhere else.
I've been told by some who've tried that the new communities have different page rules and requirements so it's not a simple re-post, it's a full rework to get the content in there.
Further IBM ignore with that is often the content is created by people in spare time, not paid, and as a consequence they simply don't have the bandwidth to make that move. For some it will be 'the last straw' and the content, it not preserved in another way, will vanish.
And even IF it moves will you be able to find it???
- Larry "DrFranken" Bolhuis
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 11/1/2019 10:56 AM, midrangel@xxxxxxxxxxxxxxxxx wrote:
In ITJungle the IBM director with responsibility to Developerworks, Greg
Gorman says we "overreacted to the announcement and that the closures are
not a broad as they are believed"
That may be a true statement. I will counter with being alarmed at: "We
are removing half the brain of the patient" as being just as overreactive
since the brain is only a small percentage of the total body weight of the
Since that announcement I have tracked every time I use information from
that portion of Developerworks that is "being sunsetted" and it's nearly 98%
of the time. Mr. Gorman is clearly not informed of the criticality of the
information contained in that portion of the site, and clearly does not
care. IBM documentation is good. Everything is in there. It's also almost
useless when really figuring out how to do things. Hence the Developerworks
Wiki portion has become IBMs way of making things easy. Mr. Gorman
apparently does not know or care about this fundamental truth.
Put another way: How to hack off your most ardent supporters and get their
management to start looking for alternatives.
Nice play IBM.
Agile Technology Architects
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.