Define plugin strategy
Registered by
brian.pedersen
Which plugins will we aim to port ourselves, will there be any changes needed to the plugin api, how can we make it easy for the end-user to know which plugins are compatible
Blueprint information
- Status:
- Not started
- Approver:
- GNOME Do Windows Port Team
- Priority:
- Medium
- Drafter:
- GNOME Do Windows Port Team
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
03.07.2008 brian.pedersen>
Which plugins will we aim to port ourselves, will there be any changes needed to the plugin api, how can we make it easy for the end-user to know which plugins are compatible
03.07.2008 Krisztian Gyuris>
We can set up a seperate web site for the windows version and host the plugins there. Or we can introduce some ways of describing the plugin platform
03.07.2008 brian.pedersen>
With binary compatibility as a goal, self-describing plugins would be great.
(?)
