We must organize the doc

[giacomo (Giacomo Sanchietti)]

@stephdl

does the trademark on the start page with the footnote is satisfying in term of visibility

Yes for me.

[stephdl (Stéphane de Labrusse)]

quick try with http://nethserver.org/dokuwiki and http://mirror.de-labrusse.fr (it is the default favicon) I cannot have a specific icon (it is the default firefox logo) on the desktop shortcut with gnome3 and window7

does other can try ??? I feel a specific apple issue.

[davidep (Davide Principi)]

@stephdl

I feel a specific apple issue.

Me too

Probably this issue has the same solution of

Why the Netserver Webgui doesn't have a favicon?

Hello, Why the Netserver webgui doesn’t have a favicon? How can I put the same favicon as the comunity nethserver site? [image]

The HTML HEAD points to dokuwiki images. Perhaps we can replace them with ours?

<link rel="shortcut icon" href="/lib/tpl/dokuwiki/images/favicon.ico" />
<link rel="apple-touch-icon" href="/lib/tpl/dokuwiki/images/apple-touch-icon.png" />

[alefattorini (Alessio Fattorini)]

I have been a little busy lately, but I’m very happy to follow this discussion, I’m proud of you guys!

@stephdl

a) a registration must be approved by an admin for editing the wiki

Check this proposal:

Building Docs Team

Given that we have a new kids here, the wiki, we need to re-organize the HowTo Team: howto member are you still around? @AbsyntH, @sitz, @etino, @nrauso new members earned the right to join the team: @stephdl @Jim @robb @apradoc @Ctek @WillZen @GG_jr we need new coordinators: @stephdl @Jim would you like to lead it? This pic speaks for itself I’d like to suggest to rename the name of the team to Docs Team [image] What do you think?

• Anyone can read (any registered user)
• Just someone can write
  What do you think to ask the approval here? So you can see also the user profile here on Discourse.
  Docs Team members should be able to given the right rights

b) author name in the howto page

What about adding editor’s name on the bottom? For example something like:

Also edited by: ctek, jim.

d) markdown

ok, it’s fair

e) think about categories

we can tag with many categories the wiki page, see already existing tags
…
a think tank about categories could be nice.

Ok for that, tags are really powerful. Open a new topic about categories we could start from currently howtos to have an overview of big topics.

[alefattorini (Alessio Fattorini)]

@stephdl

I have started to write a volunteering page @alefattorini can you verify and ask to the translator team to have a look, my english is so bad http://www.nethserver.org/dokuwiki/doku.php?id=volunteering

Of course! I have the right guys! The new team: @medworthy, @Huxy, @Bluelake, @tzar, @Adam, @fasttech
Please, could you check the doc?
http://www.nethserver.org/dokuwiki/doku.php?id=howto:volunteering

[robb (Rob Bosch)]

The signing issue has been mentioned before. Personally I don’t see any good in having a document on the wiki signed by the author (and co-signed by editors)
We will make it difficult for outselves when we allow signing because in the end we will end up with angry authors that see “their” document edited or co-signed.
In order to prevent “rooster behaviour” (sorry it is a Dutch term, I don’t know if it exists in English ) I think it is better to have no signing at all. (history of a doc will tell if you have contributed or not).

[fasttech]

Oh Lord. In no way to I mean any offense, but that page gave me quite a laugh.

This, I believe, will require some collaboration.

Example: the use of padawan in parenthesis before developer… is that deliberate, padawan… as in Jedi apprentice… developer?

So who’s going to set editing permissions?

[fasttech]

First example of my thoughts.

from this;

All skills are needed to the NethServer project. You can be a (padawan) developer, a graphist designer, a (futur) poweruser, a simple wiki player, even if you think that you have no linux skills, we will find something to do for you.

The willingness of doing things is what characterizes this community

to this;

The Nethserver project is open to contributors of all skillsets, from wiki editors, power users, graphic designers to developers, even if you think you have no linux skills at all we can find a way for you to help push our project ever forward.

The enthusiasm and participation of our members is what characterizes our community.

[stephdl (Stéphane de Labrusse)]

For now only admin can validate the approval…easy to understand that we cannot have 30 admin with all rights

Please register an account…once approved, do the modification you proposed

[stephdl (Stéphane de Labrusse)]

my ego rang each time I edited a page, never when I created one.

I agree no signature, except on the talk page because you let informations for others with specific content : who, when, what

[robb (Rob Bosch)]

agreed on that 100%

[fasttech]

This confuses me, I have no idea what the intent was with this.

Below you will find all teams which are working hard for the Nethserver community, be part of them.

Check also this document: How can I help NethServer project?

[stephdl (Stéphane de Labrusse)]

In my (french) english word, welcome, these are the guys who work, if you feel good, come on

[robb (Rob Bosch)]

Fasttech, have a laugh when you see the changes on that part of the document…
And yes, as @stephdl says: do join the team and help us out. Looks like you have a ton of good ideas!

[stephdl (Stéphane de Labrusse)]

@fasttech

Check also this document: How can I help NethServer project?

this was added by @alefattorini maybe you can pick up Ideas and reuse what is not redundant

[fasttech]

@stephdl

In my (french) english word, welcome, these are the guys who work, if you feel good, come on

The content following doesn’t really correlate. I’ll have to mull it over to see what I can come up with that follows your intent.

I’ve made some tweaks to the content, some of the remaining I’ll have to chew on a bit to see if I can improve it. I’m off for now.

[giacomo (Giacomo Sanchietti)]

@Jim

I not agree with this… Because it will be hard to decide what is relevant and what is not? Or define what, how and who decide…

@stephdl

I would disagree, even if the case is not yet there, the wiki is alive, so even if you copy and paste a good page to the documentation, at least the wiki must keep it for enhancement.

I see your points, so I will twist the question: which documents documents should be written inside the manual and not inside the wiki? Or viceversa?

[davidep (Davide Principi)]

This is a good question. I want to remark the original idea behind HowTos.

It is the first step towards the implementation of a new module in NethServer. It starts the discussion about a new feature and helps gathering the requirements that are needed to write down an “issue” on the bugtracker.

So an howto should be created here at first, on community.

Having a wiki to organize howtos, improve them and ease information retrieval is a very good thing, however I still consider them as next steps.

Edit: at the end the main goal is producing an RPM for one-click install, which is not having a good howto

[robb (Rob Bosch)]

Should there be a difference between “official docs” and “community docs”?
Who will maintain “official docs”? Is that the “Docs Team” or Nethesis?
If so, official docs can get another status (and ACL) and be placed at a separate location in dokuwiki.

[davidep (Davide Principi)]

official/nethesis/community …I think there must not be such distinction!

From the manual point of view, that has its source code on GitHub, I’d like a Docs Team with write access that merges pull requests. I know “NethServer Enterprise” manual is now in the same repository. For this reason, I’d like to move it to the Nethesis organization.

In the future, I’d like to apply the same formula to the Dev Team, too: write access on GitHub repositories to merge pull requests. This is another thread, I promise I’ll come back on this point soon.