[LEDE-DEV] Fwd: [OpenWrt-Devel] GSoC 2018 announced

[tapper via Lede-dev]

The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.

To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---




 Forwarded Message 
Subject:[OpenWrt-Devel] GSoC 2018 announced
Date:   Sun, 1 Oct 2017 12:04:17 +0200
From:   Andreas Bräu 
To: openwrt-de...@lists.openwrt.org



Hi there,

GSoC 2017 is barely over and Google already announced the next Summer of 
Code for 2018: https://developers.google.com/open-source/gsoc/


Applications start at Jan 4 2018 and will end on Jan 23. Student 
applications will start in March.


I already prepared our wiki ideas page for new ideas: 
https://wiki.freifunk.net/Ideas

Our 2017s ideas you can find at https://wiki.freifunk.net/Ideas_GSoC_2017

Please submit your new ideas, talk to possible students or forward this 
mail to people that may be interested as mentors or students.


Best regards,

Andi

—
Andreas Bräu

XMPP: andibr...@jabber.weimarnetz.de 
Twitter:@evAltenberga 
Blog:https://blog.andi95.de 
PGP:0xB7E04818

___
openwrt-devel mailing list
openwrt-de...@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] Adding acct_interval to wireless configuration

[tapper]

Hi there mate thanks for your first patch!I am not a coder or  a dev. I 
just wanted to let you know that OpenWRT and LEDE are in the middle of 
re merging, so if you don't get any feedback for your patch it's because 
people are trying to sort out the re merging not ignoring you. If you 
dont get your patch merged or any feed back in 1-2 weeks then resend 
your mail. I am glad that we are getting new people around so thanks 
again. Tapper


On 29/05/2017 13:04, Yury Shvedov wrote:

Hi, I'm new here and I wonder why there is still no UCI option to configure 
Radius-Accounting-Interim-Interval.
I've made a patch to fix that and like to share it to others and ask is there 
any serious reason for lack of such
option?

Make an ability to configure Accounting-Interim-Interval via UCI

Signed-off-by: Yury Shvedov <yshve...@wimarksystems.com>
---
  package/network/services/hostapd/files/hostapd.sh | 5 -
  1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/package/network/services/hostapd/files/hostapd.sh 
b/package/network/services/hostapd/files/hostapd.sh
index 6fb902e376..e6bccef39b 100644
--- a/package/network/services/hostapd/files/hostapd.sh
+++ b/package/network/services/hostapd/files/hostapd.sh
@@ -151,6 +151,7 @@ hostapd_common_add_bss_config() {
config_add_string acct_server
config_add_string acct_secret
config_add_int acct_port
+   config_add_int acct_interval
config_add_string dae_client
config_add_string dae_secret
@@ -208,7 +209,7 @@ hostapd_set_bss_options() {
wps_independent wps_device_type wps_device_name 
wps_manufacturer wps_pin \
macfilter ssid wmm uapsd hidden short_preamble rsn_preauth \
iapp_interface eapol_version acct_server acct_secret acct_port \
-   dynamic_vlan ieee80211w
+   acct_interval dynamic_vlan ieee80211w
set_default isolate 0
set_default maxassoc 0
@@ -249,6 +250,8 @@ hostapd_set_bss_options() {
append bss_conf "acct_server_port=$acct_port" "$N"
[ -n "$acct_secret" ] && \
append bss_conf "acct_server_shared_secret=$acct_secret" 
"$N"
+   [ -n "$acct_interval" ] && \
+   append bss_conf "radius_acct_interim_interval=$acct_interval" 
"$N"
}
local vlan_possible=""




___
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 V2

[tapper]

Sounds good to me!

On 22/05/2017 08:40, John Crispin wrote:

Hi,

here is a V2 of the remerge proposal, I tried to fold all the comments 
people made into it, if anything is missing let me know.



 John

*) branding
- the owrt side sees no option of using the lede brand
- a (minor) majority voted for openwrt as a name over lede whilst most 
people said they did not care
- as the last vote had a 100% ACK for a remerge using the owrt brand is 
the only feasible option


*) domain
- transfer owner ship to SPI for openwrt.org and lede-project.org
- add them to the pool of urls at digital ocean
- post remerge build a setup where we have several DNS servers in 
various locations

- point git.openwrt.org at the lede git server
- point bugs.openwrt.org to the lede flyspray instance
- keep both wikis and forums as is (we should decide post remerge how to 
proceed to avoid these issues blocking the progress)
- update the lede domain entries for build/download/rsync/... servers so 
that the openwrt domain also points at them


