On Sat, Apr 21, 2012 at 8:10 PM, Olav Vitters <[email protected]> wrote:
> On Sat, Apr 21, 2012 at 11:48:59AM -0700, Sriram Ramkrishna wrote: > > For instance, let's say Xan who has indicated some interest to use > Zeitgist > > in Web wanted to use it but not add any new features but instead uses Zg > to > > store bookmarks then really does this process help that? Does he even > need > > to come on DDL and say anything? After all, as maintainer it's his call > as > > far as I'm concerned if he wants Zeitgist to powr his bookmarks. > > Essentially: > * If you propose a new feature, it is accepted and it requires some new > dependency: go ahead > * If you want a new external dependency in an existing module: request > approval or propose it as a new feature > > Thanks Olav for making that clearer. Maybe something for the FAQ? This will eliminate discussions on libraries and external dependencies. This also seems to make things a lot easier. > The point is that we don't want new external dependencies. But if you > have a new feature, then make a choice propose it, and once accepted, > run with it. The goal is having a new feature, if you need something to > make the feature happen, use it. Further, this nicely avoids the cases > where external dependencies have been approved, but actually nothing > used it for various releases. > What about you want to use a new technology but you don't want any new features but rather using this new external dependency will simpifiy things and making maintainance easier? I suppose that itself is the feature? Easier maintenance? sri > > -- > Regards, > Olav > _______________________________________________ > desktop-devel-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/desktop-devel-list >
_______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
