> a) in my book, giving the maintainer four (4) weeks to respond is ok, > only if there's no reply after that it's ok to push for taking over > maintainership. AFAIK, there's no official 'window of slacking'; of > course there's key system components / add-ons where things might be > dealt with faster with good reason (flash-player and a propriety > browser come to mind);
I was told two weeks by an SBo admin via IRC. > b) if the script works by just adapting $VERSION, that's ok. > Maintainers are not obligated (yet?) to keep up with upstream for > such trivial things. No, just switching the version will not work. Chromium has switched to a new build system, ninja, since the version posted on SBo. Other minor changes are required as well. > c) what exactly is the impact of (not) having google API keys as > maintainer in this context of taking over maintainership? As you > stated, the SBo project should 'get them'; Does this need to be > happening right now or is this a general good strategy to have in > place for future chromium integration? If so, how's the handling of > the API keys for projects at SBo documented? http://www.chromium.org/developers/how-tos/api-keys https://groups.google.com/a/chromium.org/d/msg/chromium-dev/Qks4W0xLxqc/MVhyo3o0JgoJ James On Sun, Aug 11, 2013 at 8:21 AM, Markus Reichelt <[email protected]> wrote: > > * James Geboski <[email protected]> wrote: > > > A little over two weeks ago (July 26), I contacted the maintainer > > of the Chromium SlackBuild, Francisco Ambrozio. I still have yet > > to hear back from Francisco on issues pertaining to the Chromium > > SlackBuild. There are two key issues with the SlackBuild: 1) it is > > four releases behind; 2) it is missing Google API keys. > > pardon me for being frank: > > a) in my book, giving the maintainer four (4) weeks to respond is ok, > only if there's no reply after that it's ok to push for taking over > maintainership. AFAIK, there's no official 'window of slacking'; of > course there's key system components / add-ons where things might be > dealt with faster with good reason (flash-player and a propriety > browser come to mind); > > b) if the script works by just adapting $VERSION, that's ok. > Maintainers are not obligated (yet?) to keep up with upstream for > such trivial things. > > c) what exactly is the impact of (not) having google API keys as > maintainer in this context of taking over maintainership? As you > stated, the SBo project should 'get them'; Does this need to be > happening right now or is this a general good strategy to have in > place for future chromium integration? If so, how's the handling of > the API keys for projects at SBo documented? > > d) I'm not a chromium user, so bare with me. Thanks. > > > -- > The Tahoe-LAFS spirit. > _______________________________________________ > SlackBuilds-users mailing list > [email protected] > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > _______________________________________________ SlackBuilds-users mailing list [email protected] http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
