Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Swordfish Documentation: GIT Repository
{{#eclipseproject:rt.swordfish}}
Contents
Description
We need to have a repository for automating patch creation for the Swordfish project which will allow non-eclipse commiters to work with the Swordfish sources.
Current Problem / Pain
Only eclipse commiters could commit to the Swordfish repository, patches need to be send to them to check in.
Advantages/Business Case
GIT repository will automate patch creation and let external (internal) developers work with SCM cycle without Eclipse commiter rights.
Use Cases
• Developers creating a git repository on GITHub. • Developers are forking the one of the eclipse commiters GIT repository. • Developers are working with checkin-checkout cycles, also branching and merging. • Developers are notifying a forked repository owner when they are ready to merge it back.
Conditions of satisfaction
- GIT works for all developers.
- Developers can work via GIT with Eclipse Swordfish sources.
- Patches from the deveopers could be submitted to Eclipse Swordfish subversion repository.
- Updates from Eclipse Swordfish Subversion repository could be fetched from GIT repository.
Limitations
Non Functional aspects
Volume/Load
Security aspects
It shall be possible to add an agreed policy validation in a future version.
Ease of Use
The policies resolver shall be able to process policies in the format provided through the Policy editor. It shall be possible to integrate the policy resolver into the Police Editor at a later point in time.
Architecture Outline/ Implementation Ideas
How much reuse of the Policy Resolver in Policy Editor of the Eclipse STP would be possible?
Open Questions
Which assertions do we want to support in the first version?
Return to Eclipse Swordfish Swordfish Product Backlog