Community
Participate
Working Groups
Migrate all remaining functionality from Portal to PMI/Website/Site_login and close down the portal. We've already identified all the remaining components, who owns them and possible new homes.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
(In reply to Denis Roy from comment #0) > Migrate all remaining functionality from Portal to PMI/Website/Site_login > and close down the portal. > > We've already identified all the remaining components, who owns them and > possible new homes. +1 We need to be more transparent about this change since it will change where our committers update their information. We have quite a few bugs open in our private bugzilla instance and we should probably move them to bugzilla to announce our plans. Eric, can you move portal related bugs in infrazilla to bugzilla and mark them has a blocker for this bug?
(In reply to Christopher Guindon from comment #2) > (In reply to Denis Roy from comment #0) > > Migrate all remaining functionality from Portal to PMI/Website/Site_login > > and close down the portal. > > > > We've already identified all the remaining components, who owns them and > > possible new homes. > > +1 > > We need to be more transparent about this change since it will change where > our committers update their information. > > We have quite a few bugs open in our private bugzilla instance and we should > probably move them to bugzilla to announce our plans. > > Eric, can you move portal related bugs in infrazilla to bugzilla and mark > them has a blocker for this bug? Ok no problem.
> We have quite a few bugs open in our private bugzilla instance and we should > probably move them to bugzilla to announce our plans.
I meant to +1 that comment.
All the blocker bugs have been resolved. I think to shut down the portal we need to find out what are the paperworks that are still active in the Portal and wait for the them to be done.
(In reply to Eric Poirier from comment #6) > All the blocker bugs have been resolved. > > I think to shut down the portal we need to find out what are the paperworks > that are still active in the Portal and wait for the them to be done. It's time to schedule a EOL date for the EOL of the Portal!!
(In reply to Christopher Guindon from comment #7) > (In reply to Eric Poirier from comment #6) > > All the blocker bugs have been resolved. > > > > I think to shut down the portal we need to find out what are the paperworks > > that are still active in the Portal and wait for the them to be done. > > It's time to schedule a EOL date for the EOL of the Portal!! It's time to schedule a EOL date for the Portal!!
Is 'right now' acceptable? :) How about Oct 31st? That gives us an extra month in case something got missed, but it's soon enough that we'll all be looking forward to it. -M.
+1 for Oct 31!!!
(In reply to Eclipse Webmaster from comment #9) > Is 'right now' acceptable? :) > > How about Oct 31st? That gives us an extra month in case something got > missed, but it's soon enough that we'll all be looking forward to it. > > -M. As far as I know, there is a possibility that we still have some elections on-going in the portal. Can someone confirm this?
(In reply to Christopher Guindon from comment #11) > (In reply to Eclipse Webmaster from comment #9) > > Is 'right now' acceptable? :) > > > > How about Oct 31st? That gives us an extra month in case something got > > missed, but it's soon enough that we'll all be looking forward to it. > > > > -M. > > As far as I know, there is a possibility that we still have some elections > on-going in the portal. > > Can someone confirm this? I would like to propose that we communicate our plan with Foundation staff and our community before we pull the plug. We should send out an email to announce that we will turn off the Eclipse Portal on Oct 31, 2018. I want to make sure that we are not missing an important corner case.
(In reply to Christopher Guindon from comment #11) > Can someone confirm this? From what I can see there is one election open, but it's due to close on September 28. > We should send out an email to announce that we will turn off the Eclipse > Portal on Oct 31, 2018. I've notified both staff and cross-project about the impending shutdown, and that any services they need migrated are to be reported as blockers to this bug. -M.
(In reply to Eclipse Webmaster from comment #13) > (In reply to Christopher Guindon from comment #11) > > > Can someone confirm this? > > From what I can see there is one election open, but it's due to close on > September 28. > > > We should send out an email to announce that we will turn off the Eclipse > > Portal on Oct 31, 2018. > > I've notified both staff and cross-project about the impending shutdown, and > that any services they need migrated are to be reported as blockers to this > bug. > > -M. Awesome! Thanks for doing this! In the meanwhile we can discuss what we should do with existing urls to the portal. As previously discussed, we should create a redirect to accounts.eclipse.org or redirect all the traffic to a new page with some verbiage that explain that we've replaced the portal with accounts.eclipse.org.
Hi, I just miss one topic from the portal -> decommitterize Project Leads: [manage] inactive committers on the project Or did I miss something? Best regars Angelika
(In reply to Angelika Wittek from comment #15) > Hi, > > I just miss one topic from the portal -> decommitterize > > Project Leads: > [manage] inactive committers on the project > > Or did I miss something? > > Best regars > Angelika Hi Angelika, it's possible for Project lead to retire committers on a project via projects.eclipse.org. You can start this process by clicking on the committer you wish to retire via the "Who's involved" page: https://projects.eclipse.org/projects/technology.mdmbl/who
Hi, thanks. I looked at it, the link is there. Unfortunaltly there is no documentation about that. And it is not obvious. Why this is not a topic on the project page, like "nominate a committer" only shown for PLs? Thanks Angelika
(In reply to Angelika Wittek from comment #17) > Hi, > thanks. I looked at it, the link is there. > Unfortunaltly there is no documentation about that. And it is not obvious. You are right! The PMI page on the wiki mention that the Developer Portal is still used for Committer elections, Committer retirement (emeritus designation); and Intellectual Property Contribution Questionnaires. https://wiki.eclipse.org/Project_Management_Infrastructure We should update this page before the Developer Portal is shutdown! I will open a blocker bug for this. > > Why this is not a topic on the project page, like "nominate a committer" > only shown for PLs? Any committer on a project can nominate a committer. Are you sure that this link is only visible to PLs? > > Thanks > Angelika
Yes, every commmitter from a project can nomitate new committer for this project. Only the PL can retire committer.
The portal is now gone and Wayne updated the wiki documentation. Closing this bug!
https://portal.eclipse.org/ now shows the API docs. I think we should redirect to the api docs. WDYT?
(In reply to Denis Roy from comment #21) > https://portal.eclipse.org/ now shows the API docs. I think we should > redirect to the api docs. WDYT? +1 It should be a redirect! As we just discussed, we should redirect to accounts.eclipse.org since the portal was ment to allows committers to update their information.