Re: [LEDE-DEV] [wiki] Permalinks to page sections
> There is a small usability issue with the wiki: there is no easy way to > get a permalink to a page section (i.e. a link that includes an > anchor). > > First, it would be nice to have a small clickable permalink just beside > a section title. Done. > Also, there is a bug in the table of contents of a page. The table of > contents provides correct links to sections, but after clicking on the > link, the URL (with the anchor to the section) is not updated in the > address bar of the browser. That's a problem of the fantastic bootstrap3 template and does not happen with the monobook template. Currently, I can not do anything against this. :( If someone stumbles upon the solution for this problem, please let me know. Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [wiki] Permalinks to page sections
> If someone stumbles upon the solution for this problem, please let me > know. Since I havn't found any open issue that could cause this, I opened a ticket: https://github.com/LotarProject/dokuwiki-template-bootstrap3/issues/268 Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] Any interest in adding runit to OpenWRT?
> An idea would be, to provide some small hint for the googlebot, to > switch to the new content via some "#REDIRECT" wiki command ... googlebot will notice. He's a frequent visitor, afaics. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [Forum] Certificate expired
It's currently not possible to visit the forum with Firefox + Chrome: forum.lede-project.org verwendet ein ungültiges Sicherheitszertifikat. Das Zertifikat ist am Donnerstag, 8. Dezember 2016 20:00 abgelaufen. Die aktuelle Zeit ist Donnerstag, 8. Dezember 2016 22:01. Fehlercode: SEC_ERROR_EXPIRED_CERTIFICATE <>___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [Frontpage] Stuff that cannot be found since switch to wiki software
> Can we get some of those old links back on the front page? Which would "some of those old links" be? Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [Frontpage] Stuff that cannot be found since switch to wiki software
> That link I added disappears if someone opens the "Documentation" link > though, I think it's due to a sidebar plugin/feature that needs to re- > cache the entries in it, I hope tmomas can explain how to deal with > that properly. :) :) Simple reason: $someone proposed to have the sidebar expand depending on the link. For Documentation, I added a separate sidebar (i.e. :docs:sidebar) with additional sub-topics. Drawback: Sidebars need to be synced somehow. Not that big a deal, since the change frequency should be low, but one needs to keep that in mind when changing a sidebar. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] gateworks patches in the tree
Sidenote: Gateworks devices are the same in the OpenWrt as in the LEDE ToH. https://lede-project.org/toh/start?dataflt%5BBrand*%7E%5D=gatewo https://wiki.openwrt.org/toh/start?dataflt%5BBrand*%7E%5D=gatewo The reason why there are less devices listed with "snapshot" in the LEDE ToH: No firmware file listed for them, see https://lede-project.org/toh/views/toh_fwdownload2?dataflt%5BBrand*%7E%5D=ga tewo Thomas > -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von Tim Harvey > Gesendet: Mittwoch, 21. Dezember 2016 18:28 > An: John Crispin > Cc: LEDE Development List > Betreff: Re: [LEDE-DEV] gateworks patches in the tree > > On Wed, Dec 21, 2016 at 1:54 AM, John Crispin wrote: > > Hi Tim, > > > > Hi John, > > > we currently have these patches in the tree, which i think you were > > involved in. could you tell us which of these can be sent upstream > > and/or what is blocking us sending them upstream ? > > > > 160-usb-gadget-udc-net2280-add-usb2380-support.patch:From: Tim Harvey > > > > I mainlined this one (5185c91385d73cdf79836eb8548e4726e43ae831) and it > appears in Linux 4.8 > > > 412-mtd-partial_eraseblock_unlock.patch:From: Tim Harvey > > > > The commit message for this applied in OpenWrt r33681 on 10/10/12 was: > > mtd: allow partial block unlock > > This allows sysupgrade for devices such as the Gateworks Avila/Cambria > product families based on the ixp4xx using the redboot bootloader with > combined FIS directory and RedBoot config partitions on larger FLASH > devices with larger eraseblocks. > > This second iteration of this patch addresses previous issues: > - whitespace breakage fixed > - unlock in all scenarios > - simplification and fix logic bug > > -- > > The ixp4xx Xscale processors have been EOL for a couple of years and as > such there are no plans to mainline this. I don't see Gateworks > Avila/Cambria in the LEDE Table of hardware (they are still in the > OpenWrt list). Perhaps there is a plan to drop ixp4xx support from LEDE > in general, which I would be fine with. > > > 880-gateworks_system_controller.patch:Signed-off-by: Tim Harvey > > > > This is an old driver replaced by a newer version which I intend on > mainlining - drop it. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] firmware file naming
Is this intentional? 1) country sometimes in the middle (il, cn), most times at the end (us, eu, AU, NA, WW) 2) country NA vs. us (different name for same thing?) 3) country EU vs. eu (capitals or not?) 4) country north-america vs. NA vs. us 5) country other-regions vs. WW If this is not intentional: Would it be a good idea, and be it only for cleanliness sake and having a clear scheme, to commonize placement, capitalization and naming of countries? lede-ar71xx-generic-archer-c7-v2-il-squashfs-factory.bin lede-ar71xx-generic-archer-c7-v2-il-squashfs-sysupgrade.bin lede-ar71xx-generic-archer-c7-v2-squashfs-factory-eu.bin lede-ar71xx-generic-archer-c7-v2-squashfs-factory-us.bin lede-ar71xx-generic-dir-601-b1-squashfs-factory-NA.bin lede-ar71xx-generic-tl-wr941nd-v6-cn-squashfs-factory.bin lede-ar71xx-generic-tl-wr941nd-v6-cn-squashfs-sysupgrade.bin lede-brcm47xx-mips74k-netgear-wgr614-v10_north-america-squashfs.chk lede-brcm47xx-mips74k-netgear-wgr614-v10_other-regions-squashfs.chk lede-brcm47xx-mips74k-netgear-wnr3500l-v1-north-america-squashfs.chk lede-brcm47xx-mips74k-netgear-wnr3500l-v1-other-regions-squashfs.chk lede-brcm63xx-generic-DSL274XB-F1-squashfs-cfe-AU.bin lede-brcm63xx-generic-DSL274XB-F1-squashfs-cfe-EU.bin lede-brcm63xx-smp-DSL274XB-F1-squashfs-cfe-AU.bin lede-brcm63xx-smp-DSL274XB-F1-squashfs-cfe-EU.bin lede-lantiq-xway-DGN3500-squashfs-factory-NA.bin lede-lantiq-xway-DGN3500-squashfs-factory-WW.bin lede-lantiq-xway-DGN3500-squashfs-sysupgrade-NA.bin lede-lantiq-xway-DGN3500-squashfs-sysupgrade-WW.bin lede-ramips-rt305x-whr-g300n-squashfs-factory-EU.bin lede-ramips-rt305x-wnce2001-squashfs-factory-NA.bin <>___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Branching LEDE 17.01 / problems with ath9k
> -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von Bastian Bittorf > Gesendet: Donnerstag, 12. Januar 2017 10:39 > An: Jo-Philipp Wich > Cc: l...@kitschensync.net; LEDE Development List > Betreff: Re: [LEDE-DEV] Branching LEDE 17.01 / problems with ath9k > > Thanks for these strong steps toward a release, the last weeks where > full of commits and everybody seems to work very hard. > > What i want to mention is, that older ath9k chips (ar91xx?) are not > useable with LEDE anymore, e.g. TP-Link 1043nd v1 > > This needs more testing and reporting. Maybe someone has time to jump > in. I have opened a ticket for that: > https://bugs.lede-project.org/index.php?do=details&task_id=373 > > bye, bastian > > BTW: > the page https://lede-project.org changed again and 'reporting bugs' > is hidden under 'Developer Guide' which is just...wrong Please make > this more "friendly". https://lede-project.org/contact contains a link to https://bugs.lede-project.org/ since 11/11/2016. IMHO the perfect place. regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [LEDE DEV][wiki] Login with github
Hi Baptiste, jow already fixed this issue with a workaround (see comments in your linked bug report). To get this fixed in the OAuth plugin, I created a bug report https://github.com/cosmocode/dokuwiki-plugin-oauth/issues/45 Regards, Thomas > -Ursprüngliche Nachricht- > von Baptiste Jonglez > Gesendet: Montag, 20. Februar 2017 16:20 > > Hi Thomas, > > Is the github login integration supposed to work? There is a bug > reported about a 404 error when trying to login: > > https://bugs.lede-project.org/index.php?do=details&task_id=531 > > Thanks! > Baptiste > > On Sat, Oct 01, 2016 at 05:25:54PM +0200, Thomas Endt wrote: > > IIRC it was Martin who proposed to use oAuth to log in to the wiki > > with github credentials. > > > > I installed the oAuth plugin (https://www.dokuwiki.org/plugin:oauth) > > for this purpose and created an oAuth application with my github > > account for testing purposes. > > > > Since the owner of the application is shown under > > https://github.com/settings/applications and to avoid a SPOF, the > > owner of the LEDE-Wiki login application should probably be someone > other than me. > > I'm not sure if github organizations (i.e. lede-project) can create > > oAuth applications. Can someone of the devs please try? > > > > Things to enter in https://github.com/settings/applications/new > > > > Application name: LEDE wiki login > > Homepage URL: https://wiki.lede-project.org/doku.php > > Application description : Log in to the LEDE wiki with your > github account. > > Authorization callback URL : https://wiki.lede-project.org/doku.php > > > > After successful creation of the application, the "Client ID" and > > "Client Secret" need to be entered in the oAuth config of the wiki (- > > > > admin -> config -> oAuth). You can either do this yourself or let me > know. > > > > To use the login via github, the user needs to update his wiki > profile > > accordingly: > > -> Update profile -> Login with other Services -> check Github -> > save > > > > Please let me know your thoughts. > > > > Regards, > > Thomas > > > > ___ > > Lede-dev mailing list > > Lede-dev@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] MikroTik RB493G supported?
RB493G hasn't been removed AFAICS, but was never listed as supported. If you know which firmware files are needed for installation, you can update the dataentry accordingly [1]. Datafields to be updated: Firmware LEDE Install URL Firmware LEDE Upgrade URL LEDE Supported Current Rel If you know more MikroTik devices which should be supported, feel free to update the dataentries accordingly. All mikrotik devices + firmware download links can be found at [2]. [1] https://lede-project.org/toh/hwdata/mikrotik/mikrotik_rb493g [2] https://lede-project.org/toh/views/toh_fwdownload?dataflt%5BBrand*%7E%5D=mikrotik > -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von John Ricardo > Gesendet: Freitag, 24. Februar 2017 03:43 > An: lede-dev@lists.infradead.org > Betreff: [LEDE-DEV] MikroTik RB493G supported? > > I noticed that the MikroTik RB493G has been removed from the list of > supported devices. Why was that? What would it take to add it back? > I have serial access so I can pull logs. I don't want to risk > installing 17.01 after reading the thread: MikroTik RB411AH sysupgrade > issues. > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] rb112/rb133 (adm5120) compile fail
> -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von Stefan Lippers-Hollmann > Gesendet: Montag, 27. Februar 2017 07:51 > An: Denis Periša > Cc: LEDE Development List > Betreff: Re: [LEDE-DEV] rb112/rb133 (adm5120) compile fail > > Hi > > On 2017-02-27, Denis Periša wrote: > > Ah, now I saw if I enable "BROKEN" that it will show as rb1xx, not > > generic.. And does compile altho I cannot get ath5k running for some > > crypto reason.. > [...] > > Be aware that adm5120 has never been ported to kernel 4.4, nor 4.9 and > is stuck on kernel 3.18, which is now EOL. This dependency on a no > longer supported kernel version and the fact that the platform as a > whole hasn't seen sufficient (or probably any-) development to bump the > kernel version to 4.4 (or now 4.9) is one of the major reasons why it > is marked BROKEN (another is because most of its devices only have > 16 MB RAM, which means you need a very specific/ targetted config to > keep it running at all). [...] Do you know which of the devices listed in the LEDE ToH (Table of Hardware [1]) belong to the rb1xx subtarget? Is it only the MikroTik RB133? The adm5120 devices have only very little information. It would be helpful if anybody knowledgable can jump in and fill in a little information in the following columns: * LEDE supported current rel * LEDE unsupported * Subtarget * Firmware LEDE install URL * Firmware LEDE upgrade URL And if someone has something more to write about this target than what currently can be found on the target description page [2], feel invited to add your knowledge to this page. [1] https://lede-project.org/toh/views/toh_dev_arch-target-cpu?dataflt%5B0%5D=target_%3Dadm5120 [2] https://lede-project.org/docs/targets/adm5120 Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] lantiq: FritzBox 3370 questions
Hi Joerg, > -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von joerg jungermann > Gesendet: Montag, 6. März 2017 16:27 > An: lede-dev@lists.infradead.org > Betreff: [LEDE-DEV] lantiq: FritzBox 3370 questions > > Hi, > > I try to get lede to run on a FritzBox 3370 (xrx200). There is lack of > documentation, if I get it to run I like to add some docs to the wiki. > Is there already a structure like in the openwrt wiki? There's currently no structure like in the OpenWrt wiki, but we can c/o the well known and working structure, e.g. LEDE Devicepage of D-Link DIR-505 = https://lede-project.org/toh/dlink/dir-505 As for the structure of the devicepages: There has been some discussion in the forum, which resulted in this proposal (the @@ are for filling in via bureaucracy forms): https://lede-project.org/playground/sample-device-page We should discuss the details of the devicepage-templates in the forum. Comments from users and developers are very welcome. BTW: It is nice to see that now that 17.01.0 is out there's some interest in filling the LEDE wiki. :) Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] imx6: add support for GW5904
Just curious: Why is the GW5904 not listed on http://www.gateworks.com/? I'm searching for technical data to include in the Table of Hardware (https://lede-project.org/toh/views/toh_minimal_all?dataflt%5BBrand*%7E%5D=g ateworks&dataflt%5BModel*%7E%5D=ventana) Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] WG: [source] ramips: add support for Sanlinking D240
When will there be a precompiled 17.01 image for this device? With 17.01.2 or with the next major release? I'm asking because there were some devices with snapshot support that I would have expected to have a 17.01.1 image available, but there is none. Thomas -Ursprüngliche Nachricht- Von: lede-commits [mailto:lede-commits-boun...@lists.infradead.org] Im Auftrag von LEDE Commits Gesendet: Freitag, 28. April 2017 17:11 An: lede-comm...@lists.infradead.org Betreff: [source] ramips: add support for Sanlinking D240 jow pushed a commit to source.git, branch lede-17.01: https://git.lede-project.org/49ce6d04b0fa56facd37924003df02b4ebf14aab commit 49ce6d04b0fa56facd37924003df02b4ebf14aab Author: Kristian Evensen AuthorDate: Sat Feb 4 21:28:52 2017 +0100 ramips: add support for Sanlinking D240 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] ramips: Add support for GL-MT300N-V2
> -Ursprüngliche Nachricht- > von Piotr Dymacz > Gesendet: Donnerstag, 4. Mai 2017 10:30 > > Hello, > > Please, make sure to add a proper SoB line as described in "Submitting > patches": [1]. > > Also, could you please include in your commit message short description > about the hardware and how to install LEDE on it? Have a look at the > recent ramips board additions for some examples: [2]. > > [1] https://lede-project.org/submitting-patches > [2] > https://github.com/lede- > project/source/search?&q=ramips+add+support+for&type=Commits I think it would make sense to add a note to [1] regarding hardware description and install instructions. This is really helpful information for adding devices to the Table of Hardware, especially for devices where not much if any information can be found on the net. Hopefully it will also save you from having to repeat that note with each new "add support for..." commit. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] Documentation for router support means the famous Table of Hardware
[Sorry if this message is out-of-thread. I joined the mailinglist only today] Russel> If you want something that's pretty, hire someone to watch Russel> RecentChanges and clean stuff up. I did this quite intensively in the past, but needed some time for other stuff during the last 5 months. Triggered by a notice on the OpenWrt mailing list that the wiki got spammed again, I slowly start watching the changes to the wiki again. However, I'm hesitating to invest as much time as I used to some months ago, since I don't want to see my efforts wasted in a project that's somehow stalled due to the split in LEDE and OpenWrt. I can only invest time in _one_ project, and preferrably that would be a project that is live and vital. Russel> If the experts had the time and raw information to do it, we wouldn't be talking about this. What I always said: Let the developers do what they can do best: Develop. Documentation is an unliked child (I see this at my own privat projects) and should be left to people dedicated to documentation. Jan-Tarek> My goal is to make the ToH more easyer undastandlebil and human writebil. Can you be more precise what is hard to understand on the current OpenWrt ToH? It has been created by only a small bunch of highly interested people, and what I was always missing was a broader feedback from the community and the developers. If there is the need for improvement, and if there are useful proposals, I'd be happy to implement whatever is possible. Jan-Tarek> Also I wish we can establish a reviewing and applying process. Jan-Tarek> But I dont know how we can resolv this inside a wiki You need reviewers for this, but where to find them? Review process: Dokuwiki has some plugins for this purpose: - https://www.dokuwiki.org/plugin:publish - https://www.dokuwiki.org/plugin:approve I havn't tried them out, though. But as others already said: This would be a hurdle that not every user wants to take. It would slow down the evolution of the wiki pages significantly, IMHO. The better way would be the one described by Russel: Have some dedicated people that take care of the changes being made, correct errors, revert spamming etc. However, the same question again: Where to find those people? I am only _one_ of the needed "gardeners", and I whish there would be some more. I can take care of syntax/grammar/formalisms/tidyness, but could use some support on the technical side. One thing that is important for either way: Have some rules set up regarding how to groom the wiki. Currently, in the absence of such rules, everybody is editing the wiki as he likes, leading to the mess we have today in the wiki. What the editors do not understand: The modularity that was there when the wiki started. For each device, the whole installation process is repeated over and over again. John> minor details, openwrt wiki still has 0 admins that delete John> and protect pages, which is the important part of my mail. I'm still there... but to pick up the idea of LEDE, to have several people for the same function in order to avoid a mess like at the beginning of this year: OpenWrt or LEDE needs more gardeners like me. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] lede forum
moeller0> I am not advocating to keep the ban-hammer swinging moeller0> all times, but there should be some feed-back and moeller0> potential consequences of prolonged and repeated lack of nice-ness. I am of the same opinion. The OpenWrt forum didn't need any moderation for long time (years!), but then there are times where a single user destroys the harmonic and helpful atmosphere, since he can safely do so without the fear of any consequences. This single user made me turn away completely from the forum. A forum needs an admin / moderator that can take actions, just in case. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] A Wiki for LEDE Documentation
> I recommend we use Dokuwiki as the primary means of maintaining the > LEDE documentation. That would be my first choice, too. However, if there is another wiki that has significant advantages over Dokuwiki, I wouldn't mind to try something new. One thing to keep in mind when chosing a new wiki software: At least two people are needed that bring some knowledge about this software with them. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Hardware for VDSL with ISDN or 4 x TAE (VoIP) ?
> what Router is recommendation for VDSL and VOIP with a ISDN-Port or 4x > TAE Ports All supported devices with modem: https://wiki.openwrt.org/toh/views/toh_modem_supported?dataflt%5BModem*%7E%5D=dsl There's not much information available about TAE in the ToH, though. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] A Wiki for LEDE Documentation
> We got no answer from LEDE devs apart from jow saying he had some space > on the server and asking what wiki people prefers, but that discussion > died up quickly. > I'd personally prefer your "jump the gun" approach where someone starts > the wiki unofficially and all those that want to contribute do it there > before we get old waiting. I would definetely wait for Jow to answer on this subject. AFAIK he is quite busy these days. A LEDE wiki should be part of the LEDE infrastructure, with proper control and multiple admins, in order to avoid situations like at the beginning of this year. Give Jow a little time to respond. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Documentation for router support means the famous Table of Hardware
> On a related note I wonder if anyone ever thought about joining forces > with WikiDevi? Indeed, I already thought about this long ago. That's the reason why I implemented the link to wikidevi in the dataentry pages. wikidevi provides usefull data, and in fact, more data and more detailed data than we have in our ToH. The big advantage of wikidevi: It has a broader spectrum of potential contributors. Not only OpenWrt / LEDE users might be interested to contribute to wikidevi, but also DD-WRT or other interested users. That's also the reason why I advised: If the device is not supported by OpenWrt, feed your data to wikidevi, where it has a broader audience which could contribute. However, as you mentioned, the guy(s) at wikidevi are hard to catch. But since I didn't think it to the end, we should first make up our minds how the "joined forces" could look like and what we expect from it. What I was thinking back then: The ToH contains much technical information from wikidevi, plus some OpenWrt specific like 'Current supported release' or 'Unsupported (e.g. wifi not working)' and some more. Why do we need to copy the technical information from wikidevi in our ToH? Can't we directly pull from the wikidevi database? And also the other way round: wikidevi has already some links to OpenWrt... Can't wikidevi pull directly from our ToH database to always have the latest data on OpenWrt support? The same applies to techinfodepot.info. They actively have included OpenWrt in their dataentry. Nice! (e.g. http://techinfodepot.info/wiki/Linksys_WRT1900AC) My expectations: 1) By using wikidevi as source for hardware information, we can participate in the knowledge of a broader audience than OpenWrt/LEDE has alone. -> Less maintenance efforts for the LEDE wiki admin -> Faster input of missing hardware information through broader audience 2) By providing LEDE support status information to other websites, LEDE shows presence and gives the user a convenient information at hand, that his device is supported by LEDE, together with a link on how to install etc (a.k.a. devicepage). Comments are welcome! Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] A Wiki for LEDE Documentation
> From what I can see the next steps to get an actual wiki up and running > would be: > > - Assemble a team of volunteers to maintain the wiki Let me be the first to offer my services as wiki admin to LEDE as I did to OpenWrt. ssh root access would be helpful. At least I need access to /conf/userstyle.css /conf/wordblock.local.conf Access to daily backup with easy playback script would be helpful (just in case). > - Among those volunteers who want to work on the wiki, decide on a > software / markup flavor Reading through this thread, I see - some support for Dokuwiki, with the main advantages: 1) we know it is working, 2) there is an experienced admin with in-depth knowledge of the ToH (me) - no reasons against Dokuwiki - some notes to avoid MoinMoin - some mentiones of Twiki, but no good reasons to switch to it - some mentions of Mediawiki To get things going, and since there is no obvious reason to switch the wiki software, I advise to setup a Dokuwiki, if no one else has good reasons against it. Please slow me down in case I'm going too fast. > - Setup the chosen wiki software - we can use LEDE's donated Digital > Ocean resources to setup production and test instances Very good point: Test instances! I did this with my "demowiki" on a raspberry pi, but having a dedicated test instance or even better clone of the productive wiki would be really great. Looking forward to build a wiki from ground up. Oh, what is really needed for this build: Discussion between the volunteers, either via mailing list, or via forum. I'd prefer the latter, since it's easier to access for the standard user than a mailing list. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] A Wiki for LEDE Documentation
> I think we should avoid forums for now and should lay out the wiki's > plans in a wiki page and activate a plugin (there are at least a couple > for docuwiki) to make a "talk" page or "discussion" page like > Wikipedia's for wiki volunteer interactions. Interesting idea. The "discussion" page is disabled in the OpenWrt wiki. I guess because those discussions require quite some admin-time, which wasn't available in the past. Shouldn't be a problem to at least try it out. If it doesn't work as expected, it can be deactivated with a click. I somehow feel the need to collect ideas like this somewhere more suitable than a mailing list... *hint* ;-) Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] A Wiki for LEDE Documentation
> von John Crispin > Gesendet: Donnerstag, 15. September 2016 07:20 > if you need a strong leader to tell you what you can(not) do, > then you are in the wrong place buddy. I think the reason for asking the devs about their approval or at least their opinion was just respect. In the absence of any other guideline and if you are polite, you just ask, before doing anything. > consider the core team as > members of the community that have just been around for a long time and > played a big role in some part of the project. Thank you for this clear statement. Also thanks to Jow for his clear statement. Short summary: - The wiki is community driven. - The devs are equal members of the community. - There is no special approval of the devs necessary for wiki content, appearance, ... - If the community (which the devs are part of) objects to some content, appearance, whatever in the wiki, it can be discussed and possibly changed to a better. That is what the engaged people in the OpenWrt wiki were looking for: A clear statement. > the problem is > that people tend to sit around, not get involved and use the "the > leader gave no orders" excuse to legitimate their silence. Well, at least there was the attempt to start a conversation. Can you imagine how frustrating it can be to get no answer at all? No yes, no no, no maybe? Anyways, we have a direction now. The past is behind us, the future before us. It will be as good as the community can make it. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Documentation for router support means the famous Table of Hardware
> von Alberto Bursi > Gesendet: Donnerstag, 15. September 2016 00:44 > I think techinfodepot is going to be more cooperative with this plan > than wikidevi, although wikidevi is already queryable somehwhat so > extracting data would work. >From a PM: "I believe that DarkShadow the creator of TechInfoDepot is in the process of entering all of the data into WikiDevi and plans to discontinue TechInfoDepot when the process is complete. You can see some of the progress by looking at Recent changes on WikiDevi." > For an expansion into the NAS area (an area where LEDE is still not > really that present atm), it might be considered to do a similar thing > with NAS Central, which seems to have a similar wiki about most NAS > hardware http://www.nas-central.org/wiki/Main_Page Another good idea to put on the list. > But I also think that this isn't a top priority for now, the work > needed to get this working should be done later, when the wiki is more > or less in shape about documentation and tutorials. > Really I think documentation and tutorials are the top priority (as > they are in the worst shape overall), hardware database is decent as- > is. Agreed. The hardware DB is the easiest to carry over, however, it will require some work to do it right. More about this when the wiki is set up. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] LEDE Wiki Teambuilding
Proposal to get things started. Usage: Copy & paste w/o quoting, add your name / function, send. With each reply, the list should get longer. Note : We need multiple persons for the same functions. LEDE Wiki Teambuilding == FunctionDescription / Activity == Infrastructure Take care of the webserver and the hardware it is running on wiki admin General configuration, spam countermeasures (i.e. avoid spam), ACL, ... wiki enablerIf you need a special function / plugin installed, let me know wiki maintenanceKeep wiki software + plugins updated ToH maintainer Take care of dataentries, usage of datatables, ToH structures and rules for dataentry values Add new dropdown values (Brands, targets, ...) GardenerGroom the wiki (syntax, grammar, spelling, ...) Take care of tidyness, appearance, modularity Editor Create new pages, edit existing ones ... ... NameFunction == N.N.Infrastructure ---- Thomas Endt wiki admin / enabler / maintenance ToH maintainer, Gardener, Editor N.N.wiki admin / enabler / maintenance ToH maintainer N.N.Editor, Gardener N.N.Function I forgot ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] A Wiki for LEDE Documentation
> von Jo-Philipp Wich > Gesendet: Mittwoch, 14. September 2016 00:14 > - Assemble a team of volunteers to maintain the wiki In progress. Thread started for teambuilding: http://lists.infradead.org/pipermail/lede-dev/2016-September/002807.html > - Among those volunteers who want to work on the wiki, decide on a > software / markup flavor >From the feedback in the threads regarding the wiki, I see a tendency towards Dokuwiki. > - Setup the chosen wiki software - we can use LEDE's donated Digital > Ocean resources to setup production and test instances In above mentioned thread, Martin already volunteered for taking care of the infrastructure. Since we preferably have more than one person per function: Would you be the second one? Who would do the initial setup of the webserver etc? Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] A Wiki for LEDE Documentation
Wiki has been set up: https://wiki.lede-project.org/ You can now register yourself and contribute in building the LEDE wiki. Discussions are available either in the wiki (lets see how good this works) or in this mailing list. Please use '[LEDE-DEV][wiki]' in the subject of your email to enable easy filtering. Please always remember: The wiki is from the community and for the community. It can only be as good and as up to date as you make it. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] A Wiki for LEDE Documentation
What would be the official LEDE logo for the wiki? This one? https://www.lede-project.org/logo/logo_small.png If yes: Can I have this in a bigger size, please? FYI: I changed the wiki template to monobook, but other templates are available [1], up to creating our own one. Comments are welcome. Thomas [1] https://www.dokuwiki.org/template ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [wiki]Wiki structure proposals and some questions
> I recently posted in the discussion page of the todo page of the wiki. > https://wiki.lede-project.org/talk:to_do_list > Now, apart from that I'd like to note that while I can get a nice > forum-like interface where I cal also select if I want to get emails to > notify answers when it's my first post in a discussion page I implemented a more comfortable way for discussions. See the above link. > Also, it would be cool to get email notifications about any page > modification to pages I subscribed or have chosen somehow too, I didn't > find anything to set that. dokuwiki is RSS capable, however, I havn't done anything yet with RSS. I'll check this out. Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [wiki]Wiki structure proposals and some questions
> > Structure: > > I was thinking about dividing the wiki in five main pages [...] > Looks good to time, maybe Thomas has also comments on that? Just go ahead and show something. Playground for temporary presentations: https://wiki.lede-project.org/playground:playground > > Also I'd like to have the “hardware support” page to have the devices > divided by most likely usecase Like "show me all modems"? https://wiki.openwrt.org/toh/views/toh_minimal_all?dataflt%5B0%5D=device%20type_%3DModem Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [wiki]Wiki structure proposals and some questions
> Also, it would be cool to get email notifications about any page > modification to pages I subscribed or have chosen somehow too, I didn't > find anything to set that. You now find an additional button on top of the page "manage subscriptions". Good for now, but needs some attention regarding the downsides mentioned here: https://www.dokuwiki.org/subscription#enabling_subscriptions Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [wiki] Creation of discussion pages simplified
To make it easier to create discussion pages and post comments on wiki pages, I implemented a namespace template for the talk: namespace. To create a new discussion regarding a wiki page * just click on "discussion" * then "create this page" * then save it without any edits. A nice discussion editor will appear only after saving (it will not be visible in the preview). Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [LEDE DEV][wiki] Login with github
IIRC it was Martin who proposed to use oAuth to log in to the wiki with github credentials. I installed the oAuth plugin (https://www.dokuwiki.org/plugin:oauth) for this purpose and created an oAuth application with my github account for testing purposes. Since the owner of the application is shown under https://github.com/settings/applications and to avoid a SPOF, the owner of the LEDE-Wiki login application should probably be someone other than me. I'm not sure if github organizations (i.e. lede-project) can create oAuth applications. Can someone of the devs please try? Things to enter in https://github.com/settings/applications/new Application name: LEDE wiki login Homepage URL: https://wiki.lede-project.org/doku.php Application description : Log in to the LEDE wiki with your github account. Authorization callback URL : https://wiki.lede-project.org/doku.php After successful creation of the application, the "Client ID" and "Client Secret" need to be entered in the oAuth config of the wiki (-> admin -> config -> oAuth). You can either do this yourself or let me know. To use the login via github, the user needs to update his wiki profile accordingly: -> Update profile -> Login with other Services -> check Github -> save Please let me know your thoughts. Regards, Thomas <>___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [LEDE DEV][wiki] Login with github
> Hi, thanks for setting that up! Works for me but I hope it's possible > to reduce the required permissions for the login. At the moment the > OAuth Plugin gets full read+write access to the profile of the github > account. $someone opened a ticket recently: https://github.com/cosmocode/dokuwiki-plugin-oauth/issues/41 rw access is really a bit too much. > Should we just patch the oauth plugin? > Is there a way to make this update proof? We could test this in the testwiki. Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [LEDE DEV][wiki] Template switcher / mobile version added
I added a template switcher which allows you to switch between two templates or themes. You find a dropdown list in the upper left of the page. Full version = monobook Mobile Version = bootstrap3 This is just for tryout. Please let me know if you think it's useful to provide this dropdown list. Regards, Thomas <>___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [wiki]Wiki structure
> the wiki's "full version" (the desktop version) lacks the navigation > panel on the left side. > To get anywhere I need to switch to "mobile version". > > -Alberto Fixed. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [wiki] ditaa: Converts ASCII to nice graphics
You can now easily create nice graphics in the wiki via drawing in ASCII. Example: https://wiki.lede-project.org/playground:playground Syntax: https://www.dokuwiki.org/plugin:ditaa Have fun! Thomas <>___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [wiki]Wiki structure
> By the way, the mobile template looks usable enough on a regular > computer, is there a need to have two different templates? There's no real need for two different templates, I was just experimenting. I permanently switched to Bootstrap3 and removed the template switcher (Full/mobile template). Should there arise the need for special mobile/desktop templates, we can implement this later on. > Also, I find it a bit annoying that the menu on the left changes > whenever visiting different pages. For instance, the links provided by > the left sidebar (with the mobile template) are very practical on the > main page, but when visiting e.g. https://wiki.lede- > project.org/docs:start , an entirely different set of links is > displayed. I find this somewhat confusing. It's a feature to have different sidebars for different namespaces, but I see the concerns regarding this feature. I removed the different sidebar for now. If we want to have it back again: no problem, can easily be done. Comments and improvement proposals are welcome! Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] openwrt and lede - remerge proposal
> -Ursprüngliche Nachricht- > Von: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] Im > Auftrag von Imre Kaloz > Gesendet: Mittwoch, 10. Mai 2017 11:36 > > On 2017-05-09 18:29, Philip Prindeville wrote: > > > > > I’d like to suggest one more action item to this list if I can. It > would be handy to have a single database for user > authentication/identification for submitting bugs, editing the Wiki, > etc. > > > > Previously there were too many places where you had to create an > account. If we can’t do “single sign-on”, can we at least do “single > sign-up”? > > > > And part of a user’s profile should include their IRC handle > (assuming they have one). > > I agree, SSO would be way more user friendly. We should look into it > for sure. The LEDE wiki and LEDE forum currently offer login via github. Others are possible, e.g. Auth0, Google, Doorkeeper, Keycloak, ... Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] github oauth for webpage editing requests too many permission
> Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von Alberto Bursi > Gesendet: Mittwoch, 7. Juni 2017 20:11 > > On 06/07/2017 05:45 PM, Martin Tippmann wrote: > > On Wed, Jun 7, 2017 at 5:00 PM, Karl Palsson > wrote: > >> Hi, > >> > >> I was trying to fix something on the documentation pages of > >> lede-project today, and tried to login with github. > >> > >> However, the docuwiki/oauth thing is demanding full read/write > access > >> to my account, which seems excessive... > > Hi, we already noticed this: > > http://lists.infradead.org/pipermail/lede-dev/2016- > October/003099.html > > > > https://github.com/cosmocode/dokuwiki-plugin-oauth/issues/41 > > > > Looks like the original plugin is still not updated. > > > > Seems like the fix is pretty trivial though (change a line in a php > file), see this commit from a fork: > https://github.com/micgro42/dokuwiki-plugin- > oauth/commit/39b9184bb4c606c3d0fc43d8e565368bcaab2f92 > > Anyone with root access to the server can easily do that on our side. > > I can do that if we agree it's OK to do so. > > -Alberto Seems there is finally some movement after I nudged a bit: Pull request has been opened. https://github.com/cosmocode/dokuwiki-plugin-oauth/issues/41 However, the real implementation date is still unknown, and since the solution is so easy, I'd say: Go ahead, apply that change to the LEDE wiki. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] LEDE call for vote on remerge proposal V3
> Transferring the openwrt.org domain to the SPI is seen as a > prerequisite before the next steps will be taken by the LEDE > developers. > > @Imre: I assume this needs multiple steps, could you please update us > on the status of transferring the openwrt.org domain to the SPI please. Almost two weeks later: What is the status of the domain transfer to the SPI? Is there an estimated timeline available for when the domain transfer will be done and the next steps can start? Please forgive me my impatience, but I'm already thinking of the merge of the two wikis, now that the voting has been done. Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Lede/Openwrt documentation
> -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von John Norton > Gesendet: Dienstag, 24. Oktober 2017 18:20 > An: lede-dev@lists.infradead.org > Betreff: Re: [LEDE-DEV] Lede/Openwrt documentation > > > > On 24/10/2017 18:02, Javier Domingo Cansino wrote: > > Hello, > > > > I have been reviewing email on the archive about what will happen > with > > openwrt/lede documentation on the remerge, and I couldn't reach any > > conclusion. Would mind anyone clarifying? > > > > Cheers, > > > > Javier > > > > ___ > > Lede-dev mailing list > > Lede-dev@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/lede-dev > > Afaik it's not decided what will happen to it until they have finished > the repo/code merging. > > Imho (what I would do) is just migrate current LEDE wiki content in > OpenWRT wiki, Question @devs: Which way will we be moving? From LEDE server to OpenWrt server or vice versa? > while current OpenWRT stuff is either obsoleted (where it > is replaced by the LEDE wiki articles) or moved to suit the same > general structure of LEDE wiki. Sounds easier than it is / will be, or maybe I'm thinking too complicated. Alberto, I'd really appreciate having you in the wiki-admin team to accomplish the wiki merge. > Since both use the same wiki framework (mediawiki) it should be easy. It's dokuwiki for both. > If this happens I'll probably need ssh access and sudo rights for the > OpenWRT wiki server and an admin account in the wiki software, Depends on the direction we will be moving, see above. Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Lede/Openwrt documentation
> > What exactly do you need? All wiki pages? Including history? > > Will look into this this evening. We will find an easy way. > > Someone mentioned there were private pages, but if possible, I would > create a git repo, commit all the content and upload it to github. I > can work on a proper history rewrite if we want to keep history, but I > would just focus on the latest version, rewriting history later is just > git work. Just to get a clear picture: - We are talking about the LEDE wiki pages or the OpenWrt wiki pages, or both? - We are talking about the developer pages only, or about the complete content? Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Lede/Openwrt documentation
> > The wiki currently hosts and renders tables on the basis of data > > acquired and stored in a database. > > The table of packages and table of hardware. They are searchable and > > can be filtered. > > The table of hardware has a template system to let people add new > > devices to the "hardware database". > > https://lede-project.org/meta/create_new_dataentry_page > > Is there a way to do something like that with this new system? > > We can setup a file to be copied and filled, and people would just fill > it. What is the objective of the database? What uses does it have? https://lede-project.org/toh/start The ToH (Table of Hardware) lists devices which are supported by OpenWrt (and quite some that are not supported; remainders of old times). It comes in different views, showing different columns, paying respect to limited horizontal screen space. - All views: https://lede-project.org/toh/views/start - View for selecting a new device to be bought, filtered for supported devices which have >4MB flash + >32MB RAM -> https://lede-project.org/toh/views/toh_available_864 - View for downloading firmware: https://lede-project.org/toh/views/toh_fwdownload Just having a "file that people fill" seems to go in the direction of having a static table. That's not what we want. Filtering for certain data is a mandatory feature. This whole ToH thing is worth a discussion on its own. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Lede/Openwrt documentation
> > - We are talking about the developer pages only, or about the > complete > > content? > > Everything That's contrary to your statements in the start posting: > [...] documentation targeted at hackers, contributors, and would-be > developers. > [...] RFC proposal of a new developer documentation > Links [1] [2] [3] > [...] more focused scope: the scope is explicitly limited to developer > documentation. > [...] this new doc would serve as a detailed and up-to-date reference for > OpenWrt internals, while the wiki would still be extremely useful for > user-oriented documentation Why is this contrary? Because "Everything" includes everything in here: https://wiki.openwrt.org/toh/?do=index and I guess you don't really want to have each and every little change to the devicepages (/toh/yourbrand/yourmodel) go through git. Don't get me wrong, I just want to clarify the scope of your proposal. You can and will get everything you want, because I support your proposal to lift the developer docs to a new level of quality. Keep you posted. Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Lede/Openwrt documentation
> It seems that there was a bit of confusion. What you quote here is > from me, not from Javier. Also, it's from a different thread [1], in > which I indeed proposed a new system from the developer documentation > (only). > > The current thread is about how to merge the LEDE wiki and the OpenWrt > wiki. > Or at least, that was the initial discussion. I indeed mixed that up as much as possible. Sorry for that! Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] fixing of image file names
See also http://lists.infradead.org/pipermail/lede-dev/2017-January/005307.html, where I mentioned some of this and some more. > -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von Moritz Warning > Gesendet: Dienstag, 28. November 2017 19:05 > An: lede-dev@lists.infradead.org > Betreff: [LEDE-DEV] fixing of image file names > > Hi, > > I noticed that there are some image file names that do not follow the > "common" name scheme. > Is it ok to change it? I would like to submit a patch. > > Some examples: > - all lower case image names > - lede-ipq806x-EA8500-squashfs-sysupgrade.tar => lede-ipq806x-ea8500- > squashfs-sysupgrade.tar > - revision between - > - lede-mvebu-linksys-wrt1900acv2-squashfs-sysupgrade.bin => lede- > mvebu-linksys-wrt1900ac-v2-squashfs-sysupgrade.bin > - region specific images with region identifiers (us, eu, il, ...) > - lede-ramips-rt305x-wnce2001-squashfs-factory-northamerica.bin => > lede-ramips-rt305x-wnce2001-us-squashfs-factory.bin > - separate images for each version > - lede-brcm47xx-mips74k-linksys-e1000-v1-v2-v2.1-squashfs.bin => > lede-brcm47xx-mips74k-linksys-e1000-v1-squashfs.bin, ... > > best wishes and unicorns, > mwarning > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] owrt landing page
Hi John, Since the styling is based on CSS, we would need the OpenWrt wiki's CSS for that. Once we have that, it will be relatively easy. But instead of doing the merge of the wikis step by step, I would suggest a hard cut. 1.) Make OpenWrt wiki read only -> I can do that or Imre 2.) Create .tgz of OpenWrt wiki and hand it over to LEDE wiki admins -> Imre 3.) Move LEDE wiki to OpenWrt styling (apply OpenWrt theme and CSS to LEDE wiki) -> I can do that. Some help of CSS experienced guys could be necessary for hard cases. 4.) Move content of old OpenWrt wiki to new OpenWrt wiki (former LEDE) -> I can take the toh part (devicepages); dataentries will be taken from LEDE since they are way more up to date and contain more datafields. -> Rest of the wiki: A plan needs to be worked out what will be carried over from old to new OpenWrt wiki -> Community discussion I'm in the starting blocks since weeks, waiting only for the GO and the OpenWrt wiki sources, and I'm sure, we will have some helping heands ready to start the wiki merge. Thomas > -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von John Crispin > Gesendet: Freitag, 5. Januar 2018 18:54 > An: LEDE Development List; LEDE Project Administration; OpenWrt > Development List > Betreff: [LEDE-DEV] owrt landing page > > Hi, > > could someone please help us with rebranding the lede landing page to > an openwrt colour/theme ? i would like to see this swithced over within > the next 7 days. > > John > > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] owrt landing page
Hi John, First results on a private demowiki, see: https://lede-project.org/_media/wiki/ledewiki-owrtstyling.jpg 1) red marking: What are we going to do with the sidebar (raw, untouched styling; could be beautified)? Keep or remove? 2) blue marking: I remember there was some discussion about a new, fresh logo. I think now with the move to the LEDE codebase is the right time to refresh the wiki a bit too. Does anybody remember where that discussion happened and what the outcome was? 3) I changed my mind regarding hard cut. The OpenWrt wiki is still rw, and we should keep it that way until we have a plan on how to accomplish the actual merge of the wikis. Thomas > -Ursprüngliche Nachricht- > Von: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] Im > Auftrag von Thomas Endt > Gesendet: Samstag, 6. Januar 2018 18:06 > An: 'John Crispin'; 'LEDE Development List'; 'LEDE Project > Administration'; 'OpenWrt Development List' > Betreff: Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page > > Hi John, > > Since the styling is based on CSS, we would need the OpenWrt wiki's CSS > for that. Once we have that, it will be relatively easy. > But instead of doing the merge of the wikis step by step, I would > suggest a hard cut. > > 1.) Make OpenWrt wiki read only -> I can do that or Imre > 2.) Create .tgz of OpenWrt wiki and hand it over to LEDE wiki admins -> > Imre > 3.) Move LEDE wiki to OpenWrt styling (apply OpenWrt theme and CSS to > LEDE > wiki) -> I can do that. Some help of CSS experienced guys could be > necessary for hard cases. > 4.) Move content of old OpenWrt wiki to new OpenWrt wiki (former LEDE) > -> I can take the toh part (devicepages); dataentries will be taken > from LEDE since they are way more up to date and contain more > datafields. > -> Rest of the wiki: A plan needs to be worked out what will be > carried over from old to new OpenWrt wiki -> Community discussion > > I'm in the starting blocks since weeks, waiting only for the GO and the > OpenWrt wiki sources, and I'm sure, we will have some helping heands > ready to start the wiki merge. > > Thomas > > > -Ursprüngliche Nachricht- > > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im > Auftrag > > von John Crispin > > Gesendet: Freitag, 5. Januar 2018 18:54 > > An: LEDE Development List; LEDE Project Administration; OpenWrt > > Development List > > Betreff: [LEDE-DEV] owrt landing page > > > > Hi, > > > > could someone please help us with rebranding the lede landing page to > > an openwrt colour/theme ? i would like to see this swithced over > > within the next 7 days. > > > > John ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] owrt landing page
FYI - LEDE wiki styling updated - Sidebar background added - Sidebar fontsize increased --> https://lede-project.org/_media/wiki/ledewiki-owrtstyling2.jpg Of course, sidebar content to be adapted to OpenWrt i/o LEDE, but apart from that: Can we go live with that styling? Thomas > -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von Alberto Bursi > Gesendet: Donnerstag, 11. Januar 2018 19:54 > An: lede-dev@lists.infradead.org > Betreff: Re: [LEDE-DEV] [OpenWrt-Devel] owrt landing page > > 1) sidebar > > I think it should have some background to make it readable, and > possible a slight font increase. > > > 2) logo > > see [1] for the thread about the logo. Nothing was decided. > > I personally agree that having one of the logos from there would be > great, we'd need to ask the developers/project owners for a vote on > this > as the logo is their own decision to make. > > This will probably take months, so for now just use the current logo. > > 3) my idea was to move in a "legacy" section only the parts the current > LEDE wiki already has (and are the up-to-date ones), while all other > stuff that does not have an equivalent is just added as-is to the > current wiki (just linked in the right place). > > > > 1. http://lists.infradead.org/pipermail/lede-dev/2017-May/007783.html > > -Alberto > > > On 01/10/2018 10:56 PM, Thomas Endt wrote: > > Hi John, > > > > First results on a private demowiki, see: https://lede- > project.org/_media/wiki/ledewiki-owrtstyling.jpg > > > > 1) red marking: What are we going to do with the sidebar (raw, > untouched styling; could be beautified)? Keep or remove? > > 2) blue marking: I remember there was some discussion about a new, > fresh logo. > > I think now with the move to the LEDE codebase is the right time > to refresh the wiki a bit too. > > Does anybody remember where that discussion happened and what the > outcome was? > > 3) I changed my mind regarding hard cut. The OpenWrt wiki is still > rw, and we should keep it that way until we have a plan on how to > accomplish the actual merge of the wikis. > > > > > > Thomas > > > >> -Ursprüngliche Nachricht- > >> Von: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > Im > >> Auftrag von Thomas Endt > >> Gesendet: Samstag, 6. Januar 2018 18:06 > >> An: 'John Crispin'; 'LEDE Development List'; 'LEDE Project > >> Administration'; 'OpenWrt Development List' > >> Betreff: Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page > >> > >> Hi John, > >> > >> Since the styling is based on CSS, we would need the OpenWrt wiki's > CSS > >> for that. Once we have that, it will be relatively easy. > >> But instead of doing the merge of the wikis step by step, I would > >> suggest a hard cut. > >> > >> 1.) Make OpenWrt wiki read only -> I can do that or Imre > >> 2.) Create .tgz of OpenWrt wiki and hand it over to LEDE wiki admins > -> > >> Imre > >> 3.) Move LEDE wiki to OpenWrt styling (apply OpenWrt theme and CSS > to > >> LEDE > >> wiki) -> I can do that. Some help of CSS experienced guys could be > >> necessary for hard cases. > >> 4.) Move content of old OpenWrt wiki to new OpenWrt wiki (former > LEDE) > >> -> I can take the toh part (devicepages); dataentries will be > taken > >> from LEDE since they are way more up to date and contain more > >> datafields. > >> -> Rest of the wiki: A plan needs to be worked out what will be > >> carried over from old to new OpenWrt wiki -> Community discussion > >> > >> I'm in the starting blocks since weeks, waiting only for the GO and > the > >> OpenWrt wiki sources, and I'm sure, we will have some helping heands > >> ready to start the wiki merge. > >> > >> Thomas > >> > >>> -Ursprüngliche Nachricht- > >>> Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im > >> Auftrag > >>> von John Crispin > >>> Gesendet: Freitag, 5. Januar 2018 18:54 > >>> An: LEDE Development List; LEDE Project Administration; OpenWrt > >>> Development List > >>> Betreff: [LEDE-DEV] owrt landing page > >>> > >>> Hi, > >>> > >>> could someone please help us with rebranding the lede landing page > to > >>> an openwrt colour/theme ? i would like to see this swithced over > >>> within the next 7 days. > >>> > >>> John > > > > ___ > > Lede-dev mailing list > > Lede-dev@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/lede-dev > > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [wiki] LEDE / OpenWrt wiki merge
Short status regarding the wiki merge: - c/o OpenWrt wiki styling: Prepared, can be implemented with a click I didn't switch yet to the OpenWrt styling, since IMHO this would confuse users, seeing two identically styled wikis, but with different content. - Merge process: Some thoughts on the details of the merge process cast into a presentation: -> https://lede-project.org/_media/wiki/openwrt_lede_wiki_merge.pdf Please see this as a proposal with many "???". I am really unsure if I'm seeing things more complicated than they are. Your thoughts, questions and comments are very welcome. Thomas <>___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] owrt landing page
> -Ursprüngliche Nachricht- > Von: Vincenzo Romano [mailto:vincenzo.rom...@notorand.it] > Gesendet: Montag, 29. Januar 2018 15:34 > > I think that the merge should be finalized as soon as possible. > > As of now: > > 1. openwrt.org home page is still the old one with just the merge > announcement 2. Development link goes to dev.openwrt.org which gives an > error with no way out (at least with chrome) 3. Documentation link goes > to wiki.openwrt.org/doc/start 4. Downloads link goe to > downloads.openwrt.org which neither looks like Openwrt nor Lede. > 5. Wiki link goes to wiki.openwrt.org > 6. Forum goes to forum.openwrt.org > 7. Trademark policy goes to openwrt.org/trademark.php 8. The "download" > link on the right panel gives a 404 error. > 9. The "Headlines" are still outdatedly pointing to OpenWRT 15.05.1. > > Everything else is more or less the same old OpenWRT stuff. > It looks like the amount of work to be done is huge. > I can volunteer for anything the administrators want. Hey Vincenzo, we're currently discussing how to get things started quickly, please see https://forum.lede-project.org/t/lede-openwrt-wiki-merge/10861/8 Helping hands are welcome! Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] ramips: add support for TP-Link TL-WR902AC v3
> -Ursprüngliche Nachricht- > Von: Lede-dev [mailto:lede-dev-boun...@lists.infradead.org] Im Auftrag > von Peter Lundkvist > Gesendet: Samstag, 17. März 2018 18:48 > TP-Link TL-WR902AC v3 is a pocket-size dual-band (AC750) router based > on MediaTek MT7628N + MT7650E. wikidevi shows MT7628AN @575MHz + MT7610EN for the v3. https://wikidevi.com/wiki/TP-LINK_TL-WR902AC_v3.x Is wikidevi wrong? Do you have better photos of the PCB than in the FCC documents? Regards, Thomas ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
