Bugzilla – Full Text Bug Listing
| Summary: | Move and rename DSDP/TmL to DSDP/Sequoyah | ||
|---|---|---|---|
| Product: | Community | Reporter: | Eric Cloninger <ericc> |
| Component: | Website | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | anne.jacko, emo, ericc, kpqb38, sharon.corbett, webmaster, wmg040 |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Eric Cloninger
Hi Eric: I have a few questions that I need your help with in order to kick off this process regarding committers and IPzilla CQs. 1. Is the intent to completely archive DSDP TML and move fully to DSDP Sequoyah? 2. Confirming the intent to move certain MTJ content to Sequoyah as well with MTJ continuing to function as a sub project of DSDP? 3 All existing TML committers will move to Sequoyah? If not all, please indicate which committers? 4. Certain MTJ committers will move to Sequoyah? Please identify those committers? For those that will also commit to Sequoyah, will they also remain as MTJ committers? 5. I will arrange to move all TML CQs in IPzilla to align with the new sub project of Sequoyah. 6. Please advise which MTJ CQs need to be aligned with Sequoyah (if any)? If any are to move, can you please ensure they can move vs the project will have to create new ones in Sequoyah. The intent here is to ensure we don't move any CQs from MTJ that MTJ may still require(especially if third party content). Look forward to hearing from you. Regards, Sharon FYI, I added the new project dsdp.sequoyah to the Foundation database. Please let me know when it's time to archive the projects that are going away. (In reply to comment #1) > Hi Eric: Hi Sharon, I will do my best to answer these. > I have a few questions that I need your help with in order to kick off this > process regarding committers and IPzilla CQs. > > 1. Is the intent to completely archive DSDP TML and move fully to DSDP > Sequoyah? Only those components that are active in TmL. We have several deprecated components and some that were never completed. Those will not be migrated. Plug-ins that are in active development: org.eclipse.tml.common.utilities org.eclipse.tml.framework.device org.eclipse.tml.framework.device.sdk org.eclipse.tml.framework.device.ui org.eclipse.tml.framework.device.wizard org.eclipse.tml.framework.device.additional org.eclipse.tml.protocol org.eclipse.tml.service.start org.eclipse.tml.service.stop org.eclipse.tml.service.vncviewer org.eclipse.tml.vncviewer org.eclipse.tml.vncviewer.vncviews New components (not in Galileo) to be added to new project: org.eclipse.tml.fakedevice.display org.eclipse.tml.fakedevice.keyboard org.eclipse.tml.fakedevice.storage org.eclipse.tml.framework.device.fake org.eclipse.tml.framework.device.fake.ui org.eclipse.tml.service.fake org.eclipse.tml.localization.tools org.eclipse.tml.localization.stringeditor org.eclipse.tml.localization.android Example components: org.eclipse.tml.device.qemu org.eclipse.tml.device.qemuarm org.eclipse.tml.device.qemureact org.eclipse.tml.echo > 2. Confirming the intent to move certain MTJ content to Sequoyah as well with > MTJ continuing to function as a sub project of DSDP? Correct. The Pulsar components will move into Sequoyah. All the Java ME components will continue to exist as MTJ. > 3 All existing TML committers will move to Sequoyah? If not all, please > indicate which committers? All will move. > 4. Certain MTJ committers will move to Sequoyah? Please identify those > committers? For those that will also commit to Sequoyah, will they also remain > as MTJ committers? Gustavo Paula, Diego Sandin, and Jon Dearden should be added once their paperwork in MTJ is completed. > 5. I will arrange to move all TML CQs in IPzilla to align with the new sub > project of Sequoyah. Agreed. > 6. Please advise which MTJ CQs need to be aligned with Sequoyah (if any)? If > any are to move, can you please ensure they can move vs the project will have > to create new ones in Sequoyah. The intent here is to ensure we don't move any > CQs from MTJ that MTJ may still require(especially if third party content). I will ask Christian Kurzke to take action on this. > Look forward to hearing from you. > Regards, > Sharon Thanks -E Webmaster: Legal has checked the paperwork for the TML committers and all active committers may be moved to Sequoyah. Regarding MTJ committers to move to Sequoyah namely; Gustavo Paula, Diego Sandin, and Jon Dearden... I need to check their paperwork a little further and will advise. I do not see Jon Dearden listed as a committer however. Christian: It will be important to get the CQs moved as soon as Webmaster arranges the move so I'll stand by to hear from you. Thanks, Sharon For the transition to SVN I'll need a complete map of what in CVS(I'll presume paths are rooted in /cvsroot/dsdp) is moving. Just attach the map to this bug and I'll ask if I have questions. Just so you know our tool for converting from CVS to SVN works best when everything is in a 'monolithic' CVS repository. Since your repositories appear to be spread out we may have some difficulty in importing things. -M. After a polite nudge from Eric here's what I"m proposing to move this along: 1) Copy the TML website from /www/dsdp/tml to /www/sequoyah . When the team is ready we'll clean out /www/dsdp/tml and they can commit a 're-direct' to point requests at the new site. 2) Move the TML downloads from downloads.eclipse.org/dsdp/tml to downloads.eclipse.org/sequoyah . 3) Move the TML archives in the same way as the downloads. 4) Create the SVN repository and import code. I'll need the import map previously requested but I can create the initial repository without it. I have a couple of more questions: Should the SVN repository be accessible for commits over HTTPS? It's not part of our default setup since we(webmaster) view it as a security risk. Mailing lists and newsgroups - We can't rename these, the best we can do is archive the current ones and create new ones. How would you like to handle this? -M. (In reply to comment #6) > Should the SVN repository be accessible for commits over HTTPS? It's not part > of our default setup since we(webmaster) view it as a security risk. HTTPS is not necessary. > Mailing lists and newsgroups - We can't rename these, the best we can do is > archive the current ones and create new ones. How would you like to handle > this? We don't presently use the newsgroups, so there is no concern there. The mailing list is low- to medium- traffic, so the impact is negligible. Just create new ones and archive the existing ones. It would be nice if we have access to the mailing list archives for historical purposes. Thanks > HTTPS is not necessary. Ok. > We don't presently use the newsgroups, so there is no concern there. The > mailing list is low- to medium- traffic, so the impact is negligible. Just > create new ones and archive the existing ones. It would be nice if we have > access to the mailing list archives for historical purposes. Not a problem. The archives remain on-line after a list is archived. -M. Updating assignee. I've added a note on my calendar to revisit the read-only timing in January. -M. Hi Eric: Couple of other issues.... 1. We really need to move the necessary CQs in IPzilla. Have you heard from Christian concerning this? 2. The MTJ committers cannot be moved at this time as their paperwork unfortunately does not align to provide for this access. I have emailed their employer but have received no response to date. Perhaps you can let them know and one of them can work with the employer to gain the necessary response. Regards, Sharon Hi,
we have completed the list of packages to be moved to Sequoyah, as follow:
/cvsroot/dsdp/tml/
org.eclipse.tml.device
examples
org.eclipse.tml.device.qemu
org.eclipse.tml.device.qemuarm
org.eclipse.tml.device.qemureact
features
org.eclipse.tml.common.feature
org.eclipse.tml.device.examples.feature
org.eclipse.tml.device.feature
org.eclipse.tml.framework.device.sdk
org.eclipse.tml.linuxtools.feature
org.eclipse.tml.device.sdk.feature
org.eclipse.tml.site
plugins
org.eclipse.tml.common.utilities
org.eclipse.tml.framework.device
org.eclipse.tml.framework.device.additional -> will be org.eclipse.sequoyah.framework.device.sdk
org.eclipse.tml.framework.device.ui
org.eclipse.tml.framework.device.wizard
org.eclipse.tml.linuxtools
org.eclipse.tml.linuxtools.base
org.eclipse.tml.service.start
org.eclipse.tml.service.stop
org.eclipse.tml.service.vncviewer
org.eclipse.tml.localization
features
org.eclipse.tml.localization.android.feature
org.eclipse.tml.localization.tools.feature
plugins
org.eclipse.tml.localization.android
org.eclipse.tml.localization.android.help
org.eclipse.tml.localization.stringeditor
org.eclipse.tml.localization.tools
org.eclipse.tml.vnc
features
org.eclipse.tml.protocol.feature
org.eclipse.tml.vnc.feature
org.eclipse.tml.vnc.protocol.examples.feature
org.eclipse.tml.vnc.viewer.feature -> will be org.eclipse.sequoyah.vncviewer.feature (notice the removal of the dot)
org.eclipse.tml.vncviewer.vncviews.feature
plugins
org.eclipse.tml.protocol
org.eclipse.tml.vncviewer
org.eclipse.tml.vncviewer.vncviews
Thanks,
Daniel Pastore
I'm working on a script to handle the import. I'll post here when I've managed an initial import so you can verify that things are as you expect them. -M. Ok, I've setup the repository here: http://dev.eclipse.org/svnroot/dsdp/org.eclipse.sequoyah . Please note that this is a 'read-only' copy for the TML team to verify the import. Once I have that confirmation I'll open the repository for writing via svn+ssh. -M. Hi Matt,
I was verifying the repository and I found some issues. Could you take a look at them, please?
1) The plugins directory is missing for org.eclipse.tml.vnc. There are 3 plugins missing:
org.eclipse.tml.protocol
org.eclipse.tml.vncviewer
org.eclipse.tml.vncviewer.vncviews
2) All plugins/features/examples names will change from org.eclipse.tml to org.eclipse.sequoyah. I wasn't specific about these names, but all of them should be changed.
Thanks for the attention,
Daniel Pastore
Ok, I've added the missing folders and renamed the files. Please check the repository again and let me know what's not right. -M. Hi Matt, I'll explicit some other final changes, alright? 1) On org.eclipse.sequoyah.device: a) features: *org.eclipse.sequoyah.common.feature -> org.eclipse.sequoyah.device.common.feature *org.eclipse.sequoyah.framework.device.sdk -> org.eclipse.sequoyah.device.framework.sdk.feature *org.eclipse.sequoyah.linuxtools.feature -> org.eclipse.sequoyah.device.linuxtools.feature *org.eclipse.sequoyah.site -> org.eclipse.sequoyah.site.feature b) plugins: *org.eclipse.sequoyah.common.utilities -> org.eclipse.sequoyah.device.common.utilities *org.eclipse.sequoyah.framework.device -> org.eclipse.sequoyah.device.framework *org.eclipse.sequoyah.framework.device.additional -> org.eclipse.sequoyah.device.framework.sdk *org.eclipse.sequoyah.framework.device.ui -> org.eclipse.sequoyah.device.framework.ui *org.eclipse.sequoyah.framework.device.wizard -> org.eclipse.sequoyah.device.framework.wizard *org.eclipse.sequoyah.linuxtools -> org.eclipse.sequoyah.device.linuxtools *org.eclipse.sequoyah.linuxtools.base -> org.eclipse.sequoyah.device.linuxtools.base *org.eclipse.sequoyah.service.start -> org.eclipse.sequoyah.device.service.start *org.eclipse.sequoyah.service.stop -> org.eclipse.sequoyah.device.service.stop *org.eclipse.sequoyah.service.vncviewer -> org.eclipse.sequoyah.device.service.vncviewer 2) On org.eclipse.sequoyah.vnc a) features: *org.eclipse.sequoyah.protocol.feature -> org.eclipse.sequoyah.vnc.protocol.feature *org.eclipse.sequoyah.vnc.viewer.feature -> org.eclipse.sequoyah.vnc.vncviewer.feature *org.eclipse.sequoyah.vncviewer.vncviews.feature -> org.eclipse.sequoyah.vnc.vncviewer.vncviews.feature b) plugins: *org.eclipse.sequoyah.protocol -> org.eclipse.sequoyah.vnc.protocol *org.eclipse.sequoyah.vncviewer -> org.eclipse.sequoyah.vnc.vncviewer *org.eclipse.sequoyah.vncviewer.vncviews -> org.eclipse.sequoyah.vnc.vncviewer.vncviews With these changes we'll be ok with the moving. Thanks again for the attention and a Happy Christmas to all you guys! Daniel Pastore Hi Matt, I'll explicit some other final changes, alright? 1) On org.eclipse.sequoyah.device: a) features: *org.eclipse.sequoyah.common.feature -> org.eclipse.sequoyah.device.common.feature *org.eclipse.sequoyah.framework.device.sdk -> org.eclipse.sequoyah.device.framework.sdk.feature *org.eclipse.sequoyah.linuxtools.feature -> org.eclipse.sequoyah.device.linuxtools.feature *org.eclipse.sequoyah.site -> org.eclipse.sequoyah.site.feature b) plugins: *org.eclipse.sequoyah.common.utilities -> org.eclipse.sequoyah.device.common.utilities *org.eclipse.sequoyah.framework.device -> org.eclipse.sequoyah.device.framework *org.eclipse.sequoyah.framework.device.additional -> org.eclipse.sequoyah.device.framework.sdk *org.eclipse.sequoyah.framework.device.ui -> org.eclipse.sequoyah.device.framework.ui *org.eclipse.sequoyah.framework.device.wizard -> org.eclipse.sequoyah.device.framework.wizard *org.eclipse.sequoyah.linuxtools -> org.eclipse.sequoyah.device.linuxtools *org.eclipse.sequoyah.linuxtools.base -> org.eclipse.sequoyah.device.linuxtools.base *org.eclipse.sequoyah.service.start -> org.eclipse.sequoyah.device.service.start *org.eclipse.sequoyah.service.stop -> org.eclipse.sequoyah.device.service.stop *org.eclipse.sequoyah.service.vncviewer -> org.eclipse.sequoyah.device.service.vncviewer 2) On org.eclipse.sequoyah.vnc a) features: *org.eclipse.sequoyah.protocol.feature -> org.eclipse.sequoyah.vnc.protocol.feature *org.eclipse.sequoyah.vnc.viewer.feature -> org.eclipse.sequoyah.vnc.vncviewer.feature *org.eclipse.sequoyah.vncviewer.vncviews.feature -> org.eclipse.sequoyah.vnc.vncviewer.vncviews.feature b) plugins: *org.eclipse.sequoyah.protocol -> org.eclipse.sequoyah.vnc.protocol *org.eclipse.sequoyah.vncviewer -> org.eclipse.sequoyah.vnc.vncviewer *org.eclipse.sequoyah.vncviewer.vncviews -> org.eclipse.sequoyah.vnc.vncviewer.vncviews With these changes we'll be ok with the moving. Thanks again for the attention and a Happy Christmas to all you guys! Daniel Pastore Ok, I've updated the import scripts and have run them against the latest CVS. With this import tags and branches should also be correctly renamed. Please take a look and confirm that everything is as expected. -M. Hi Matt, there's still one item to correct: on org.eclipse.sequoyah.device/plugins, org.eclipse.sequoyah.device.framework.additional should be org.eclipse.sequoyah.device.framework.sdk. After you make this change, will the repository be ready for us to commit? Thanks, Daniel Pastore Ok, the repo should be ready. Can we move the downloads/archives and website this week as well? -M. (In reply to comment #20) > Ok, the repo should be ready. Thanks! > Can we move the downloads/archives and website this week as well? Yes, as long as TmL's stuff stays available for the next six months (not a problem if it becomes read-only). Thanks, Daniel Pastore Hi Matt, (In reply to comment #20) > Ok, the repo should be ready. Could you please grant us permission to commit? Thanks, Daniel Pastore Sorry about that, I forgot to update the authz file. I'm planning to 'move' the rest of your data tomorrow and set the old stuff as read only. -M. Hi Matt, (In reply to comment #23) > Sorry about that, I forgot to update the authz file. Not a problem, but it isn't working yet. :) When you check, could you please grant permission to all TmL committers at once? > I'm planning to 'move' the rest of your data tomorrow and set the old stuff as > read only. Ok. Thanks, Daniel Pastore Looks like the ACLs were getting in the way. I've committed a test file(and removed it) and things are working.
I've also:
-Closed the old mailing lists and created new ones which can be found here:
https://dev.eclipse.org/mailman/listinfo/dsdp-sequoyah-dev
and here:
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev
and here:
https://dev.eclipse.org/mailman/listinfo/sequoyah-commit
-Copied the downloads/archives/website data into:
download.eclipse.org/sequoyah
archive.eclipse.org/sequoyah
www/sequoyah
The old data has been marked read only, and we need to organize the re-direct as mentioned in comment 6.
In a few months we'll clean up the 'old' data', but I think that's it.
-M.
Hi Folks: I've moved all the TML CQs in Ipzilla to align with Sequoyah. If any of those CQs are determined to be no longer required, please let us know and we will mark them as "obsolete" for the project. TML had previously been marked as conforming to incubation. Based on the rename/ move, the project will need to ensure it meets the incubating conformance guidelines once again. Those guidelines can be located @ http://wiki.eclipse.org/Development_Resources/HOWTO/Conforming_Incubation_Branding. When the project is conforming, please send an email to emo@eclipse.org and request the project status to be changed. Thanks, Sharon Hi Matt, Now it's time for us to work with MTJ components that will move to Sequoyah. Could you please also move these packages from MTJ's SVN to Sequoyah's? features/ -- org.eclipse.mtj.pulsar/ -- org.eclipse.mtj.pulsar.test/ -- org.eclipse.mtj.pulsar.tool/ -- org.eclipse.mtj.tfm.sign/ -- org.eclipse.mtj.tfm.sign.sdk/ plugins/ -- org.eclipse.mtj.tfm.sign.core/ -- org.eclipse.mtj.tfm.sign.core.permission/ -- org.eclipse.mtj.tfm.sign.smgmt.ibm/ -- org.eclipse.mtj.tfm.sign.smgmt.j9/ -- org.eclipse.mtj.tfm.sign.smgmt.sun/ -- org.eclipse.mtj.tfm.sign.ui/ -- org.eclipse.mtj.tfm.sing.doc.isv/ -- org.eclipse.mtj.tfm.sing.doc.user/ tests/ -- org.eclipse.mtj.pulsar.core.tests/ -- org.eclipse.mtj.tfm.sign.test.core/ tools/ -- org.eclipse.mtj.pulsar.metadata.generator/ If possible, please don't refactor the packages, we will do it ourselves. Thanks again for your attention, Daniel Pastore Hi Daniel; Before Webmaster can begin; can you please provide input regarding committers and CQs as follows: 1. Please identify MTJ committers that should move as well (Gustavo and Diego cannot move until updated paperwork is received) 2. Please identify any MTJ CQs that need to be moved. When confirming this, please ensure MTJ does not require the CQ any longer. We will stand by to hear from you. Thanks, Sharon (In reply to comment #28) Hi Sharon, 1) It is our understanding that no other MTJ committers will move to Sequoyah right now. 2) The only CQ that needs to be migrated is "3273 Nokia Pulsar Contribution". Since the correspondent component will be migrated to Sequoyah, MTJ will not require this CQ once the migration is done. Can you please move it to Sequoyah? Thanks and regards, Marcel > Hi Daniel; > > Before Webmaster can begin; can you please provide input regarding committers > and CQs as follows: > > 1. Please identify MTJ committers that should move as well (Gustavo and Diego > cannot move until updated paperwork is received) > > 2. Please identify any MTJ CQs that need to be moved. When confirming this, > please ensure MTJ does not require the CQ any longer. > > We will stand by to hear from you. > > Thanks, > Sharon Excellent - thanks for your prompt response. Over to Webmaster. Thanks, Sharon I have a couple of questions: Should these 'directories' have the same location in the Sequoyah SVN? Are the revision numbers important, or can I import them with all new revision numbers? How should we handle the MTJ repo? What I'm asking is this: should I 'leave' this code in the MTJ repo, but mark it as read only (which increases the admin overhead), or should I 'filter' it out of the MTJ repo (as if it had never been there). The later would be similar to what we do with CVS moves, but either solution needs to have MTJs input. -M. Good morning, Matt! (In reply to comment #31) > I have a couple of questions: > > Should these 'directories' have the same location in the Sequoyah SVN? Yes, but we would like to move them to /branches/pulsar. > Are the revision numbers important, or can I import them with all new revision > numbers? They are nice to have, but if it represents too much trouble (like conflicts with sequoyah's actual revision numbers), they can be left aside. > How should we handle the MTJ repo? What I'm asking is this: should I 'leave' > this code in the MTJ repo, but mark it as read only (which increases the admin > overhead), or should I 'filter' it out of the MTJ repo (as if it had never > been there). We need to really *move* the code, so it's your second option. > The later would be similar to what we do with CVS moves, but either > solution needs to have MTJs input. I'm sorry, but can you clarify this a little bit? What kind of input you mean? Thanks again, Daniel Pastore > They are nice to have, but if it represents too much trouble (like conflicts > with sequoyah's actual revision numbers), they can be left aside. Ok. > We need to really *move* the code, so it's your second option. Ok. > > The later would be similar to what we do with CVS moves, but either > > solution needs to have MTJs input. > I'm sorry, but can you clarify this a little bit? What kind of input you mean? Sure. In order for me to filter these components out of the MTJ repo, I need to take their repo offline until I can verify that the data is gone. So I just want to make sure we organize a time that is convenient for both Sequoyah and MTJ to have your repos offline while this move is preformed. Now both repos don't have to be offline at the same time, but theirs does need to be offline first. -M. Hi Matt, (In reply to comment #33) > > We need to really *move* the code, so it's your second option. > > Ok. I know it sounds awkward, but we had a second thought and it is better that we just copy the code for now. > > > The later would be similar to what we do with CVS moves, but either > > > solution needs to have MTJs input. > > I'm sorry, but can you clarify this a little bit? What kind of input you mean? > > Sure. In order for me to filter these components out of the MTJ repo, I need > to take their repo offline until I can verify that the data is gone. So I just > want to make sure we organize a time that is convenient for both Sequoyah and > MTJ to have your repos offline while this move is preformed. Now both repos > don't have to be offline at the same time, but theirs does need to be offline > first. From our side, it's alright to take our repo offline anytime from now until monday morning. Also, if you *copy* MTJ's repository, it won't be necessary to take theirs offline, right? Thanks, Daniel Pastore (In reply to comment #34) Hi Matt, just one comment. If possible, we would prefer just to copy the code (for now). Our concern is that if we remove the code from MTJ repo, Pulsar EPP might break (we are not sure about this, but copying would be the safest approach right now). After we have the code migrated and Pulsar EPP correctly updated, we can remove the migrated code. What do you think? Tks, Marcel > Hi Matt, > (In reply to comment #33) > > > We need to really *move* the code, so it's your second option. > > > > Ok. > I know it sounds awkward, but we had a second thought and it is better that we > just copy the code for now. > > > > > The later would be similar to what we do with CVS moves, but either > > > > solution needs to have MTJs input. > > > I'm sorry, but can you clarify this a little bit? What kind of input you mean? > > > > Sure. In order for me to filter these components out of the MTJ repo, I need > > to take their repo offline until I can verify that the data is gone. So I just > > want to make sure we organize a time that is convenient for both Sequoyah and > > MTJ to have your repos offline while this move is preformed. Now both repos > > don't have to be offline at the same time, but theirs does need to be offline > > first. > From our side, it's alright to take our repo offline anytime from now until > monday morning. > > Also, if you *copy* MTJ's repository, it won't be necessary to take theirs > offline, right? > > Thanks, > > Daniel Pastore Works for me. I'm starting to filter the MTJ repo now, and I'll test against a copy of the Sequoyah when that's done. -M. I've put up a read only version of the 'updated' Sequoyah repo here: http://dev.eclipse.org/svnroot/dsdp/org.eclipse.sequoyah.test . Please take a look and tell me if anything is missing. -M. Hi Matt, (In reply to comment #37) > I've put up a read only version of the 'updated' Sequoyah repo here: > http://dev.eclipse.org/svnroot/dsdp/org.eclipse.sequoyah.test . Please take a > look and tell me if anything is missing. Unfortunately, there's a lot of things missing: features/ -- org.eclipse.mtj.pulsar/ -- org.eclipse.mtj.pulsar.test/ plugins/ -- org.eclipse.mtj.tfm.sign.core/ -- org.eclipse.mtj.tfm.sign.core.permission/ -- org.eclipse.mtj.tfm.sign.smgmt.ibm/ -- org.eclipse.mtj.tfm.sign.smgmt.j9/ -- org.eclipse.mtj.tfm.sign.smgmt.sun/ -- org.eclipse.mtj.tfm.sign.ui/ -- org.eclipse.mtj.tfm.sing.doc.isv/ -- org.eclipse.mtj.tfm.sing.doc.user/ tests/ -- org.eclipse.mtj.pulsar.core.tests/ -- org.eclipse.mtj.tfm.sign.test.core/ Thanks, Daniel Pastore Ok I've tuned the import filters some more and put the results in org.eclipse.sequoyah.test. Please confirm that it's what you expect. -M. Hi Matt, (In reply to comment #39) > Ok I've tuned the import filters some more and put the results in > org.eclipse.sequoyah.test. Please confirm that it's what you expect. > > -M. It's just as we need it for now. Thanks, Daniel Pastore Awesome. I'm just going to back up your repository before I run the import. -M. Ok, I've finished the backup and have imported the MTJ code into the Sequoyah repo. I'll just set the MTJ bits for this code as read only and I think we're done. -M. You guys have been very busy with this but it appears to be nearing completion. When you're done, please update the bug to say when it's time to marked TmL as "achived" in the Foundation db. Thanks. (In reply to comment #42) > Ok, I've finished the backup and have imported the MTJ code into the Sequoyah > repo. > > I'll just set the MTJ bits for this code as read only and I think we're done. > > -M. Hi Matt, could you please copy a couple of plugins to org.eclipse.sequoyah/branches/pulsar? They are located at org.eclipse.mtj/plugins: org.eclipse.mtj.pulsar.core org.eclipse.mtj.pulsar.ui I now realized that they were missing in the list, sorry for the inconvenience. Thanks, Daniel Pastore I've added the requested plugins into the Sequoyah SVN. -M. Is there anything left to do here? (In reply to comment #46) > Is there anything left to do here? Hi Denis, I think we are all set. :) (If really needed, we can reopen it later.) Thanks, Daniel Pastore Ok, closing. -M. Is it time for dsdp.tml to be archived? Hi Anne, yes, I think the time has come. How should we proceed? Best, Marcel Since TmL moved rather than terminated, once the move tasks are done I archive the old project simply by marking it as archived in the Foundation database. There may be other archiving-type tasks that the Webmasters do that are associated with this type of move, but I'm sure those have been done. So I'll update the database. Thanks. |