Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.deeplearning4j | ||
|---|---|---|---|
| Product: | Community | Reporter: | Kasandra Darwin <kasandra.darwin> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cydnie.smith, mike.milinkovich, raver119, sharon.corbett, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows NT | ||
| URL: | https://projects.eclipse.org/proposals/deeplearning4j | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 525867, 525869 | ||
| Bug Blocks: | |||
|
Description
Kasandra Darwin
Congratulations! Your project review is successful! We will initiate the project resources provisioning process shortly. Please tell your project committers to carefully monitor their email for a message from The Eclipse Foundation with instructions for providing committer paperwork [1]. Our IT team cannot allocate project resources until after we have processed the paperwork for at least one committer, so your attention in this matter will keep the process moving forward. Be advised that the paperwork process will time out after 120 days; any committers who are unable to complete their paperwork requirements in this timeframe will have to be elected to the project (your project mentors can provide assistance with this). [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution Licensing was approved by board. I will mark this ticket as resolved. 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=deeplearning4j Outbound Communication: Mailing list: https://dev.eclipse.org/mailman/listinfo/deeplearning4j-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/deeplearning4j.git Commits will be published to www.eclipse.org/deeplearning4j within 5 minutes Downloads: http://download.eclipse.org/deeplearning4j Archives: http://archive.eclipse.org/deeplearning4j Builds: You can upload releases to ~committer_id/downloads/deeplearning4j 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. -M. 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 “check in” 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 Hello project team, Your initial contribution was approved (2017-11-21) and you have no outstanding CQs. AFAICT, this project is active; however, there have been no releases planned. What is the status of your first release? If you need any assistance, please let us know! For more information on the release process, please feel free to check out our handbook [1]. [1] https://www.eclipse.org/projects/handbook/#release 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. 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. The project is up and running. |