On Wed, 2014-06-11 at 00:16 +0300, Hannu Nyman wrote:
> The current buildbot run was the first after the default feed change, and as 
> "oldpackages" are not built by buildbot, many packages will be missing from 
> the snapshot directory as of today... So I expect to see a flow of bugs for 
> missing binary packages :-(
> How are you going to ease the transition to the new repository? The default 
> feed was changed yesterday, but only a few packages have been transferred to 
> github so far.
> Will core developers add/move selected key packages that they assume being 
> widely used?
> Or are you expecting non-core people to assume maintenance of all packages to 
> be transferred and move them?

I am not speaking on their behalf but I guess they are trying to ease
the burden on them, and form a new team that will maintain the
additional packages. 

> There are also packages like collectd, which is the core part of 
> luci-statistics and part of the code lies in Luci repository. It would be no 
> use for a non-core developer to assume maintenance of collectd, as proper 
> maintenance would also require access to the luci repository.  (I have 
> submitted version bump patches for collectd, but I have no interest in trying 
> to assume maintenance for it, as the packages part is only half of the 
> picture.)

I think the 'assume maintenance' is pretty strong wording. Even if you
did you'd always be free to quit, so my opinion would be to feel free to
add packages that you consider essential and do update them when and if
you can. My experience with the "official" maintainers at gnu shows that
one way or an other, there will be abandonware that we need to cope
with. However, that move to the new repository would help to keep only
software that is used and is safe to use, and hopefully get the critical
mass of people needed to maintain them.

regards,
Nikos
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to