Hi all,
git-lfs looks promising and seems to be used by other projects. It would
really help with a not-bloated RIOT repo. The only issue is the fact
git-lfs has to be installed in order to interact with the files
(commands like `make doc`) won't pick the images because they will be
sort of symlinks.
Are the benefits greater than the drawbacks? If so, I can open a PR.
Cheers,
José
On 08/21/2018 01:06 PM, Jose wrote:
Hi all,
Thank you for your responses!
So, it seems we are converging to have them close to the code (RIOT
repo). I will give a look to git-lfs in the meantime.
How problematic/complicated is it to ask the owners of the pictures
if we
can use them? (I have no idea, so maybe my question is not super
valid) I
guess it would be a matter of publishing the picture with a copyleft
license.
I mean this because that would ease the way we treat them. I’d say if we
support a board from which we already have schematics and lots of other
information which is open, then a picture seems for me the least of the
protected information.
I agree with this and maybe it's not that problematic to ask the owner
of the pictures. Some other platforms are hosting pictures in their
own website, so I think it's possible.
Cheers,
José
On 08/21/2018 12:29 PM, Francisco Acosta wrote:
Hi!
On 21 August 2018 at 11:31:37, Jose (jose.ala...@haw-hamburg.de) wrote:
Hi all,
After some time since the board entries were moved to the doxygen
documentation [1], we are facing the problem on where to put board
pictures.
I see 2 cases:
1. We don't have the rights to distribute the picture.
2. The responsible of the board has the ownership of the picture
How problematic/complicated is it to ask the owners of the pictures
if we
can use them? (I have no idea, so maybe my question is not super
valid) I
guess it would be a matter of publishing the picture with a copyleft
license.
I mean this because that would ease the way we treat them. I’d say if we
support a board from which we already have schematics and lots of other
information which is open, then a picture seems for me the least of the
protected information.
Cheers,
Paco.
For 1. I propose to keep what we have been doing and add
deep-links to
the board manufacturer (e.g [2])
For 2. some options:
1. Put them in the RIOT repo under /doc
2. Put them in a folder in the RIOT wiki
3. Put them in a separate RIOT-OS doc repo
I personally think 2. (put them in the RIOT wiki) is the fastest
way to
go and doesn't bloat the RIOT repository. But I would like to hear some
comments about this topic.
When we find consensus, I will update the Porting Guide [3] to
indicate
where to store the files.
Cheers,
José
[1]: http://doc.riot-os.org/group__boards.html
[2]: http://doc.riot-os.org/group__boards__feather-m0.html
[3]: https://github.com/RIOT-OS/RIOT/wiki/Porting-Guide
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
