Open lewtds opened 10 years ago
Absolutely.
Progress so far:
oops... why an other organization? It'll take more time to sync membership
we can prefix/suffix projects with the word patch
, can't we?
It's easier to navigate. Have you seen this repo listing hell on launchpad? https://code.launchpad.net/elementaryos
it's not an organization's problem. It's how we introduce things in wiki
Yeah, of course the getting started page will need some major rewrite, in which we will introduce the two organizations.
any other reasons for creating a new org? we shouldn't care about things we can't control (the way org listing look!). Anw, when Gokien get bigger and bigger, any org listings will be hell
That's exactly the reason why patches should be in their own org. Over time, more and more repos will be created and mixing patches with original repos won't help with navigation.
Forget navigating github organizations! Always start your work with a wiki page & an issue tracker. You can't group or arrange child projects of an organization. All of them are just sorted by last commit, I guest?
State your proposed workflow more clearly, please.
Well, it's not a workflow. Answer this: What's the purpose of looking at an organization project listing? Can we do better for the same purpose?
Elementary OS Patches is a system to override Ubuntu's packages' behaviors. The procedure is describe here: http://wiki.gokien.org/dev:elementary_os_patches
We need to implement a similar system.