*) SPI
- nominate a new liaison team (imre and john offer to do this, if anyone 
else is interested let us know)

- inform SPI of the new liaisons, voters and project rules
- this should be done early in the remerge process s.t. the domains can 
be handed over


*) github
- start pushing to the openwrt organisation
- cleanup the list of owners in the openwrt organisation
- obsolete all issues on the openwrt organisation and close the issue 
tracker
- go through the open openwrt and lede PRs, pickup whats useful and 
close the rest, asking people to repost (things wont be rebasable anyhow)

- close the lede PR tracker
- obsolete the lede github org after a grace period of 3-6 months

*) landing page
- add a letter of intent / notice to both current landing pages 
announcing the remerge

- update the lede landing page to represent the openwrt name
- update the landing page to have the same look & feel as the current 
openwrt landing page

- point openwrt.org at the lede landing page
- try to find some design guru that will transform the owrt theme to one 
appropriate to this century


*) trac
- trac is already readonly, keep content so that search engines can 
still find the it
- edit the trac html templates, adding a note pointing at the 
bug.openwrt.org instance


*) email accounts
- currently there are around ~20 active openwrt.org mail accounts (the 3 
owrt devs would like to keep theirs active)
- turn all the webmaster@, hostmaster@, ... accounts into aliases that 
anyone with voting rights can be subscribed to
- ask those people that are no longer active to voluntarily give up 
their accounts
- mail addresses may under no conditions be used for any personal 
business, consultancy, applying for jobs, ... purposes
- any mail sent from an openwrt.org account needs to adhere the 
trademark policy and should only be used for FOSS purposes


*) wiki / forum
- TBD
- asking in either forum/wiki will get a biased vote so keep them both 
around

- start a separate discussion regarding these post remerge

*) LF
- find out what doubts folks have about LF
- find out benefits - we would have their hosting and sponsorship ?!
- start a separate discussion regarding these post remerge

*) git trees
- rebrand the lede tree to openwrt
- work out what has happened inside the openwrt tree since the reboot 
and pick up the useful bits (zoltan has done some prior work on this 
already)


*) mailing list
- ask david to add the openwrt-adm and openwrt lists
- send out invitation mails to the new list
- setup redirect/auto-reply for the existing lists

*) trademark/sponsorship policy
- review/ack imres trademark policy (https://openwrt.org/trademark)
- review/ack jows sponsorship policy (link pending)

*) timeline
- vote / agree on the proposal within the next week
- work on the action items in the 4 weeks after that

 John
___
openwrt-devel mailing list
openwrt-de...@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] openwrt and lede - remerge proposal

[tapper]

+1

Tapper

On 12/05/2017 16:53, Stefan Peter wrote:

On 12.05.2017 10:02, Edwin van Drunen wrote:

Not having WRT in the name, implying it would be for wireless routers, but 
instead using the broad term “development environment” was helping to better 
describe what the platform is and give it a more professional sound.
With the new name the platform was now seen as a professional piece of 
infrastructure.


I fully second this. However, as a non-commiter, my voice does not count.

But I'm relieved that there finally is an open discussion about the
proposed re-merge.

With kind regards

Stefan Peter




___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Drumming up more interest in LEDE

[tapper]

Hi Mauro have you asked on the irc channel or pleas send a mail to the 
list and explain what is not going write for you and some body will try 
and help. One thing to remember is that the devs are fue and don't have 
much time. Sorry you are getting frustrated.



Hi Carlos  you make some good points.
>>Thanks for your input. It's good to let new people to embedded 
devices  know just how people got started and how you conquered the 
learning curve.



On 03/03/2017 18:36, Carlos Ferreira wrote:

Embedded development requires patience and strong will. Yes it is a
frustrating process and although that scares a lot of new junior
developers, it is not the only reason.

Software development for embedded devices is a very different niche
when compared to android/ios development or what is currently called
"cloud development". I have seen CS students running away from a
simple application development, when discovering that it would be
implemented in C language. There's an addiction in CS degrees for
teaching "high-level languages" like Java and so on. It is not the
same thing nor it works the same way. That is also why there are
specific degrees for this, which usually mix Electronics and System
Development.

Although an expert buddy is an interesting idea, it requires time and
dedication from the experts. Most of the time, such is not possible
without personal sacrifice and most of the experts are already
sacrificing much of their personal time. MS has something that
LEDE/OpenWRT do not have. Money, lots of it.

