[OpenWrt-Devel] [PATCH v3] gemini: Support sysupgrade on DIR-685

[Petr Štetiar]

Alberto Bursi <bobafetthotmail at gmail.com> [2019-05-21 11:44:37]:

> On 20/05/19 23:48, Linus Walleij wrote:
> > On Mon, May 20, 2019 at 10:56 PM Petr Štetiar <ynezz at true.cz> wrote:
> > 
> > I can start while I still have it in fresh memory and you can chime
> > in on how you want people to do generic checksum etc.
>
> You don't need to worry too much about formatting and making it look cool,

It's not about the formatting, it's about the content. How could I (or possibly
someone else) chime in and improve the docs (easily)?

You mean, that Linus starts adding a new wiki content, then he sends me the
link to the wiki via email, I'm going to log into that wiki (learn just
another wiki markup syntax meanwhile the page loads in order to forget all of
this once I close that tab), then I'll send a reply to Linus (and all other
interested) over the email, that I've added some changes and so on? 

From a developer's point of view it seems like a waste of time and it will
inevitably lead to just another wiki page with the outdated content anyway.

BTW are we going to add links to the wiki into the code? So in case if someone
touches the code one day, then (s)he don't forget to update the wiki page
(sometimes more then one) with the documentation as well? Or are we going to
do the opposite, adding links to the code on the Wiki so in case I'm going to
change something, I'll first check wiki if there's any reference to that code?

Maybe I'm exaggerating, but what is faster then `git grep` ? How could you
potentionaly automate code/documentation checks if you've documentation
somewhere else?

> I'm afraid that waiting for people to decide where they want to bikeshed the
> developer docs will end nowhere, just like it did in the past.

Well, the difference is, that I'm willing to help make it happen this time, if
there's still some interest around this topic. It simply makes sense to me.

Actually I'm not saying, that I'm going to prepare patches which would add
this feature to the tree, but I'm willing help with testing and giving it my
+1 in a potential vote.

I've abused this thread in order to spark exactly this discussion and to see
if there's some interest in potentialy moving forward with this. It will serve
also as a small reminder to me, that this might be next topic I should bring
to to the discussion on our meeting in June.

Don't take me wrong, you're all doing amazing work on the wiki, I'm sorry that
I'm not contributing there as well, but Wiki simply doesn't fits well into my
mutt/vim/git daily workflow.

In the end, we could simply just delete that docs folder again in 2022 if we
find out, that it didn't worked as expected :-)

-- ynezz

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel