The themes bundled with Dockbar should be a seperate branch
This is just an idea, and I'm not sure if it's a good idea or not. That's why I'm putting it up for discussion.
So, anyway. The idea is that the themes that are bundles with Dockbar should be a seperate branch of dockbar development, or maybe a whole new project (though still controlled by Dockbar Main Group).
The benefits of this would be that it would allow blueprints and bugs relating to the themes themselves to be seperated. Also, creating themes takes a somewhat different skillset than developing an application.
I would be willing to take some position of authority there (though I'd not like to do it by myself).
So,any thoughts?
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Matias Särs
Related branches
Related bugs
Sprints
Whiteboard
Matias: This answers what you want to do on dockbar team. I should check blueprints more often. :)
I'm not good at the unwritten rules of launchpad. I don't know what's considered a good reason for branching. I'll ask Michael to give his thoughts on this.
Alex: Having though about it, I think a new project would be appropriate. There could be seperate branches for official themes and community themes, and it could provide something of a repository, or a central location, for dockbar themes, as well as a place to develop them.
Michael: I agree with the seperated branch for themes. Not a seperated project. Themes should also be within a seperated .deb then. Thus we only deliver the official theme with dockbarx, but also create a .deb called official-
Alex: That should work. The only problem I see is keeping bug reports and blueprints organized. Launchpad should have a better way to do this without starting a new project.. maybe there is already. I'll poke around :)
