Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.ceylon | ||
|---|---|---|---|
| Product: | Community | Reporter: | Stephanie Swart <stephanie.swart> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | frederic.gurr, gavin, sharon.corbett, stef, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows NT | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-ceylon | ||
| Whiteboard: | |||
| Bug Depends on: | 515787, 515788 | ||
| Bug Blocks: | |||
|
Description
Stephanie Swart
We’ve received all of the project requirements and have scheduled the creation review to conclude on July 19, 2017. Please continue to monitor communication channels. Following the creation review, we will initiate the provisioning process. As part of this process, we will bring committers on board. To gain committer status, some paperwork [1] must be completed. The exact nature of that paperwork depends on several factors, including the employment status of the individual and the Eclipse Foundation membership status of the employer. If you can be ready with the paperwork in time for the completion of the creation review, then we can move quickly through the provisioning process. When we initiate provisioning, committers will be sent an email with instructions; please don't send any paperwork in until after you receive those instructions. Please encourage all future project committers to join the incubation mailing list [2]. We use this list to connect committers from new projects to their peers in other projects in the incubation phase and to mentors who can help answer questions and discuss issues related to the project onboarding process. [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://dev.eclipse.org/mailman/listinfo/incubation The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management: As your project's main Git repository is hosted at GitHub, we will need to move it to the Eclipse organization and flatten any previous history. This work can begin as soon as you have check in permission from EMO legal. Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=ceylon Outbound Communication: Mailing list: https://dev.eclipse.org/mailman/listinfo/ceylon-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/ceylon.git Commits will be published to www.eclipse.org/ceylon within 5 minutes Downloads: http://download.eclipse.org/ceylon Archives: http://archive.eclipse.org/ceylon Builds: You can upload releases to ~committer_id/downloads/ceylone via SFTP or SCP (to build.eclipse.org) or from a CI instance at Eclipse.org Older builds should be moved to the archives area when they are no longer required. Your next step is to submit an initial contribution [1] for review by the IP Team. Please do not commit any code to an Eclipse Foundation Git repository until after you receive the IP Team's approval. IP requests are referred to as Contribution Questionnaires (CQs). When the initial CQ receives “checkin” and/or “full approval” you are now ready to check the initial project code contribution into your project’s repository. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution -M. Thanks! Hi, I have created https://dev.eclipse.org/ipzilla/show_bug.cgi?id=14123 for the initial contribution. Otherwise, when this is cleared, we'll need to move the git repos to the Eclipse github organisation, right? Since we have several repos, do we have to rename them to adhere to a particular naming scheme? As for the website, you guys wanted us to move the content to one of your servers, right? How do I get information on that server, including SSH account and HTTP server configuration, Ruby installation? Thanks, cheers. I'm doing the CQs for our deps. One of our dep is a shared fat-jar containing several external libs that we renamed as part of the shading. Do you know how what the process is for a CQ for that? (In reply to Stephane Epardaud from comment #4) > Otherwise, when this is cleared, we'll need to move the git repos to the > Eclipse github organisation, right? Since we have several repos, do we have > to rename them to adhere to a particular naming scheme? It depends on what the names are right now. We prefer to use either eclipse.projectshortname.someothername or just projectshortname.someothername . The history of any repos migrating will need to be squashed[1]. This is something you can do in advance or we can do at import time. > As for the website, you guys wanted us to move the content to one of your > servers, right? How do I get information on that server, including SSH > account and HTTP server configuration, Ruby installation? Your project has a repository here: ssh://committerid@git.eclipse.org/r/www.eclipse.org/ceylon or https://committerid@git.eclipse.org/r/a/www.eclipse.org/ceylon Anything added there will get published to www.eclipse.org/ceylon within a minute. We support both HTML and PHP, although the PHP install is limited to minimize potential security risks. -M. [1]https://wiki.eclipse.org/GitHub Ah, the current workflow for our website is to generate it statically via awestruct (ruby) by the server which pulls from the github repo when it gets a hook notification. I suppose if you have a custom git repo we'll need to regenerate our site manually and push the resulting HTML there as a second git remote. Or do you have a better idea where the generation would keep on being automatic? As for the location of the website, it's currently sitting at http://ceylon-lang.org (whose DNS is already owned by Eclipse, if not hosted). As you can see its design is very different from the Eclipse web site, and I'm not sure it'd make a lot of sense to move it as-is to http://www.eclipse.org/ceylon. I assume that site should maintain some coherence with the rest of the site, no? Can we just redirect http://www.eclipse.org/ceylon to http://ceylon-lang.org or if not possible, add links to it and leave it stand-alone? As for the github repo names, we currently have: https://github.com/ceylon/ceylon https://github.com/ceylon/ceylon-lang.org https://github.com/ceylon/ceylon-sdk https://github.com/ceylon/ceylon-ide-common https://github.com/ceylon/ceylon-ide-eclipse https://github.com/ceylon/ceylon-ide-intellij https://github.com/ceylon/ceylon.formatter https://github.com/ceylon/ceylon.tool.converter.java2ceylon https://github.com/ceylon/ceylon-herd https://github.com/ceylon/ceylon-web-ide-backend Would keeping those names be possible under the Eclipse github organisation? Thanks! (In reply to Stephane Epardaud from comment #7) > I suppose if you have a custom git repo we'll need to regenerate our site > manually and push the resulting HTML there as a second git remote. That is certainly one option. A JIPP instance might be able to handle some of the work as well. > I'm not sure it'd make a lot of sense to move it as-is to > http://www.eclipse.org/ceylon. I assume that site should maintain some > coherence with the rest of the site, no? We provide a theme for projects if they want to use it, but if you want to do something else 'awesome' we'd like to try and help(see: https://www.eclipse.org/Xtext). Basically if you want to do the work(within the confines of our setup) we'll let you. > Can we just redirect http://www.eclipse.org/ceylon to http://ceylon-lang.org > or if not possible, add links to it and leave it stand-alone? Those are also options. Currently your Eclipse website is simply a redirect to https://projects.eclipse.org/projects/technology.ceylon, so you can simply change where that points. > As for the github repo names, we currently have: > > https://github.com/ceylon/ceylon > https://github.com/ceylon/ceylon-lang.org > https://github.com/ceylon/ceylon-sdk > https://github.com/ceylon/ceylon-ide-common > https://github.com/ceylon/ceylon-ide-eclipse > https://github.com/ceylon/ceylon-ide-intellij > https://github.com/ceylon/ceylon.formatter > https://github.com/ceylon/ceylon.tool.converter.java2ceylon > https://github.com/ceylon/ceylon-herd > https://github.com/ceylon/ceylon-web-ide-backend > > Would keeping those names be possible under the Eclipse github organisation? Those look ok to me. Wayne can you confirm? -M. (In reply to Eclipse Webmaster from comment #8) > > I'm not sure it'd make a lot of sense to move it as-is to > > http://www.eclipse.org/ceylon. I assume that site should maintain some > > coherence with the rest of the site, no? > > We provide a theme for projects if they want to use it, but if you want to > do something else 'awesome' we'd like to try and help(see: > https://www.eclipse.org/Xtext). Basically if you want to do the work(within > the confines of our setup) we'll let you. OK those do look a bit separate indeed. > > Can we just redirect http://www.eclipse.org/ceylon to http://ceylon-lang.org > > or if not possible, add links to it and leave it stand-alone? > > Those are also options. Currently your Eclipse website is simply a redirect > to https://projects.eclipse.org/projects/technology.ceylon, so you can > simply change where that points. Well, are we allowed to make it point to where http://ceylon-lang.org is currently hosted? Because that would be the easiest for us since we don't have to change anything. But I was under the impression that the HTML files had to be served by Eclipse. Did I get that wrong? (In reply to Stephane Epardaud from comment #9) > Well, are we allowed to make it point to where http://ceylon-lang.org is > currently hosted? Because that would be the easiest for us since we don't > have to change anything. But I was under the impression that the HTML files > had to be served by Eclipse. Did I get that wrong? Wayne, can you answer this? -M. We're ready to move our github repos. How does it work, you give us permission to move them and then I squash history and remove all tags/branches, and then I move them? Can I fork them first so that others can inject the history to preserve tags/commits? (In reply to Stephane Epardaud from comment #11) > We're ready to move our github repos. How does it work, you give us > permission to move them and then I squash history and remove all > tags/branches, and then I move them? Usually when projects need to transfer a repo to the Eclipse organization, they make us(eclipsewebmaster) admins on their organization and we do the actual transfer, and then they remove us. I would encourage you to do the history squash first and then the transfer as that gives you the most control to the last possible second. The method we use to squash history is documented here: https://wiki.eclipse.org/GitHub , and it covers how the history can be 'restored'. -M. OK, I'll gladly let you do it then, and will grant you permissions. What's your github ID? Then I guess I only have to wait until the initial contribution CQ is done, and give you the go ahead, right? (In reply to Stephane Epardaud from comment #13) > OK, I'll gladly let you do it then, and will grant you permissions. What's > your github ID? eclipsewebmaster > Then I guess I only have to wait until the initial contribution CQ is done, > and give you the go ahead, right? I'd wait on inviting us until the CQ is approved, and then we can do it all. Please make sure you have either 'tagged' the initial contribution in your repos, or that master contains an unmodified copy of the initial CQ (https://wiki.eclipse.org/GitHub) -M. We have the initial contrib cleared for every repo except https://github.com/ceylon/ceylon-web-ide-backend (I forgot that one). I've assigned you as admin to all the other repos, you can move them! Thanks. Has the history been squashed? If not which branch or tag is the initial contribution? -M. We didn't squash history. Master has the initial contribution. Ok this is slow going. So far the following repos have been moved and the history squashed: ceylon ceylon.formatter ceylon-ide-common ceylon-ide-eclipse ceylon-sdk Ceylon committers should receive invites to join the Eclipse Github Ceyon team shortly. I'll keep moving the rest next week. Also I didn't get an invite to 'admin' the ceylon-lang.org repo. If it's not supposed to move that's fine, if not could I please get an invite? -M. Ah yes, I gave you "write" instead of "admin. Fixed. Ok I've moved: ceylon-herd ceylon-ide-intellij ceylon-lang.org ceylon.tool.converter.java2ceylon Which just leaves: https://github.com/ceylon/ceylon-web-ide-backend I'll need an invite to admin that repo as well if it needs to move. -M. Sorry, I forgot that one. Now done. Ok ceylon-web-ide-backend is done, as such I declare you good to go. Let me know if there's anything else needed. -M. Thanks! Actually, can I get admin rights back on the repos? I don't even appear to be able to edit issues. (In reply to Stephane Epardaud from comment #24) > Actually, can I get admin rights back on the repos? I don't even appear to > be able to edit issues. We don't grant admin permissions to project repos on Github, expcept in specific circumstances and for a short period of time. In this case the issue is more fundamental: you aren't a member of the eclipse-celyon team . Digging further it seems you haven't added your GitHub id to your Eclipse.org account(accounts.eclipse.org -> details tab). Once you do that you should receive an invite to join the team which should let you interact with the Github repos more effectively. -M. Thanks, I was able to set up my GitHub username and join the org.
> We don't grant admin permissions to project repos on Github, expcept in specific circumstances and for a short period of time.
How do we set up repo hooks and integrations, then? This feels very restrictive.
Without being able to set up repo hooks, I can't set up CI or even deploy our web site changes.
>
> How do we set up repo hooks and integrations, then? This feels very
> restrictive.
Those would fall under the 'specific instances and for a limited time' I mentioned. Just file a bug indicating that you need admin permissions to set these up and we'll grant it for 12-24h(or a little longer depending).
-M.
(In reply to Stephane Epardaud from comment #26) > How do we set up repo hooks and integrations, then? This feels very > restrictive. > > Without being able to set up repo hooks, I can't set up CI or even deploy > our web site changes. You can either request temporary access, or we can set this up for you. Unfortunately the GitHub permissions can not be set granular enough to allow simple actions like setting up webhooks and prevent dangerous actions like deleting the whole repo, etc. OK, filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=52909 for the first case, thanks. Hi, we seem to have lost a lot of issues during the migration. Did you touch our GitHub issues at all? I thought it was only supposed to close open PRs. We're down to about a thousand closed issues when we should have +6000. Even open issues are missing. That's very worrying. We don't specifically touch GitHub issues as part of our on-boarding process. Depending on how GitHub stores/references them I guess it's possible the history squash might have some impact, but I wouldn't expect it to. -M. OK thanks, I've asked GitHub support. All issues below 5735 have been lost. They managed to bring the issues back, good. Thanks. (In reply to Eclipse Webmaster from comment #32) > We don't specifically touch GitHub issues as part of our on-boarding > process. Depending on how GitHub stores/references them I guess it's > possible the history squash might have some impact, but I wouldn't expect it > to. Has anybody been able to confirm whether or not the history squash caused this? Apparently no, it was the move to another organisation which triggered some spam filter that decided most issues were spam. Not your fault at all, AFAICT. Apparently gavinking doesn't have permission to close/label issues in the new repos, while I do. Can you grant him the proper permissions please? Gavin needs to add his Github ID to his Eclipse.org account(https://accounts.eclipse.org -> account details tab). Once that's done he'll get an invite to join the Ceylon Github team. -M. Hi, apparently https://github.com/eclipse/ceylon-web-ide-backend is missing from https://github.com/orgs/eclipse/teams/eclipse-ceylon/repositories Can you please add it? We can't commit to that repo otherwise. Thanks (In reply to Stephane Epardaud from comment #39) > Hi, apparently https://github.com/eclipse/ceylon-web-ide-backend is missing > from https://github.com/orgs/eclipse/teams/eclipse-ceylon/repositories I've updated the PMI so you should be able to access this repo once the sync tool runs. -M. Thanks a lot! (In reply to Eclipse Webmaster from comment #2) > Downloads: http://download.eclipse.org/ceylon I don't see this directory. Am I just missing it? (In reply to Wayne Beaton from comment #42) > I don't see this directory. Am I just missing it? Not sure what happened here, but fixed. -M. |