Re: [riot-devel] Where to put board pictures?
Gunar, Joakim >> >> Would it also be possible with git-lfs to give the board developers >> access rights to upload pictures? >> With LFS it will work as with a regular file, and one would need to open a PR to add/change a picture. I would expect such PRs to be approved almost immediately. On 9/4/18 11:44 AM, Joakim Nohlgård wrote: Does git-lfs let the contributor include the pictures and other git-lfs blobs as part of a Github pull request? Yes. It even shows a preview. See https://help.github.com/articles/collaboration-with-git-large-file-storage/ Regards Juan ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Where to put board pictures?
Hi all, Ideally, the pictures and figures should be part of the pull request to add the board configuration, to make reviewing easier for maintainers. Having the maintainers to upload the pictures manually of a proposed board is too much extra administration and will steal maintainer focus from other areas. I have no experience with git-lfs, but maybe someone on this list can answer: Does git-lfs let the contributor include the pictures and other git-lfs blobs as part of a Github pull request? /Joakim On Tue, Sep 4, 2018 at 11:36 AM, Gunar Schorcht wrote: > Hi Juan, > > every approach which is not bloating a git repository is surely the best > one. IMHO, it is important that the approach gives the board developer > the possibility to upload/update pictures without involving maintainers. > > Would it also be possible with git-lfs to give the board developers > access rights to upload pictures? > > Regards > Gunar > > On 04.09.2018 10:41, Juan Ignacio Carrano wrote: >> Gunar, Jose >> >> > >> > In the end, it should not matter which git repository is bloated. >> > >> >> What about NO repository gets bloated? >> This was already discussed with some other maintainers offline, but I >> want to reinstate it here: >> >> We are not *special* in any way. Compared to other projects, RIOT OS >> does not have any crazy wacky requirements or limitations, and we are >> facing similar issues, for which- after similar sufferings- specialized >> tools were developed. Then why do we insist in doing things differently? >> >> I'm talking about git-lfs. This tools was invented to overcome all those >> issues we are mentioning in this thread. To me it is the only non-hacky >> solution. The only time a user will be exposed to the tool will be when >> building/editing the docs. >> >> git-lfs does not bloat the repo because binary blobs are not stored in >> there, and only the needed versions for the commits you are checking out >> are downloaded (not the entire diff history as with a regular text file.) >> >> Really, all this wiki-as-object-storage thing feels like hammering a >> nail with a screwdriver. If we go with the hacky solution we will regret >> it later when we have to maintain the mess. >> >> Regards, >> >> Juan. >> >> ___ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel >> > > > -- > Wenn du laufen willst, lauf eine Meile. Wenn du ein neues Leben > kennenlernen willst, dann lauf Marathon. (Emil Zatopek) > > > ___ > 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
Re: [riot-devel] Where to put board pictures?
Hi Juan, every approach which is not bloating a git repository is surely the best one. IMHO, it is important that the approach gives the board developer the possibility to upload/update pictures without involving maintainers. Would it also be possible with git-lfs to give the board developers access rights to upload pictures? Regards Gunar On 04.09.2018 10:41, Juan Ignacio Carrano wrote: > Gunar, Jose > > > > > In the end, it should not matter which git repository is bloated. > > > > What about NO repository gets bloated? > This was already discussed with some other maintainers offline, but I > want to reinstate it here: > > We are not *special* in any way. Compared to other projects, RIOT OS > does not have any crazy wacky requirements or limitations, and we are > facing similar issues, for which- after similar sufferings- specialized > tools were developed. Then why do we insist in doing things differently? > > I'm talking about git-lfs. This tools was invented to overcome all those > issues we are mentioning in this thread. To me it is the only non-hacky > solution. The only time a user will be exposed to the tool will be when > building/editing the docs. > > git-lfs does not bloat the repo because binary blobs are not stored in > there, and only the needed versions for the commits you are checking out > are downloaded (not the entire diff history as with a regular text file.) > > Really, all this wiki-as-object-storage thing feels like hammering a > nail with a screwdriver. If we go with the hacky solution we will regret > it later when we have to maintain the mess. > > Regards, > > Juan. > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > -- Wenn du laufen willst, lauf eine Meile. Wenn du ein neues Leben kennenlernen willst, dann lauf Marathon. (Emil Zatopek) signature.asc Description: OpenPGP digital signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Where to put board pictures?
Gunar, Jose > > In the end, it should not matter which git repository is bloated. > What about NO repository gets bloated? This was already discussed with some other maintainers offline, but I want to reinstate it here: We are not *special* in any way. Compared to other projects, RIOT OS does not have any crazy wacky requirements or limitations, and we are facing similar issues, for which- after similar sufferings- specialized tools were developed. Then why do we insist in doing things differently? I'm talking about git-lfs. This tools was invented to overcome all those issues we are mentioning in this thread. To me it is the only non-hacky solution. The only time a user will be exposed to the tool will be when building/editing the docs. git-lfs does not bloat the repo because binary blobs are not stored in there, and only the needed versions for the commits you are checking out are downloaded (not the entire diff history as with a regular text file.) Really, all this wiki-as-object-storage thing feels like hammering a nail with a screwdriver. If we go with the hacky solution we will regret it later when we have to maintain the mess. Regards, Juan. ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT Summit 2018: Registration open
Dear RIOTers, there are still some free tickets available to join the RIOT Summit 2018 in Amsterdam. Registration is free (thanks to our sponsors!) but mandatory: https://riot-summit18.eventbrite.com/ Highlights: - Keynote by Jaime Jimenez, Ericsson - 12 talks on networking, security, applications, and future directions - Tutorials - Demos - Social at Rolling Rock Kitchen Amsterdam - For more details: see http://summit.riot-os.org/ We gratefully thank the following companies for their generous support: Cisco, RIPE NCC, Savoir-faire Linux, SIDN Labs, STMicroelectronics, wolfSSL, Zühlke. Looking forward to meet all of you in Amsterdam!___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