I myself, have learned a lot by example. By following the work of
others and a good amount of dedication in reading the literature. By
reading theory books, blogs and mailing lists. It's a continuous
process. Not everyone is capable of accepting this. That is why there
are so few embedded devs when compared to web development.

--
Carlos Ferreira


On 3 March 2017 at 16:55, Mauro Mozzarelli <ma...@ezplanet.org> wrote:

I have been trying to make a very simple contribution to LEDE, but it has
been a frustrating process because my contribution got stuck due to form
rather than substance.

Unfortunately this might turn away contributors who do not have the patience
to persevere.

I would like to suggest, that when a new potential contributor is putting
forward his proposed change, an expert buddy is assigned to guide the new
contributor through to getting his changes reviewed and pushed into the
mainstream code. A successful contribution would mean a lot and inspire more
work.


Mauro



On 01/03/17 19:42, tapper wrote:


Hi Is LEDE ready to try and get more people from the wider community
involved?

A thought I had is to do a code optimization week.
I know that LEDE is optimized to fit on small flash chips, but It mite be
a good way of getting other coders to look in the code to see if they can
save a bite here and there, or try and make something run a little faster.
Or if that is know good what about a bug bash week? MS has bug bashes and
they seem to get a lot of people talking about windows 10. I am not a coder
and don't understand all the ins and outs of what I am talking about, but I
like LEDE. If just one new dev or doc righter was to be added to the team it
is a net win for all.

If something like this was to be tryed you could post about it on the
forLinux forums and on Slashdot, Hacker News and /r/linux r/openwrt.

___
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 mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] Drumming up more interest in LEDE

[tapper]

Hi Is LEDE ready to try and get more people from the wider community 
involved?


A thought I had is to do a code optimization week.
I know that LEDE is optimized to fit on small flash chips, but It mite 
be a good way of getting other coders to look in the code to see if they 
can save a bite here and there, or try and make something run a little 
faster.
Or if that is know good what about a bug bash week? MS has bug bashes 
and they seem to get a lot of people talking about windows 10. I am not 
a coder and don't understand all the ins and outs of what I am talking 
about, but I like LEDE. If just one new dev or doc righter was to be 
added to the team it is a net win for all.


If something like this was to be tryed you could post about it on the 
forLinux forums and on Slashdot, Hacker News and /r/linux r/openwrt.


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] lede forum

[tapper]

Hi i have bin looking around at forums on the web and it seems that 
discourse,  is not good with a screen reader. From what i can see phpBB 
seems to be the best for a11y.



On 25/07/2016 12:01, tapper wrote:

On 25/07/2016 11:49, Micha Stöcker wrote:

Am 25.07.2016 um 12:37 schrieb Andrew | PolkaSpots:

https://www.discourse.org/ is not bad either.


i have used discourse, it's a little bit bloated in my opinion. but if
resources are no problem it is also a good alternatvice imho.



Micha

Hi can we make sure that the software we choose will be OK with a screen
reader pleas. The openwrt and the Gargoyle forums are both very good for
blind folks to get around with a screen reader thanks.









___
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

Re: [LEDE-DEV] lede forum

[tapper]

On 25/07/2016 11:49, Micha Stöcker wrote:

Am 25.07.2016 um 12:37 schrieb Andrew | PolkaSpots:

https://www.discourse.org/ is not bad either.


i have used discourse, it's a little bit bloated in my opinion. but if
resources are no problem it is also a good alternatvice imho.



Micha
Hi can we make sure that the software we choose will be OK with a screen 
reader pleas. The openwrt and the Gargoyle forums are both very good for 
blind folks to get around with a screen reader thanks.










___
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] lede forum

[tapper]

Hi with the ssl sert being messed up on the openwrt forum we really need 
a forum for lede. I don't know how to set one up but wen one is put up i 
wood like to be a admin to help with noobs and getting rid of spam. I 
have bin a admin on the Gargoyle forum now for a long time and like 
helping people out. thanks  Tapper..


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] Fwd: Re: [OpenWrt-Devel] move OpenWrt codebase to Git and GitHub

[tapper]

 Forwarded Message 
Subject: Re: [OpenWrt-Devel] move OpenWrt codebase to Git and GitHub
Date: Tue, 31 May 2016 13:44:56 +
From: Abhijit Mahajani 
To: openwrt-de...@lists.openwrt.org 

Hello Luka,

