[luci] [DISCUSSION] How to support LuCI applications not in OpenWrt packages repository

[Christian Schoenebeck]

Hi,

we got a new ticket inside OpenWrt Ticket #18018 with problems inside LuCI app.
This is normally not an OpenWrt ticket it's a LuCI ticket, but the user don't know.

If the user try to post the ticket at LuCI trac it takes weeks before the ticket 
is reported by LuciTrac to the mailing lists. So for a me as an "external" developer 
there is no chance to help quick. 
LuCi trac is also no good choice to send patches or possibly new functionality.
LuCI trac has problems to accept file attachments when creating a new ticket.
LuCI trac gives no chance to correct/edit a ticket or append a comment if you just create it.
>From my point of view LuCi trac is more then awful including used CHAPTCHA.

Sending patches or new functionality to luci mailing list is also not a choice 
because there is no guarantee that the code is implemented short term.

My idea is to move code of LuCI applications like tinyproxy, samba, hd-idle, ddns-scripts, .....
to OpenWrt/packages as samba/samba-luci, tinyproxy/tinyproxy-luci or ddns-scripts/ddns-scripts-luci.
The mwan3 package already doing this. 

I think this is the best way, because openwrt/packages are moving fast forward 
and needed changes to the corresponding LuCI apps needs to be in sync.

My port/move for luci-app-ddns is ready for take off.

What do you think ?

Christian