PPAs for unoffical eHIG-compliant apps
There's a number of software we'd prefer to have installable in the OS, like apps using our technology but not in elementary OS scope. We have to develop an infrastructure that allows that, and enable those PPAs in the OS by default.
It should probably follow the structure of elementary's official release channels.
Blueprint information
- Status:
- Complete
- Approver:
- Fabian Thoma
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Sergey "Shnatsel" Davidoff
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Danielle Foré
Related branches
Related bugs
Sprints
Whiteboard
Creating a PPA that only serves this purpose is probably the right way to do this.
--tai
We disagreed if the PPA and project group should include apps that we don't maintain or apps that don't meet our quality standards [yet].
IRC log: http://
Finally we came to agreement that apps outside the scope of elementary OS and development for it should go to a separate project group. The proposed names are: "unofficial", "third-party", "community". --shnatsel
Added to contributor meeting agenda. --shnatsel
I like the sound of community apps. ~cassidyjames
Well, we're a community... and I don't think it's a good idea to differentiate "us" from the "community [outside]". Kinda discourages joining/
What about calling them elementary-partners apps? It's friendly and doesn't differentiate "us" from the "community". -- Chris
Elementary-inspired apps? Elementary-based apps? Maybe just call "official" apps elementary-
elementary-style is also an option. the elementary update site has released a PPA for unofficial elementary apps (and icons). ~nemo
"Elementary-
I'm not really for elementary-
Work Items
Dependency tree
* Blueprints in grey have been implemented.
