> How would it look if OpenWrt tried to write into each of the package
> make files who's maintaining them - something like this:
I think that could work. AFAICT it still doesn't cover updates to
trunk and its packages, but it's a start in the direction of helping
focus updates for at least par
RB wrote:
>> It would be really good to extend the list of package maintainers, then
>> patches for packages could be send directly to the maintainer - or?
> As long as those package maintainers are reasonably responsive and
> have commit access. It would also need to be very clear who each
> p
Dear All
This months WIP-Day will take place on next saturday (28th of June) on
irc channel #openwrt-devel at UTC 12:00, and 24 hours ahead.
The focus will be on tickets and patches for the upcoming release and
discussions in regard to package maintaining,etc.
Sincerely
--
Gregers Petersen
P
> The original thought behind the present model for submission of patches
> was based on the existing procedure for kernel patch submission - it
> looked like a model which worked, and by implementing it OpenWrt would
> "teach" people a skill which could be needed later on.
I don't disagree, bu
The original thought behind the present model for submission of patches
was based on the existing procedure for kernel patch submission - it
looked like a model which worked, and by implementing it OpenWrt would
"teach" people a skill which could be needed later on.
The suggestions which have com
