I cite from Marcos:
> I was analyzing the licensing situation in the lime-packages
> repository. There is no file that indicates the global license, there
> is no CLA (Contributor License Agreements) and there are copyright
> headers set in some files inconsistently.
>> Talking with some of the developers we consider it appropriate to
> establish a license (such as GLPv3 or AGPLv3). This would affect future
> contributions, but it would be necessary for contributors to accept
> that their already written code is also licensed.
>
> To solve this situation I propose:
>
> * Set a license
> * Clarify that the contributions made in this repository respect that
> license.
> * Change existing headers and add missing ones.
> * Create a pull request with all these changes and approve the merge
> among all contributors as a form of acceptance.
The discussion started here:
https://github.com/libremesh/lime-packages/issues/213
Hi everyone,
I've following the list for quite some time and it was only in the last
month that I got myself together and installed LiMe in some Mesh Potatoes
(based on Dragino MS14) that I had with me. In Zenzeleni we've been using
MPs and VillageTelco firmware from the beginning, and although they are
"very Plug & Play" and easy to use for non-geeks, I was pretty impressed by
LiMe. What you have done making IP disappear is quite something as it is
one of the concepts people struggle with the most.
So now, we are seriously considering using LiMe at Zenzeleni. However, we
need a bit of guidance on creating a built for the MP02-AWD which is the
hardware we have in our networks. It is based on the Dragino MS14, so the
internal radio works from scratch after flashing. However, I'd like to add
the secondary radio (ralink usb) to the build, and have the wireless config
files modified accordingly, so it works directly after being flashed.
Anyone keen to guide me about how to do it?
Thanks in advance,
carlos
--
Carlos Rey-Moreno, PhD
PostDoctoral Fellow University of the Western Cape
Zenzeleni Networks: zenzeleni.nethttps://www.youtube.com/watch?v=YxTPSWMX26M
Cel: +27 (0) 76 986 3633 <+27%2076%20986%203633>
Skype: carlos.reymoreno Twitter: Creym
Hi,
Sometimes I feel shy to ask in the mailing list things that have been
answered before. Sometimes it is not easy to find those old answers.
If someone is new to the list, maybe she should first browse within the
old archives published in the web [0] so that you don't get sick of us.
I do not know an easy way to browse those old mail archives in the web.
Would you be interested in having the mailing list published as a web
forum too? That might boost the learning curve for just-arrived people.
New users would have all the answers easily accessible in a web forum.
In Trisquel the mailing list [1] and the web forum [2] -which has a very
useful 'search' box- are connected. They are the same thing, they have
the same contents, published in real time. You can use either the
mailing list or the web forum to both read and write.
I do not know if you find this interesting to have it for LibreMesh.
I do not know if this is something easy to implement. But I am sure the
animals in the Trisquel community would be happy to share with you. (Or
maybe you know better solutions)
I do not know whether old LiMe mail archives could be dumped into a web
forum so that old mail is also published there, or the forum would need
to start from scratch.
It was just a suggestion, if you do nothing it's alright, you normally
answer everything we ask.
[0] https://lists.libremesh.org/pipermail/lime-users/
[1] https://listas.trisquel.info/mailman/listinfo/
[2] https://trisquel.info/en/forum
Hello everyone,
Ilario and I finally finished to have everything configured to have
continuous integration for the lime-packages repository.
https://github.com/libremesh/lime-packages/pull/186
Continuous Integration (CI) is the practice of having tests done on
every branch that is going to become part of your master branch, in
order to fulfill a certain level of quality.
The current stake on doing CI runs a build on all the repo and verifies
that it runs successfully.
So, if you have any tests on your code (hint: nothing there for the
moment) it will be run with your build and fail if something changed
that broke the code.
Also, the CI will publish the resulting images from the build as a
comment on the Pull Request to facilitate the testing... no more need
to build locally to test the branch. Just download the image, run it on
qemu and test. That way we reduce preparation time for testing from 30+
minutes to 5 minutes or less.
if you are interested in adding tests to the code, I've written a
blogpost on freifunk blog about talking about lua and testing (one of
the languages we use on LibreMesh):
https://blog.freifunk.net/2017/06/29/tdd-unit-testing-lua-openwrtlede-c
ase/
If you want to check past previous executions, you can check them here:
https://travis-ci.org/libremesh/lime-packages
Also we have a badge that indicates the health of the branch on the
README:
https://github.com/libremesh/lime-packages/blob/develop/README.md
Hope this helps people get more involved on coding for LibreMesh!
Regards,
