Well, some information can likely be pulled directly from version control, such as model/chipset/broken status/supported etc. That information could then be tied into a wiki templating system to autogenerate pages which could have additional model specific information added if available. I don't think Cyanognemod imports directly from version control but as many devices are extremely similar they use master templates to define aspects that are the same. Some devices would probably still have to be manually added but there may be a way to generate indexes from version control in mediawiki, such as target subtarget and device profiles. By creating corresponding templates there would at least be some usable information about a device under one page even if nobody wrote anything specifically about it in the wiki entry. Cyanogenmod also uses the repo system for version control which is a little different than traditional svn/git. I wonder if repo would be useable for a project like openwrt, it certainly makes readability better by clearly defining what is device specific in separate git repos. I think it also allows global build overrides per device. Right now OpenWRT is not all that accessable to the general public due its rather unique and somewhat confusing build system in addition to the source code itself being the only documentation for a number of devices. Just thinking of ideas that may make things more available to the general public.
On Thu, Dec 5, 2013 at 12:52 AM, Pavel Simerda <psime...@redhat.com> wrote: > ----- Original Message ----- > > From: "James Hilliard" <james.hillia...@gmail.com> > > To: "OpenWrt Development List" <openwrt-devel@lists.openwrt.org> > > Sent: Thursday, December 5, 2013 7:36:56 AM > > Subject: Re: [OpenWrt-Devel] Interest in a openwrt router database to > partially replace TOH? > > > > I would say that the best thing to do would be to tie a replacement TOH > > directly into version control and have supported router models populate > > directly from there somehow. > > Yeah, that sounds even better. But don't you still need a place (wiki) to > handle the notes about specific (whether supported or unsupported) > hardware, so that people can easily share the information? > > > Maybe something along the lines of how > > cyanognmod uses their template system > > http://wiki.cyanogenmod.org/w/Template:Device_info would work. > > Does that mean they're importing the device info directly into the wiki? > > Pavel > > > > > > > On Thu, Dec 5, 2013 at 12:25 AM, Pavel Simerda < psime...@redhat.com > > wrote: > > > > > > > > ----- Original Message ----- > > > From: "Manuel Munz" < freif...@somakoma.de > > > > To: "OpenWrt Development List" < openwrt-devel@lists.openwrt.org > > > > Sent: Wednesday, December 4, 2013 10:27:49 PM > > > Subject: [OpenWrt-Devel] Interest in a openwrt router database to > partially > > > replace TOH? > > > > > > Hi, > > > > > > i needed a database to be able to implement a selector where users can > > > choose their router model and from that parameters like > > > target/subtarget/profile/others are automatically set for the selected > > > model. > > > > I like the idea. But you also need someone to maintain the content. Even > the > > official TOH is obsolete already (e.g. there's no information about > tp-link > > 1043nd v2). You'd need a full replacement for the wiki TOH (making the > TOH > > obsolete once again) as well as an easy way to add loads of information > and > > comments and people willing to update the data. Or, alternatively, you > could > > just specify some format bits for the wiki and feed the database from the > > wiki. > > > > > A first demo for this can be seen here (where it says WIP): > > > > > > http://testing.meshkit.freifunk.net/ > > > > It looks a little bit too javascripty for me. I would like to be able to > > *also* just view the table of hardware like I do in the wiki. > > > > Cheers, > > > > Pavel > > > > > For that reason i started playing with a router database using web2py > as > > > framework. A somehow working demo version can be found here: > > > > > > http://meshkit.freifunk.net/routerdb > > > > > > Login as user openwrt and with password openwrt to be able to edit > > > routers (that part is still a bit ugly) and wiki pages (also not as > nice > > > as other wikis, but its usable). I already implemented a lot of stuff > in > > > the database schema as you can see here: > > > > > > http://meshkit.freifunk.net/routerdb/static/images/bg_graph_model.jpg > > > > > > I also just comitted the code for it: > > > https://github.com/mmunz/openwrt-routerdb > > > > > > This is more than i need for my usecase, but i wanted to experiment > what > > > is possible. > > > > > > The question for me is now: Is it worth putting more time > > > into this and further improve it? Is there any interest in trying to > > > figure out how such a database could be combined with TOH in wiki? > > > > > > Regards, Manuel > > > > > > > > > > > > > > > _______________________________________________ > > > openwrt-devel mailing list > > > openwrt-devel@lists.openwrt.org > > > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > > > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
