Created attachment 267234 [details] [review]
Add item for help in global menu

Created attachment 267235 [details] [review]
Initialization of documentation

the real patch

Review of attachment 267235 [details] [review]:

I think you need a licence file and an index.page in this commit as well.

I'll leave it up to the maintainer to decide if they want the help in now. In my experience, it's safe to let docs be written on master, but we can also write it in a branch.

(In reply to comment #3)
> I'll leave it up to the maintainer to decide if they want the help in now.

I don't like the idea of having broken links in the UI for an indefinite amount of time, but if you (or anyone) plan(s) to actually fill in documentation in the near future, I'm perfectly fine with this work happening now and on master.

In general, I'll be happy with whatever works best for you as far as documentation is concerned. I can get you a 'documentation' component if that's of any help, or just go ahead and push :-)

Hello,

The patch is not intended to be pushed right now and off course has to wait some content to be commited.

I can create a tracker for the user documentation and add that block this bug.

(In reply to comment #5)
> The patch is not intended to be pushed right now and of course has to wait
> some content to be committed.

Well, if you know that there'll be content in a week or so, I wouldn't have a problem with just going ahead now. But up to you really :-)


> I can create a tracker for the user documentation and add that block this bug.

Dto.

Refering to the potential introduction of a new string after the freeze, you could comment out the code and the string for the time being and check if it still gets picked up by the po files. ;)

(In reply to comment #7)
> Refering to the potential introduction of a new string after the freeze

I'd say if the user documentation misses string freeze, the actual string "Help" is the least problem - the documentation itself would be a massive freeze break, no?

User documentation has never been under a string freeze.

Created attachment 327408 [details] [review]
help: Initialize the documentation infrastructure

Updated patch, taking into account Kat's feedback in comment #3.

Should we just push this now, or do you usually wait until you have some content first?

(In reply to Florian Müllner from comment #10)
> Created attachment 327408 [details] [review] [review]
> help: Initialize the documentation infrastructure
> 
> Updated patch, taking into account Kat's feedback in comment #3.
> 
> Should we just push this now, or do you usually wait until you have some
> content first?

I think waiting for some content makes sense..

Maybe. But then, getting a stub into place may increase the likelihood of content to appear in the first place.

(In reply to Florian Müllner from comment #12)
> Maybe. But then, getting a stub into place may increase the likelihood of
> content to appear in the first place.

Perhaps having some very basic docs like index page content and then pushing it.

Attachment 327408 [details] pushed as 24ff9b0 - help: Initialize the documentation infrastructure

(In reply to Kunaal Jain from comment #13)
> Perhaps having some very basic docs like index page content and then pushing
> it.

Let's try to get out of the chicken/egg situation where everybody is waiting for somebody else to do the first step. If we don't have anything in time for 3.22, we can simply comment out the entry in the app menu ...

Is anybody working on this patch?

This patch has been pushed a while ago, so no. If you want to follow the current documentation status, you should track bug 722498 instead.