Re: [modularity] Guidelines & Process

2017-08-22 Thread Kevin Kofler
Owen Taylor wrote: > My particular interest is in what I consider the simplest use case - > taking an existing leaf-node application (desktop or otherwise), creating > a module that only includes that application and is not meant for building > on top of, and creating a container or flatpak out of

Re: [modularity] Guidelines & Process

2017-08-22 Thread Langdon White
On Tue, Aug 22, 2017 at 9:53 AM Owen Taylor wrote: > Hi Langdon, > > Thanks for all the work that went into the process and guidelines! > > My particular interest is in what I consider the simplest use case - > taking an existing leaf-node application (desktop or otherwise), creating a > module t

Re: [modularity] Guidelines & Process

2017-08-22 Thread Langdon White
On Tue, Aug 22, 2017 at 5:23 AM Petr Pisar wrote: > On 2017-08-21, Langdon White wrote: > > [2]: https://fedoraproject.org/wiki/Module:Review_Process > > I don't understand purpose of this paragraph: > > > As a Contributor, you should only be creating modules out of > > pre-existing software in

Re: [modularity] Guidelines & Process

2017-08-22 Thread Owen Taylor
Hi Langdon, Thanks for all the work that went into the process and guidelines! My particular interest is in what I consider the simplest use case - taking an existing leaf-node application (desktop or otherwise), creating a module that only includes that application and is not meant for buildi

Re: [modularity] Guidelines & Process

2017-08-22 Thread Petr Pisar
On 2017-08-21, Langdon White wrote: > [2]: https://fedoraproject.org/wiki/Module:Review_Process I don't understand purpose of this paragraph: > As a Contributor, you should only be creating modules out of > pre-existing software in the Fedora RPM repositories which adheres to > the Package Namin