First of all, we would welcome the move of openwrt into GitHub. We have 
been using openwrt for one of the project and we have already 
opensourced our port on GitHub (https://github.com/IMGCreator/openwrt) . 
And willing to upstream this to the openwrt community. So having openwrt 
codebase in the GitHub will certainly help in the upstreaming. Any 
guidance is highly appreciated.


Thanks and Regards,
Abhijit A. Mahajani


-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On 
Behalf Of openwrt-devel-requ...@lists.openwrt.org

Sent: Thursday, May 26, 2016 8:34 AM
To: openwrt-de...@lists.openwrt.org
Subject: openwrt-devel Digest, Vol 125, Issue 104

Send openwrt-devel mailing list submissions to
openwrt-de...@lists.openwrt.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
or, via email, send a message with subject or body 'help' to
openwrt-devel-requ...@lists.openwrt.org

You can reach the person managing the list at
openwrt-devel-ow...@lists.openwrt.org

When replying, please edit your Subject line so it is more specific than 
"Re: Contents of openwrt-devel digest..."



Today's Topics:

   1. Re: OpenWrt / LEDE (Bjørn Mork)
   2. Re: OpenWrt / LEDE (Rafał Miłecki)
   3. Re: [PROPOSAL] move OpenWrt codebase to Git and GitHub
  (Luka Perkov)
   4. Re: [PROPOSAL] move OpenWrt codebase to Git and GitHub
  (Luka Perkov)
   5. Re: [OpenWrt-Users] [PROPOSAL] move OpenWrt codebase to Git
  and GitHub (Luka Perkov)
   6. Re: [OpenWrt-Users] [PROPOSAL] move OpenWrt codebase to Git
  and GitHub (Valent Turkovic)
   7. How to debug/config qos-scripts to work with  OpenWRT AA? (Danng)


--

Message: 1
Date: Wed, 25 May 2016 12:55:43 +0200
From: Bjørn Mork 
To: mbm 
Cc: Rafał Miłecki ,
openwrt-de...@lists.openwrt.org, LEDE Development List

Subject: Re: [OpenWrt-Devel] OpenWrt / LEDE
Message-ID: <8760u2pftc@nemi.mork.no>
Content-Type: text/plain; charset=utf-8

mbm  writes:


The hackers email address represents the primary point of contact for
OpenWrt, particularly in regards to donations. Following the surprise
LEDE announcement, forwarding rules for @openwrt.org email addresses
were disabled. This was done to mitigate further damage to OpenWrt due
to misrepresentation, intentional or otherwise.


Failing to see the damage your action has caused is your biggest problem 
right now. Even if we accept the rather far fetched possibilty of 
misrepresentation, there is no way that can outweight the effect on the 
maintainership status OpenWrt.


Right now, 95 of the 145 (PKG_)MAINTAINER entries for OpenWrt packages 
points to an openwrt.org email address belonging to a LEDE committer:


 bjorn@canardo:/usr/local/src/openwrt$ git grep 
'MAINTAINER:=.*<\(lynxis\|noltari\|dangole\|nbd\|hauke\|jow\|blogic\|neoraider\|rmilecki\|cyrus\|stintel\|thess\)@openwrt.org>' 
origin/master -- package/|wc -l

95
 bjorn@canardo:/usr/local/src/openwrt$ git grep 'MAINTAINER' 
origin/master -- package/|wc -l

145

I don't know if all these were disabled, but the package I tried to 
submit to after the split was one of these.  You don't seem to 
understand the devastating effect it has on OpenWrt if occasional 
contributors gets an email bounce from the published maintainer address. 
 There is no way you can blame those maintainers for this situation. 
The problem is solely the responsibility of whoever decided to disable 
those addresses.



Bjørn


--

Message: 2
Date: Wed, 25 May 2016 13:52:54 +0200
From: Rafał Miłecki 
To: mbm 
Cc: OpenWrt Development List ,  LEDE
Development List 
Subject: Re: [OpenWrt-Devel] OpenWrt / LEDE
Message-ID:

Content-Type: text/plain; charset=UTF-8

On 25 May 2016 at 10:09, mbm  wrote:

The hackers email address represents the primary point of contact for
OpenWrt, particularly in regards to donations. Following the surprise
LEDE announcement, forwarding rules for @openwrt.org email addresses
were disabled. This was done to mitigate further damage to OpenWrt due
to misrepresentation, intentional or otherwise.


Hackers e-mail address (mailing list) was also used for internal 
discussions. You not only disabled forwarding rules for @openwrt.org