Hi Gerwin,

just a question; is it possible to make questions in this list that are not
100% seL4's source code related? I mean, seL4 will be build and deployed on
a variety of platforms, configurations, environments, etc. The tutorials
themselves deal with several platforms. So, is it welcome/appropiate to
make more generic questions or this is not the right list?

Thank you,

El sáb, 29 may 2021 a las 7:12, Gerwin Klein (<[email protected]>)
escribió:

>
> > On 28 May 2021, at 21:06, Roderick Chapman <[email protected]> wrote:
> >
> > On 28/05/2021 03:38, Matthew Fernandez wrote:
> >> I would guess click the “Edit page on GitHub” link at the bottom of the
> tutorial page.
> >
> > Yes... but I'm a clueless newbie, so I wouldn't presume to make such
> changes correctly. Who's in charge of quality assurance for the
> documentation?
>
> Everybody :-) Ultimately the responsibility is with the foundation
> steering committee, but we rely on developers and everyone else to improve
> docs as they encounter problems.
>
> If you edit on GitHub, this will ultimately raise a pull request on the
> markdown file that backs that particular change, and will be reviewed by
> someone with (hopefully ;-)) more knowledge. So there is no danger of
> breaking anything by accident.
>
> For tutorials, there tend to be two "edit" links, because text gets
> included from multiple sources. One link is for the main page, and one for
> the included text, linking to the repository it comes from (it should say
> something like "Tutorial included from [github repo]. [edit]")
>
> I'm happy to do the edit, though. Just to double check, you mean the page
> https://docs.sel4.systems/Tutorials/hello-world.html ?
>
> What would make sense to add at the bottom to be less confusing?
>
> Cheers,
> Gerwin
>
> _______________________________________________
> Devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to