Re: [orion-dev] Fresh workspace on orion.eclipse.org

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

Sorry, I should have been ultra-clear here.
I am referring to orion.eclipse.org. This is a self-hosting server used
by Orion committers and contributors (about 20 people). This does not affect
orionhub.org. Orion hub will likely also need clearing out at some point,
although we might wait for closer to the 0.4 release.

John

John Arthorne/Ottawa/IBM@IBMCA
Sent by: orion-dev-bounces@xxxxxxxxxxx

01/13/2012 11:38 AM

Please respond to
Orion developer discussions <orion-dev@xxxxxxxxxxx>

To	Orion developer discussions <orion-dev@xxxxxxxxxxx>
cc
Subject	Re: [orion-dev] Fresh workspace on orion.eclipse.org

As discussed in yesterday's orion meeting,
I will be wiping the Orion workspace this weekend. It will be done some
time after 9pm EST *tonight*. User accounts will remain active. I will
copy the actual project contents to a backup folder so it will be around
for awhile if you forgot to push something to a remote repository.

John

John Arthorne/Ottawa/IBM@IBMCA
Sent by: orion-dev-bounces@xxxxxxxxxxx

01/11/2012 05:20 PM

Please respond to
Orion developer discussions <orion-dev@xxxxxxxxxxx>

To	orion-dev@xxxxxxxxxxx
cc
Subject	[orion-dev] Fresh workspace on orion.eclipse.org

We had a bug in Orion 0.3 that could result in multiple users having write
access to the same project [1]. Even though it was fixed long ago, we are
still having it show up on orion.eclipse.org. This is how it happens:

1) Using Orion 0.3 or earlier, User A deleted a project. Due to the bug
we did not remove that user's permission to edit that project
2) Much later (i.e., now), User B creates a new project, and the project
id from 1) is reused (because no such project exists right now)

-> Now User A and B both have write access to the project created by
User B. 

To free us from this bug I am suggesting that we wipe out the orion.eclipse.org
server workspace and start fresh. We can pick a time well in advance to
ensure everyone has pushed their changes to a git branch. Team members
would just need to re-clone their repositories in the new workspace.

The alternative is to attempt to "fix" our existing metadata
to repair the broken permissions still kicking around from the old bug.
I wrote up a script to do this, but I'm really not feeling confident about
running this over a large existing install. Starting fresh is the only
way we can be certain that no similar problems have come up since the original
bug was fixed. This still happens to people once in awhile, and we have
no way to determine if it's a new problem or caused by bad old metadata.

We can talk about the logistics of the workspace wipe at our call tomorrow
and proceed from there. 

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=356974_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev