Eclipse Oniro Blueprints

changed due date to May 04, 2022

added Project Proposal Review Request Trademark Approval Request labels

assigned to @wbeaton and @mdelgado624

added Mentor label

@shmacdonald please initiate trademark search for the Oniro Blueprints project.

@mmilinkovich we need your approval to use the Apache License, Version 2.0 for the Oniro Blueprint project.

Use of the APACHE-2.0 license is approved.

changed title from Oniro Blueprints to Eclipse Oniro Blueprints

changed the description

marked the checklist item License(s) approved as completed

The Trademark name Oniro Blueprints is approved.

marked the checklist item Project name trademark approved. Trademark transfer agreement available here in case you need it. as completed

changed the description

removed Trademark Approval Request label

changed the description

Project team: we need you to confirm the project resources that need to be created.

marked the checklist item Committers have Eclipse Foundation Accounts as completed

marked the checklist item Two weeks of community review completed as completed

@mdelgado624

Project repository group: https://gitlab.eclipse.org/eclipse/oniro-blueprints is fine
For Project mailing list, we'd like to reuse oniro-dev mailing lists to keep discussions consolidated for now
For the repositories, since we don't yet support subgroups, here is the initial list that we'd like to be created:
1. https://gitlab.eclipse.org/eclipse/oniro-blueprints/blueprints-core (meta-oniro-blueprints-core and other core repos shared across blueprints)
2. https://gitlab.eclipse.org/eclipse/oniro-blueprints/cats (meta-layers + code + oniro-cats)
3. https://gitlab.eclipse.org/eclipse/oniro-blueprints/dj-gesture (meta-layers + code + oniro-dj-gesture)
4. https://gitlab.eclipse.org/eclipse/oniro-blueprints/doorlock (meta-layers + code + oniro-doorlock)
5. https://gitlab.eclipse.org/eclipse/oniro-blueprints/eddie (meta-layers + code + oniro-eddie)
6. https://gitlab.eclipse.org/eclipse/oniro-blueprints/energy-gateway (meta-layers + code + oniro-energy-gateway)
7. https://gitlab.eclipse.org/eclipse/oniro-blueprints/gateway (meta-layers + code + oniro-gateway)
8. https://gitlab.eclipse.org/eclipse/oniro-blueprints/vending-machine (meta-layers + code + oniro-vending-machine)

cc: @pidge

I should clarify something here:

If we do not support subgroups (the list above was created as the subgroup list), then we will need to create this list of repos:

Sorry I didn't notice these when doing the initial provisioning. I've added them to your metadata and they should get created in an hour or so once the sync tooling runs.

Some of the above seem to have not been created.

That said, the initial list of repos should not exist:

https://gitlab.eclipse.org/eclipse/oniro-blueprints/blueprints-core (meta-oniro-blueprints-core and other core repos shared across blueprints)
https://gitlab.eclipse.org/eclipse/oniro-blueprints/cats (meta-layers + code + oniro-cats)
https://gitlab.eclipse.org/eclipse/oniro-blueprints/dj-gesture (meta-layers + code + oniro-dj-gesture)
https://gitlab.eclipse.org/eclipse/oniro-blueprints/doorlock (meta-layers + code + oniro-doorlock)
https://gitlab.eclipse.org/eclipse/oniro-blueprints/eddie (meta-layers + code + oniro-eddie)
https://gitlab.eclipse.org/eclipse/oniro-blueprints/energy-gateway (meta-layers + code + oniro-energy-gateway)
https://gitlab.eclipse.org/eclipse/oniro-blueprints/gateway (meta-layers + code + oniro-gateway)
https://gitlab.eclipse.org/eclipse/oniro-blueprints/vending-machine (meta-layers + code + oniro-vending-machine)

These repos should:

I've removed the repos in the top section, and queued those in the bottom section for creation.

Thanks, @mward, that helps.

"For Project mailing list, we'd like to reuse oniro-dev mailing lists to keep discussions consolidated for now"

I see that a new mailing list has been created. Is that an automated process and we now can proceed to remove it or is it mandatory to have a mailing list per project?

Both(sort of).

The list creation is done automatically as part of the project setup process.

We strongly encourage projects to use their mailing lists(rather than using those belonging to other projects) to help keep things in scope rather than the list becoming more of a confusing mix of project discussions. That said, it wouldn't be the first time projects have shared a mailing list.

Oniro, as an operating system, is a fairly monolithic project, having strong dependencies. Blueprints are use cases of such OS, in theory we might think of them as separate outputs. The technical reality, which affects how the community is managed, is that blueprints require intensive coordination with the OS developers. At this point, having two lists is overkill, introducing an overhead that OS integrators do not want to have. Even with an increasing number of blueprints, the management of the lists would probably be per topic (based on OS architecture) and not per project.

The problem of having it is that it shows in the list so community people might subscribe and then the core developers would need to pay attention to it. This is why, instead of simply ignoring it, we suggest to remove it.

Can I get a +1 from the PL regarding the list deletion? This is our usual requirement for project mailing list removals.

@pidge @idlethread please +1 the ML deletion.

+1

removed Mentor label

@idlethread thanks for the feedback. The repositories will be created later by @webmaster, but thanks for the heads up. You'll need to open an issue requesting them once the project has been provisioned and the initial contribution has been granted check in by the project team.

For now I'll proceed with the project creation. Will provide more updates once it's done.

marked the checklist item Project lead(s) designated as completed

marked the checklist item Architecture Council mentor designated as completed

marked the checklist item Project created as completed

assigned to @webmaster

This review creation has concluded successfully! the project has been created and the provisioning process will begin shortly.

You'll receive the committer paperwork in your emails soon, please make sure you check your spam folders!

@webmaster handling this to you.

added Successful label

added EDPProvisioning label

changed due date to June 01, 2022

Thanks @mdelgado624

marked the checklist item Project provisioned (including at least one committer) as completed

The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project:

Source Code Management:

A new repository has been created on our Gitlab instance for your project: https://gitlab.eclipse.org/eclipse/oniro-blueprints/oniro-blueprints . Committers should be added to the oniro-blueprints team shortly.

Issue tracker:

Gitlab issues have been enabled for your project.

Outbound Communication:

Mailing list: https://accounts.eclipse.org/mailing-list/oniro-blueprints-dev

Downloads: http://download.eclipse.org/oniro-blueprints

Archives: http://archive.eclipse.org/oniro-blueprints

Builds: You can upload releases to oniro-blueprints via SFTP or SCP from a CI instance at Eclipse.org

Older builds should be moved to the archives area when they are no longer required.You can do this by visiting http://download.eclipse.org/oniro-blueprints in your favorite web browser and using the web ui.

@mward the set of blueprint repos we asked for had a mispelling 's/bluprint/blueprints/g'. I've corrected the names in the setup repos but I'm not sure if any internal scripts will be effected by this change/override this change.

I've updated the PMI. Hopefully between that and Gitlabs internal repo redirection on name change we won't have any issues.

Ok. Can we get https://gitlab.eclipse.org/eclipse/oniro-blueprints/meta-oniro-bleuprints-eddie/edit removed?

added EDPInitial Contribution label and removed EDPProvisioning label

It is now time for the project team to submit the project’s initial contribution of project code and wait for the Eclipse Intellectual Property (IP) Team to grant checkin of that contribution. Let us know if you need assistance in the process.

Information is available in the EF handbook: https://www.eclipse.org/projects/handbook/#ip-initial-contribution

It looks like the project team has already pushed some content into the provided repositories without first going through the initial contribution process.

@skilpatrick and I decided to use this as an opportunity to experiment with some revisions to our due diligence process that we've been discussing. We're still just experimenting with this, so the process itself is not final (or documented). I will capture what we've learned on eclipsefdn/helpdesk#1369 (closed).

In the meantime, we have completed the initial contribution process for the following repositories:

meta-oniro-blueprints-eddie
meta-oniro-blueprints-cats-main
meta-oniro-blueprints-core

These repositories all good-to-go.

@pidge Please let us know when add content to the other repositories and we'll do the same thing with them.

/cc @toscalix

@wbeaton I've added an additional repo https://gitlab.eclipse.org/eclipse/oniro-blueprints/oniro-gesture-glove and pushed to https://gitlab.eclipse.org/eclipse/oniro-blueprints/meta-oniro-blueprints-dj-gesture

@mdelgado624 is there anything left to do on this ticket or should be the process considered done?

We're done here @toscalix.

@pidge the project team can engage directly with the EMO when you're ready to make your first official release. There is useful information on the EF handbook regarding this topic.

changed due date to July 06, 2022

added EDPOperational label and removed EDPInitial Contribution label

closed

mentioned in issue #293 (closed)

Eclipse Oniro Blueprints

Project

Basic Information

Pre-creation Checklist

Project resources to be created

Post-creation Checklist

After provisioning

Designs

Child items ...

Activity