Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.basyx | ||
|---|---|---|---|
| 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: | cydnie.smith, kasandra.darwin, mariateresa.delgado, markus.damm, philippe.krief, sharon.corbett, thomas.kuhn, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows NT | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-basys-4.0 | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 519647, 519648 | ||
| Bug Blocks: | |||
|
Description
Stephanie Swart
We’ve received all of the project requirements and have scheduled the creation review to conclude on September 20, 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 Congratulations! Your project review is successful! We have initiated the project resources provisioning process. 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 The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management:(At Eclipse) ssh://committer_id@git.eclipse.org:29418/basyx/basyx.git Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=basyx Outbound Communication: Mailing list: https://dev.eclipse.org/mailman/listinfo/basyx-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/basyx.git Commits will be published to www.eclipse.org/basyx within 5 minutes Downloads: http://download.eclipse.org/basyx Archives: http://archive.eclipse.org/basyx Builds: You can upload releases to ~committer_id/downloads/basyx 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 “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 As far as I can tell, there has been no activity on this project. What is the status?" (In reply to Cydnie Smith from comment #4) > As far as I can tell, there has been no activity on this project. What is the > status?" Hi Cydnie, we have quite some activity in the git - please check our log and feel free to have a look on our code: https://git.eclipse.org/r/plugins/gitiles/basyx/basyx/ At the moment we are implementing the BaSyx SDK for end-to-end communciation and distributed asset administration shells. Best regards, Thomas (In reply to Thomas Kuhn from comment #5) > we have quite some activity in the git - please check our log and feel free > to have a look on our code: > https://git.eclipse.org/r/plugins/gitiles/basyx/basyx/ I've included this repository in the project metadata [1]. This will make it easier for folks (including us) to find it. You should see some activity charts on the "Who's involved" page [2] (the process that populates these charts will run tonight). Note that any committer can update the project metadata by first logging in and then clicking "Edit" on this page. For completeness, the proposal indicates that the project did not have code before it was created at the EF, so there is no initial contribution. This is a bit of a corner case for us, and--without the initial contribution process--we don't necessarily notice that you've started working. Does the project have a CI build instance, or plans to stand one up? I don't see any build scripts; will the the project be using something like Maven or Gradle for Java builds? AFAICT, the project has numerous JAR files that include third party content in the repository. All third party content must be presented to the IP Team for their review before it can be included here (don't remove it right now, but please do engage in the intellectual property process [3] ASAP). I can provide help if you need it. [1] https://projects.eclipse.org/projects/technology.basyx/developer [2] https://projects.eclipse.org/projects/technology.basyx/who [3] https://eclipse.org/projects/handbook/#ip (In reply to Wayne Beaton from comment #6) > Does the project have a CI build instance, or plans to stand one up? Not yet, but this is planned. > I don't see any build scripts; will the the project be using something like > Maven or Gradle for Java builds? Again, not yet, but we think about Maven for the JAVA parts of the project. > AFAICT, the project has numerous JAR files that include third party content > in the repository. All third party content must be presented to the IP Team > for their review before it can be included here (don't remove it right now, > but please do engage in the intellectual property process [3] ASAP). I can > provide help if you need it. I'll look into it. BTW would using Maven mitigate that problem, as the JARs wouldn't actually be included any more but merely referenced? Best Regards Markus (In reply to Markus Damm from comment #7) > I'll look into it. BTW would using Maven mitigate that problem, as the JARs > wouldn't actually be included any more but merely referenced? No. As the documentation states: -- The simplest form of third party content is the Prerequisite (or prereq). Prerequisites are required by the Eclipse project content to provide core functionality. Prerequisite content is not generally stored in an Eclipse project’s source code repositories, but is likely included in build scripts and referenced as runtime dependencies. Since adopters of Eclipse project content are compelled to adopt the Prerequisite content, that content must also be reviewed by the IP Team. The review requirement applies recursively: the entire transitive closure of a Prerequisite’s dependencies needs to reviewed (the dependencies of a Prerequisite are themselves Prerequisites). -- 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. AFAICT the project is active and has already completed its first successful release review. AFAICT the project is active and has already completed its first successful release review. |